Re: Getting oops with 3.2.10 when removing a SD card

From: Josh Boyer
Date: Wed Mar 14 2012 - 11:43:59 EST


On Wed, Mar 14, 2012 at 11:38 AM, Francis Moreau <francis.moro@xxxxxxxxx> wrote:
> Hi,
>
> I'm getting this oops (pretty often) after writing to a SD card and
> removing the card.
>
> Here's the oops:
>
> [17610.371580] usb 1-1.6: new high-speed USB device number 14 using ehci_hcd
> [17610.469928] usb 1-1.6: New USB device found, idVendor=0bda, idProduct=0159
> [17610.469935] usb 1-1.6: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [17610.469939] usb 1-1.6: Product: USB2.0-CRW
> [17610.469942] usb 1-1.6: Manufacturer: Generic
> [17610.469946] usb 1-1.6: SerialNumber: 20071114173400000
> [17610.485966] scsi16 : usb-storage 1-1.6:1.0
> [17611.489253] scsi 16:0:0:0: Direct-Access     Generic- Multi-Card
>   1.00 PQ: 0 ANSI: 0 CCS
> [17611.489556] sd 16:0:0:0: Attached scsi generic sg2 type 0
> [17612.177470] sd 16:0:0:0: [sdb] 7744512 512-byte logical blocks:
> (3.96 GB/3.69 GiB)
> [17612.178347] sd 16:0:0:0: [sdb] Write Protect is off
> [17612.178355] sd 16:0:0:0: [sdb] Mode Sense: 03 00 00 00
> [17612.179333] sd 16:0:0:0: [sdb] No Caching mode page present
> [17612.179338] sd 16:0:0:0: [sdb] Assuming drive cache: write through
> [17612.182988] sd 16:0:0:0: [sdb] No Caching mode page present
> [17612.182993] sd 16:0:0:0: [sdb] Assuming drive cache: write through
> [17612.214565]  sdb: sdb1
> [17612.218666] sd 16:0:0:0: [sdb] No Caching mode page present
> [17612.218672] sd 16:0:0:0: [sdb] Assuming drive cache: write through
> [17612.218677] sd 16:0:0:0: [sdb] Attached SCSI removable disk
> [17620.408767] usb 1-1.6: USB disconnect, device number 14
> [17620.410224] scsi 16:0:0:0: killing request
> [17620.410512] BUG: unable to handle kernel NULL pointer dereference
> at 0000000000000008
> [17620.411480] IP: [<ffffffffa01e08ef>] sd_revalidate_disk+0x3f/0x1a10 [sd_mod]
> [17620.411501] PGD 286a3067 PUD aef9f067 PMD 0
> [17620.411507] Oops: 0000 [#1] SMP
> [17620.411512] CPU 0

There's a patch to fix this that will hopefully be pulled into Linus' tree
today. It should work it's way back to 3.2-stable after that.

josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/