On Thu, 16 Nov 2006 23:37:18 -0800
[EMAIL PROTECTED] wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=7541
> 
>            Summary: dhcp + suspend-to-RAM sometimes trashes the NIC
>     Kernel Version: 2.6.17.7
>             Status: NEW
>           Severity: normal
>              Owner: [EMAIL PROTECTED]
>          Submitter: [EMAIL PROTECTED]
> 
> 
> Most recent kernel where this bug did *NOT* occur: Sorry, dunno
> Distribution: Debian
> Hardware Environment: Fujitsu P-2040 laptop
> Software Environment: dhcp-client 2.0pl5-19.4 (debian)
> Problem Description:
> 
> I have hit this bug ever since I started using DHCP. Prior to DHCP, I never 
> had
> a problem with suspend to RAM.
> 
> Steps to reproduce:
> 
> My laptop travels from home to work and back. Every time I switch on, I run
> "ifdown eth0" and "ifup eth0" to switch to the appropriate network configured
> using DHCP. Usually, this works fine. Here's my ethernet chipset:
> 
> 00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
> 
> Anyway, sometimes, maybe once a week, something goes wrong and I get this 
> error:
> 
> SIOCSIFFLAGS: No such device
> 
> The NIC still exists, see:
> 
> emit:/home/joshua# ifconfig eth0
> eth0      Link encap:Ethernet  HWaddr 00:E0:00:8C:8B:8E
>           inet addr:192.168.0.4  Bcast:192.168.0.255  Mask:255.255.255.0
>           BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:739959 errors:4 dropped:5 overruns:3 frame:0
>           TX packets:441931 errors:0 dropped:0 overruns:2 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1059867013 (1010.7 MiB)  TX bytes:37902281 (36.1 MiB)
>           Interrupt:9 Base address:0x4800
> 
> However, it's impossible to configure:
> 
> emit:/home/joshua# ifconfig eth0 132.147.1.109 up
> SIOCSIFFLAGS: No such device
> SIOCSIFFLAGS: No such device
> 
> Weird, huh?
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to