Re: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

Re: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

[Ben Hutchings]

[-- Attachment #1: Type: text/plain, Size: 8043 bytes --]

This bug report was made against Debian's package of Linux 2.6.37:

On Tue, 2011-02-22 at 13:08 -0500, Daniel Kahn Gillmor wrote:
> Package: linux-2.6
> Version: 2.6.37-1
> Severity: normal
> 
> I recently switched from 2.6.37-trunk-686 to 2.6.37-1-686.
> 
> after the switch, i find that sometimes my atl2.ko-driven onboard NIC
> persistently claims NO CARRIER after resuming from suspend-to-RAM,
> even when plugged into a legitimate ethernet port.  This is not
> entirely reliable, but maybe 50% of the time.
> 
> if i remove and re-load atl2.ko, the interface can properly detect the
> ethernet.
> 
> i'm happy to help debug this further if there is any information you
> want me to gather on this hardware.  Please let me know.

I don't see any changes to this driver between 2.6.37-rc4 (the first
version we built as '2.6.37-trunk-686') and 2.6.37, so I think Daniel
just had good luck with the earlier versions.

> ** Kernel log:
[...]
> [67880.276036] PM: suspend of devices complete after 147.583 msecs
> [67880.292274] PM: late suspend of devices complete after 16.227 msecs
> [67880.292426] ACPI: Preparing to enter system sleep state S3
> [67880.316648] PM: Saving platform NVS memory
> [67880.357927] Disabling non-boot CPUs ...
> [67880.357927] Back to C!
> [67880.357927] PM: Restoring platform NVS memory
> [67880.357927] Force enabled HPET at resume
> [67880.357927] ACPI: Waking up from system sleep state S3
> [67880.400865] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002)
> [67880.400904] pci 0000:00:1c.0: restoring config space at offset 0x9 (was 0x1fff1, writing 0x3fc13fb1)
> [67880.400913] pci 0000:00:1c.0: restoring config space at offset 0x8 (was 0xfff0, writing 0x3fa03f90)
> [67880.400923] pci 0000:00:1c.0: restoring config space at offset 0x7 (was 0xf0, writing 0x1010)
> [67880.400937] pci 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100104, writing 0x100107)
> [67880.400976] pci 0000:00:1c.1: restoring config space at offset 0x9 (was 0x1fff1, writing 0x3fe13fd1)
> [67880.400987] pci 0000:00:1c.1: restoring config space at offset 0x7 (was 0xf0, writing 0x2020)
> [67880.401001] pci 0000:00:1c.1: restoring config space at offset 0x1 (was 0x100106, writing 0x100107)
> [67880.401042] pci 0000:00:1c.2: restoring config space at offset 0x7 (was 0xf0, writing 0x3030)
> [67880.401056] pci 0000:00:1c.2: restoring config space at offset 0x1 (was 0x100106, writing 0x100107)
> [67880.401099] uhci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
> [67880.401132] uhci_hcd 0000:00:1d.1: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
> [67880.401165] uhci_hcd 0000:00:1d.2: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
> [67880.401197] uhci_hcd 0000:00:1d.3: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
> [67880.401239] ehci_hcd 0000:00:1d.7: restoring config space at offset 0x1 (was 0x2900006, writing 0x2900002)
> [67880.401265] pci 0000:00:1e.0: restoring config space at offset 0xf (was 0x60000, writing 0x600ff)
> [67880.401538] PM: early resume of devices complete after 0.795 msecs
> [67880.406036] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [67880.406048] HDA Intel 0000:00:1b.0: setting latency timer to 64
> [67880.406093] HDA Intel 0000:00:1b.0: irq 40 for MSI/MSI-X
> [67880.406136] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [67880.406143] pci 0000:00:1c.0: setting latency timer to 64
> [67880.406156] pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
> [67880.406163] pci 0000:00:1c.1: setting latency timer to 64
> [67880.406176] pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
> [67880.406183] pci 0000:00:1c.2: setting latency timer to 64
> [67880.406198] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
> [67880.406208] uhci_hcd 0000:00:1d.0: setting latency timer to 64
> [67880.406234] usb usb2: root hub lost power or was reset
> [67880.406253] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
> [67880.406262] uhci_hcd 0000:00:1d.1: setting latency timer to 64
> [67880.406287] usb usb3: root hub lost power or was reset
> [67880.406303] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
> [67880.406313] uhci_hcd 0000:00:1d.2: setting latency timer to 64
> [67880.406337] usb usb4: root hub lost power or was reset
> [67880.406354] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
> [67880.406363] uhci_hcd 0000:00:1d.3: setting latency timer to 64
> [67880.406387] usb usb5: root hub lost power or was reset
> [67880.406405] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
> [67880.406415] ehci_hcd 0000:00:1d.7: setting latency timer to 64
> [67880.406486] pci 0000:00:1e.0: setting latency timer to 64
> [67880.406505] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
> [67880.406513] ata_piix 0000:00:1f.2: setting latency timer to 64
> [67880.406543] atl2 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> [67880.406551] atl2 0000:03:00.0: setting latency timer to 64
> [67880.411177] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [67880.411186] i915 0000:00:02.0: setting latency timer to 64
> [67880.413110] sd 0:0:0:0: [sda] Starting disk
> [67880.652031] usb 1-5: reset high speed USB device using ehci_hcd and address 2
> [67880.896031] usb 1-8: reset high speed USB device using ehci_hcd and address 3
> [67882.532200] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
> [67882.532209] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
> [67882.548191] ata1.00: configured for UDMA/133
> [67882.548697] PM: resume of devices complete after 2147.034 msecs
> [67882.549278] PM: Finishing wakeup.
> [67882.549283] Restarting tasks ... done.
> [67882.549761] video LNXVIDEO:00: Restoring backlight state
> [67882.980083] usb 3-2: new low speed USB device using uhci_hcd and address 5
> [67883.150414] atl2 0000:03:00.0: irq 41 for MSI/MSI-X
> [67883.151364] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [67883.159163] usb 3-2: New USB device found, idVendor=0973, idProduct=0001
> [67883.159174] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [67883.159181] usb 3-2: Product: SchlumbergerSema Cryptoflex e-gate
> [67883.159187] usb 3-2: Manufacturer: SchlumbergerSema

I assume this is where Daniel reloads the driver:

> [67977.344181] atl2 0000:03:00.0: PCI INT A disabled
> [67977.379792] Atheros(R) L2 Ethernet Driver - version 2.2.3
> [67977.379802] Copyright (c) 2007 Atheros Corporation.
> [67977.379870] atl2 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> [67977.379892] atl2 0000:03:00.0: setting latency timer to 64
> [67993.948723] atl2 0000:03:00.0: irq 41 for MSI/MSI-X
> [67993.949268] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [67994.154327] atl2: eth0 NIC Link is Up<100 Mbps Full Duplex>
> [67994.154739] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

[...]
> ** PCI devices:
[...]
> 03:00.0 Ethernet controller [0200]: Atheros Communications L2 Fast Ethernet [1969:2048] (rev a0)
>         Subsystem: ASUSTeK Computer Inc. Device [1043:8233]
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 0, Cache Line Size: 16 bytes
>         Interrupt: pin A routed to IRQ 41
>         Region 0: Memory at fbfc0000 (64-bit, non-prefetchable) [size=256K]
>         Expansion ROM at fbfa0000 [disabled] [size=128K]
>         Capabilities: <access denied>
>         Kernel driver in use: atl2
[...]

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

RE: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

[Xiong Huang]

after the onboard NIC claims NO Carrier after resuming from suspend-to-RAM, how about it if unplug then re-plug the cable ?


best regards
Xiong
-----Original Message-----
From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org] On Behalf Of Ben Hutchings
Sent: Wednesday, February 23, 2011 9:14
To: Jay Cliburn; Chris Snook; Jie Yang
Cc: 614622@bugs.debian.org; netdev; Daniel Kahn Gillmor
Subject: Re: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

This bug report was made against Debian's package of Linux 2.6.37:

On Tue, 2011-02-22 at 13:08 -0500, Daniel Kahn Gillmor wrote:
> Package: linux-2.6
> Version: 2.6.37-1
> Severity: normal
> 
> I recently switched from 2.6.37-trunk-686 to 2.6.37-1-686.
> 
> after the switch, i find that sometimes my atl2.ko-driven onboard NIC 
> persistently claims NO CARRIER after resuming from suspend-to-RAM, 
> even when plugged into a legitimate ethernet port.  This is not 
> entirely reliable, but maybe 50% of the time.
> 
> if i remove and re-load atl2.ko, the interface can properly detect the 
> ethernet.
> 
> i'm happy to help debug this further if there is any information you 
> want me to gather on this hardware.  Please let me know.

I don't see any changes to this driver between 2.6.37-rc4 (the first version we built as '2.6.37-trunk-686') and 2.6.37, so I think Daniel just had good luck with the earlier versions.

> ** Kernel log:
[...]
> [67880.276036] PM: suspend of devices complete after 147.583 msecs 
> [67880.292274] PM: late suspend of devices complete after 16.227 msecs 
> [67880.292426] ACPI: Preparing to enter system sleep state S3 
> [67880.316648] PM: Saving platform NVS memory [67880.357927] Disabling 
> non-boot CPUs ...
> [67880.357927] Back to C!
> [67880.357927] PM: Restoring platform NVS memory [67880.357927] Force 
> enabled HPET at resume [67880.357927] ACPI: Waking up from system 
> sleep state S3 [67880.400865] HDA Intel 0000:00:1b.0: restoring config 
> space at offset 0x1 (was 0x100006, writing 0x100002) [67880.400904] 
> pci 0000:00:1c.0: restoring config space at offset 0x9 (was 0x1fff1, 
> writing 0x3fc13fb1) [67880.400913] pci 0000:00:1c.0: restoring config 
> space at offset 0x8 (was 0xfff0, writing 0x3fa03f90) [67880.400923] 
> pci 0000:00:1c.0: restoring config space at offset 0x7 (was 0xf0, 
> writing 0x1010) [67880.400937] pci 0000:00:1c.0: restoring config 
> space at offset 0x1 (was 0x100104, writing 0x100107) [67880.400976] 
> pci 0000:00:1c.1: restoring config space at offset 0x9 (was 0x1fff1, 
> writing 0x3fe13fd1) [67880.400987] pci 0000:00:1c.1: restoring config 
> space at offset 0x7 (was 0xf0, writing 0x2020) [67880.401001] pci 
> 0000:00:1c.1: restoring config space at offset 0x1 (was 0x100106, 
> writing 0x100107) [67880.401042] pci 0000:00:1c.2: restoring config 
> space at offset 0x7 (was 0xf0, writing 0x3030) [67880.401056] pci 
> 0000:00:1c.2: restoring config space at offset 0x1 (was 0x100106, 
> writing 0x100107) [67880.401099] uhci_hcd 0000:00:1d.0: restoring 
> config space at offset 0x1 (was 0x2800005, writing 0x2800001) 
> [67880.401132] uhci_hcd 0000:00:1d.1: restoring config space at offset 
> 0x1 (was 0x2800005, writing 0x2800001) [67880.401165] uhci_hcd 
> 0000:00:1d.2: restoring config space at offset 0x1 (was 0x2800005, 
> writing 0x2800001) [67880.401197] uhci_hcd 0000:00:1d.3: restoring 
> config space at offset 0x1 (was 0x2800005, writing 0x2800001) 
> [67880.401239] ehci_hcd 0000:00:1d.7: restoring config space at offset 
> 0x1 (was 0x2900006, writing 0x2900002) [67880.401265] pci 
> 0000:00:1e.0: restoring config space at offset 0xf (was 0x60000, 
> writing 0x600ff) [67880.401538] PM: early resume of devices complete 
> after 0.795 msecs [67880.406036] HDA Intel 0000:00:1b.0: PCI INT A -> 
> GSI 16 (level, low) -> IRQ 16 [67880.406048] HDA Intel 0000:00:1b.0: 
> setting latency timer to 64 [67880.406093] HDA Intel 0000:00:1b.0: irq 
> 40 for MSI/MSI-X [67880.406136] pci 0000:00:1c.0: PCI INT A -> GSI 16 
> (level, low) -> IRQ 16 [67880.406143] pci 0000:00:1c.0: setting 
> latency timer to 64 [67880.406156] pci 0000:00:1c.1: PCI INT B -> GSI 
> 17 (level, low) -> IRQ 17 [67880.406163] pci 0000:00:1c.1: setting 
> latency timer to 64 [67880.406176] pci 0000:00:1c.2: PCI INT C -> GSI 
> 18 (level, low) -> IRQ 18 [67880.406183] pci 0000:00:1c.2: setting 
> latency timer to 64 [67880.406198] uhci_hcd 0000:00:1d.0: PCI INT A -> 
> GSI 23 (level, low) -> IRQ 23 [67880.406208] uhci_hcd 0000:00:1d.0: 
> setting latency timer to 64 [67880.406234] usb usb2: root hub lost 
> power or was reset [67880.406253] uhci_hcd 0000:00:1d.1: PCI INT B -> 
> GSI 19 (level, low) -> IRQ 19 [67880.406262] uhci_hcd 0000:00:1d.1: 
> setting latency timer to 64 [67880.406287] usb usb3: root hub lost 
> power or was reset [67880.406303] uhci_hcd 0000:00:1d.2: PCI INT C -> 
> GSI 18 (level, low) -> IRQ 18 [67880.406313] uhci_hcd 0000:00:1d.2: 
> setting latency timer to 64 [67880.406337] usb usb4: root hub lost 
> power or was reset [67880.406354] uhci_hcd 0000:00:1d.3: PCI INT D -> 
> GSI 16 (level, low) -> IRQ 16 [67880.406363] uhci_hcd 0000:00:1d.3: 
> setting latency timer to 64 [67880.406387] usb usb5: root hub lost 
> power or was reset [67880.406405] ehci_hcd 0000:00:1d.7: PCI INT A -> 
> GSI 23 (level, low) -> IRQ 23 [67880.406415] ehci_hcd 0000:00:1d.7: 
> setting latency timer to 64 [67880.406486] pci 0000:00:1e.0: setting 
> latency timer to 64 [67880.406505] ata_piix 0000:00:1f.2: PCI INT B -> 
> GSI 19 (level, low) -> IRQ 19 [67880.406513] ata_piix 0000:00:1f.2: 
> setting latency timer to 64 [67880.406543] atl2 0000:03:00.0: PCI INT 
> A -> GSI 17 (level, low) -> IRQ 17 [67880.406551] atl2 0000:03:00.0: 
> setting latency timer to 64 [67880.411177] i915 0000:00:02.0: PCI INT 
> A -> GSI 16 (level, low) -> IRQ 16 [67880.411186] i915 0000:00:02.0: setting latency timer to 64 [67880.413110] sd 0:0:0:0: [sda] Starting disk [67880.652031] usb 1-5: reset high speed USB device using ehci_hcd and address 2 [67880.896031] usb 1-8: reset high speed USB device using ehci_hcd and address 3 [67882.532200] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out [67882.532209] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out [67882.548191] ata1.00: configured for UDMA/133 [67882.548697] PM: resume of devices complete after 2147.034 msecs [67882.549278] PM: Finishing wakeup.
> [67882.549283] Restarting tasks ... done.
> [67882.549761] video LNXVIDEO:00: Restoring backlight state 
> [67882.980083] usb 3-2: new low speed USB device using uhci_hcd and 
> address 5 [67883.150414] atl2 0000:03:00.0: irq 41 for MSI/MSI-X 
> [67883.151364] ADDRCONF(NETDEV_UP): eth0: link is not ready 
> [67883.159163] usb 3-2: New USB device found, idVendor=0973, 
> idProduct=0001 [67883.159174] usb 3-2: New USB device strings: Mfr=1, 
> Product=2, SerialNumber=0 [67883.159181] usb 3-2: Product: 
> SchlumbergerSema Cryptoflex e-gate [67883.159187] usb 3-2: 
> Manufacturer: SchlumbergerSema

I assume this is where Daniel reloads the driver:

> [67977.344181] atl2 0000:03:00.0: PCI INT A disabled [67977.379792] 
> Atheros(R) L2 Ethernet Driver - version 2.2.3 [67977.379802] Copyright 
> (c) 2007 Atheros Corporation.
> [67977.379870] atl2 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> 
> IRQ 17 [67977.379892] atl2 0000:03:00.0: setting latency timer to 64 
> [67993.948723] atl2 0000:03:00.0: irq 41 for MSI/MSI-X [67993.949268] 
> ADDRCONF(NETDEV_UP): eth0: link is not ready [67994.154327] atl2: eth0 
> NIC Link is Up<100 Mbps Full Duplex> [67994.154739] 
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

[...]
> ** PCI devices:
[...]
> 03:00.0 Ethernet controller [0200]: Atheros Communications L2 Fast Ethernet [1969:2048] (rev a0)
>         Subsystem: ASUSTeK Computer Inc. Device [1043:8233]
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 0, Cache Line Size: 16 bytes
>         Interrupt: pin A routed to IRQ 41
>         Region 0: Memory at fbfc0000 (64-bit, non-prefetchable) [size=256K]
>         Expansion ROM at fbfa0000 [disabled] [size=128K]
>         Capabilities: <access denied>
>         Kernel driver in use: atl2
[...]

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

[Daniel Kahn Gillmor]

[-- Attachment #1: Type: text/plain, Size: 605 bytes --]

Hi Xiong,

On 02/22/2011 08:22 PM, Xiong Huang wrote:
> after the onboard NIC claims NO Carrier after resuming from suspend-to-RAM, how about it if unplug then re-plug the cable ?

i've tried that, and it is not sufficient to remove the NO CARRIER flag
from the output of "ip link".  I've also tried power-cycling the 10/100
miniswitch on the other end of the ethernet cable, but no luck there either.

So far, the only thing i've found that clears the NO CARRIER state is to
remove and re-insert atl2.ko.

I remain open to other suggestions.  And thanks for the speedy followup!

	--dkg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]

RE: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

[Xiong Huang]

Hi Daniel

   What I mean is to check if the cable link (you can check the peer link LED if your onboard NIC haven't) is ON.
If the cable link is ON, we may focus on software layer :)

Thanks
Xiong
-----Original Message-----
From: Daniel Kahn Gillmor [mailto:dkg@fifthhorseman.net] 
Sent: Wednesday, February 23, 2011 9:35
To: Xiong Huang
Cc: Ben Hutchings; Jay Cliburn; Chris Snook; Jie Yang; 614622@bugs.debian.org; netdev
Subject: Re: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

Hi Xiong,

On 02/22/2011 08:22 PM, Xiong Huang wrote:
> after the onboard NIC claims NO Carrier after resuming from suspend-to-RAM, how about it if unplug then re-plug the cable ?

i've tried that, and it is not sufficient to remove the NO CARRIER flag from the output of "ip link".  I've also tried power-cycling the 10/100 miniswitch on the other end of the ethernet cable, but no luck there either.

So far, the only thing i've found that clears the NO CARRIER state is to remove and re-insert atl2.ko.

I remain open to other suggestions.  And thanks for the speedy followup!

	--dkg

Re: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

[Daniel Kahn Gillmor]

[-- Attachment #1: Type: text/plain, Size: 590 bytes --]

Hi Xiong--

On 02/22/2011 08:38 PM, Xiong Huang wrote:
>    What I mean is to check if the cable link (you can check the peer link LED if your onboard NIC haven't) is ON.
> If the cable link is ON, we may focus on software layer :)

the peer (mini-switch) link LED stays off, regardless of unplug/replug
of the cable, power-cycling the mini-switch, or of tweaking the
interface via:

 ip link set eth0 down
 ip link set eth0 up

However, the peer link LED turns on immediately when i do:

 modprobe -v -r atl2
 modprobe -v atl2

hope this is useful info,

	--dkg




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]

Re: Bug#614622: linux-image-2.6.37-1-686: atl2 NIC claims NO CARRIER after suspend/resume; rmmod+insmod fixes the problem

[Daniel Kahn Gillmor]

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

On 02/22/2011 08:14 PM, Ben Hutchings wrote:
> This bug report was made against Debian's package of Linux 2.6.37:
 [...]
> I don't see any changes to this driver between 2.6.37-rc4 (the first
> version we built as '2.6.37-trunk-686') and 2.6.37, so I think Daniel
> just had good luck with the earlier versions.

I was running 2.6.37-1~experimental.1, fwiw, since 2011-01-09.  I don't
think that was based off of rc4, because i was running
2.6.37~rc5-1~experimental.3 before that since 2010-12-16.

so the dates are:

 2010-12-16: start running 2.6.37~rc5-1~experimental.3
 2011-01-09: start running 2.6.37-1~experimental.1
 2011-02-17: start running 2.6.37-1

I run this machine every day, connect it to multiple wired networks, and
have a usage pattern of suspend-to-ram at least twice a day.  I never
saw this problem until i was running 2.6.37-1.

I don't think i was simply lucky with the previous versions.

	--dkg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]