2.6.23-rc1-mm2 + cpufreq patch + hot-fixes -- [<f8ea528f>] usb_stor_scan_thread+0xbd/0x15a [usb_storage]

2.6.23-rc1-mm2 + cpufreq patch + hot-fixes -- [<f8ea528f>] usb_stor_scan_thread+0xbd/0x15a [usb_storage]

[Miles Lane]

usb usb4: usb resume
ehci_hcd 0000:00:1d.7: resume root hub
hub 4-0:1.0: hub_resume
hub 4-0:1.0: state 7 ports 6 chg 0000 evt 0000
ehci_hcd 0000:00:1d.7: GetStatus port 3 status 001803 POWER sig=j CSC CONNECT
hub 4-0:1.0: port 3, status 0501, change 0001, 480 Mb/s
hub 4-0:1.0: debounce: port 3: total 100ms stable 100ms status 0x501
ehci_hcd 0000:00:1d.7: port 3 high speed
ehci_hcd 0000:00:1d.7: GetStatus port 3 status 001005 POWER sig=se0 PE CONNECT
usb 4-3: new high speed USB device using ehci_hcd and address 2
ehci_hcd 0000:00:1d.7: port 3 high speed
ehci_hcd 0000:00:1d.7: GetStatus port 3 status 001005 POWER sig=se0 PE CONNECT
usb 4-3: default language 0x0409
usb 4-3: new device found, idVendor=0781, idProduct=5150
usb 4-3: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-3: Product: Cruzer Mini
usb 4-3: Manufacturer: SanDisk Corporation
usb 4-3: SerialNumber: SNDK5C31950CBB106202
usb 4-3: uevent
usb 4-3: usb_probe_device
usb 4-3: configuration #1 chosen from 1 choice
usb 4-3: adding 4-3:1.0 (config #1, interface 0)
usb 4-3:1.0: uevent
usb 4-3:1.0: uevent
drivers/usb/core/inode.c: creating file '002'
Initializing USB Mass Storage driver...
usb-storage 4-3:1.0: usb_probe_interface
usb-storage 4-3:1.0: usb_probe_interface - got id
scsi2 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
schedule_timeout: wrong timeout value f8ea51d2
 [<c01080ab>] show_trace_log_lvl+0x12/0x25
 [<c0108a9e>] show_trace+0xd/0x10
 [<c0108bac>] dump_stack+0x16/0x18
 [<c031e31e>] schedule_timeout+0x2c/0x8b
 [<f8ea528f>] usb_stor_scan_thread+0xbd/0x15a [usb_storage]
 [<c0139d64>] kthread+0x3b/0x63
 [<c0107c63>] kernel_thread_helper+0x7/0x10
 =======================
USB Mass Storage support registered.
scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer Mini      0.4  PQ: 0 ANSI: 2
sd 2:0:0:0: [sdb] 2001888 512-byte hardware sectors (1025 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] 2001888 512-byte hardware sectors (1025 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI removable disk
sd 2:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete

Re: [linux-usb-devel] 2.6.23-rc1-mm2 + cpufreq patch + hot-fixes -- [<f8ea528f>] usb_stor_scan_thread+0xbd/0x15a [usb_storage]

[Alan Stern]

On Sat, 4 Aug 2007, Miles Lane wrote:

> Initializing USB Mass Storage driver...
> usb-storage 4-3:1.0: usb_probe_interface
> usb-storage 4-3:1.0: usb_probe_interface - got id
> scsi2 : SCSI emulation for USB Mass Storage devices
> usbcore: registered new interface driver usb-storage
> usb-storage: device found at 2
> usb-storage: waiting for device to settle before scanning
> schedule_timeout: wrong timeout value f8ea51d2
>  [<c01080ab>] show_trace_log_lvl+0x12/0x25
>  [<c0108a9e>] show_trace+0xd/0x10
>  [<c0108bac>] dump_stack+0x16/0x18
>  [<c031e31e>] schedule_timeout+0x2c/0x8b
>  [<f8ea528f>] usb_stor_scan_thread+0xbd/0x15a [usb_storage]
>  [<c0139d64>] kthread+0x3b/0x63
>  [<c0107c63>] kernel_thread_helper+0x7/0x10
>  =======================

Does this happen repeatably?

Did you set usb-storage's delay_use parameter to something peculiar?

Alan Stern

Re: [linux-usb-devel] 2.6.23-rc1-mm2 + cpufreq patch + hot-fixes -- [<f8ea528f>] usb_stor_scan_thread+0xbd/0x15a [usb_storage]

[Akinobu Mita]

2007/8/6, Alan Stern <stern@rowland.harvard.edu>:
> On Sat, 4 Aug 2007, Miles Lane wrote:
>
> > Initializing USB Mass Storage driver...
> > usb-storage 4-3:1.0: usb_probe_interface
> > usb-storage 4-3:1.0: usb_probe_interface - got id
> > scsi2 : SCSI emulation for USB Mass Storage devices
> > usbcore: registered new interface driver usb-storage
> > usb-storage: device found at 2
> > usb-storage: waiting for device to settle before scanning
> > schedule_timeout: wrong timeout value f8ea51d2
> >  [<c01080ab>] show_trace_log_lvl+0x12/0x25
> >  [<c0108a9e>] show_trace+0xd/0x10
> >  [<c0108bac>] dump_stack+0x16/0x18
> >  [<c031e31e>] schedule_timeout+0x2c/0x8b
> >  [<f8ea528f>] usb_stor_scan_thread+0xbd/0x15a [usb_storage]
> >  [<c0139d64>] kthread+0x3b/0x63
> >  [<c0107c63>] kernel_thread_helper+0x7/0x10
> >  =======================
>
> Does this happen repeatably?
>
> Did you set usb-storage's delay_use parameter to something peculiar?

I also have same problem. It is caused by
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc1/2.6.23-rc1-mm2/broken-out/freezer-introduce-freezer-firendly-waiting-macros.patch

The patch below may not be good fix. But it shows what is problem.

Index: 2.6-mm/include/linux/freezer.h
===================================================================
--- 2.6-mm.orig/include/linux/freezer.h
+++ 2.6-mm/include/linux/freezer.h
@@ -149,13 +149,13 @@ static inline void set_freezable(void)

 #define wait_event_freezable_timeout(wq, condition, timeout)		\
 ({									\
-	long __ret = timeout;						\
+	long ____ret = timeout;						\
 	do {								\
-		__ret = wait_event_interruptible_timeout(wq,		\
+		____ret = wait_event_interruptible_timeout(wq,		\
 				(condition) || freezing(current),	\
-				__ret); 				\
+				____ret); 				\
 	} while (try_to_freeze());					\
-	__ret;								\
+	____ret;							\
 })
 #else /* !CONFIG_PM_SLEEP */
 static inline int frozen(struct task_struct *p) { return 0; }