From: Andrew Morton <akpm@osdl.org>
To: Hendrik Visage <hvjunk@gmail.com>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
Ion Badulescu <ionut@badula.org>
Subject: Re: Starfire (Adaptec) kernel 2.6.13+ panics on AMD64 NFS server
Date: Thu, 29 Sep 2005 21:16:49 -0700 [thread overview]
Message-ID: <20050929211649.69eaddee.akpm@osdl.org> (raw)
In-Reply-To: <d93f04c70509292036x269df799y7b51c5be9c3356d6@mail.gmail.com>
Hendrik Visage <hvjunk@gmail.com> wrote:
>
> Traced a panicing kernel to what appears the starfire changes for
> 2.6.13 up to 2.6.14_rc2
>
> During a relative heavy NFS read (client a 32bit 2.6.13.1 P2-350) with
> rsync (ripped CD archive) I get kernel panics (Aieee interupt handler
> lost or something... okay also need
> a way to capture those errors as it's a hard panic and needs a reset button :()
A serial console is useful. Often people will take a digital photo of the
screen, which works OK. But we do need that info somehow, please.
> I've isolated the problem going from 2.6.12.5/2.6.12-gentoo-r10 (both
> working) to
> 2.6.13/2.6.13-gentoo/2.6.14_rc2 while the NFS is served through the
> Adaptec/starfire,
> and further more the onboard forceth(nvidia) is serving the data
> without hassles (at least
> on 2.6.14_rc2)
The starfire changes in 2.6.12->2.6.13 look fairly innocuous. Need that
trace, please.
next prev parent reply other threads:[~2005-09-30 4:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 3:36 Starfire (Adaptec) kernel 2.6.13+ panics on AMD64 NFS server Hendrik Visage
2005-09-30 4:16 ` Andrew Morton [this message]
2005-09-30 8:14 ` Hendrik Visage
2005-09-30 16:46 ` Ion Badulescu
2005-09-30 16:01 ` Hendrik Visage
2005-09-30 17:40 ` Andrew Morton
2005-09-30 20:10 ` Hendrik Visage
2005-09-30 20:55 ` Ion Badulescu
2005-09-30 22:39 ` Herbert Xu
2005-10-01 19:21 ` Hendrik Visage
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=20050929211649.69eaddee.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=hvjunk@gmail.com \
--cc=ionut@badula.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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