public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Meier <crazy-b-Mmb7MZpHnFY@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	pp-YuCZbdju05vHOG6cAo2yLw@public.gmane.org,
	davem-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: b44 -- Re: No network after S3
Date: Thu, 26 Feb 2004 16:50:23 +0100	[thread overview]
Message-ID: <1077810622.5332.54.camel@homer> (raw)
In-Reply-To: <1077660024.3036.56.camel-D2Zvc0uNKG8@public.gmane.org>


> It would be interesting to know if you can unload the driver before
> going to S3, and then load it after resuming from S3.  ie. can the b44
> hardware survive the S3 transition if it is quiescent?

No, that does not help. The same error message.

> > Kernel is 2.6.3-mm3; I have IO-APIC enabled. cat /proc/interrupts
> > gives
> > me the idea that the network card uses PIC.
> 
> system will be in XT-PIC mode or IO-APIC mode -- can't be both.  I
> assume that /proc/interrupts shows this device receiving no interrupts
> after the S3 resume?

Yeah, /proc/interrupts shows XT-PIC mode.



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

  parent reply	other threads:[~2004-02-26 15:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16  6:10 No network after S3 Brown, Len
     [not found] ` <BF1FE1855350A0479097B3A0D2A80EE0025A6344-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-02-16 11:02   ` Peter.Zeipelt-zqRNUXuvxA0b1SvskN2V4Q
2004-02-16 13:17   ` Thorsten Zachmann
     [not found]     ` <200402161417.42755.t.zachmann-c61pB8mzqkY@public.gmane.org>
2004-02-17  6:53       ` Len Brown
     [not found]         ` <1077000806.2515.46.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-17  7:56           ` Thorsten Zachmann
     [not found]             ` <200402170856.42059.t.zachmann-c61pB8mzqkY@public.gmane.org>
2004-02-24  6:41               ` Thorsten Zachmann
     [not found]                 ` <200402240741.30530.t.zachmann-c61pB8mzqkY@public.gmane.org>
2004-02-24 16:41                   ` Peter Meier
     [not found]                     ` <1077640877.5369.12.camel-0dCjsm2Eg2I@public.gmane.org>
2004-02-24 22:00                       ` b44 -- " Len Brown
     [not found]                         ` <1077660024.3036.56.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-24 22:34                           ` Pekka Pietikainen
     [not found]                             ` <20040224223421.GA6225-YuCZbdju05vHOG6cAo2yLw@public.gmane.org>
2004-02-26 15:48                               ` Peter Meier
2004-02-26 15:50                           ` Peter Meier [this message]
2004-02-17 21:49           ` Peter.Zeipelt-zqRNUXuvxA0b1SvskN2V4Q

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=1077810622.5332.54.camel@homer \
    --to=crazy-b-mmb7mzphnfy@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=davem-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=pp-YuCZbdju05vHOG6cAo2yLw@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