public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at net/ipv4/tcpoutput.c:922 2.6.10-bk7
Date: Sat, 08 Jan 2005 18:41:38 +0400	[thread overview]
Message-ID: <41DFF122.4020604@wasp.net.au> (raw)
In-Reply-To: <41DFEDA8.7030805@wasp.net.au>

Brad Campbell wrote:
> Warning
> This oops is hand transcribed
> 
> This machine is set up for a serial console, but of course one is never 
> there when you actually need it. It would be handy to perhaps loop the 
> oops once every 60 seconds or so, then you could always connect up a 
> serial console when you get home and capture it.
> There was no I  connected at oops time, so no magic-sysrq would work.
> Any interest in such a thing? Perhaps I could have a go at knocking 
> something up.
> 

Forgot to mention, it's a vanilla kernel pulled from BK when -bk7 was current on kernel.org. It also 
has Jeff's libata-dev-2.6 tree pulled in. No other patches.

Regards,
Brad

  reply	other threads:[~2005-01-08 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 14:26 kernel BUG at net/ipv4/tcpoutput.c:922 2.6.10-bk7 Brad Campbell
2005-01-08 14:41 ` Brad Campbell [this message]
2005-01-20 13:16 ` 2.6.10-ac8 - kernel BUG at net/ipv4/tcp_output.c:922! syrius.ml

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=41DFF122.4020604@wasp.net.au \
    --to=brad@wasp.net.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox