Georg Acher wrote:
>
> On Wed, Apr 19, 2000 at 01:58:45PM +0000, Mikael Nystr�m wrote:
>
> > Apr 19 13:39:04 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
> > 64
> > Apr 19 13:39:04 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
> > 192
> > Apr 19 13:39:04 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
> > 320
>
> > Exactly whats has happened when the kernel generates this messages?
>
> There seems to be a problem with the 128ms-interrupt. Since full
> debugging is not enabled, it is not clear, which device causes this.
Oki, I search some file but couldn't find out how to enable "full"
debugging, I turned on "verbose mode" hovever, here is a new run:
Apr 19 16:41:06 veiron kernel: usb.c: registered new driver hub
Apr 19 16:41:06 veiron kernel: usb-uhci.c: $Revision: 1.228 $ time
16:38:45 Apr 19 2000
Apr 19 16:41:06 veiron kernel: usb-uhci.c: High bandwidth mode enabled
Apr 19 16:41:06 veiron kernel: usb-uhci.c: Intel USB controller: setting
latency timer to 0
Apr 19 16:41:06 veiron kernel: usb-uhci.c: USB UHCI at I/O 0xe000, IRQ 9
Apr 19 16:41:06 veiron kernel: usb-uhci.c: Detected 2 ports
Apr 19 16:41:06 veiron kernel: usb.c: new USB bus registered, assigned
bus number 1
Apr 19 16:41:06 veiron kernel: usb.c: USB new device connect, assigned
device number 1
Apr 19 16:41:06 veiron kernel: Product: USB UHCI Root Hub
Apr 19 16:41:06 veiron kernel: SerialNumber: e000
Apr 19 16:41:06 veiron kernel: hub.c: USB hub found
Apr 19 16:41:06 veiron kernel: hub.c: 2 ports detected
Apr 19 16:41:06 veiron kernel: usb.c: registered new driver usbscanner
Apr 19 16:41:06 veiron kernel: scanner.c: USB Scanner support
registered.
Apr 19 16:41:12 veiron kernel: usb.c: USB new device connect, assigned
device number 2
Apr 19 16:41:12 veiron kernel: Manufacturer: Canon Inc.
Apr 19 16:41:12 veiron kernel: Product: PowerShot S20
Apr 19 16:41:12 veiron kernel: scanner.c: probe_scanner: User specified
USB scanner -- Vendor:Product - 4a9:3043
Apr 19 16:41:17 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
192
Apr 19 16:41:17 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
320
Apr 19 16:41:17 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
448
Apr 19 16:41:17 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
576
Apr 19 16:41:17 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
704
Apr 19 16:41:17 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
832
Apr 19 16:41:17 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
960
Apr 19 16:41:18 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
1088
Apr 19 16:41:18 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
1216
Apr 19 16:41:18 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
1344
Apr 19 16:41:18 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
1472
Apr 19 16:41:18 veiron kernel: usb-uhci.c: interrupt, status 3, frame#
1600
> Usually a device should NAK the polling, if it has nothing to say.
> But here it doesn't say anything...
Isn't it the camera sending these interrupts?
If so who is responsible for taking care of the information eventually
carried along whith the interrupt, scanner.c?
> > They start as soon as my program have made some handshaking with the
> > camera.
> >
> > File transfers and everything work smoothly, but these interrupts seems
> > to come reguraly, even during long file transfers.
>
> Does it stop when the transfer is over?
Nope, its before, during and after. After trying to turn the camera off,
its still "alive" 10s and generating these nice logs.
I have no other USB equipment and using Kernel 2.3.99-pre5.
Mikael Nystr�m
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
