On Fri, Nov 18, 2016 at 9:52 AM, Eric Shelton <[email protected]> wrote: > On Thursday, November 17, 2016 at 11:01:34 AM UTC-5, Outback Dingo wrote: >> >> On Thu, Nov 17, 2016 at 4:01 AM, Eric Shelton <[email protected]> wrote: >> > On Tuesday, November 15, 2016 at 9:25:44 PM UTC-5, Outback Dingo wrote: >> >> >> >> . . . >> >> >> >> [ 2.020731] rtsx_pci 0000:00:00.0: Xen PCI mapped GSI17 to IRQ26 >> >> [ 2.020976] rtsx_pci 0000:00:00.0: rtsx_pci_acquire_irq: >> >> pcr->msi_en = 1, pci->irq = 27 >> >> [ 2.021054] BUG: unable to handle kernel paging request at >> >> ffffc900002f4010 >> >> [ 2.021059] IP: [<ffffffff813f297e>] iowrite32+0x2e/0x40 >> >> [ 2.021066] PGD 12b3a067 PUD 12b39067 PMD 1091a067 PTE >> >> 80100000df415075 >> >> [ 2.021072] Oops: 0003 [#1] SMP >> >> [ 2.021075] Modules linked in: rtsx_pci(+) mii mfd_core intel_rapl >> >> x86_pkg_temp_thermal coretemp crct10dif_pclmul crc32_pclmul >> >> crc32c_intel ghash_clmulni_intel pcspkr xen_pcifront dummy_hcd >> >> udc_core u2mfn(O) xen_blkback xenfs xen_privcmd xen_blkfront >> >> [ 2.021093] CPU: 0 PID: 293 Comm: systemd-udevd Tainted: G >> >> O 4.8.7-12.pvops.qubes.x86_64 #1 >> >> [ 2.021098] task: ffff88000f353d00 task.stack: ffff8800101a0000 >> >> [ 2.021101] RIP: e030:[<ffffffff813f297e>] [<ffffffff813f297e>] >> >> iowrite32+0x2e/0x40 >> >> [ 2.021107] RSP: e02b:ffff8800101a39a8 EFLAGS: 00010296 >> >> [ 2.021110] RAX: ffffc900002f4000 RBX: 0000000000000400 RCX: >> >> 0000000000000000 >> >> [ 2.021113] RDX: ffff8800101a39df RSI: ffffc900002f4010 RDI: >> >> 00000000bc320000 >> >> [ 2.021116] RBP: ffff8800101a39c8 R08: ffff88000cd01800 R09: >> >> ffff880010418db0 >> >> [ 2.021119] R10: 0000000000000000 R11: 0000000000000040 R12: >> >> ffff8800102e5400 >> >> [ 2.021123] R13: ffff8800101a39df R14: ffff8800102e5430 R15: >> >> ffff8800102e5400 >> >> [ 2.021128] FS: 00007f7adb4d58c0(0000) GS:ffff880012800000(0000) >> >> knlGS:0000000000000000 >> >> [ 2.021133] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 >> >> [ 2.021136] CR2: ffff8000006fa0a8 CR3: 000000001037d000 CR4: >> >> 0000000000042660 >> >> [ 2.021137] Stack: >> >> [ 2.021139] ffffffffa00a2358 ffff8800102e5400 0000000000000000 >> >> ffff88000fb040a0 >> >> [ 2.021140] ffff8800101a39f0 ffffffffa00a5cec 0000000000000000 >> >> 0000000097637213 >> >> [ 2.021140] ffff8800102e5400 ffff8800101a3a18 ffffffffa00a5fa5 >> >> 0000000097637213 >> >> [ 2.021141] Call Trace: >> >> [ 2.021145] [<ffffffffa00a2358>] ? >> >> rtsx_pci_read_register+0x38/0x80 [rtsx_pci] >> >> [ 2.021148] [<ffffffffa00a5cec>] >> >> rtl8411_init_common_params+0x7c/0xb0 [rtsx_pci] >> >> [ 2.021151] [<ffffffffa00a5fa5>] rtl8411b_init_params+0x25/0xc0 >> >> [rtsx_pci] >> >> [ 2.021153] [<ffffffffa00a3dd7>] rtsx_pci_init_chip+0x147/0x2e0 >> >> [rtsx_pci] >> >> [ 2.021155] [<ffffffffa00a434b>] rtsx_pci_probe+0x3db/0x670 >> >> [rtsx_pci] >> >> [ 2.021157] [<ffffffff81427725>] local_pci_probe+0x45/0xa0 >> >> [ 2.021159] [<ffffffff81428b4d>] pci_device_probe+0xfd/0x140 >> >> [ 2.021162] [<ffffffff8151e014>] driver_probe_device+0x224/0x430 >> >> [ 2.021163] [<ffffffff8151e2ff>] __driver_attach+0xdf/0xf0 >> >> [ 2.021165] [<ffffffff8151e220>] ? driver_probe_device+0x430/0x430 >> >> [ 2.021166] [<ffffffff8151b9bc>] bus_for_each_dev+0x6c/0xc0 >> >> [ 2.021167] [<ffffffff8151d70e>] driver_attach+0x1e/0x20 >> >> [ 2.021168] [<ffffffff8151d1dd>] bus_add_driver+0x1fd/0x270 >> >> [ 2.021169] [<ffffffffa0085000>] ? 0xffffffffa0085000 >> >> [ 2.021171] [<ffffffff8151ec30>] driver_register+0x60/0xe0 >> >> [ 2.021172] [<ffffffff8142707c>] __pci_register_driver+0x4c/0x50 >> >> [ 2.021174] [<ffffffffa008501e>] rtsx_pci_driver_init+0x1e/0x1000 >> >> [rtsx_pci] >> >> [ 2.021176] [<ffffffff81002190>] do_one_initcall+0x50/0x180 >> >> [ 2.021177] [<ffffffff811b5f13>] ? free_hot_cold_page+0x193/0x2a0 >> >> [ 2.021179] [<ffffffff81218945>] ? >> >> kmem_cache_alloc_trace+0x165/0x1d0 >> >> [ 2.021181] [<ffffffff811abaf8>] ? do_init_module+0x27/0x1ee >> >> [ 2.021182] [<ffffffff811abb30>] do_init_module+0x5f/0x1ee >> >> [ 2.021183] [<ffffffff811248bf>] load_module+0x15cf/0x1b60 >> >> [ 2.021184] [<ffffffff81121430>] ? __symbol_put+0x60/0x60 >> >> [ 2.021186] [<ffffffff8123f9f3>] ? vfs_read+0x123/0x140 >> >> [ 2.021188] [<ffffffff811250af>] SYSC_finit_module+0xdf/0x110 >> >> [ 2.021189] [<ffffffff811250fe>] SyS_finit_module+0xe/0x10 >> >> [ 2.021190] [<ffffffff81003c67>] do_syscall_64+0x67/0x160 >> >> [ 2.021192] [<ffffffff817a3361>] >> >> entry_SYSCALL64_slow_path+0x25/0x25 >> >> [ 2.021201] Code: ff ff 03 00 77 25 48 81 fe 00 00 01 00 76 07 0f >> >> b7 d6 89 f8 ef c3 55 48 89 f7 48 c7 c6 e9 72 a7 81 48 89 e5 e8 54 fe >> >> ff ff 5d c3 <89> 3e c3 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 >> >> 81 ff >> >> [ 2.021203] RIP [<ffffffff813f297e>] iowrite32+0x2e/0x40 >> >> [ 2.021203] RSP <ffff8800101a39a8> >> >> [ 2.021203] CR2: ffffc900002f4010 >> >> [ 2.021204] ---[ end trace e9b49b19823b58a0 ]--- >> >> [.[32m OK .[0m] Started Update UTMP about System Boot/Shutdown. >> >> [.[32m OK .[0m] Found device /dev/xvdc1. >> >> Activating swap /dev/xvdc1... >> >> [ 5.001835] Adding 1048572k swap on /dev/xvdc1. Priority:-1 >> >> extents:1 across:1048572k SSFS >> >> [.[32m OK .[0m] Activated swap /dev/xvdc1. >> > >> > >> > It looks like everything goes downhill in connection with the SD card >> > reader >> > (uses the rtsx_pci driver) that is paired up with the ethernet adapter. >> > Does your BIOS allow the SD card reader to be disabled independently? >> > Alternatively, maybe you can block the driver from loading by doing: >> > >> > qvm-prefs -s sys-net kernelopts "no pat iommu=soft swiotlb=8192 >> > rd.driver.blacklist=rtsx_pci" >> > >> > Assuming that method of blacklisting a driver works in a Qube (I have >> > never >> > tried it). >> > >> > Even if that gets you past the current crash, you may encounter a >> > similar >> > one with the ethernet device, seeing as it is part of the same hardware >> > component, but one thing at a time... >> > >> > Eric >> >> >> thanks, but no change recognized, still seeing the same issues > > > When you say "no change," do you just mean that it is still crashing, or are > you still seeing the exact same crash? If you are still seeing lines > mentioning rtsx_pci, then that means that my suggested approach to blocking > the module did not work, and it is still causing the crash. Does the > beginning of dmesg output: > > [ 0.000000] Command line: root=/dev/mapper/dmroot ro nomodeset > console=hvc0 rd_NO_PLYMOUTH 3 nopat iommu=soft swiotlb=8192 > > Now also include "rd.driver.blacklist=rtsx_pci"? That is what should have > happened via the qvm-prefs setting. If dmesg output is still mentioning > rtsx_pci, then another approach to not loading the module should be pursued. > > If the rtsx_pci stuff is gone, and it is crashing elsewhere, then it is a > step forward, and you should put up the new dmesg output for comparison.
I mean its the same as dmesg as before so it appears the driver is still loading > > Eric > > -- > You received this message because you are subscribed to the Google Groups > "qubes-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-devel/bc3b8bdf-2ea6-41e9-a11d-b949bc6172b6%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CAKYr3zw4pfH3P6WudBjuRj3o5OHoooe18B4nq%2Bw7vJepUPe-Ww%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
