Date: Wed, 18 Mar 2009 17:29:50 +0300 From: "Marat N.Afanasyev" <amarat@ksu.ru> To: Pete French <petefrench@ticketswitch.com> Cc: ns@got2get.net, freebsd-stable@freebsd.org Subject: Re: Crazy "interrupt storm detected" on atapci0 Message-ID: <49C1055E.7000303@ksu.ru> In-Reply-To: <E1LjvOF-000Biu-IM@dilbert.ticketswitch.com> References: <E1LjvOF-000Biu-IM@dilbert.ticketswitch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Pete French wrote: >> as I supposed in previous message your MB is MicroStar product. So I >> insist that you read thread [1] in freebsd-stable named 'Interrupt >> storm' started by Dan Langille > > I (still) have the same problem on my MSI Platinum .... and having re-read > all of those threads in case I missed somehting, there still isn't a > solution there. All the suggested ones (using 'Linux" as ACPI name, moving > com interrupt ports, disabling onboard ether) are reported as failing > after a few days. Luckily I have a colleague who can reboot the remote > machine, and that has been my solution - but it is not really workable > long term. > > (actually this has reminded me to check dmesg, and it seems I need to > reboot this machine due to an interrupt storm right now). > > -pete. > _______________________________________________ > 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" > did you try to make a kernel with KDB and DDB? DEBUG-kernel? it seems that turning off optimization and place a debugging stuff in kernel solved my problem. -- SY, marat
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49C1055E.7000303>