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]
Date:	Mon, 31 Mar 2008 14:51:08 +0200
From:	Chr <chunkeey@....de>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7

On Monday 31 March 2008 09:10:34 Andi Kleen wrote:
> Chr <chunkeey@....de> writes:
> > Ever since I went to the new 2.6.25-rcX, I encountered lots of random
> > system freezes after about 2 or 3 hours of uptime... but until now,
> > I couldn't _catch_ them, since the system
> > (AMD Athlon 4200+ X2 (Manchester) / nforce 4 SLI / x86_64) went
> > straight into oblivion (nothing on the serial console or anywhere else,
> > heck I couldn't even hit reset, It didn't POST anymore)
>
> Not POSTing would point to some kind of hardware problem. Normally
> the kernel shouldn't be able to cause that.
Normally yes.. but this is the first time that this ever happend!
(And my system has been stable so far (more than a year now, in fact more like 
2 years)... even with nvidia & madwifi drivers!). 

>
> I would recommend you double check if the problem is really not
> there with an older kernel by going back there and testing.
Well... older kernels won't freeze that way..
I can hit reset whenever I want and it still POSTs.

But, I'll try... maybe I get another change. 
(BTW, if it happends again, is there anything special, that
could help to find the real bugs?)
>
> -Andi
Regards,
	Chr.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ