From: Andre Noll <maan@systemlinux.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org,
mchan@broadcom.com
Subject: Re: 2.6.21.x kernel panic (tg3 and nfs related)
Date: Wed, 27 Jun 2007 18:12:28 +0200 [thread overview]
Message-ID: <20070627161228.GS22589@skl-net.de> (raw)
In-Reply-To: <4682891A.2070900@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 703 bytes --]
On 11:58, Chuck Ebbert wrote:
> > Screenshots of the resulting kernel panics are available at
> >
> > http://www.systemlinux.org/~maan/shots/huangho-crash-2.6.21.1.png
> > and
> > http://www.systemlinux.org/~maan/shots/huangho-crash-2.6.21.5.png
> >
>
> Looks the the known oops in show_mem(); patch is queued for 2.6.21.6.
I see. Thanks.
> But it is hard to tell when the screen shot doesn't show the whole
> message...
There's no way to scroll up after a kernel panic. I already changed
the video setting to use a smaller font, so if it happens again,
there will be more info visible.
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #3: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: Andre Noll <maan@systemlinux.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: mchan@broadcom.com, linux-kernel@vger.kernel.org,
nfs@lists.sourceforge.net
Subject: Re: 2.6.21.x kernel panic (tg3 and nfs related)
Date: Wed, 27 Jun 2007 18:12:28 +0200 [thread overview]
Message-ID: <20070627161228.GS22589@skl-net.de> (raw)
In-Reply-To: <4682891A.2070900@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
On 11:58, Chuck Ebbert wrote:
> > Screenshots of the resulting kernel panics are available at
> >
> > http://www.systemlinux.org/~maan/shots/huangho-crash-2.6.21.1.png
> > and
> > http://www.systemlinux.org/~maan/shots/huangho-crash-2.6.21.5.png
> >
>
> Looks the the known oops in show_mem(); patch is queued for 2.6.21.6.
I see. Thanks.
> But it is hard to tell when the screen shot doesn't show the whole
> message...
There's no way to scroll up after a kernel panic. I already changed
the video setting to use a smaller font, so if it happens again,
there will be more info visible.
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-27 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 10:16 2.6.21.x kernel panic (tg3 and nfs related) Andre Noll
2007-06-27 10:16 ` Andre Noll
2007-06-27 15:58 ` Chuck Ebbert
2007-06-27 15:58 ` Chuck Ebbert
2007-06-27 16:12 ` Andre Noll [this message]
2007-06-27 16:12 ` Andre Noll
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=20070627161228.GS22589@skl-net.de \
--to=maan@systemlinux.org \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=nfs@lists.sourceforge.net \
/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.