Bug#801925: Linux Null Pointer Dereference on boot
Hi,
Same here, last working debian kernel is linux-image-4.1.0-2-amd64 .
Kernel hangs on early boot, after a while it notices and drops to an
initramfs shell, lacking a root device. I managed to capture de OOPS
using the handy netconsole module (attached).
> On second thought, it seems more likely that this issue probably was
> _caused_ by that commit. The fix can be found in these two emails:
>
> http://marc.info/?l=linux-scsi&m=144185206825609&w=2
> http://marc.info/?l=linux-scsi&m=144185208525611&w=2
>
> which have not been merged yet as far as I know even though they were
> submitted back in September.
Those patches do not fix the problem for me. I tested using
debian/bin/test-patches from the Debian Linux source.
Thanks,
Alex
[ 2.561223] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.561719] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 2.561775] ata2.00: supports DRM functions and may not be fully accessible
[ 2.565750] ata2.00: disabling queued TRIM support
[ 2.565758] ata2.00: ATA-9: Crucial_CT256M550SSD1, MU01, max UDMA/133
[ 2.565762] ata2.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 2.570661] ata2.00: supports DRM functions and may not be fully accessible
[ 2.579029] ata2.00: configured for UDMA/133
[ 2.905416] ata4: SATA link down (SStatus 0 SControl 300)
[ 2.910964] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
[ 2.911135] PGD 0
[ 2.911215] Modules linked in: sd_mod(+) crc32c_intel ahci libahci libata xhci_pci scsi_mod xhci_hcd i915 ehci_pci ehci_hcd sdhci_pci sdhci mmc_core i2c_algo_bit drm_kms_helper usbcore usb_common e1000e ptp drm pps_core wmi thermal video button
[ 2.911552] Hardware name: Hewlett-Packard HP ProBook 6470b/179C, BIOS 68ICE Ver. F.45 10/07/2013
[ 2.911665] RIP: 0010:[<ffffffffa00149ed>] [<ffffffffa00149ed>] sd_resume+0xd/0x70 [sd_mod]
[ 2.911731] RSP: 0018:ffff8801390a3a60 EFLAGS: 00010246
[ 2.911818] RDX: 0000000000000001 RSI: ffff880139398168 RDI: ffff880139398168
[ 2.911918] R10: ffffffff81827b86 R11: 000000000000000e R12: ffffffffa0019220
[ 2.912017] FS: 00007fc6c2e168c0(0000) GS:ffff88013fac0000(0000) knlGS:0000000000000000
[ 2.912113] CR2: 0000000000000008 CR3: 00000001390c7000 CR4: 00000000001406e0
[ 2.912161] Stack:
[ 2.912247] 0000000000000000 ffffffff81403aae ffff880139398168 ffffffffa03f2a20
[ 2.912382] Call Trace:
[ 2.912470] [<ffffffff81403aae>] ? __rpm_callback+0x2e/0x70
[ 2.912519] [<ffffffffa03f2a20>] ? scsi_autopm_put_device+0x20/0x20 [scsi_mod]
[ 2.912619] [<ffffffffa03f2a20>] ? scsi_autopm_put_device+0x20/0x20 [scsi_mod]
[ 2.912744] [<ffffffff81404c17>] ? __pm_runtime_resume+0x47/0x70
[ 2.912848] [<ffffffffa0014fc5>] ? sd_probe+0x35/0x340 [sd_mod]
[ 2.912959] [<ffffffff813fb14b>] ? __driver_attach+0x7b/0x80
[ 2.913064] [<ffffffff813f8aa7>] ? bus_for_each_dev+0x67/0xb0
[ 2.913152] [<ffffffffa0024000>] ? 0xffffffffa0024000
[ 2.913190] [<ffffffff813fb907>] ? driver_register+0x57/0xc0
[ 2.913312] [<ffffffff81002122>] ? do_one_initcall+0xb2/0x200
[ 2.913417] [<ffffffff810f0ef3>] ? load_module+0x2173/0x2780
[ 2.913504] [<ffffffff811d2b4b>] ? kernel_read+0x4b/0x70
[ 2.913623] [<ffffffff81581332>] ? system_call_fast_compare_end+0xc/0x67
[ 2.914161] RIP [<ffffffffa00149ed>] sd_resume+0xd/0x70 [sd_mod]
[ 2.914212] RSP <ffff8801390a3a60>
[ 2.914239] CR2: 0000000000000008
[ 2.916695] ---[ end trace 6a25c092cd6e126d ]---
Reply to: