Message-Id: <200902171751.52961.philippe.grenard@laposte.net>
Date:	Tue, 17 Feb 2009 17:51:52 +0100
From:	Philippe Grenard <philippe.grenard@...oste.net>
To:	linux-kernel@...r.kernel.org
Cc:	"John Stoffel" <john@...ffel.org>
Subject: Re: PROBLEM: cannot get stable system since 2.6.28 kernel (amd64)

On Tuesday 17 February 2009 05:46:47 John Stoffel wrote:
> >>>>> "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?
>

hem..... I've tried it the "old way" somehow ;-)

> 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.
Well, for the moment 2.6.28 does not even boot.... so I'll try to install the 
latest 2.6.27.xx and then make the "oldconfig" on 2.6.29-rc5

If you have some kind of "minimalist config file", i'll gladly test that, even 
if it means that I miss some features....(as soon as I can have harddisk, even 
without proper network, system could boot and I may be able to see if that 
config works)
>
> 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.
Yep, understood that : I wont build it anymore for the moment (I was 
optimistic up to now : every new kernel was installed along nvidia module 
without problem ;-) )
>
> 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.
>
For info, my motherboard is an Asus P5Q3 Deluxe, the processor is Core2Duo 
E8400, and harddisk is 250Go Seagate, Graphic card is Nvidia GeForce 9600 GT
I suspect some motherboard feature here... 
I haven't tried to modified my dsdt table for the moment neither .

> John

Thanks for your help,

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