linux-kernel - Re: PROBLEM: cannot get stable system since 2.6.28 kernel (amd64)

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, 16 Feb 2009 23:46:47 -0500
From:	"John Stoffel" <john@...ffel.org>
To:	Philippe Grenard <philippe.grenard@...oste.net>
Cc:	linux-kernel@...r.kernel.org, "John Stoffel" <john@...ffel.org>
Subject: Re: PROBLEM: cannot get stable system since 2.6.28 kernel (amd64)

>>>>> "Philippe" == Philippe Grenard <philippe.grenard@...oste.net> writes:

Philippe> well, I don't really believe in hardware problem for two
Philippe> reasons : 1st, nearly all my hardware is quite new ( < 1
Philippe> year old ), which is, I agree, not a solid proof ;-) 2nd,
Philippe> the problem is really repetitive : every time I boot on
Philippe> older kernel, everything works like a charm, every time I
Philippe> boot on the newer kernel, I end up crashing : the "random"
Philippe> part is only the time before crash....

Philippe> I haven't any "overclocking" settings, and every hardware
Philippe> and bios settings are the same : same computer, same
Philippe> harddisk partition, and so on.  2.6.28 will everytime stop
Philippe> after "Booting the kernel".  2.6.29-rc* will boot, but then
Philippe> stalls after a random delay... Except the "/proc/cpuinfo"
Philippe> difference between the two kernels, I don't have a clue....

Philippe> The thing is I can continue using the old kernel, but I
Philippe> thought I better report this since It could hide some
Philippe> regression on amd64 systems ?

It's certainly sounding like a regression, or misconfiguration
somewhere.  Can you start doing a 'git bisect' routine on this to see
if you can find the commit which causes this regression?

It will take around 10 or some recompiles and reboots, but should do
the trick, or at least help narrow things down alot.  Read
Documentation/BUG-HUNTING ofr how to do a bisect run.  

You could also go back and re-build your 2.6.28 kernel and config from
scratch to confirm that it's really working properly.  Then, jump to
2.6.29-rc5 (just released) and do a 'make oldconfig' and see what
you're prompted for.  If it still crashes, send us the original
config, and a diff to the new config (diff -u) so we can look it over.

Also, make sure you're not running *any* binary kernel modules, since
that will make us completely ignore you.  We can't debug issues like
this when nVidia graphics modules are in the system since we can't
tell what that module does to the rest of the kernel and it's not
worth ou time to figure out.

I'm running 2.6.29-rc3 on my AMD64 system and it's been nice and
stable and my hardware too is under a year old.  

John

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