linux-kernel - Re: "do_IRQ: 0.89 No irq handler for vector (irq -1)"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <89k83a$9u8ggv@azsmga001.ch.intel.com>
Date:	Fri, 08 Oct 2010 12:53:23 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Dave Airlie <airlied@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: "do_IRQ: 0.89 No irq handler for vector (irq -1)"

On Thu, 7 Oct 2010 23:35:43 +0200 (CEST), Thomas Gleixner <tglx@...utronix.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/