Re: Thinkpad 600e interrupt storm
Understudy <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.mobile |
|---|---|
| Message-ID | <[email protected]> |
Thomas Kempka wrote: >Thomas Kempka <[email protected]> wrote: > > >>John Baldwin <[email protected]> wrote: >> >> >>>Can you try using the interrupt storm modifications from HEAD: >>> >>>Index: kern_intr.c >>>=================================================================== >>>RCS file: /usr/cvs/src/sys/kern/kern_intr.c,v >>>retrieving revision 1.113.2.5 >>>diff -u -r1.113.2.5 kern_intr.c >>>--- kern_intr.c 31 Jan 2005 23:26:15 -0000 1.113.2.5 >>>+++ kern_intr.c 7 Feb 2005 16:51:48 -0000 >>> >>> >>Hi, >> >>I just tested the patch with no success. I still get the interrupt >>storm error messages and cbb device slowdowns. >> >> >> > >I was able to resolve the device slowdowns by rearranging the IRQ >setup via the ps2 utility after I realized that they appear on cbb[01] >with ACPI enabled while the IRQ is shared with uhci0. > > Which ps2 utility did you use and what did you arrange your IRQs to be set at.? >The interrupt storm error messages do not disappear for me, but >I do not care about this while anything works like it should. > > Are you using a IBM thinkpad 600e or another laptop. If so which model? If you are using the 600e would please post the following information: What you set your IRQs at with the PS2 utility? The results of uname -r A copy of your kernel. A copy of your device.hints. A copy of your dmesg. A copy of any customizing you have done to your /usr/src/ files. >Thanks to Matthew N. Dodd for encouraging me to test all possible >IRQ setups in order to solve the device slowdown. > >Greetings, Thomas Kempka > > > This seems somewhat encouraging, I hope it can solve my problem with the interrupt storm. I get that one solved I will go onto other issues. Sincerely, Brendhan _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-mobile To unsubscribe, send any mail to "[email protected]"