From: Simeon Penev <simeon_penev@web.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-laptop@vger.kernel.org
Subject: Re: 2.6.17-1.2174_FC5: : Disabling IRQ #7 / nobody cared / usb_hcd_irq
Date: Wed, 06 Sep 2006 15:56:52 +0200 [thread overview]
Message-ID: <44FED3A4.2010204@web.de> (raw)
In-Reply-To: <44FD8932.60906@tmr.com>
Hi Bill,
thank you for the fast reply!
Bill Davidsen wrote:
> Although IRQ7 is traditionally LP, it seems to get identified for almost
> any unexpected interrupt. I knew why once, but I haven't seen this for
> some time. The real problem is that the kernel disables the IRQ, making
> the system unusable. You can try any of several things:
> - try the last 2.6.16 kernel
> - remove the IRQ disable code, or add a counter. It happens only once on
> many machines,
> as something comes ready.
I'll try that, but actually i wanted to help fix the problem if it's a
bug with the kernel.
> - switch to IRQ poll
Already tried, but kernel panics.
> - disable any CPU speed stuff you have running (just for information)
Yes, i'm using cpufreq, but it's a feature i'm not willing to give away
because the laptop is more silent. The fan works less.
> - try the question on a Fedora list, or report as a bug
Ok, i'll do that.
> - look for newer BIOS formware
Already have the latest.
>
> Yes, that's a shotgun approach, I'm still running 2.6.16.2111 on FC4
> because later kernels don't init the video or wireless correctly.
>
Thank you once again.
Best regards,
simeon
next prev parent reply other threads:[~2006-09-06 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 17:16 2.6.17-1.2174_FC5: : Disabling IRQ #7 / nobody cared / usb_hcd_irq Simeon Penev
2006-09-05 14:26 ` Bill Davidsen
2006-09-06 13:56 ` Simeon Penev [this message]
2006-09-06 15:36 ` Bill Davidsen
2006-09-07 22:22 ` Simeon Penev
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=44FED3A4.2010204@web.de \
--to=simeon_penev@web.de \
--cc=davidsen@tmr.com \
--cc=linux-laptop@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).