linux-kernel - Re: 2.6.39-rc5-git2 boot crashs

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]

Date:	Thu, 05 May 2011 02:46:42 -0400
From:	"werner" <w.landgraf@...ru>
To:	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	tglx@...utronix.de, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.39-rc5-git2 boot crashs

   Just now I compiled 2.6.39-rc6-git1 (including still 
the patchs by hand because not yet included), its also OK, 
good running, without all these problems.  :)

Yes, I continue with my everythingyesconfig, which all the 
time and also now
after this patchs gives good generic kernels for the 
distro, working good on my
server and on the laptops of the neighbours except that 
sometimes
(instead of ELAN) I'll make 486 binaries. And now put the 
package on the mirrors because everything is OK, and I 
dont need to switch on and off the server so that they can 
sync, and the users can use the now working packages of 
2.6.39-rcX ,
which have many new drivers and other good improvements.

Like since years, I continue to compile new versions since 
-rc1 and report problems.
But it was very important that Linus take care of these 
problems now, because
nobody else searched for the reasons. These bugs in logfs 
and in slub.c and percpu.h
probably were processor-type / arch independent, and would 
have given problems
for the most users, so that they could not have been 
ignored.
wl




=======================================================
On Thu, 5 May 2011 08:02:04 +0200
  Ingo Molnar <mingo@...e.hu> wrote:
> 
> * werner <w.landgraf@...ru> wrote:
> 
>> I'll test the patchs with a 486 config, switching off 
>>ELAN.
> 
> I think you can skip all those other test suggestions in 
>this thread - as you 
> confirmed in this email the root cause of your crashes 
>has been found.
> 
> So the best testing you could do would be for you to 
>resume testing whatever 
> original config you were using on your system, and make 
>sure there's really no 
> crashes left - and report any other regressions you 
>might see.
> 
> Thanks,
> 
> 	Ingo
> 
> 

"werner" <w.landgraf@...ru>
---
Professional hosting for everyone - http://www.host.ru
--
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/