On Wed, 2005-11-23 at 21:58 -0500, Alan Stern wrote: > On Wed, 23 Nov 2005, Steve Bangert wrote: > > > > What happens if you move or rename the usblp.ko driver module, so that > > > it's not available at boot time? You could then insmod it later on. > > > Normally the file is found in > > > > > > /lib/modules/<linux-version>/kernel/drivers/usb/class > > > > > > It may turn out when you do this that the printer just starts working, or > > > you may encounter the same problem as before. If you do then you'll be > > > in a good position to use usbmon. > > > > Here's a usbmon trace when i insmod the printer driver, the printer > > works fine at this time. > > > So far i have been unable to produce a non-working printer condition > > using this procedure and thus no trace so far, i suspect that i may > > never be able to capture a trace under these conditions, do you know of > > a way to start usbmon before /sbin/modprobe runs at system boot? That > > seems to be the only time the printer fails to work. > > If worse comes to worst and we never find an answer, at least you know now > how to prevent the problem from occurring... :-) > > What if instead of delaying usblp.ko, you delay the host controller driver > (uhci-hcd.ko)? At this point it's not clear whether the key is having the > printer on when the computer boots or having the printer on when the USB > host controller initializes.
Five days later the printer decides to stop working again, so here's a trace when i insmod the printer driver ( printer inop.) cf4f3e00 3833162829 S Co:004:00 s 01 0b 0000 0000 0000 0 cf4f3e00 3833164379 C Co:004:00 0 0 cf4f3e00 3833164481 S Ci:004:00 s a1 00 0000 0000 03ff 1023 < cf4f3e00 3833166375 C Ci:004:00 0 90 = 005a4d46 473a4550 534f4e3b 434d443a 45534350 4c322c42 44432c44 343b4d44 cf4f3e00 3833166496 S Ci:004:00 s a1 01 0000 0000 0001 1 < cf4f3e00 3833167375 C Ci:004:00 0 1 = 18 cf4f3800 3833319716 S Bi:004:02 -115 8192 < d9951980 3833319863 S Ci:004:00 s a1 00 0000 0000 03ff 1023 < cf4f3800 3833320353 C Bi:004:02 0 10 = 0000000a 00007f00 0080 d9951980 3833322347 C Ci:004:00 0 90 = 005a4d46 473a4550 534f4e3b 434d443a 45534350 4c322c42 44432c44 343b4d44 cf4f3800 3842205355 S Bi:004:02 -115 8192 < cf4f3580 3842205514 S Ci:004:00 s a1 00 0000 0000 03ff 1023 < cf4f3800 3842206916 C Bi:004:02 0 0 cf4f3580 3842207930 C Ci:004:00 0 90 = 005a4d46 473a4550 534f4e3b 434d443a 45534350 4c322c42 44432c44 343b4d44 cf4f3800 3842239697 S Bi:004:02 -115 8192 < cf4f3800 3842239906 C Bi:004:02 -2 0 cf4f3800 3871345926 S Bi:004:02 -115 8192 < cf4f3800 3871347206 C Bi:004:02 0 0 cf4f3800 3881657946 S Bi:004:02 -115 8192 < cf4f3800 3881659536 C Bi:004:02 0 0 cf4f3a80 3881677066 S Bo:004:01 -115 9 = 31313131 31313131 0a cf4f3a80 3881677525 C Bo:004:01 0 9 > And here's a repost of a working printer when i insmod the printer driver: dc3d9a00 3212138081 S Co:003:00 s 01 0b 0000 0000 0000 0 dc3d9a00 3212139822 C Co:003:00 0 0 dc3d9a00 3212139939 S Ci:003:00 s a1 00 0000 0000 03ff 1023 < dc3d9a00 3212141819 C Ci:003:00 0 90 = 005a4d46 473a4550 534f4e3b 434d443a 45534350 4c322c42 44432c44 343b4d44 dc3d9a00 3212141968 S Ci:003:00 s a1 01 0000 0000 0001 1 < dc3d9a00 3212142819 C Ci:003:00 0 1 = 18 d3f6e500 3212294992 S Bi:003:02 -115 8192 < dc3d9d00 3212295141 S Ci:003:00 s a1 00 0000 0000 03ff 1023 < d3f6e500 3212296796 C Bi:003:02 0 0 dc3d9d00 3212297811 C Ci:003:00 0 90 = 005a4d46 473a4550 534f4e3b 434d443a 45534350 4c322c42 44432c44 343b4d44 d3f6e500 3220781493 S Bi:003:02 -115 8192 < dc3d9d00 3220781649 S Ci:003:00 s a1 00 0000 0000 03ff 1023 < d3f6e500 3220783424 C Bi:003:02 0 0 dc3d9d00 3220784438 C Ci:003:00 0 90 = 005a4d46 473a4550 534f4e3b 434d443a 45534350 4c322c42 44432c44 343b4d44 d3f6e500 3220817200 S Bi:003:02 -115 8192 < d3f6e500 3220817412 C Bi:003:02 -2 0 d3f6e500 3277341929 S Bi:003:02 -115 8192 < d3f6e500 3277343279 C Bi:003:02 0 0 d3f6e500 3303234088 S Bi:003:02 -115 8192 < d3f6e500 3303236087 C Bi:003:02 0 0 dd4b7e80 3303263204 S Bo:003:01 -115 17 = 31313131 31313131 31313131 31313131 0a dd4b7e80 3303264076 C Bo:003:01 0 17 > I tried getting a usbmon trace while doing an insmod of uhci-hcd.ko but there's a chicken and egg scenario, /sys/kernel/debug needs to be mounted before a usbmon snapshot is taken, but it can't be mounted unless uhci-hcd.ko is loaded first. Steve ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
