Re: kern/39093: usb doesn't work anymore on IBM T43p

[Kurt Schreiner <ks%ub.uni-mainz.de@localhost>]

The following reply was made to PR kern/39093; it has been noted by GNATS.

From: Kurt Schreiner <ks%ub.uni-mainz.de@localhost>
To: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
Cc: "gnats-bugs%NetBSD.org@localhost" <gnats-bugs%NetBSD.org@localhost>,
   "kern-bug-people%NetBSD.org@localhost" 
<kern-bug-people%NetBSD.org@localhost>,
   "gnats-admin%NetBSD.org@localhost" <gnats-admin%NetBSD.org@localhost>,
   "netbsd-bugs%NetBSD.org@localhost" <netbsd-bugs%NetBSD.org@localhost>
Subject: Re: kern/39093: usb doesn't work anymore on IBM T43p
Date: Mon, 7 Jul 2008 10:36:35 +0200

 On Sun, Jul 06, 2008 at 09:31:32PM +0200, Manuel Bouyer wrote:
 > On Fri, Jul 04, 2008 at 09:42:54PM +0200, Kurt Schreiner wrote:
 > > > Do you mean is started failing on Jun 27, or that it worked on Jun 27 and
 > > > started failing later ? I commited some changes to the USB drivers on 
 > > > Jun 28.
 > > First failure is from Jun 27. Here's the relevant excerpt from 
 > > /var/log/messages
 > 
 > OK, so it's probably not caused by uhci.c rev 1.223. You could try reverting
 > it to 1.222 to see if it changes anything, but I don't think so.
 Over the weekend I played around w/ older kernels from source back to
 Jun 14 20:21 - the problem appears sooner or later... Even the kernel
 compiled on Jun 14 18:43 which (I thought?) worked previously shows
 the problem. I've found a very old kernel from May, 4 which booted fine
 and didn't show the problem but new userland (ifconfig etc) doesn't work
 so well. I'll experiment more later at home...
 
 
 > > Hm, there are 41 minutes from finishing boot 'till the errors first 
 > > appeared.
 > > Following boots show the error message w/o "pause"... (see attached parts 
 > > of
 > > /var/log/messages)
 > 
 > there's still more than one minute before getting the first message (and
 > probably more than that because syslog doesn't start right after init).
 > So I guess something is corrupting uhci's memory.
 > Could you see if not using ath (maybe disabling it with boot -c) would
 > avoid the issue ?
 Just tried w/ ath disabled using one of the "problematic" kernels built
 saturday and until now no error message! Hmmmmmmm....
 Same w/ a kernel just built from fresh sources: no problems so far...
 
 So the questions are: What and why is ath doing bad to uhci?
 
 Maybe this excerpt from /var/log/messages* could give a clue?
 
 /var/log/messages.9.gz:Jun  7 21:40:17 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.9.gz:Jun  7 21:56:00 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.9.gz:Jun  7 21:56:32 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.5.gz:Jun 19 14:37:29 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.5.gz:Jun 19 14:39:03 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.5.gz:Jun 19 14:44:19 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.5.gz:Jun 19 14:46:39 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.5.gz:Jun 19 15:09:40 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.5.gz:Jun 21 14:10:32 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.5.gz:Jun 21 22:59:35 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 22 23:13:05 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 26 12:59:18 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 26 13:04:55 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 26 13:06:23 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 26 13:58:39 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 26 14:41:53 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 26 14:45:08 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 26 16:15:41 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 26 18:04:12 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 26 18:04:12 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.4.gz:Jun 26 19:48:45 ipaddi /netbsd: ath0: hardware error; 
resetting
 /var/log/messages.3.gz:Jun 27 20:11:18 ipaddi /netbsd: uhci2: host controller 
process error
 /var/log/messages.3.gz:Jun 27 20:11:50 ipaddi /netbsd: uhci0: host controller 
process error
 /var/log/messages.3.gz:Jun 27 20:11:50 ipaddi /netbsd: uhci1: host controller 
process error
 /var/log/messages.3.gz:Jun 27 20:11:50 ipaddi /netbsd: uhci3: host controller 
process error
 /var/log/messages.3.gz:Jun 27 20:37:34 ipaddi /netbsd: uhci0: host controller 
process error
 /var/log/messages.3.gz:Jun 27 20:37:36 ipaddi /netbsd: uhci1: host controller 
process error
 /var/log/messages.3.gz:Jun 27 20:37:36 ipaddi /netbsd: uhci3: host controller 
process error
 /var/log/messages.3.gz:Jun 27 20:37:37 ipaddi /netbsd: uhci2: host controller 
process error
 /var/log/messages.3.gz:Jun 29 13:44:28 ipaddi /netbsd: uhci0: host controller 
process error
 /var/log/messages.3.gz:Jun 29 13:44:28 ipaddi /netbsd: uhci2: host controller 
process error
 /var/log/messages.3.gz:Jun 29 13:44:29 ipaddi /netbsd: uhci1: host controller 
process error
 
 /var/log/messages.1.gz:Jul  3 17:26:52 ipaddi /netbsd: ath0: hardware error; 
resetting
        *** but this ath0: error came from a kernel w/o uhci! ***
 
 /var/log/messages.1.gz:Jul  3 18:12:00 ipaddi /netbsd: uhci1: host controller 
process error
 /var/log/messages.1.gz:Jul  3 18:12:00 ipaddi /netbsd: uhci2: host controller 
process error
 /var/log/messages.1.gz:Jul  3 18:12:00 ipaddi /netbsd: uhci3: host controller 
process error
 /var/log/messages.1.gz:Jul  3 18:12:02 ipaddi /netbsd: uhci0: host controller 
process error
 /var/log/messages.0.gz:Jul  5 09:18:51 ipaddi /netbsd: uhci0: host controller 
process error
 /var/log/messages.0.gz:Jul  5 09:18:51 ipaddi /netbsd: uhci1: host controller 
process error
 /var/log/messages.0.gz:Jul  5 09:18:51 ipaddi /netbsd: uhci2: host controller 
process error
 /var/log/messages.0.gz:Jul  5 09:18:51 ipaddi /netbsd: uhci3: host controller 
process error
 /var/log/messages.0.gz:Jul  5 11:21:39 ipaddi /netbsd: uhci0: host controller 
process error
 /var/log/messages.0.gz:Jul  5 11:21:39 ipaddi /netbsd: uhci1: host controller 
process error
 /var/log/messages.0.gz:Jul  5 11:21:39 ipaddi /netbsd: uhci2: host controller 
process error
 /var/log/messages.0.gz:Jul  5 11:21:39 ipaddi /netbsd: uhci3: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:39:12 ipaddi /netbsd: uhci1: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:39:12 ipaddi /netbsd: uhci3: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:39:13 ipaddi /netbsd: uhci0: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:44:17 ipaddi /netbsd: uhci0: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:44:17 ipaddi /netbsd: uhci1: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:44:17 ipaddi /netbsd: uhci2: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:44:17 ipaddi /netbsd: uhci3: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:50:58 ipaddi /netbsd: uhci0: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:50:59 ipaddi /netbsd: uhci1: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:50:59 ipaddi /netbsd: uhci2: host controller 
process error
 /var/log/messages.0.gz:Jul  5 12:50:59 ipaddi /netbsd: uhci3: host controller 
process error
 /var/log/messages.0.gz:Jul  5 13:07:30 ipaddi /netbsd: uhci0: host controller 
process error
 /var/log/messages.0.gz:Jul  5 13:07:30 ipaddi /netbsd: uhci1: host controller 
process error
 /var/log/messages.0.gz:Jul  5 13:07:30 ipaddi /netbsd: uhci3: host controller 
process error
 /var/log/messages.0.gz:Jul  5 13:07:31 ipaddi /netbsd: uhci2: host controller 
process error
 
 Kurt