Re: Interrupt messages from usb0 on CURRENT
Vladimir B. Grebenschikov wrote: Ollivier Robert writes: I just upgraded to the latest sources (two hours ago) on my VAIO laptop an d I'm now getting dozens of messages: Aug 22 15:00:07 sidhe /boot/kernel/kernel: usb0: interrupt, but not for us Aug 22 15:00:51 sidhe last message repeated 8 times Aug 22 15:03:02 sidhe last message repeated 19 times Aug 22 15:12:59 sidhe last message repeated 92 times Have same problem on VAIO, on fresh sources. Yes, back out the last change to dev/usb/uhci.c and dev/usb/ohci.c. Nick's commit is 100% bogus. It is a fundamental nature of PCI shared interrupts that all possible sources have to be polled. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Interrupt messages from usb0 on CURRENT
Same thing here, started with the build this morning... I know of one change that had been done in the past 36 hours to usb, but it should not have done this, as the patches I was using didn't produce this before the committer committed the patches. Maybe something else got changed as well? Vladimir B. Grebenschikov wrote: Ollivier Robert writes: I just upgraded to the latest sources (two hours ago) on my VAIO laptop and I'm now getting dozens of messages: Aug 22 15:00:07 sidhe /boot/kernel/kernel: usb0: interrupt, but not for us Aug 22 15:00:51 sidhe last message repeated 8 times Aug 22 15:03:02 sidhe last message repeated 19 times Aug 22 15:12:59 sidhe last message repeated 92 times Have same problem on VAIO, on fresh sources. Any idea? I also got an error where pccardd tried to attach my pcmcia card two times -- TSB Russian Express, Moscow Vladimir B. Grebenschikov, [EMAIL PROTECTED] jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Interrupt messages from usb0 on CURRENT
In servalan.mailinglist.fbsd-current you write: I just upgraded to the latest sources (two hours ago) on my VAIO laptop and I'm now getting dozens of messages: Aug 22 15:00:07 sidhe /boot/kernel/kernel: usb0: interrupt, but not for us Aug 22 15:00:51 sidhe last message repeated 8 times Aug 22 15:03:02 sidhe last message repeated 19 times Aug 22 15:12:59 sidhe last message repeated 92 times This is apparently due to a change last night in the uhci and ohci drivers to report interrupts the USB code sees but which don't correspond to any actual USB activity. I saw the same thing last night after I upgraded (to try out jhb's latest fixes, which worked like a charm on the sound problem). I note that on my system the uhci0 and fxp0 are on the same IRQ: uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xef80-0xef9f irq 2 at device 7.2 on pci0 fxp0: Intel Pro 10/100B/100+ Ethernet port 0xef40-0xef5f mem 0xfea0-0xfeaf,0xfc4ff000-0xfc4f irq 2 at device 17.0 on pci0 I wonder if the interrupts not for us are actually interrupts from the Ethernet that the USB code sees because both the USB and the Ethernet are on the same irq. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Interrupt messages from usb0 on CURRENT
Richard Todd wrote: In servalan.mailinglist.fbsd-current you write: I just upgraded to the latest sources (two hours ago) on my VAIO laptop and I'm now getting dozens of messages: Aug 22 15:00:07 sidhe /boot/kernel/kernel: usb0: interrupt, but not for us Aug 22 15:00:51 sidhe last message repeated 8 times Aug 22 15:03:02 sidhe last message repeated 19 times Aug 22 15:12:59 sidhe last message repeated 92 times This is apparently due to a change last night in the uhci and ohci drivers to report interrupts the USB code sees but which don't correspond to any actual USB activity. I saw the same thing last night after I upgraded (to try out jhb's latest fixes, which worked like a charm on the sound problem). I note that on my system the uhci0 and fxp0 are on the same IRQ: uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xef80-0xef9f irq 2 at device 7.2 on pci0 fxp0: Intel Pro 10/100B/100+ Ethernet port 0xef40-0xef5f mem 0xfea0-0xf eaf,0xfc4ff000-0xfc4f irq 2 at device 17.0 on pci0 I wonder if the interrupts not for us are actually interrupts from the Ethernet that the USB code sees because both the USB and the Ethernet are on the same irq. Yes. Revert the last revision to uhci.c and/or ohci.c. usb was assuming it was the sole generator of those interrupts. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
