From: dth@cistron.nl (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: 2.6.14-rc2-git7 crashed on amd64 (usenet gateway) after 18 hours
Date: Fri, 30 Sep 2005 06:54:29 +0000 (UTC) [thread overview]
Message-ID: <dhinf5$skf$1@news.cistron.nl> (raw)
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/
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.
Danny
next reply other threads:[~2005-09-30 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 6:54 Danny ter Haar [this message]
2005-09-30 7:13 ` 2.6.14-rc2-git7 crashed on amd64 (usenet gateway) after 18 hours Andrew Morton
2005-09-30 7:13 ` Andrew Morton
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
2005-09-30 13:04 ` Jens Laas
2005-10-04 10:47 ` Age Strand
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='dhinf5$skf$1@news.cistron.nl' \
--to=dth@cistron.nl \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.