From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Russell Neches <russell-1vnkWVZi4QaVc3sceRu5cw@public.gmane.org>
Cc: ACPI-Devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: networking half-working after S3 resume
Date: Tue, 17 Aug 2004 11:37:01 +0200 [thread overview]
Message-ID: <20040817093701.GA10109@elf.ucw.cz> (raw)
In-Reply-To: <1092533697.1841.78.camel@localhost>
Hi!
> After an S3 resume, my laptop comes back to life perfectly, with the
> exception of networking. I had originally blamed this on the card
> drivers until I noticed that my wireless card can still get a link. So,
> I tried playing around a bit, and I discovered the following:
>
> * The wireless card correctly detects my AP (SSID, speed, link power, et
> cetera)
>
> * I can see DHCP requests coming from the laptop's wired interface, but
> the responses from my DHCP server are ignored.
>
> * If I manually configure the wired interface on my laptop and attempt
> to ping my desktop, I can see ARP requests coming from the laptop's IP
> looking for my desktop.
>
> * If I run "arp -s <desktop_IP> <desktop_ETHER>" on my laptop to
> manually create an ARP table entry for my desktop, and then attempt to
> ping my desktop, I can see ICMP Echo requests coming from my laptop. My
> desktop acknowledges them, but my laptop still gets 100% packet loss.
>
> * dmesg reports transmit timeouts, despite the fact the the packets are,
> in fact, reaching my switch:
>
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timeout, status 0c 0005 c07f media 10.
> eth0: Tx queue start entry 4 dirty entry 0.
> eth0: Tx descriptor 0 is 0008a03c. (queue head)
> eth0: Tx descriptor 1 is 0008a03c.
> eth0: Tx descriptor 2 is 0008a03c.
> eth0: Tx descriptor 3 is 0008a03c.
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
>
> So, networking is *half* working; I can send packets, I just can't
> receive any (the watchdog warnings notwithstanding). It's affecting two
> different cards, and persists after removing and reloading modules for
> each of them. Both cards seem to retain most basic link layer
> functionality. Could this be a bug higher up in the networking stack?
> (As opposed to a bug in the drivers.) I've never had an issue with any
> kernel networking code above the link layer. Is there a way to prod,
> smack or otherwise reload it?
Looks like your cards are not getting interrupts? Try hooking them on
timer interrupt.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
prev parent reply other threads:[~2004-08-17 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 1:34 networking half-working after S3 resume Russell Neches
2004-08-15 4:30 ` Cameron Patrick
2004-08-17 9:37 ` Pavel Machek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040817093701.GA10109@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=russell-1vnkWVZi4QaVc3sceRu5cw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox