[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#417575: marked as done (kernel crash while accessing a usb storage device)

Your message dated Tue, 20 May 2008 20:48:46 +0200
with message-id <20080520184846.GO13383@stro.at>
and subject line RE: kernel crash while accessing a usb storage device
has caused the Debian Bug report #417575,
regarding kernel crash while accessing a usb storage device
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 owner@bugs.debian.org
immediately.)


-- 
417575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417575
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kernel-image
Version: linux-kernel
Severity: important

*** Please type your report below this line ***

I have experienced a complete system lockup multiple times while using 2 usb
devices.
it always happens at a time when the usb harddrive is
accessed, while there is a wlan usb device connected.

here's /var/log/messages:

Apr  3 14:30:13 localhost kernel: NETDEV WATCHDOG: eth3: transmit timed out
Apr  3 14:30:14 localhost kernel: eth3: Tx timed out.
Apr  3 14:30:14 localhost kernel:  [<b0288f89>] schedule+0x43/0x4cf
Apr  3 14:30:14 localhost kernel:  [<d0056664>] hcd_unlink_urb+0xe9/0x10b
[usbcore]
Apr  3 14:30:14 localhost kernel:  [<d0056ee7>] usb_kill_urb+0x8e/0xa7
[usbcore]
Apr  3 14:30:14 localhost kernel:  [<b01242e4>]
autoremove_wake_function+0x0/0x3a
Apr  3 14:30:14 localhost kernel:  [<b02432f5>] dev_watchdog+0x0/0x81
Apr  3 14:30:14 localhost kernel:  [<b0243347>] dev_watchdog+0x52/0x81
Apr  3 14:30:14 localhost kernel:  [<b011c791>] run_timer_softirq+0xfd/0x13f
Apr  3 14:30:14 localhost kernel:  [<b0119bbf>] __do_softirq+0x34/0x7f
Apr  3 14:30:14 localhost kernel:  [<b0119c2c>] do_softirq+0x22/0x26
Apr  3 14:30:14 localhost kernel:  [<b0104ac2>] do_IRQ+0x1e/0x24
Apr  3 14:30:14 localhost kernel:  [<b01033fe>] common_interrupt+0x1a/0x20
Apr  3 14:30:14 localhost kernel:  [<d046a1c4>]
acpi_processor_idle+0x157/0x323 [processor]
Apr  3 14:30:14 localhost kernel:  [<b0101d4c>] cpu_idle+0x3a/0x4f
Apr  3 14:30:14 localhost kernel:  [<b032062c>] start_kernel+0x293/0x295
Apr  3 14:31:27 localhost syslogd 1.4.1#18: restart.


the wlan usb device is a ZD1211B with their own driver, which is not
included in the kernel, so it could be a problem with their driver, but the
var/log/messages-output above doesn't look like it.

here's the wlan driver initialization output:
Apr  3 10:47:07 localhost kernel: |__  /   _|  _ \  / \  / ___|
Apr  3 10:47:07 localhost kernel:   / / | | | | | |/ _ \ \___ \
Apr  3 10:47:07 localhost kernel:  / /| |_| | |_| / ___ \ ___) |
Apr  3 10:47:07 localhost kernel: /____\__, |____/_/   \_\____/
Apr  3 10:47:07 localhost kernel:      |___/
Apr  3 10:47:07 localhost kernel: ZD1211B - version 2.14.0.0
Apr  3 10:47:07 localhost kernel: vendor_id = 0ace
Apr  3 10:47:07 localhost kernel: product_id = 1215
Apr  3 10:47:07 localhost kernel: USB 2.0 Host
Apr  3 10:47:07 localhost kernel: Release Ver = 4810
Apr  3 10:47:07 localhost kernel: EEPORM Ver = 4810
Apr  3 10:47:07 localhost kernel: PHYNEWLayout = 1
Apr  3 10:47:07 localhost kernel: Airoha AL2230S_RF
Apr  3 10:47:07 localhost kernel: AllowedChannel = 000107ff
Apr  3 10:47:07 localhost kernel: Region:48
Apr  3 10:47:07 localhost kernel: usbcore: registered new driver zd1211b



and here's initialization output of the usb harddrive:
Apr  3 14:19:11 localhost kernel: usb 5-1: new high speed USB device using
ehci_hcd and address 8
Apr  3 14:19:11 localhost kernel: usb 5-1: configuration #1 chosen from 1
choice
Apr  3 14:19:11 localhost kernel: scsi1 : SCSI emulation for USB Mass
Storage devices
Apr  3 14:19:16 localhost kernel:   Vendor: WDC WD25  Model: 00BB-14RDA0
Rev: 20.0
Apr  3 14:19:16 localhost kernel:   Type:   Direct-Access
ANSI SCSI revision: 00
Apr  3 14:19:16 localhost kernel: SCSI device sda: 488397167 512-byte hdwr
sectors (250059 MB)
Apr  3 14:19:16 localhost kernel: sda: Write Protect is off
Apr  3 14:19:16 localhost kernel: SCSI device sda: 488397167 512-byte hdwr
sectors (250059 MB)
Apr  3 14:19:16 localhost kernel: sda: Write Protect is off
Apr  3 14:19:16 localhost kernel:  sda: sda1
Apr  3 14:19:16 localhost kernel: sd 1:0:0:0: Attached scsi disk sda
Apr  3 14:19:25 localhost kernel: kjournald starting.  Commit interval 5
seconds
Apr  3 14:19:25 localhost kernel: EXT3-fs warning: maximal mount count
reached, running e2fsck is recommended
Apr  3 14:19:25 localhost kernel: EXT3 FS on sda1, internal journal
Apr  3 14:19:25 localhost kernel: EXT3-fs: recovery complete.
Apr  3 14:19:25 localhost kernel: EXT3-fs: mounted filesystem with ordered
data mode.



-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

-- 
Stefan Strasser

--- End Message ---
--- Begin Message --- 
Version: 2.6.25-1

> it always happens at a time when the usb harddrive is
> accessed, while there is a wlan usb device connected.
> the wlan usb device is a ZD1211B with their own driver


sorry we can't support tainted kernel.

just use zd1211rw from linux-2.6 it has ZD1211B support


-- 
maks

--- End Message ---
Reply to: