From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: noah <noah123@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: Possibly SATA related freeze killed networking and RAID
Date: Tue, 20 Nov 2007 22:05:12 +0000 [thread overview]
Message-ID: <20071120220512.46b9e975@the-village.bc.nu> (raw)
In-Reply-To: <d00698fb0711201109m23ff096eiabeb22c8f9a917dc@mail.gmail.com>
> kernel: [734344.717844] irq 21: nobody cared (try booting with the
> "irqpoll" option)
> kernel: [734344.717866]
Your machine decided to emit interrupt 21 without an apparent reason.
Whatever caused that made the kernel shut down IRQ 21 at which point the
disk drives on that IRQ were no longer being serviced. Everything on IRQ
21 would have died - which may be why your networking failed too.
What do you have on IRQ 21 and is this a one off ?
next prev parent reply other threads:[~2007-11-20 22:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 19:09 Possibly SATA related freeze killed networking and RAID noah
2007-11-20 22:05 ` Alan Cox [this message]
2007-11-20 22:16 ` noah
2007-11-21 0:45 ` Alan Cox
2007-11-21 19:06 ` noah
2007-12-10 12:33 ` noah
2007-11-26 12:06 ` Pavel Machek
2007-11-28 1:55 ` Tejun Heo
2007-11-29 22:16 ` Phillip Susi
2007-11-30 0:02 ` Tejun Heo
2007-11-30 18:45 ` Phillip Susi
2007-11-30 23:56 ` Tejun Heo
2007-12-03 17:15 ` Phillip Susi
2007-12-04 1:32 ` Tejun Heo
2007-11-30 13:13 ` Alan Cox
2007-11-26 7:55 ` Pavel Machek
2007-11-30 15:00 ` Mark Lord
2007-11-30 20:25 ` Pavel Machek
[not found] <fa.hz1AWBbuhaxCXiVbvWdM1r83meE@ifi.uio.no>
[not found] ` <fa.fUEfthqYoWrlov4j7OjtVSgx42g@ifi.uio.no>
[not found] ` <fa.qGibmi9xfm4JHJhvn0KM4rdFM+M@ifi.uio.no>
[not found] ` <fa.YcQmwdppCKfJhxSMgOb0RJPmHg8@ifi.uio.no>
[not found] ` <fa.0muxGr+d7CjnQ/J5GaB+TSqouuU@ifi.uio.no>
2007-11-30 0:03 ` Robert Hancock
2007-12-10 21:25 Thiemo Nagel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071120220512.46b9e975@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noah123@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).