Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-17 Thread Akkana Peck
Alan Stern writes:
 On Mon, 16 Jul 2007, Akkana Peck wrote:
  But if the bad device doesn't
  have a handler registered, does that mean it might not even show
  up in /proc/interrupts?
 
 That's right.  Or it might have a handler registered for a different 
 IRQ number, a wrong one.

Sure enough. My firewire-free kernel worked fine all yesterday, but
after leaving the laptop suspended overnight, the USB mouse failed,
and dmesg says:

hub 1-0:1.0: suspend error -16
suspend_device(): usb_suspend+0x0/0x20() returns -16
Could not suspend device usb1: error -16
PM: Writing back config space on device :02:00.0 at offset f (was 50a0100, 
writing 50a0109)
PM: Writing back config space on device :02:00.0 at offset 6 (was 0, 
writing 1480)
PM: Writing back config space on device :02:00.0 at offset 5 (was 0, 
writing 1400)
PM: Writing back config space on device :02:00.0 at offset 4 (was 1, 
writing 1401)
PM: Writing back config space on device :02:00.0 at offset 3 (was 0, 
writing 4000)
PM: Writing back config space on device :02:00.0 at offset 1 (was 210, 
writing 217)

and although I'm not getting any nobody cared messages, the behavior
is the same (flaky mouse, and unplugging/replugging doesn't help).

Any tips on finding the source of the extra IRQ9? Or on what option
might have changed since about 2.6.19 to make the kernel more sensitive
to the problem?

...Akkana

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-17 Thread Jesus Jr M Salvo
On 15/07/07, Matthew Dharm [EMAIL PROTECTED] wrote:
 On Sat, Jul 14, 2007 at 10:14:11PM -0700, Akkana Peck wrote:
   On Fri, 13 Jul 2007, Dylan Taft wrote:
Thanks for the reply.
This started happening in 2.6.21 suddenly, which is why I tried
upgrading to 2.6.22.
 
  Alan Stern writes:
   It would be a good idea for you to post this on the Bluetooth
   development list
 
  I don't think it's bluetooth specific. I just started seeing this
  too, and I don't have bluetooth.  I built 2.6.22.1 and tried it; it
  worked for a short time, but then sound and a USB mouse (plugged in
  through an external USB2 hub) both started getting flaky. Turns out
  sound and USB are both on IRQ 9 (as is pcmcia, and I guess the
  pcmcia network card wins).  The machine is a Vaio SR17 laptop.
  Strangely, 2.6.21.3 had been working fine for weeks, even with a hub.
 
  I got a dmesg similar to the one that started this thread (pasted at
  the end of this message).  Booting with irqpoll does fix it, but I'd
  rather not do that: this is an old and slow PIII machine, but it
  worked great with older kernels.  Booting with noapic doesn't help.

 Not long ago, I learned that IRQ 9 is commonly used by ACPI.  I've got
 several machines which won't boot certain kernel versions (and this problem
 seems to come and go as the versions progress).

 Booting with acpi=off makes them all work.  I have no idea why.  You may
 also want to fiddle with any BIOS settings to enable/disable ACPI.

 Matt

 --
 Matthew Dharm  Home: [EMAIL PROTECTED]
 Maintainer, Linux USB Mass Storage Driver


Although the OP was about IRQ 23, the above reply is about IRQ9.
To contribute my own findings ( irq 7 ), which is now solved (
pci=msi,mmconf ) for an x86_64 kernel as mentioned in the end of the
bug report below:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244563

Regards,

John

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-16 Thread Alan Stern
On Sun, 15 Jul 2007, Akkana Peck wrote:

 Alan Stern writes:
  On Sat, 14 Jul 2007, Akkana Peck wrote:
   irq 9: nobody cared (try booting with the irqpoll option)
  ...
   handlers:
   [c02c1e50] (ohci_irq_handler+0x0/0x920)
   [c02d2910] (yenta_interrupt+0x0/0xe0)
   [c02d8ab0] (usb_hcd_irq+0x0/0x60)
   Disabling IRQ #9
  
  You must have a copy of ohci-hcd left over from somewhere.  Perhaps you 
  need to do clean rebuild and re-install.
 
 I did some experiments. I tried a clean rebuild, but while I was
 grepping to make sure I had no OHCI remnants, I noticed that
 CONFIG_IEEE1394_OHCI1394 was still set, so I tested both with
 and without that.
 
 It turns out that was the problem. That ohci_irq_handler message
 apparently isn't referring to USB OHCI after all (I'm fairly sure
 that's never been enabled in this kernel tree -- it's been 4 years
 since I owned a machine that used OHCI). It was referring to
 the Firewire OHCI1394 controller.

Of course.  I should have realized it from the start; a real USB OHCI 
handler would have shown up only as usb_hcd_irq.

 So this probably belongs as a bug report against 1394 and probably
 isn't a USB problem, at least on my machine. And it looks like
 Dylan, the original poster, also has Firewire. I don't use Firewire
 so I'm perfectly happy disabling it, and meanwhile I'll take this to
 the appropriate Firewire list.

Maybe.  The difficulty with trying to solve these nobody cared 
problems is that you can't rely on the list of known interrupt 
handlers.  By definition, nobody cared means some interrupts occurred 
which the handlers all ignored.  Maybe something is wrong with one of 
the handlers, but more likely the interrupts were caused by a 
completely different device -- one without a registered handler on that 
IRQ.

Quite often ACPI ends up being involved, one way or another.  What 
happens if you boot with acpi=off?

Alan Stern


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-16 Thread Akkana Peck
Alan Stern writes:
 Maybe.  The difficulty with trying to solve these nobody cared 
 problems is that you can't rely on the list of known interrupt 
 handlers.  By definition, nobody cared means some interrupts occurred 
 which the handlers all ignored.  Maybe something is wrong with one of 
 the handlers, but more likely the interrupts were caused by a 
 completely different device -- one without a registered handler on that 
 IRQ.

Interesting. I have a lot on IRQ9: /proc/interrupts shows yenta,
uhci_hcd:usb1, YMFPCI, eth0. Those are all working now (the cardbus
eth0 card, the usb hub, and sound). But if the bad device doesn't
have a handler registered, does that mean it might not even show
up in /proc/interrupts?

(Hmm, maybe I spoke too soon. Turns out the cardbus network card
no longer gets configured properly on insert, only at boot. But I
suspect that's an unrelated issue: dmesg does show eject/insert
events, and that means the IRQ is working for yenta, right?)

 Quite often ACPI ends up being involved, one way or another.  What 
 happens if you boot with acpi=off?

It's definitely not ACPI -- I disable that entirely and use APM,
because of bug 8274 where kacpid eats up all available CPU time.

...Akkana

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-16 Thread Alan Stern
On Mon, 16 Jul 2007, Akkana Peck wrote:

 Alan Stern writes:
  Maybe.  The difficulty with trying to solve these nobody cared 
  problems is that you can't rely on the list of known interrupt 
  handlers.  By definition, nobody cared means some interrupts occurred 
  which the handlers all ignored.  Maybe something is wrong with one of 
  the handlers, but more likely the interrupts were caused by a 
  completely different device -- one without a registered handler on that 
  IRQ.
 
 Interesting. I have a lot on IRQ9: /proc/interrupts shows yenta,
 uhci_hcd:usb1, YMFPCI, eth0. Those are all working now (the cardbus
 eth0 card, the usb hub, and sound). But if the bad device doesn't
 have a handler registered, does that mean it might not even show
 up in /proc/interrupts?

That's right.  Or it might have a handler registered for a different 
IRQ number, a wrong one.

 (Hmm, maybe I spoke too soon. Turns out the cardbus network card
 no longer gets configured properly on insert, only at boot. But I
 suspect that's an unrelated issue: dmesg does show eject/insert
 events, and that means the IRQ is working for yenta, right?)

Yes.  But your problem isn't that an IRQ is failing to work; the 
problem is that an IRQ is firing when the kernel thinks it shouldn't 
be.

Alan Stern


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-15 Thread Akkana Peck
Matthew Dharm writes:
 Not long ago, I learned that IRQ 9 is commonly used by ACPI.  [ ... ]
 Booting with acpi=off makes them all work.  I have no idea why.  You may
 also want to fiddle with any BIOS settings to enable/disable ACPI.

Interesting! Though it wouldn't help in this case -- I already 
disable ACPI in my kernel, because otherwise I get kacpid lockups
(kernel bug 8274). But I wonder if IRQ sharing is part of the reason
some machines get a runaway kacpid and others don't?

...Akkana

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-15 Thread Alan Stern
On Sat, 14 Jul 2007, Akkana Peck wrote:

 I just noticed one weirdness, though: it lists ohci_irq_handler as
 one of the handlers. But this machine uses UCHI, not OHCI, and I
 configured my kernel accordingly.  But when I look at .config, I see:
 #
 # USB support
 #
 CONFIG_USB_ARCH_HAS_HCD=y
 CONFIG_USB_ARCH_HAS_OHCI=y
 CONFIG_USB_ARCH_HAS_EHCI=y
 
 and then later I see what I configured,
 #
 # USB Host Controller Drivers
 #
 # CONFIG_USB_EHCI_HCD is not set
 # CONFIG_USB_ISP116X_HCD is not set
 # CONFIG_USB_OHCI_HCD is not set
 CONFIG_USB_UHCI_HCD=y
 # CONFIG_USB_SL811_HCD is not set
 
 What are the USB support ones? I don't see them in menuconfig.

They indicate that your computer can support USB.  Some computers
can't.  For example, you could go out and buy a PCI card with an OHCI
controller; therefore your computer can support OHCI even though it
doesn't have OHCI at the moment.  These options don't appear in
menuconfig because they aren't something you can turn on and off;  
either your computer is capable of supporting USB or it isn't.

 Could that HAS_OHCI be causing the problem?

No.  The ohci-hcd driver won't be built unless CONFIG_USB_OHCI_HCD is 
set.

 Here's the dmesg output:
 
 irq 9: nobody cared (try booting with the irqpoll option)
...
 handlers:
 [c02c1e50] (ohci_irq_handler+0x0/0x920)
 [c02d2910] (yenta_interrupt+0x0/0xe0)
 [c02d8ab0] (usb_hcd_irq+0x0/0x60)
 Disabling IRQ #9

You must have a copy of ohci-hcd left over from somewhere.  Perhaps you 
need to do clean rebuild and re-install.

Alan Stern


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-15 Thread Akkana Peck
Alan Stern writes:
 On Sat, 14 Jul 2007, Akkana Peck wrote:
  irq 9: nobody cared (try booting with the irqpoll option)
 ...
  handlers:
  [c02c1e50] (ohci_irq_handler+0x0/0x920)
  [c02d2910] (yenta_interrupt+0x0/0xe0)
  [c02d8ab0] (usb_hcd_irq+0x0/0x60)
  Disabling IRQ #9
 
 You must have a copy of ohci-hcd left over from somewhere.  Perhaps you 
 need to do clean rebuild and re-install.

I did some experiments. I tried a clean rebuild, but while I was
grepping to make sure I had no OHCI remnants, I noticed that
CONFIG_IEEE1394_OHCI1394 was still set, so I tested both with
and without that.

It turns out that was the problem. That ohci_irq_handler message
apparently isn't referring to USB OHCI after all (I'm fairly sure
that's never been enabled in this kernel tree -- it's been 4 years
since I owned a machine that used OHCI). It was referring to
the Firewire OHCI1394 controller.

So this probably belongs as a bug report against 1394 and probably
isn't a USB problem, at least on my machine. And it looks like
Dylan, the original poster, also has Firewire. I don't use Firewire
so I'm perfectly happy disabling it, and meanwhile I'll take this to
the appropriate Firewire list.

Thanks!

...Akkana

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-14 Thread Akkana Peck
 On Fri, 13 Jul 2007, Dylan Taft wrote:
  Thanks for the reply.
  This started happening in 2.6.21 suddenly, which is why I tried
  upgrading to 2.6.22.

Alan Stern writes:
 It would be a good idea for you to post this on the Bluetooth 
 development list

I don't think it's bluetooth specific. I just started seeing this
too, and I don't have bluetooth.  I built 2.6.22.1 and tried it; it
worked for a short time, but then sound and a USB mouse (plugged in
through an external USB2 hub) both started getting flaky. Turns out
sound and USB are both on IRQ 9 (as is pcmcia, and I guess the
pcmcia network card wins).  The machine is a Vaio SR17 laptop.
Strangely, 2.6.21.3 had been working fine for weeks, even with a hub.

I got a dmesg similar to the one that started this thread (pasted at
the end of this message).  Booting with irqpoll does fix it, but I'd
rather not do that: this is an old and slow PIII machine, but it
worked great with older kernels.  Booting with noapic doesn't help.

It's not a problem with the USB hub hardware -- I've tried two
different hubs.  But sometimes it works if I plug the USB mouse
directly into the machine, no hub.

I found another report of a similar problem:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123617

Is there an alternative to irqpoll? Any idea what might have changed
in 2.6.21 or 2.6.22 to make it required on some machines?

I just noticed one weirdness, though: it lists ohci_irq_handler as
one of the handlers. But this machine uses UCHI, not OHCI, and I
configured my kernel accordingly.  But when I look at .config, I see:
#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y

and then later I see what I configured,
#
# USB Host Controller Drivers
#
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set

What are the USB support ones? I don't see them in menuconfig.
Could that HAS_OHCI be causing the problem?

Here's the dmesg output:

irq 9: nobody cared (try booting with the irqpoll option)
 [c01321a4] __report_bad_irq+0x24/0x90
 [c0132412] note_interrupt+0x202/0x240
 [c0131825] handle_IRQ_event+0x25/0x60
 [c0132d6b] handle_level_irq+0x8b/0xc0
 [c01044cc] do_IRQ+0x3c/0x80
 [c01029eb] common_interrupt+0x23/0x28
 [c01029eb] common_interrupt+0x23/0x28
 [c0117c7d] __do_softirq+0x2d/0x90
 [c0117d06] do_softirq+0x26/0x30
 [c01044d1] do_IRQ+0x41/0x80
 [c01029eb] common_interrupt+0x23/0x28
 [c034007b] snd_card_ymfpci_probe+0x42b/0x740
 [c0219d5d] pci_bus_write_config_byte+0x2d/0x40
 [c0344ff7] pirq_piix_set+0x17/0x20
 [c0344fe0] pirq_piix_set+0x0/0x20
 [c0344d82] pcibios_lookup_irq+0x3b2/0x420
 [c0344e2c] pirq_enable_irq+0x3c/0xc0
 [c0345128] pcibios_enable_device+0x28/0x30
 [c021cc22] do_pci_enable_device+0x22/0x50
 [c021cc77] pci_enable_device_bars+0x27/0x40
 [c0340db3] snd_ymfpci_create+0x23/0x610
 [c034505a] pci_write+0x2a/0x30
 [c033fe3b] snd_card_ymfpci_probe+0x1eb/0x740
 [c018603f] sysfs_make_dirent+0x2f/0x50
 [c021f1b6] pci_device_probe+0x56/0x80
 [c026ed3d] driver_probe_device+0x8d/0x190
 [c026efaa] __driver_attach+0x9a/0xa0
 [c026e12a] bus_for_each_dev+0x3a/0x60
 [c026ebb6] driver_attach+0x16/0x20
 [c026ef10] __driver_attach+0x0/0xa0
 [c026e4fb] bus_add_driver+0x8b/0x1b0
 [c021f349] __pci_register_driver+0x49/0x90
 [c0494740] kernel_init+0x80/0x250
 [c0102726] ret_from_fork+0x6/0x1c
 [c04946c0] kernel_init+0x0/0x250
 [c04946c0] kernel_init+0x0/0x250
 [c0102adb] kernel_thread_helper+0x7/0x1c
 ===
handlers:
[c02c1e50] (ohci_irq_handler+0x0/0x920)
[c02d2910] (yenta_interrupt+0x0/0xe0)
[c02d8ab0] (usb_hcd_irq+0x0/0x60)
Disabling IRQ #9
Clocksource tsc unstable (delta = 72015919 ns)
PCI: Assigned IRQ 9 for device :00:09.0
pccard: CardBus card inserted into slot 0

...Akkana

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-14 Thread Matthew Dharm
On Sat, Jul 14, 2007 at 10:14:11PM -0700, Akkana Peck wrote:
  On Fri, 13 Jul 2007, Dylan Taft wrote:
   Thanks for the reply.
   This started happening in 2.6.21 suddenly, which is why I tried
   upgrading to 2.6.22.
 
 Alan Stern writes:
  It would be a good idea for you to post this on the Bluetooth 
  development list
 
 I don't think it's bluetooth specific. I just started seeing this
 too, and I don't have bluetooth.  I built 2.6.22.1 and tried it; it
 worked for a short time, but then sound and a USB mouse (plugged in
 through an external USB2 hub) both started getting flaky. Turns out
 sound and USB are both on IRQ 9 (as is pcmcia, and I guess the
 pcmcia network card wins).  The machine is a Vaio SR17 laptop.
 Strangely, 2.6.21.3 had been working fine for weeks, even with a hub.
 
 I got a dmesg similar to the one that started this thread (pasted at
 the end of this message).  Booting with irqpoll does fix it, but I'd
 rather not do that: this is an old and slow PIII machine, but it
 worked great with older kernels.  Booting with noapic doesn't help.

Not long ago, I learned that IRQ 9 is commonly used by ACPI.  I've got
several machines which won't boot certain kernel versions (and this problem
seems to come and go as the versions progress).

Booting with acpi=off makes them all work.  I have no idea why.  You may
also want to fiddle with any BIOS settings to enable/disable ACPI.

Matt

-- 
Matthew Dharm  Home: [EMAIL PROTECTED] 
Maintainer, Linux USB Mass Storage Driver

It's not that hard.  No matter what the problem is, tell the customer 
to reinstall Windows.
-- Nurse
User Friendly, 3/22/1998


pgpp8w96BAH1T.pgp
Description: PGP signature
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-13 Thread Alan Stern
On Fri, 13 Jul 2007, Dylan Taft wrote:

 Thanks for the reply.
 This started happening in 2.6.21 suddenly, which is why I tried
 upgrading to 2.6.22.  It seemed to have started happening when my
 bluetooth light mysteriously went on one day.  I went into bios and
 disabled some IO devices earlier today; Wireless USB, my firewire
 port, and the bluetooth adapter.  The bluetooth light went off, and
 this has not happened since.  I think it's safe to say it's not going
 to happen again, since I was getting the IRQ messages every few
 minutes and it's not happening at all now.  I don't have any hardware
 to test of those IO ports were working or not anyway...
 
 Some of the hardware in this laptop behaves strangely, like using the
 madwifi drivers with the Atheros wireless will throw the device into a
 state where it will not be recognized by ndiswrapper or anything until
 I power down and pull the battery or boot Vista and then boot linux.
 That's a known issue with the madwifi drivers and my chipset, I'm
 wondering if something similar happened with the bluetooth
 chipset/drivers.
 
 If anyone needs more info or wants me to try to reproduce the problem
 let me know, but it's working for the moment again.   It looks like
 others have had the same issue.
 http://www.thinkwiki.org/wiki/Installing_Debian_Lenny_on_a_ThinkPad_T61#Problems

It would be a good idea for you to post this on the Bluetooth 
development list, to make those people aware of the possible problem.

Alan Stern


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-13 Thread Dylan Taft
Thanks for the reply.
This started happening in 2.6.21 suddenly, which is why I tried
upgrading to 2.6.22.  It seemed to have started happening when my
bluetooth light mysteriously went on one day.  I went into bios and
disabled some IO devices earlier today; Wireless USB, my firewire
port, and the bluetooth adapter.  The bluetooth light went off, and
this has not happened since.  I think it's safe to say it's not going
to happen again, since I was getting the IRQ messages every few
minutes and it's not happening at all now.  I don't have any hardware
to test of those IO ports were working or not anyway...

Some of the hardware in this laptop behaves strangely, like using the
madwifi drivers with the Atheros wireless will throw the device into a
state where it will not be recognized by ndiswrapper or anything until
I power down and pull the battery or boot Vista and then boot linux.
That's a known issue with the madwifi drivers and my chipset, I'm
wondering if something similar happened with the bluetooth
chipset/drivers.

If anyone needs more info or wants me to try to reproduce the problem
let me know, but it's working for the moment again.   It looks like
others have had the same issue.
http://www.thinkwiki.org/wiki/Installing_Debian_Lenny_on_a_ThinkPad_T61#Problems

Thanks,
Dylan

On 7/12/07, Alan Stern [EMAIL PROTECTED] wrote:
 On Thu, 12 Jul 2007, Dylan Taft wrote:

  Hi all.  I'm using a vanilla linux-2.6.22 kernel.  I just noticed I
  get these messages while my laptop is sitting around doing nothing, 2
  of my USB ports get disabled.   I'm not sure what's causing them, to
  reproduce I just let the laptop sit idle for maybe 5 minutes. rmmod
  uhci_hcd

 Sure you don't mean ehci_hcd?  Acoording to your /proc/interrupts
 listing, it is the driver using IRQ 23.

   and modprobeing it brings it back for a few more minutes but
  the message pops back up.  I'm using a Lenovo T61.  Does anyone have
  any possible suggestions or kernel patches I can try?  Thanks!

 These errors occur because some device is using IRQ 23 but the kernel
 doesn't know it.  Maybe the kernel thinks it is using some other IRQ or
 maybe the kernel doesn't know of the device's existence at all.

 You could compare /proc/interrupts with earlier kernel versions to see
 if anything has changed.

 Sometimes problems in the ACPI drivers can cause this behavior.  You
 can try booting with acpi=noirq.

 Alan Stern



-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


Re: [Linux-usb-users] Problem, irq 23: nobody cared (try booting with the irqpoll option)

2007-07-12 Thread Alan Stern
On Thu, 12 Jul 2007, Dylan Taft wrote:

 Hi all.  I'm using a vanilla linux-2.6.22 kernel.  I just noticed I
 get these messages while my laptop is sitting around doing nothing, 2
 of my USB ports get disabled.   I'm not sure what's causing them, to
 reproduce I just let the laptop sit idle for maybe 5 minutes. rmmod
 uhci_hcd

Sure you don't mean ehci_hcd?  Acoording to your /proc/interrupts 
listing, it is the driver using IRQ 23.

  and modprobeing it brings it back for a few more minutes but
 the message pops back up.  I'm using a Lenovo T61.  Does anyone have
 any possible suggestions or kernel patches I can try?  Thanks!

These errors occur because some device is using IRQ 23 but the kernel 
doesn't know it.  Maybe the kernel thinks it is using some other IRQ or 
maybe the kernel doesn't know of the device's existence at all.

You could compare /proc/interrupts with earlier kernel versions to see 
if anything has changed.

Sometimes problems in the ACPI drivers can cause this behavior.  You 
can try booting with acpi=noirq.

Alan Stern


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users