Bug#460867: linux-image-2.6.23-1-amd64: kernel BUG at block/cfq-iosched.c:1147!
Astrid S. de Wijn
Version: 2.6.23-2
Severity: important
*** Please type your report below this line ***
I seem to have run into some sort of io kernel bug. I connected a usb drive
(trekstor datastation pocket x.u), mounted a partition, juggled data around
(tens of GB), and umounted it. When i removed the drive from the usb port,
I ran into a kernel bug. I have used this disk and enclosure combo with this
machine and kernel before without any problem, also shuffling lots of data,
though maybe not quite as much. An e2fsck on the mounted partition turned
up no errors.
Astrid
Here is the relevant part of the dmesg output:
usb 5-2: new high speed USB device using ehci_hcd and address 14
usb 5-2: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi4 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 14
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 4:0:0:0: Direct-Access WDC WD16 00BEVE-00UYT0 0000 PQ: 0
ANSI: 0
sd 4:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 27 00 00 00
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] 312581808 512-byte hardware sectors (160042 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 27 00 00 00
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 4:0:0:0: [sdb] Attached SCSI disk
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is
recommended
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
usb 5-2: USB disconnect, address 14
------------[ cut here ]------------
kernel BUG at block/cfq-iosched.c:1147!
invalid opcode: 0000 [1] SMP
CPU 0
Modules linked in: usb_storage iwl3945 mac80211 usbhid hid e1000 hci_usb
bluetooth xt_TCPMSS xt_tcpmss xt_tcpudp iptable_filter ip_tables
x_tables ppp_deflate zlib_deflate zlib_inflate bsd_comp pppoatm
ppp_generic slhc tun tcp_diag inet_diag ipv6 acpi_cpufreq cpufreq_stats
cpufreq_powersave cpufreq_ondemand cpufreq_conservative freq_table
cpufreq_userspace fuse loop pcmcia snd_hda_intel joydev snd_pcm_oss
snd_mixer_oss irtty_sir snd_pcm sir_dev yenta_socket rsrc_nonstatic
cfg80211 battery ac pcmcia_core snd_timer video output nsc_ircc snd
button irda i2c_i801 crc_ccitt iTCO_wdt psmouse i2c_core speedtch usbatm
ieee80211 ieee80211_crypt serio_raw soundcore snd_page_alloc
firmware_class intel_agp tsdev pcspkr thinkpad_acpi evdev nvram ext3 jbd
mbcache ide_cd cdrom ata_generic sd_mod piix ahci libata scsi_mod
generic ide_core ehci_hcd uhci_hcd thermal processor fan
Pid: 181, comm: khubd Not tainted 2.6.23-1-amd64 #1
RIP: 0010:[<ffffffff802fa752>] [<ffffffff802fa752>]
cfq_put_queue+0x12/0x89
RSP: 0018:ffff8100bd1d3bb0 EFLAGS: 00010046
RAX: 0000000000000004 RBX: ffff8100ba5ab498 RCX: ffff8100bbe96088
RDX: 0000000000000003 RSI: ffff810079238c28 RDI: ffff8100ba5ab498
RBP: ffff8100bac64c00 R08: 0000000000001bdb R09: ffff8100013e9950
R10: ffff810086b67580 R11: ffff8100bbe96088 R12: ffff8100bbe96088
R13: ffff810079238c28 R14: 0000000000000000 R15: ffff8100bad55000
FS: 0000000000000000(0000) GS:ffffffff804f6000(0000)
knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00002b89b34aa000 CR3: 00000000b267f000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process khubd (pid: 181, threadinfo ffff8100bd1d2000, task
ffff8100bd1b7850)
Stack: ffff8100bbe96088 ffff8100bac64c00 0000000000000001 ffffffff802fa97a
fff8100b579b080 ffff8100b579b100 ffff810069a51800 ffffffff802f06da
ffff810079d20190 ffff8100bbe96690 ffff8100bbe96088 ffffffff802f3efb
Call Trace:
[<ffffffff802fa97a>] cfq_exit_queue+0x92/0xbe
[<ffffffff802f06da>] elevator_exit+0x2c/0x48
[<ffffffff802f3efb>] blk_cleanup_queue+0x37/0x42
[<ffffffff880879ca>] :scsi_mod:scsi_device_dev_release_usercontext+0xe9/0x137
[<ffffffff80243ad5>] execute_in_process_context+0x23/0x57
[<ffffffff802fe8e5>] kobject_cleanup+0x52/0x70
[<ffffffff802fe903>] kobject_release+0x0/0x9
[<ffffffff802ff6af>] kref_put+0x5d/0x68
[<ffffffff88084ba3>] :scsi_mod:scsi_forget_host+0x39/0x5b
[<ffffffff8807f767>] :scsi_mod:scsi_remove_host+0x75/0xf6
[<ffffffff882a98a3>] :usb_storage:quiesce_and_remove_host+0xbf/0xce
[<ffffffff882a9989>] :usb_storage:storage_disconnect+0x10/0x19
[<ffffffff803758c4>] usb_unbind_interface+0x59/0xb6
[<ffffffff80367526>] __device_release_driver+0x8e/0xb0
[<ffffffff8036790f>] device_release_driver+0x2c/0x45
[<ffffffff80366e1c>] bus_remove_device+0x89/0x9c
[<ffffffff80365265>] device_del+0x22a/0x2b6
[<ffffffff80372f57>] usb_disable_device+0x6f/0xe8
[<ffffffff8036f1eb>] usb_disconnect+0x9b/0x148
[<ffffffff8036f9e0>] hub_thread+0x403/0xbc0
[<ffffffff80246b96>] autoremove_wake_function+0x0/0x2e
[<ffffffff8036f5dd>] hub_thread+0x0/0xbc0
[<ffffffff80246a79>] kthread+0x47/0x76
[<ffffffff8020cc08>] child_rip+0xa/0x12
[<ffffffff80246a32>] kthread+0x0/0x76
[<ffffffff8020cbfe>] child_rip+0x0/0x12
Code: 0f 0b eb fe f0 ff 0f 0f 94 c0 84 c0 74 64 48 8d 7f 30 e8 2b
RIP [<ffffffff802fa752>] cfq_put_queue+0x12/0x89
RSP <ffff8100bd1d3bb0>
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.23-1-amd64 depends on:
ii e2fsprogs 1.40.3-1 ext2 file system utilities and lib
ii initramfs-tools [linux-initr 0.91d tools for generating an initramfs
ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo
ii yaird [linux-initramfs-tool] 0.0.12-24 Yet Another mkInitRD
linux-image-2.6.23-1-amd64 recommends no packages.
-- debconf information:
linux-image-2.6.23-1-amd64/postinst/depmod-error-2.6.23-1-amd64: false
linux-image-2.6.23-1-amd64/postinst/bootloader-error-2.6.23-1-amd64:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.23-1-amd64/preinst/abort-install-2.6.23-1-amd64:
linux-image-2.6.23-1-amd64/preinst/lilo-has-ramdisk:
linux-image-2.6.23-1-amd64/postinst/kimage-is-a-directory:
linux-image-2.6.23-1-amd64/preinst/elilo-initrd-2.6.23-1-amd64: true
linux-image-2.6.23-1-amd64/preinst/bootloader-initrd-2.6.23-1-amd64: true
linux-image-2.6.23-1-amd64/preinst/lilo-initrd-2.6.23-1-amd64: true
linux-image-2.6.23-1-amd64/postinst/bootloader-test-error-2.6.23-1-amd64:
linux-image-2.6.23-1-amd64/postinst/old-dir-initrd-link-2.6.23-1-amd64: true
linux-image-2.6.23-1-amd64/postinst/depmod-error-initrd-2.6.23-1-amd64: false
linux-image-2.6.23-1-amd64/preinst/overwriting-modules-2.6.23-1-amd64: true
linux-image-2.6.23-1-amd64/preinst/abort-overwrite-2.6.23-1-amd64:
linux-image-2.6.23-1-amd64/preinst/initrd-2.6.23-1-amd64:
linux-image-2.6.23-1-amd64/postinst/create-kimage-link-2.6.23-1-amd64: true
linux-image-2.6.23-1-amd64/postinst/old-system-map-link-2.6.23-1-amd64: true
linux-image-2.6.23-1-amd64/prerm/removing-running-kernel-2.6.23-1-amd64: true
linux-image-2.6.23-1-amd64/prerm/would-invalidate-boot-loader-2.6.23-1-amd64: true
linux-image-2.6.23-1-amd64/preinst/already-running-this-2.6.23-1-amd64:
linux-image-2.6.23-1-amd64/preinst/failed-to-move-modules-2.6.23-1-amd64:
linux-image-2.6.23-1-amd64/postinst/old-initrd-link-2.6.23-1-amd64: true
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Debian Bug Tracking System
Your message dated Wed, 2 Jul 2008 17:17:41 +0200
with message-id <20080702151...@stro.at>
and subject line Re: linux-image-2.6.23-1-amd64: kernel BUG at block/cfq-iosched.c:1147!
has caused the Debian Bug report #460867,
regarding linux-image-2.6.23-1-amd64: kernel BUG at block/cfq-iosched.c:1147!
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
460867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems