The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Disabling IRQ #11 - uhci || e100 || r128-dri problem
Date: Sat, 4 Jun 2005 15:31:43 +1000	[thread overview]
Message-ID: <21d7e9970506032231390a9fe6@mail.gmail.com> (raw)
In-Reply-To: <Pine.SOC.4.61.0506021906200.11783@math.ut.ee>

> In recent 2.6.12 prereleases a bug has appeared. Whenever I log out of
> KDE, IRQ 11 is disabled on X server restart (kdm restarts it). It always
> results with the dmesg below and sometimes the new X loses keyboard
> input (ps2 keyboard, usb mouse). USB mouse works well. X works (sans
> keyboard sometimes). Network is dead.

It looks like X or something is causing the r128 to emit an IRQ after
we've stopped listening for them,...

Can you see if you get any info with drm debug on?

echo 1 > /sys/modules/drm/parameters/debug
and restart X...
Dave.

      reply	other threads:[~2005-06-04  5:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 16:15 Disabling IRQ #11 - uhci || e100 || r128-dri problem Meelis Roos
2005-06-04  5:31 ` Dave Airlie [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=21d7e9970506032231390a9fe6@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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