From: Jeff Dike <jdike@addtoit.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] kernel BUG at net/ipv4/tcp_output.c:277!
Date: Tue, 11 Jan 2005 13:55:06 -0500 [thread overview]
Message-ID: <200501111855.j0BIt7Wi003586@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Tue, 11 Jan 2005 00:49:13 CST." <063e01c4f7a9$aabaf790$0201a8c0@hawk>
caker@theshore.net said:
> kernel BUG at net/ipv4/tcp_output.c:277!
> Kernel panic - not syncing: BUG!
A bit of googling turns up
http://kerneltrap.org/node/4119
making this look like a generic kernel bug.
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-01-11 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 6:49 [uml-devel] kernel BUG at net/ipv4/tcp_output.c:277! Christopher S. Aker
2005-01-11 18:55 ` Jeff Dike [this message]
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=200501111855.j0BIt7Wi003586@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=caker@theshore.net \
--cc=user-mode-linux-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox