My machine more or less reproducibly Oops or locks-up by hot-plugging a USB hard-drive. The machine has a Gigabyte motherboard with 790gx + sb700 chipset, USB is via the sb700. The hard-drive is a Welland SunBright SATA-USB bridge with a Seagate 1TB SATA drive, the SATA-USB chipset is: New USB device found, idVendor=152d, idProduct=2329 New USB device strings: Mfr=1, Product=2, SerialNumber=5 Product: USB to ATA/ATAPI bridge Manufacturer: JMicron Kernel is 2.6.35.6-48.fc14.x86_64 #1 SMP Fri Oct 22 15:36:08 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux If I plug the drive while in X, then the machine usually gets as far as attempting to automount the first partition, and then Oopses, freezes and starts beeping once per second. The Oops does not make it to /var/log/, and only the first few lines make it my terminal window: Oops: 0000 [#1] SMP last sysfs file: /sys/devices/pci0000:00/0000:00:13.2/usrb2/2-5/2-5:1.0/host11/target11:0:0/11:0:0:0/block/sdb/sdb1/uevent Stack: Call Trace: Code: <48> 8b 80 28 01 00 00 48 39 b0 28 22 00 00 c9 0f 94 c0 0f b6 c0 c3 CR2: 0000000000000128 [Partion 1 is a 128MB ext3 partition.] Sometimes, the machine either freezes (with the display off) or reboots immediately. Sometimes when not in X, the drive does attach correctly, and I can then access the drive normally. The drive contains a number of partitions, with both ext3 and btrfs partitions.
Created attachment 464801 [details] Photograph of oops Managed to get the oops-on-mount to the console & photographed. Looks like this time we oops mounting one of the btrfs filesystems.
Created attachment 464802 [details] Second oops about 60 seconds after previous. Following on from the previous attachment, the kernel was still alive and oops'd again about a minute later. I think this one was a stuck-spin-lock being detected, and is probably a direct consequence of the first.
*** This bug has been marked as a duplicate of bug 656465 ***