Announcement

Collapse
No announcement yet.

Linux 5.6-rc2 Released - Led By Documentation + Tooling Updates

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • shmerl
    replied
    Originally posted by Awesam View Post
    WIFI is not detected on the 5.6 kernels with an ASRock X399M motherboard (Intel 802.11ac WiFi). I remember seeing that someone mentioned before that it broke back in a 5.x kernel.
    The patch still didn't reach upstream yet? I remember someone saying the fix was already proposed.

    Leave a comment:


  • Awesam
    replied
    WIFI is not detected on the 5.6 kernels with an ASRock X399M motherboard (Intel 802.11ac WiFi). I remember seeing that someone mentioned before that it broke back in a 5.x kernel.

    Leave a comment:


  • muncrief
    replied
    Originally posted by CommunityMember View Post

    I am not sure it will help your specific issue, but as I recall, for the kernel bugzilla, if your account preferences are set to allow markdown composition (the default is to not support it) you may be able to use markdown formatting (and there are a number of editors, converters, and online forms that will convert formatted text to markdown syntax).
    Aha! You were correct, thank you for the info. The default is to not even allow markdown, and just jumble everything together no matter what one does, which is even more ridiculous than I originally thought

    In any case, once I set my preferences to allow markdown, and then discovered that the kernel bugs markdown is different than the AUR markdown, I was finally able to file my bug, number 206579.

    There's a high likelihood that some developer will deride me for something about my bug report anyway, but at least I have the satisfaction of knowing I spent 2+ hours filing it, and have done my Linux duty for the night/day

    EDIT:
    Oh wow, the devs actually took my report seriously and one (Alex Williamson) left a comment that they're bisecting the problem and suspect some of the new APICv code. And no one complained about the construction or content of my report at all! I think all those years when Linus acted like a raving maniacal 10 year old school yard bully, and encouraged others to do the same, made me so paranoid to communicate with Linux devs that I'm not recognizing the recent change in Linus might be filtering down. I hope so. I actually tried to become a regular Linux developer in my mid 30s but was so put off by their "Lord of the Flies" mentality that I quit after less than a week.
    Last edited by muncrief; 02-18-2020, 02:29 PM. Reason: Added recent developer response.

    Leave a comment:


  • zboszor
    replied
    Originally posted by muncrief View Post

    Ha! I tried to report the bug. In fact I wrote a very detailed description of it with my system specs, virtual machine XML, and complete dmesg output.

    But when I try to put it in bugzilla all the formatting is lost.
    You can attach the files instead, then the formatting is kept.

    Leave a comment:


  • CommunityMember
    replied
    Originally posted by muncrief View Post
    .... I remember being screamed and yelled at by a developer awhile ago when I filed a much shorter report that was jumbled together, and at the end of his rant he gave me a link to some place with extremely ridiculous mark up instructions, but I followed them and was able to make a legible report.

    But I can't find the mark up instructions anywhere after 30 minutes of looking, and I really don't want to spend an hour going through every line of my report inserting ridiculous mark up instructions anyway.
    I am not sure it will help your specific issue, but as I recall, for the kernel bugzilla, if your account preferences are set to allow markdown composition (the default is to not support it) you may be able to use markdown formatting (and there are a number of editors, converters, and online forms that will convert formatted text to markdown syntax).

    Leave a comment:


  • muncrief
    replied
    Originally posted by Space Heater View Post
    Not reporting bugs is a good way to ensure things don't get fixed in a timely manner.
    Ha! I tried to report the bug. In fact I wrote a very detailed description of it with my system specs, virtual machine XML, and complete dmesg output.

    But when I try to put it in bugzilla all the formatting is lost.

    I remember being screamed and yelled at by a developer awhile ago when I filed a much shorter report that was jumbled together, and at the end of his rant he gave me a link to some place with extremely ridiculous mark up instructions, but I followed them and was able to make a legible report.

    But I can't find the mark up instructions anywhere after 30 minutes of looking, and I really don't want to spend an hour going through every line of my report inserting ridiculous mark up instructions anyway. But I've saved the bug report and if I can find a way to get it into bugzilla I will. However I already spent over an hour on it tonight and that's enough time for an old man to try to enter some simple text into a web page.

    Sheesh. Some kids have way, way too much time on their hands. They really thought the default should be to strip out all text formatting? That's just silly, even on the face of it.

    Leave a comment:


  • Space Heater
    replied
    Originally posted by muncrief View Post
    I went to file a bug report but when I searched I found there were so many mine must certainly be in there somewhere.

    So far it looks like KVM is an absolute mess.
    Not reporting bugs is a good way to ensure things don't get fixed in a timely manner.

    Leave a comment:


  • muncrief
    replied
    Originally posted by shmerl View Post
    kvm works fine for me (host is running 5.6-rc1). In fact, I'm now building 5.6-rc2 in a VM guest, that runs on the host that's using 5.6-rc1.
    I just compiled rc2 and VMs without passthrough are fine now. But my main VM running Windows 10 with GPU, SATA, and USB passthrough dies immediately and the physical machine has to be rebooted.

    As a simple test I just tried to passthrough the R9 390 GPU (0000:0a:00.0 is the video, 0000:0a:00.1 is the HDMI) without the other stuff and here's what I got in dmesg:

    -------------- Begin dmesg output --------------
    [ 104.053227] vm_bridge0: port 2(vnet0) entered blocking state
    [ 104.053229] vm_bridge0: port 2(vnet0) entered disabled state
    [ 104.053284] device vnet0 entered promiscuous mode
    [ 104.053407] vm_bridge0: port 2(vnet0) entered blocking state
    [ 104.053409] vm_bridge0: port 2(vnet0) entered listening state
    [ 105.209759] vfio-pci 0000:0a:00.0: enabling device (0002 -> 0003)
    [ 105.210049] vfio-pci 0000:0a:00.0: vfio_ecap_init: hiding ecap [email protected]
    [ 105.210056] vfio-pci 0000:0a:00.0: vfio_ecap_init: hiding ecap [email protected]
    [ 105.229765] vfio-pci 0000:0a:00.1: enabling device (0000 -> 0002)
    [ 106.549861] BUG: kernel NULL pointer dereference, address: 0000000000000010
    [ 106.549865] #PF: supervisor read access in kernel mode
    [ 106.549867] #PF: error_code(0x0000) - not-present page
    [ 106.549869] PGD 0 P4D 0
    [ 106.549872] Oops: 0000 [#1] PREEMPT SMP NOPTI
    [ 106.549876] CPU: 12 PID: 5762 Comm: CPU 0/KVM Tainted: P OE 5.6.0-rc2-1-mainline #1
    [ 106.549878] Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS, BIOS 1405 11/19/2019
    [ 106.549885] RIP: 0010:svm_refresh_apicv_exec_ctrl+0xe4/0x110 [kvm_amd]
    [ 106.549888] Code: 8b 83 f8 39 00 00 48 39 c5 74 31 48 8b 9b f8 39 00 00 48 39 dd 75 13 eb 23 e8 18 70 cc d3 85 c0 75 1a 48 8b 1b 48 39 dd 74 12 <48> 8b 7b 10 45 85 e4 75 e6 e8 6e 6f cc d3 85 c0 74 e6 5b 4c 89 ee
    [ 106.549890] RSP: 0018:ffffaef000d5bd50 EFLAGS: 00010082
    [ 106.549892] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff93353937d000
    [ 106.549894] RDX: 0000000000000001 RSI: ffff9334aa6afc00 RDI: 0000000000000000
    [ 106.549896] RBP: ffff9334aa6c7408 R08: 0000000000000000 R09: ffff9334aa6afc00
    [ 106.549897] R10: 00000018d0a785db R11: 0000000000000000 R12: 0000000000000000
    [ 106.549898] R13: 0000000000000202 R14: ffff9334aa6c7418 R15: ffffaef00149a7a0
    [ 106.549900] FS: 00007f80d89ff700(0000) GS:ffff93359eb00000(0000) knlGS:0000000000000000
    [ 106.549901] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [ 106.549903] CR2: 0000000000000010 CR3: 000000032a5b2000 CR4: 0000000000340ee0
    [ 106.549904] Call Trace:
    [ 106.549929] kvm_arch_vcpu_ioctl_run+0x33d/0x1b20 [kvm]
    [ 106.549949] kvm_vcpu_ioctl+0x266/0x630 [kvm]
    [ 106.549954] ksys_ioctl+0x87/0xc0
    [ 106.549957] __x64_sys_ioctl+0x16/0x20
    [ 106.549961] do_syscall_64+0x4e/0x150
    [ 106.549964] entry_SYSCALL_64_after_hwframe+0x44/0xa9
    [ 106.549967] RIP: 0033:0x7f80dbed42eb
    [ 106.549969] Code: 0f 1e fa 48 8b 05 a5 8b 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 75 8b 0c 00 f7 d8 64 89 01 48
    [ 106.549970] RSP: 002b:00007f80d89fcea8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
    [ 106.549972] RAX: ffffffffffffffda RBX: 000000000000ae80 RCX: 00007f80dbed42eb
    [ 106.549973] RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 000000000000001a
    [ 106.549974] RBP: 00007f80d97d8880 R08: 000055c551c01110 R09: 0000000000000000
    [ 106.549975] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
    [ 106.549976] R13: 00007ffeb948a03f R14: 00007f80d89fd140 R15: 00007f80d89ff700
    [ 106.549980] Modules linked in: vhost_net vhost tap cpufreq_ondemand ebtable_filter ebtables uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common tun videodev snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device mc bridge stp llc nvidia_drm(POE) nvidia_modeset(POE) nct6775 nvidia(POE) hwmon_vid amdgpu gpu_sched nls_iso8859_1 nls_cp437 vfat radeon fat fuse i2c_algo_bit ttm snd_hda_codec_realtek snd_hda_codec_generic drm_kms_helper ledtrig_audio eeepc_wmi snd_hda_codec_hdmi asus_wmi battery sparse_keymap rfkill cec snd_hda_intel wmi_bmof edac_mce_amd snd_intel_dspcfg drm snd_hda_codec crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_core snd_hwdep snd_pcm aesni_intel ipmi_devintf r8169 ipmi_msghandler agpgart snd_timer crypto_simd pcspkr sp5100_tco k10temp syscopyarea cryptd realtek sysfillrect glue_helper mousedev i2c_piix4 snd joydev input_leds sysimgblt libphy fb_sys_fops soundcore wmi pinctrl_amd evdev mac_hid acpi_cpufreq nf_log_ipv6 ip6t_REJECT
    [ 106.550017] nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_multiport xt_limit xt_addrtype xt_tcpudp xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter sg ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 sd_mod sr_mod cdrom hid_generic usbhid hid ahci libahci libata crc32c_intel xhci_pci scsi_mod xhci_hcd vfio_pci vfio_virqfd vfio_iommu_type1 vfio kvm_amd ccp rng_core kvm irqbypass
    [ 106.550039] CR2: 0000000000000010
    [ 106.550041] ---[ end trace 393523eed3771272 ]---
    [ 106.550045] RIP: 0010:svm_refresh_apicv_exec_ctrl+0xe4/0x110 [kvm_amd]
    [ 106.550047] Code: 8b 83 f8 39 00 00 48 39 c5 74 31 48 8b 9b f8 39 00 00 48 39 dd 75 13 eb 23 e8 18 70 cc d3 85 c0 75 1a 48 8b 1b 48 39 dd 74 12 <48> 8b 7b 10 45 85 e4 75 e6 e8 6e 6f cc d3 85 c0 74 e6 5b 4c 89 ee
    [ 106.550048] RSP: 0018:ffffaef000d5bd50 EFLAGS: 00010082
    [ 106.550050] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff93353937d000
    [ 106.550051] RDX: 0000000000000001 RSI: ffff9334aa6afc00 RDI: 0000000000000000
    [ 106.550052] RBP: ffff9334aa6c7408 R08: 0000000000000000 R09: ffff9334aa6afc00
    [ 106.550053] R10: 00000018d0a785db R11: 0000000000000000 R12: 0000000000000000
    [ 106.550054] R13: 0000000000000202 R14: ffff9334aa6c7418 R15: ffffaef00149a7a0
    [ 106.550055] FS: 00007f80d89ff700(0000) GS:ffff93359eb00000(0000) knlGS:0000000000000000
    [ 106.550057] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [ 106.550058] CR2: 0000000000000010 CR3: 000000032a5b2000 CR4: 0000000000340ee0
    [ 106.550060] note: CPU 0/KVM[5762] exited with preempt_count 1
    [ 120.675828] vm_bridge0: port 2(vnet0) entered learning state

    -------------- End dmesg output --------------

    So it's a pretty brutal crash. The VM works perfectly under previous kernels going back to 4.19.x by the way. In fact the R9 390 is in the primary x16 PCIE slot now and it runs like a bare metal gaming machine! I also use it for a few heavy duty video encoding and decoding programs. KVM is absolutely amazing when it works.
    Last edited by muncrief; 02-16-2020, 11:39 PM.

    Leave a comment:


  • shmerl
    replied
    kvm works fine for me (host is running 5.6-rc1). In fact, I'm now building 5.6-rc2 in a VM guest, that runs on the host that's using 5.6-rc1.

    Leave a comment:


  • muncrief
    replied
    Well, KVM was completely broken in rc1, so this isn't good news.

    I'd hoped to see a lot of work on KVM because all I got with rc1 was an immediate null pointer crash the moment a virtio driver tried to load. I couldn't even create a test machine because Windows 10 crashed right at the beginning of installation. I went to file a bug report but when I searched I found there were so many mine must certainly be in there somewhere.

    So far it looks like KVM is an absolute mess.

    Leave a comment:

Working...
X