linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: linux-acpi@vger.kernel.org
Cc: joliveirinha@gmail.com
Subject: Most interrupts are edge-triggered, non-APIC system
Date: Thu, 01 Jun 2006 22:04:46 +0100	[thread overview]
Message-ID: <447F566E.4060502@gentoo.org> (raw)

Hi,

João Oliveirinha reported a bug related to the sky2 network driver on 
the Gentoo bugzilla. Stephen Hemminger (sky2 author) kindly helped 
diagnose the issues, and he believes that one of the reasons why things 
are running sub-optimally is because the interrupt assigned to sky2 is 
edge-triggered (NAPI requires things to be level-triggered).

The system is a bit odd in that even on the latest BIOS, APIC support is 
apparently completely non-functional (or maybe just non-existent?). Even 
when the "lapic" parameter is used, ACPI appears to be used exclusively 
for interrupt routing.

This is a Toshiba M40-298 laptop.

Here is the interrupts map:

            CPU0
   0:      47094          XT-PIC  timer
   1:        541          XT-PIC  i8042
   2:          0          XT-PIC  cascade
   9:         13          XT-PIC  acpi
  10:       5548          XT-PIC  ehci_hcd:usb1, uhci_hcd:usb2, Intel ICH6
  11:         27          XT-PIC  uhci_hcd:usb3, uhci_hcd:usb4, 
uhci_hcd:usb5, yenta, sdhci:slot0, sdhci:slot1, sdhci:slot2, ohci1394, sky2
  12:        618          XT-PIC  i8042
  14:       7384          XT-PIC  libata
  15:       1275          XT-PIC  libata
NMI:          0
LOC:          0
ERR:          0
MIS:          0

And the ELCR register:
	ACPI: setting ELCR to 0200 (from 0c20)

0200 suggests that IRQ 9 is the only level-triggered interrupt. Also, 
the interrupts are heavily shared, I'm not sure if this is another 
reason for concern...

Anyway, I'm not too familiar with ACPI or interrupt routing, so: do you 
regard it as a bug that so many interrupts are level-triggered?

If so, we can get it filed at the kernel bugzilla if appropriate.

Here is some info that might be useful:

dmesg dump with ACPI debugging enabled:
http://bugs.gentoo.org/attachment.cgi?id=85619&action=view

dmesg with the lapic parameter used at boot:
https://bugs.gentoo.org/attachment.cgi?id=85540&action=view

acpidump:
https://bugs.gentoo.org/attachment.cgi?id=85685&action=view

The actual bug report:
http://bugs.gentoo.org/show_bug.cgi?id=131274

Thanks,
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2006-06-01 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 21:04 Daniel Drake [this message]
2006-06-05 18:43 ` Most interrupts are edge-triggered, non-APIC system Bjorn Helgaas
2006-06-05 19:56   ` Daniel Drake
  -- strict thread matches above, loose matches on Subject: below --
2006-06-06  4:38 Brown, Len

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=447F566E.4060502@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=joliveirinha@gmail.com \
    --cc=linux-acpi@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).