Date: Thu, 22 Jan 2009 21:05:21 -0500 From: Dan Langille <dan@langille.org> To: SEan Strand <seanjstrand@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: interrupt storm Message-ID: <B96D29B3-DE4B-4C54-9BD2-3DFAFCF63FCA@langille.org> In-Reply-To: <7619cc20901200749w5126264bka61b7ac62188a578@mail.gmail.com> References: <496D374A.3020704@langille.org> <496E9A37.20800@langille.org> <496EA339.6010808@ksu.ru> <496EB43A.8010805@langille.org> <496ECB2A.8080609@ksu.ru> <49754FA1.3070004@ksu.ru> <B37EBE5F-FD0A-480A-8FB7-EECC832E68B3@langille.org> <7619cc20901200749w5126264bka61b7ac62188a578@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 20, 2009, at 10:49 AM, SEan Strand wrote: > Re:K9A2 Platinum MSI repeated irq22. > > Hi gents, I once had this and just opened up the BIOS and changed > the comms-tty IRQ address and problem gone. Try ity and see if it > helps you? > Rgds SEanS That worked for a while. > > NB has any one had major problems updating this board from MSI with > a XP-64 bit CPU , I tryed all last week and no go, or am I the only > one? > Thanks in advance SEanS. > . > > 2009/1/20 Dan Langille <dan@langille.org> > > On Jan 19, 2009, at 11:14 PM, Marat N.Afanasyev wrote: > > Marat N.Afanasyev wrote: > Dan Langille wrote: > Marat N.Afanasyev wrote: > Dan Langille wrote: > Dan Langille wrote: > Hi, > > I'm getting this: > > kernel: interrupt storm detected on "irq22:"; throttling interrupt > source > what is your motherboard brand? I have the same issue with interrupt > storms, as stated in [1] and I think that it can be related with mb > manyfacturer > > [1] http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047644.html > > > Opening the case, reading the m/b: > > K9A2 Platinum MSI > > yeah. I suppose that microstar makes something weird in their > motherboards. I tried to disassemble dsdt and assemble it again -- > no luck, it has errors ;) more interesting, I've found that dsdt > mentions windows nt, windowses like millennium, windowses like 2000 > and linux explicitly. but no mention of any other system. I think > this is one of cases to investigate, but I have a little experience > in dsdt programming :( > still no luck with fixing dsdt. I tried to build a custom dsdt, > tried to set hw.acpi.osname="Linux" in /boot/loader.conf, nothing > changes. so it may be related with APIC, not dsdt only. So, if > anyone has any idea how to find out what is happening, please tell > me, we'll try to fix this. > > Probably Pyun will give us some advice, wouldn't you? :) > > Or should I make a problem report? > > > Please. > > -- > Dan Langille > http://langille.org/ > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > " > -- Dan Langille http://langille.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B96D29B3-DE4B-4C54-9BD2-3DFAFCF63FCA>