Subject: Re: 2.6.29 network hosed?
From: Kasper Sandberg <lkml@metanurb.dk>
To: Hua Zhong <hzhong@gmail.com>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
In-Reply-To: <01fc01c9afe9$5ecb43b0$1c61cb10$@com>
References: <01fc01c9afe9$5ecb43b0$1c61cb10$@com>
Content-Type: text/plain
Date: Sat, 28 Mar 2009 22:42:59 +0100
Message-Id: <1238276579.6669.126.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1386
Lines: 32

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/

--
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/