Le 29.09.2007 10:31, Andrew Morton a écrit :
> On Fri, 28 Sep 2007 21:48:18 +0200 Laurent Riffard <[email protected]> wrote:
>
>> Hi,
>>
>> >From time to time, I experience some complete network hangs:
>>
>> Suddenly, all network connections become unresponsive. Even "ping
>> 127.0.0.1" doesn't work. SysRq-w does not show any blocked processus.
>>
>> When such hang happen, I have to reboot (shutdown does work).
>>
>> This is not easily reproducible: it happens several minutes after
>> boot (could be 45 minutes or 2 hours). I do not use heavy networking
>> apps (like P2P). My typical usage is a Gnome desktop with browser,
>> mailer, IM, video or audio streaming.
>>
>> I have a single PC connected to a DSL router via ethernet (so no LAN
>> with NFS or CIFS).
>>
>> This happens with 2.6.23-rc8-mm2 and 2.6.23-rc6-mm1. I can't remember
>> when I first see this problem. Maybe 2 months ago.
>>
>> I attached the output of "strace ping 127.0.0.1". How can I collect
>> some more data when this problem happens ?
>>
>
> I have a second report of this from Uwe Bugla (who has been banished from
> all vger lists for various naughtinesses).
>
> Similar story - after a few hours his network router (which is using ppp in
> some fashion) craps out and dhcp queries all time out.
>
> I'd be suspecting a ppp bug in net-2.6.24.
mmm... I don't use PPP at all, nor dhcp.
My DSL box act as a NAT-router. Its local adress is 192.168.0.254 and my PC
is at 192.192.0.9 (fixed IP).
/--- telephone line
|
+----------+
| ADSL box |
+----------+
192.168.0.254
|
192.168.0.9
+-----------+
| PC |
+-----------+
Firstly, I suspected a bug in the DSL box, so I reset it but it did not help.
I have to reboot the PC (don't need to reset the DSL box).
Could a router problem prevent "ping 127.0.0.1" from working ?
[this becomes somewhat off-topic for LKML, sorry]
Here's my routing table:
linux-2.6-mm$ LANG=C netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 eth0
It seems it lacks a route for 127.0.0.1 through lo, isn't it? In this case, if
eth0 hangs, 127.0.0.1 hangs too, no?
So, it could be an ethernet driver bug. I'm using ne2k-pci.
--
laurent
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
