From: "Hua Zhong" <hzhong@gmail.com>
To: "'Kasper Sandberg'" <lkml@metanurb.dk>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: RE: 2.6.29 network hosed?
Date: Sat, 28 Mar 2009 14:50:57 -0700 [thread overview]
Message-ID: <020901c9afef$47064e90$d512ebb0$@com> (raw)
In-Reply-To: <1238276579.6669.126.camel@localhost>
Thanks. I knew there was some problem with NAPI but I thought it had been
fixed.
I'll try the patch on Monday.
> -----Original Message-----
> From: Kasper Sandberg [mailto:lkml@metanurb.dk]
> Sent: Saturday, March 28, 2009 2:43 PM
> To: Hua Zhong
> Cc: 'Linux Kernel Mailing List'
> Subject: Re: 2.6.29 network hosed?
>
> Hello.
>
> Yes, this is a common issue with network, please search lkml for a post
> made by david miller, with subject: "Re: Network died completely in
> 2.6.29", Message-Id: <20090327.155346.98210435.davem@davemloft.net>
>
> On Sat, 2009-03-28 at 14:08 -0700, Hua Zhong wrote:
> > I downloaded 2.6.29 and the network seems to be hosed on my desktop.
> Normal
> > ssh is fine, or light use of network. But whenever I run a perforce
> > integration the entire box just becomes completely dead on me. No
> traces,
> > warnings or printks. 100% reproducible. It's a FC4 based system (I
> know,
> > pretty old) for development.
> >
> > I only have an USB keyboard attached and it's not recognized after
> boot, so
> > no sysrq traces. Probably I have to upgrade udev? I can still use the
> > keyboard on the grub boot menu though.
> >
> > If it's a known issue please let me know. I'd be glad to test any
> patches.
> >
> > Hua
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-
> kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2009-03-28 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 21:08 2.6.29 network hosed? Hua Zhong
2009-03-28 21:42 ` Kasper Sandberg
2009-03-28 21:50 ` Hua Zhong [this message]
2009-03-29 1:08 ` Michael B. Trausch
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='020901c9afef$47064e90$d512ebb0$@com' \
--to=hzhong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
/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