All of lore.kernel.org
 help / color / mirror / Atom feed
From: SuD <sud_NOSPAM@latinsud.com>
To: linux-kernel@vger.kernel.org
Cc: hostap@shmoo.com
Subject: Hostap_cs shared irq oops
Date: Sun, 10 Dec 2006 05:42:08 +0100	[thread overview]
Message-ID: <457B9020.1040101@latinsud.com> (raw)

Hi, I recently upgraded to kernel 2.6.18.2 and noticed these problems:
 - I realized that having CONFIG_ISA=y makes it always crash when i 
insert the card (complains about unexpected LVT TMR interrupt). So i 
disabled Isa.
 - Hostap_cs gets a shared Irq (this didn't happen with kernel 
2.6.15.6). It crashes if the interrupt is triggered while the device is 
not fully initialized (Error is: "Divide error 0000 [#1]"). I can 
workaround that by using a flag and inserting a "if (!my_init_flag) { 
return IRQ_HANDLED }" at the begining of the irq handler.

- I don't know much about irq allocation. Can i try something to get my 
separate irq back?
- Should i try different configuration or 2.6.19?
- Should hostap_cs be enhanced to support shared irq?

I use debian etch. Laptop is a G200N 1.7GHz Centrino.

My /proc/interrupts in 2.6.18.2:
           CPU0
  0:     756865          XT-PIC  timer
  1:      11062          XT-PIC  i8042
  2:          0          XT-PIC  cascade
  5:      30453          XT-PIC  uhci_hcd:usb3, eth0
  9:     306542          XT-PIC  acpi
 10:      40192          XT-PIC  ohci1394, yenta, ipw2200, 
ehci_hcd:usb1, uhci_hcd:usb4, Intel 82801DB-ICH4, pcmcia0.0
 11:     167128          XT-PIC  uhci_hcd:usb2, i915@pci:0000:00:02.0
 12:     226854          XT-PIC  i8042
 14:      48281          XT-PIC  ide0
 15:      24932          XT-PIC  ide1

Some acpi boot messages:
PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 1180-11bf claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs *10)
ACPI: PCI Interrupt Link [LNKC] (IRQs *10)
ACPI: PCI Interrupt Link [LNKD] (IRQs 5) *11
ACPI: PCI Interrupt Link [LNKE] (IRQs 10) *11
ACPI: PCI Interrupt Link [LNKF] (IRQs 10) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs *10)
ACPI: Embedded Controller [EC0] (gpe 29) interrupt mode.
ACPI: Power Resource [PFN0] (off)
ACPI: Power Resource [PFN1] (off)

Thanks, please CC me if you can (works both with or without the "_nospam").


             reply	other threads:[~2006-12-10  4:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-10  4:42 SuD [this message]
2006-12-11  5:55 ` Hostap_cs shared irq oops Len Brown

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=457B9020.1040101@latinsud.com \
    --to=sud_nospam@latinsud.com \
    --cc=hostap@shmoo.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.