From: Chris Wilson <chris@chris-wilson.co.uk>
To: Thomas Gleixner <tglx@linutronix.de>, Dave Airlie <airlied@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: "do_IRQ: 0.89 No irq handler for vector (irq -1)"
Date: Fri, 08 Oct 2010 12:53:23 +0100 [thread overview]
Message-ID: <89k83a$9u8ggv@azsmga001.ch.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1010072329220.3354@localhost6.localdomain6>
On Thu, 7 Oct 2010 23:35:43 +0200 (CEST), Thomas Gleixner <tglx@linutronix.de> wrote:
> The first test worked fine. But after I added some debugging I got
> another weird corruption this time on the first unload:
>
> Oct 7 23:21:24 ionos kernel: Console: switching to colour VGA+ 80x25
> Oct 7 23:21:31 ionos kernel: drm: unregistered panic notifier
> Oct 7 23:21:31 ionos kernel: vga_switcheroo: disabled
> Oct 7 23:21:31 ionos kernel: [drm:drm_mm_takedown] *ERROR* Memory manager not clean. Delaying takedown
>
> That one scares me :)
That was a leak of the object handles which should have been fixed in
.36-rc2
The other horrible crashes look like the set of unload fixes that Daniel
Vetter supplied for .36-rc3 but we postponed to .37.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-10-08 11:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 8:55 "do_IRQ: 0.89 No irq handler for vector (irq -1)" Dave Airlie
2010-10-07 9:05 ` Dave Airlie
2010-10-07 20:38 ` Thomas Gleixner
2010-10-07 21:35 ` Thomas Gleixner
2010-10-08 7:52 ` Thomas Gleixner
2010-10-08 11:46 ` Dave Airlie
2010-10-11 22:48 ` Jesse Barnes
2010-10-11 23:40 ` Jesse Barnes
2010-10-12 19:01 ` Rafael J. Wysocki
2010-10-12 19:49 ` Jesse Barnes
2010-11-16 19:46 ` Florian Mickler
2010-11-16 20:11 ` Jesse Barnes
2010-11-16 20:47 ` Florian Mickler
2010-10-13 21:20 ` Jesse Barnes
2010-10-13 21:48 ` Rafael J. Wysocki
2010-10-08 11:53 ` Chris Wilson [this message]
2010-10-08 12:15 ` Thomas Gleixner
2010-10-08 12:30 ` Chris Wilson
2010-10-10 17:46 ` Maciej Rutecki
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='89k83a$9u8ggv@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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).