Re: [linux-usb-devel] Re: 2.6.17-rc4-mm2 (hard lockup after resume from disk on AMD64)

2006-05-25 Thread Alan Stern
On Sun, 21 May 2006, Rafael J. Wysocki wrote:

 On Saturday 20 May 2006 23:30, Andrew Morton wrote:
  Rafael J. Wysocki [EMAIL PROTECTED] wrote:
  
   On Saturday 20 May 2006 14:41, Andrew Morton wrote:
 
 
   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc4/2.6.17-rc4-mm2/
   
My box (Asus L5D, x86_64 kernel) locks up hard after the resume from 
   suspend
to disk.  This happens right after the console has been restored and 
   only if
all modules are loaded before suspend (eg. it doesn't lock up when 
   booted with
init=/bin/bash).  Also it's caught by the softlockup watchdog which 
   produces
traces similar to the appended one.
   
Greetings,
Rafael
   
   
BUG: soft lockup detected on CPU#0!
   
Call Trace: IRQ 8025b2f1{softlockup_tick+193}
   802360a3{run_local_timers+19} 
   802362c7{update_process_times+87}
   8020e174{main_timer_handler+548} 
   8020e3c5{timer_interrupt+21}
   8025b4e3{handle_IRQ_event+51} 
   8025b5d2{__do_IRQ+162}
   8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0}
   803cb8d0{urb_destroy+0} 
   803ca84a{usb_hcd_poll_rh_status+250}
   880dafa2{:ohci_hcd:ohci_irq+194} 
   803c9ce2{usb_hcd_irq+50}
   8025b4e3{handle_IRQ_event+51} 
   8025b5d2{__do_IRQ+162}
   8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0}
   8025b4d4{handle_IRQ_event+36} 
   8025b5d2{__do_IRQ+162}
   8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0}
   8025b4d4{handle_IRQ_event+36} 
   8025b5d2{__do_IRQ+162}
   8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0} 
   EOI
   803cb8d0{urb_destroy+0} 
   803cb788{hcd_submit_urb+2072}
   80463d4d{_spin_unlock_irqrestore+29} 
   803cb9a5{usb_free_urb+21}
   803ca0ab{usb_hcd_giveback_urb+315} 
   80463d4d{_spin_unlock_irqrestore+29}
   803cbd2b{usb_submit_urb+859} 
   803cc66a{usb_start_wait_urb+122}
   8027c58d{dbg_redzone1+29} 
   8027d804{cache_alloc_debugcheck_after+532}
   8027c58d{dbg_redzone1+29} 
   803cca40{usb_control_msg+240}
   803c5e74{set_port_feature+68} 
   803c61f9{hub_port_reset+57}
   803c64d1{hub_port_init+129} 
   803c8b31{hub_thread+2241}
   80242140{autoremove_wake_function+0} 
   803c8270{hub_thread+0}
   80241f29{kthread+217} 
   80463d84{_spin_unlock_irq+20}
   80228d99{schedule_tail+73} 
   8020a38a{child_rip+8}
   80241e50{kthread+0} 8020a382{child_rip+0}
BUG: soft lockup detected on CPU#0!
  
  What a revolting backtrace.  There were some x86_64 precise-backtrace
  patches floating around on the list this week.
 
 They seem to reappear and get squashed by Andi on a regular basis. ;-)
 
  Still, it would appear that USB has become confused.  If you have the time
  to do a bisection search, I'd start in on gregkh-usb-*.patch.
 
 Obviously it's this one:
 
 gregkh-usb-usb-ohci-avoids-root-hub-timer-polling.patch
 
 [Well, looks like it hasn't been tested properly before posting ... :-(]

Did this ever get settled?  Although I'm not familiar with the details of 
the driver, this doesn't seem like the sort of thing that should cause any 
problems with suspend/resume.

Alan Stern



---
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel


Re: [linux-usb-devel] Re: 2.6.17-rc4-mm2 (hard lockup after resume from disk on AMD64)

2006-05-25 Thread David Brownell
On Thursday 25 May 2006 1:29 pm, Alan Stern wrote:
 On Sun, 21 May 2006, Rafael J. Wysocki wrote:

  
  Obviously it's this one:
  
  gregkh-usb-usb-ohci-avoids-root-hub-timer-polling.patch
  
  [Well, looks like it hasn't been tested properly before posting ... :-(]
 
 Did this ever get settled?  

I'm still looking at it.  Some OHCI implementations like that patch,
while others don't.


 Although I'm not familiar with the details of  
 the driver, this doesn't seem like the sort of thing that should cause any 
 problems with suspend/resume.
 
 Alan Stern
 


---
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel


Re: [linux-usb-devel] Re: 2.6.17-rc4-mm2 (hard lockup after resume from disk on AMD64)

2006-05-25 Thread Rafael J. Wysocki
On Thursday 25 May 2006 22:29, Alan Stern wrote:
 On Sun, 21 May 2006, Rafael J. Wysocki wrote:
 
  On Saturday 20 May 2006 23:30, Andrew Morton wrote:
   Rafael J. Wysocki [EMAIL PROTECTED] wrote:
   
On Saturday 20 May 2006 14:41, Andrew Morton wrote:
  
  
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc4/2.6.17-rc4-mm2/

 My box (Asus L5D, x86_64 kernel) locks up hard after the resume from 
suspend
 to disk.  This happens right after the console has been restored and 
only if
 all modules are loaded before suspend (eg. it doesn't lock up when 
booted with
 init=/bin/bash).  Also it's caught by the softlockup watchdog which 
produces
 traces similar to the appended one.

 Greetings,
 Rafael


 BUG: soft lockup detected on CPU#0!

 Call Trace: IRQ 8025b2f1{softlockup_tick+193}
802360a3{run_local_timers+19} 
802362c7{update_process_times+87}
8020e174{main_timer_handler+548} 
8020e3c5{timer_interrupt+21}
8025b4e3{handle_IRQ_event+51} 
8025b5d2{__do_IRQ+162}
8020c3b1{do_IRQ+65} 
80209d5e{ret_from_intr+0}
803cb8d0{urb_destroy+0} 
803ca84a{usb_hcd_poll_rh_status+250}
880dafa2{:ohci_hcd:ohci_irq+194} 
803c9ce2{usb_hcd_irq+50}
8025b4e3{handle_IRQ_event+51} 
8025b5d2{__do_IRQ+162}
8020c3b1{do_IRQ+65} 
80209d5e{ret_from_intr+0}
8025b4d4{handle_IRQ_event+36} 
8025b5d2{__do_IRQ+162}
8020c3b1{do_IRQ+65} 
80209d5e{ret_from_intr+0}
8025b4d4{handle_IRQ_event+36} 
8025b5d2{__do_IRQ+162}
8020c3b1{do_IRQ+65} 
80209d5e{ret_from_intr+0} EOI
803cb8d0{urb_destroy+0} 
803cb788{hcd_submit_urb+2072}
80463d4d{_spin_unlock_irqrestore+29} 
803cb9a5{usb_free_urb+21}
803ca0ab{usb_hcd_giveback_urb+315} 
80463d4d{_spin_unlock_irqrestore+29}
803cbd2b{usb_submit_urb+859} 
803cc66a{usb_start_wait_urb+122}
8027c58d{dbg_redzone1+29} 
8027d804{cache_alloc_debugcheck_after+532}
8027c58d{dbg_redzone1+29} 
803cca40{usb_control_msg+240}
803c5e74{set_port_feature+68} 
803c61f9{hub_port_reset+57}
803c64d1{hub_port_init+129} 
803c8b31{hub_thread+2241}
80242140{autoremove_wake_function+0} 
803c8270{hub_thread+0}
80241f29{kthread+217} 
80463d84{_spin_unlock_irq+20}
80228d99{schedule_tail+73} 
8020a38a{child_rip+8}
80241e50{kthread+0} 8020a382{child_rip+0}
 BUG: soft lockup detected on CPU#0!
   
   What a revolting backtrace.  There were some x86_64 precise-backtrace
   patches floating around on the list this week.
  
  They seem to reappear and get squashed by Andi on a regular basis. ;-)
  
   Still, it would appear that USB has become confused.  If you have the time
   to do a bisection search, I'd start in on gregkh-usb-*.patch.
  
  Obviously it's this one:
  
  gregkh-usb-usb-ohci-avoids-root-hub-timer-polling.patch
  
  [Well, looks like it hasn't been tested properly before posting ... :-(]
 
 Did this ever get settled?

The patch has been dropped by Andrew.

 Although I'm not familiar with the details of the driver, this doesn't seem
 like the sort of thing that should cause any problems with suspend/resume.

Still it does (100% reproducible).  I think Dave knows the reason why. ;-)

Greetings,
Rafael


---
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel


[linux-usb-devel] Re: 2.6.17-rc4-mm2 (hard lockup after resume from disk on AMD64)

2006-05-21 Thread Rafael J. Wysocki
On Saturday 20 May 2006 23:30, Andrew Morton wrote:
 Rafael J. Wysocki [EMAIL PROTECTED] wrote:
 
  On Saturday 20 May 2006 14:41, Andrew Morton wrote:


  ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc4/2.6.17-rc4-mm2/
  
   My box (Asus L5D, x86_64 kernel) locks up hard after the resume from 
  suspend
   to disk.  This happens right after the console has been restored and only 
  if
   all modules are loaded before suspend (eg. it doesn't lock up when booted 
  with
   init=/bin/bash).  Also it's caught by the softlockup watchdog which 
  produces
   traces similar to the appended one.
  
   Greetings,
   Rafael
  
  
   BUG: soft lockup detected on CPU#0!
  
   Call Trace: IRQ 8025b2f1{softlockup_tick+193}
  802360a3{run_local_timers+19} 
  802362c7{update_process_times+87}
  8020e174{main_timer_handler+548} 
  8020e3c5{timer_interrupt+21}
  8025b4e3{handle_IRQ_event+51} 
  8025b5d2{__do_IRQ+162}
  8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0}
  803cb8d0{urb_destroy+0} 
  803ca84a{usb_hcd_poll_rh_status+250}
  880dafa2{:ohci_hcd:ohci_irq+194} 
  803c9ce2{usb_hcd_irq+50}
  8025b4e3{handle_IRQ_event+51} 
  8025b5d2{__do_IRQ+162}
  8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0}
  8025b4d4{handle_IRQ_event+36} 
  8025b5d2{__do_IRQ+162}
  8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0}
  8025b4d4{handle_IRQ_event+36} 
  8025b5d2{__do_IRQ+162}
  8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0} 
  EOI
  803cb8d0{urb_destroy+0} 
  803cb788{hcd_submit_urb+2072}
  80463d4d{_spin_unlock_irqrestore+29} 
  803cb9a5{usb_free_urb+21}
  803ca0ab{usb_hcd_giveback_urb+315} 
  80463d4d{_spin_unlock_irqrestore+29}
  803cbd2b{usb_submit_urb+859} 
  803cc66a{usb_start_wait_urb+122}
  8027c58d{dbg_redzone1+29} 
  8027d804{cache_alloc_debugcheck_after+532}
  8027c58d{dbg_redzone1+29} 
  803cca40{usb_control_msg+240}
  803c5e74{set_port_feature+68} 
  803c61f9{hub_port_reset+57}
  803c64d1{hub_port_init+129} 
  803c8b31{hub_thread+2241}
  80242140{autoremove_wake_function+0} 
  803c8270{hub_thread+0}
  80241f29{kthread+217} 
  80463d84{_spin_unlock_irq+20}
  80228d99{schedule_tail+73} 8020a38a{child_rip+8}
  80241e50{kthread+0} 8020a382{child_rip+0}
   BUG: soft lockup detected on CPU#0!
 
 What a revolting backtrace.  There were some x86_64 precise-backtrace
 patches floating around on the list this week.

They seem to reappear and get squashed by Andi on a regular basis. ;-)

 Still, it would appear that USB has become confused.  If you have the time
 to do a bisection search, I'd start in on gregkh-usb-*.patch.

Obviously it's this one:

gregkh-usb-usb-ohci-avoids-root-hub-timer-polling.patch

[Well, looks like it hasn't been tested properly before posting ... :-(]


---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel


[linux-usb-devel] Re: 2.6.17-rc4-mm2 (hard lockup after resume from disk on AMD64)

2006-05-20 Thread Andrew Morton
Rafael J. Wysocki [EMAIL PROTECTED] wrote:

 On Saturday 20 May 2006 14:41, Andrew Morton wrote:
   
   
 ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc4/2.6.17-rc4-mm2/
 
  My box (Asus L5D, x86_64 kernel) locks up hard after the resume from suspend
  to disk.  This happens right after the console has been restored and only if
  all modules are loaded before suspend (eg. it doesn't lock up when booted 
 with
  init=/bin/bash).  Also it's caught by the softlockup watchdog which produces
  traces similar to the appended one.
 
  Greetings,
  Rafael
 
 
  BUG: soft lockup detected on CPU#0!
 
  Call Trace: IRQ 8025b2f1{softlockup_tick+193}
 802360a3{run_local_timers+19} 
 802362c7{update_process_times+87}
 8020e174{main_timer_handler+548} 
 8020e3c5{timer_interrupt+21}
 8025b4e3{handle_IRQ_event+51} 
 8025b5d2{__do_IRQ+162}
 8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0}
 803cb8d0{urb_destroy+0} 
 803ca84a{usb_hcd_poll_rh_status+250}
 880dafa2{:ohci_hcd:ohci_irq+194} 
 803c9ce2{usb_hcd_irq+50}
 8025b4e3{handle_IRQ_event+51} 
 8025b5d2{__do_IRQ+162}
 8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0}
 8025b4d4{handle_IRQ_event+36} 
 8025b5d2{__do_IRQ+162}
 8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0}
 8025b4d4{handle_IRQ_event+36} 
 8025b5d2{__do_IRQ+162}
 8020c3b1{do_IRQ+65} 80209d5e{ret_from_intr+0} 
 EOI
 803cb8d0{urb_destroy+0} 
 803cb788{hcd_submit_urb+2072}
 80463d4d{_spin_unlock_irqrestore+29} 
 803cb9a5{usb_free_urb+21}
 803ca0ab{usb_hcd_giveback_urb+315} 
 80463d4d{_spin_unlock_irqrestore+29}
 803cbd2b{usb_submit_urb+859} 
 803cc66a{usb_start_wait_urb+122}
 8027c58d{dbg_redzone1+29} 
 8027d804{cache_alloc_debugcheck_after+532}
 8027c58d{dbg_redzone1+29} 
 803cca40{usb_control_msg+240}
 803c5e74{set_port_feature+68} 
 803c61f9{hub_port_reset+57}
 803c64d1{hub_port_init+129} 
 803c8b31{hub_thread+2241}
 80242140{autoremove_wake_function+0} 
 803c8270{hub_thread+0}
 80241f29{kthread+217} 
 80463d84{_spin_unlock_irq+20}
 80228d99{schedule_tail+73} 8020a38a{child_rip+8}
 80241e50{kthread+0} 8020a382{child_rip+0}
  BUG: soft lockup detected on CPU#0!

What a revolting backtrace.  There were some x86_64 precise-backtrace
patches floating around on the list this week.

Still, it would appear that USB has become confused.  If you have the time
to do a bisection search, I'd start in on gregkh-usb-*.patch.






---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel