All of lore.kernel.org
 help / color / mirror / Atom feed
From: walt <wa1ter@myrealbox.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.1] Kernel panic with ppa driver updates
Date: Fri, 06 Feb 2004 12:45:25 -0800	[thread overview]
Message-ID: <4023FCE5.1020300@myrealbox.com> (raw)
In-Reply-To: <20040206182844.GJ21151@parcelfarce.linux.theplanet.co.uk>

viro@parcelfarce.linux.theplanet.co.uk wrote:
> On Fri, Feb 06, 2004 at 09:36:24AM -0800, walt wrote:
> 
>>This panic started with the bk changesets applied by Linus yesterday.
>>
>>The ppa driver works fine when compiled as a module, but when compiled in
...

> Very interesting.  So it works as a module (== finds disks and handles them
> OK) and dies when it's built-in?

Right.


> Could you post the actual oops? ...

The reason I didn't post it is that it has already scrolled off the top of
my console by the time I can read anything :-(   I can see the hex values
for the registers and hex values for the stack trace, but nothing earlier
than that.  I looked in /var/log/messages but I see that kjournald doesn't
start until well after the oops.

I thought about compiling in support for console on serial-or-parallel
port but I've never been clear on just what to plug into the serial-or-
parallel port after I've done that.  Can you give me a hint how I can
get the whole oops message for you?





  reply	other threads:[~2004-02-06 20:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 17:36 [2.6.1] Kernel panic with ppa driver updates walt
2004-02-06 18:28 ` viro
2004-02-06 20:45   ` walt [this message]
2004-02-07  0:06     ` viro
2004-02-07 23:10   ` walt
2004-02-08  1:12     ` viro
     [not found] <fa.db71fu4.1gju7jo@ifi.uio.no>
     [not found] ` <fa.n1cha2m.1hhep3a@ifi.uio.no>
2004-02-08  3:35   ` walt

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=4023FCE5.1020300@myrealbox.com \
    --to=wa1ter@myrealbox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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.