linux-kernel - Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched

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

Message-ID: <4637020A.8070400@gmail.com>
Date:	Tue, 01 May 2007 11:02:02 +0200
From:	Tejun Heo <htejun@...il.com>
To:	"Berck E. Nash" <flyboy@...il.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jeff Garzik <jeff@...zik.org>, linux-ide@...r.kernel.org
Subject: Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()

Hello,

Berck E. Nash wrote:
> Tejun Heo wrote:
> 
>> Hmmm... Once properly initialized, ahci is highly unlikely to cause
>> runaway IRQs which results in nobody cared.  It has proper IRQ mask and
>> pending bits allowing the driver to reliably detect when and why the
>> controller is raising interrupt and disable it if necessary.  Can you
>> try without the NVIDIA module?
> 
> I'm beginning to think it was a one-time hardware error of some sort.
> I've been running 2.6.21-rc7-mm2 for awhile now and the problem hasn't
> reoccurred, so I think you can consider the matter settled...

Hmmmmmmmmmmmm... Please let me know if this thing happens again.

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