From: Andrew Morton <akpm@osdl.org>
To: dth@cistron.nl (Danny ter Haar)
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: 2.6.14-rc2-git7 crashed on amd64 (usenet gateway) after 18 hours
Date: Fri, 30 Sep 2005 00:13:01 -0700 [thread overview]
Message-ID: <20050930001301.08eeab9d.akpm@osdl.org> (raw)
In-Reply-To: <dhinf5$skf$1@news.cistron.nl>
dth@cistron.nl (Danny ter Haar) wrote:
>
> Known story:
> last stable kernel for this machine is/was 2.6.12-mm1
>
> Every 2.6.1[34] kernel panics so far.
> Sometimes after 40 minutes, sometimes after 4 days.
>
> Config/more info at:
> http://newsgate.newsserver.nl/kernel/2.6.14-rc2-git7/
The aic79xx driver shat itself.
The log buffer starts with
scsi1 (4:0): rejecting I/O to offline device
scsi1 (4:0): rejecting I/O to offline device
scsi1 (4:0): rejecting I/O to offline device
So we've probably lost the info which will tell us how the problems
started. A serial console would be nice.
> This time it was scsi system again which "blew-up"
>
> Obvious difference i see between 2.6.12 en 2.6.1[34] is that the
> scsi/ethernet cards have different IRQ's set.
> If i'm correct acpi code changed in 2.6.13, right ?
>
> Since the 2.6.12-mm1 kernel survived 3 weeks+ and gave super performance
> i'm convinced it's not a hardware issue.
>
> Just giving feedback.
>
> Will try git8 and mm2 and of course report here when they fail.
Are all the failures due to the aic79xx driver failing in this manner? If
not then please report the different failures separately, thanks.
next prev parent reply other threads:[~2005-09-30 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 6:54 Danny ter Haar
2005-09-30 7:13 ` Andrew Morton [this message]
2005-09-30 7:39 ` Danny ter Haar
2005-09-30 12:44 ` Sander
2005-09-30 16:22 ` Danny ter Haar
2005-09-30 11:33 ` Danny ter Haar
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=20050930001301.08eeab9d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dth@cistron.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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
all inboxes | Powered by JetHome®