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
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:[email protected]]
> 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: <[email protected]>
>
> 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 [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
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: <[email protected]>
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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
On Sat, 28 Mar 2009 14:50:57 -0700
"Hua Zhong" <[email protected]> wrote:
> Thanks. I knew there was some problem with NAPI but I thought it had
> been fixed.
>
> I'll try the patch on Monday.
>
I've been using 2.6.29 with the patch from:
http://patchwork.kernel.org/patch/14465/
And networking has been restored for me. I haven't tested the other
patch that was mentioned to you, but that can be quickly and easily
found, also on patchwork:
http://patchwork.kernel.org/patch/14804/
--- Mike