public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Null Ack <nullack@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Via Rhine II Looses Eth0 After ACPI
Date: Mon, 23 Jun 2008 14:05:05 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0806231356200.2984@localhost.localdomain> (raw)
In-Reply-To: <40ef7d130806230513w10727e9cybec253c9cfd0c276@mail.gmail.com>


> irq 23: nobody cared (try
> booting with the "irqpoll" option)


Please confirm that booting with "irqpoll", as mentioned in the messages,
works around the problem.

You might find that "noapic" is a better work around.
It will disable the IOAPIC and run in legacy PIC mode.
There may be more interrupt sharing, but most users don't
notice any difference.

If this is an MP system and has MPS, it would be interesting
to boot with "acpi=noirq" and see what MPS does with this
device interrupt.  Though if it is a client system, it will
likely have no MPS and "acpi=noirq" will just put you into
PIC mode like "noapic" did.

If the issue goes away with "acpi=off" or "acpi=noirq",
then please open a sighting here:

http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI

and attach the output from
acpidump
lspci -vv
and for each of the test cases above,
the output from
dmesg -s64000
cat /proc/interrupts

thanks,
-Len

ps. the dmesg in this case is easier to read/compare
with CONFIG_PRINTK_TIME=n


      reply	other threads:[~2008-06-23 18:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 12:13 Via Rhine II Looses Eth0 After ACPI Null Ack
2008-06-23 18:05 ` Len Brown [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=alpine.LFD.1.10.0806231356200.2984@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=nullack@gmail.com \
    /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