Re: Re: Re: patch for timer.c - two dmesgs

["Uwe Bugla" <uwe.bugla@gmx.de>]

-------- Original-Nachricht --------
Datum: Wed, 12 Jul 2006 20:41:40 +0200 (CEST)
Von: Roman Zippel <zippel@linux-m68k.org>
An: Uwe Bugla <uwe.bugla@gmx.de>
Betreff: Re: Re: patch for timer.c - two dmesgs

> Hi,
> 
> On Wed, 12 Jul 2006, Uwe Bugla wrote:
> 
> > > A lot has changed since then...
> > > Did you try using SysRq+P or Alt+ScrollLock? (A SysRq+T might be
> useful 
> > > too).
> > Sorry for this stupid sounding question:
> > At what point of the boot process do I have to use those keyboard
> combinations please? And what is the output / product of them please?
> 
> Just press them the boot stops and send the kernel log or wite it down if 
> it's not in the log.
> 
> bye, Roman

Thanks, Roman.
To avoid misunderstandings:
I in fact invest more time and energy in testing mm- or other kernels than any comparable user or admin. I in fact tested 3 or 4 different ones somewhere between 2.6.17 and 2.6.18-rc1-mm1, but got exhausted and demotivated as the only output was inability to boot.
I informed Andrew as quick as possible. And I never in my life stumbled over kernels behaving like this. In so far as a consequence I am missing tools or tricks how to produce system output for constructive feedback.
 Question: What difference is there between the output of dmesg when kernel stops out of inconvenience or just out of containing buggy code on the one hand and the output of SysRq+P or Alt+ScrollLock on the other hand?

Regards
Uwe

-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer