linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 582] New: network device does not survive laptop suspend
Date: Wed, 23 Apr 2003 16:35:22 +0200	[thread overview]
Message-ID: <20030423143521.GA1285@elf.ucw.cz> (raw)
In-Reply-To: <11750000.1050332723@[10.10.2.4]>

Hi!
> http://bugme.osdl.org/show_bug.cgi?id=582
> 
>            Summary: network device does not survive laptop suspend
>     Kernel Version: 2.5.66
>             Status: NEW
>           Severity: high
>              Owner: apmbugs@rothwell.emu.id.au
>          Submitter: devilkin@gmx.net
> 
> 
> Distribution: Debian Unstable
> Hardware Environment: Dell Latitude CPxJ 650
> Software Environment: ?
> Problem Description: 
> 
> I suspended my laptop this morning to move it from home to work without having
> to shhutdown everything. The laptop came nicely out of the suspend, except
> for my Cardbus ethernet device.
> 
> Since i resumed the laptop it hangs around every 10 seconds for around 2
> seconds. Everything hangs, from mouse movement, to audio playback, to
> pinging. This is seen in syslog, in great numbers:

> eth0: Transmitter encountered 16 collisions -- network cable problem?
> eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
>   Flags; bus-master 1, dirty 0(0) current 16(0)
>   Transmit list ffffffff vs. ce6da200.
> eth0: command 0x3002 did not complete! Status=0xffff

ACPI or APM sleep? suspend-to-RAM or disk? I see apmbugs as a owner...

Anyway it is up to someone with affected ethernet card to fix it...

								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]

  reply	other threads:[~2003-04-23 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 15:05 [Bug 582] New: network device does not survive laptop suspend Martin J. Bligh
2003-04-23 14:35 ` Pavel Machek [this message]
2003-05-07  5:23 DevilKin

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=20030423143521.GA1285@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).