From: Andrew Morton <akpm@linux-foundation.org>
To: Stefan Priebe <stefan@prie.be>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Kernel 2.6.20 does not work anymore with SCSI or SATA on old Opteron / Xeon servers
Date: Mon, 19 Mar 2007 23:27:32 -0800 [thread overview]
Message-ID: <20070319232732.854d7120.akpm@linux-foundation.org> (raw)
In-Reply-To: <45FDA626.9000404@prie.be>
On Sun, 18 Mar 2007 21:50:46 +0100 Stefan Priebe <stefan@prie.be> wrote:
> Hello!
>
> We've a very strange Problem with Kernel 2.6.20.x
>
> If i try to access a SCSI or SATA Disk (tested with Adaptec U320
> ASC-29320, ICP Vortex 9024, Promise TX300) the whole server hangs - no
> output - no error on the screen - but it hangs completely. But it does
> not happen on all our systems affected are only old 604pin xeons and
> socket 940 Opterons. Socket F Opteron or 771 Xeons does work fine.
>
> I've also testet apci=off pci=routeirq but both does not help. The
> systems work fine with 2.6.19.x and before.
Well that's a bit sad.
Could you please set up netconsole
(Documentation/networking/netconsole.txt) and add initcall_debug to the
kernel boot command line and then send us the full bootup logs?
(Even better: serial console with earlyprintk).
If that doesn't shed any light, we might have to ask you to perform a
git-bisect search to find the buggy commit, I'm afraid.
next prev parent reply other threads:[~2007-03-20 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 20:50 Kernel 2.6.20 does not work anymore with SCSI or SATA on old Opteron / Xeon servers Stefan Priebe
2007-03-20 7:27 ` Andrew Morton [this message]
2007-03-20 10:33 ` Stefan Priebe
2007-03-20 10:54 ` Olaf Kirch
2007-03-20 10:59 ` Stefan Priebe
2007-03-20 11:20 ` Stefan Priebe
2007-03-20 12:23 ` Stefan Priebe
2007-03-20 13:28 ` Stefan Priebe
2007-03-20 16:01 ` Chuck Ebbert
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=20070319232732.854d7120.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stefan@prie.be \
/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