mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Harkes <jaharkes@cs.cmu.edu>
To: Chip Salzenberg <chip@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: hostap interrupt problems, maintainers unresponsive - "wifi0: interrupt delivery does not seem to work"
Date: Fri, 11 Nov 2005 11:11:29 -0500	[thread overview]
Message-ID: <20051111161129.GB31850@delft.aura.cs.cmu.edu> (raw)
In-Reply-To: <20051110175922.GB9632@delft.aura.cs.cmu.edu>

On Thu, Nov 10, 2005 at 12:59:22PM -0500, Jan Harkes wrote:
> I am seeing similar interrupt problems, but I don't have hostap (or even
> a wireless network card) on my machine. For me a clear indication is the
> serial port overrun errors even though that port only gets a handful of
> interrupts per second from an attached GPS receiver. Under X, keyboard
> and mouse are occasionally very jerky and unreponsive.
> 
> I just rebooted with 'acpi=noirq', and I'm not seeing the serial port
> overrun errors anymore, it seems to have fixed, or at least mitigated
> the problem a bit. But I'm logged into the machine remotely at the
> moment, so I can't be sure if it really fixed the unresponsive
> keyboard/mouse issues.

Interestingly, noirq didn't actually help. The main difference seems to
be that DMA is not automatically enabled for my drives with the 2.6.14
kernel, and I'm getting permission denied errors when trying to enable
it with hdparm.

Seems like piix is coming up too late and the ide device is already
claimed by a generic driver that doesn't do dma. I'm building ide/piix
into the kernel now to see if that helps.

Jan

      reply	other threads:[~2005-11-11 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 17:46 Chip Salzenberg
2005-11-06 22:20 ` Jouni Malinen
2005-11-10 17:59 ` Jan Harkes
2005-11-11 16:11   ` Jan Harkes [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=20051111161129.GB31850@delft.aura.cs.cmu.edu \
    --to=jaharkes@cs.cmu.edu \
    --cc=chip@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®