linux-kernel - Re: Aiee, killing interrupt handler!

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>] [day] [month] [year] [list]

Message-ID: <200612210308_MC3-1-D5D4-3329@compuserve.com>
Date:	Thu, 21 Dec 2006 03:05:24 -0500
From:	Chuck Ebbert <76306.1226@...puserve.com>
To:	Hawk Xu <hxunix@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Aiee, killing interrupt handler!

In-Reply-To: <4587B2C5.9000703@...il.com>

On Tue, 19 Dec 2006 17:37:09 +0800, Hawk Xu wrote:

> > You need to post the entire oops message, not just the last part.  It should
> > start with "BUG". And using a more recent kernel would be a good idea.
> >   
> 
> I'm sorry, but that's all we have now.  Our customer just sent us a 
> photo of the kernel panic screen.

They need to boot in 50-line vga mode then, so more can be seen.

> Our client also sent the /var/log/kernel file to us.  According to the 
> log file, everytime before kernel panic, there are some error messages.  
> The server encountered kernel panic three times, below are the error 
> messages before each time:

Those are normal when running buggy usermode code, but they should
never be able to affect the kernel.

-- 
MBTI: IXTP

-
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/