On Fri, 5 Aug 2005, Ingo Molnar wrote:
it's the first oops that matters. You could try to 'freeze' the system
after printing the first stacktrace, via the patch below - but debugging
boot-time crashes without logging support is a quite tedious process.
(maybe, if the crash happens after the
On Fri, 5 Aug 2005, Ingo Molnar wrote:
it's the first oops that matters. You could try to 'freeze' the system
after printing the first stacktrace, via the patch below - but debugging
boot-time crashes without logging support is a quite tedious process.
(maybe, if the crash happens after the
* Chuck Harding <[EMAIL PROTECTED]> wrote:
> couldn't see the beginning of the oops but at the end was
> Init: no more processes left in this run level
> and have to power cycle to be able to boot. I tried vanilla -rc4, -rc5
> and -rc4-mm1 which all worked just fine. But all 3 of the -RT
* Chuck Harding [EMAIL PROTECTED] wrote:
couldn't see the beginning of the oops but at the end was
Init: no more processes left in this run level
and have to power cycle to be able to boot. I tried vanilla -rc4, -rc5
and -rc4-mm1 which all worked just fine. But all 3 of the -RT versions
I
couldn't see the beginning of the oops but at the end was
Init: no more processes left in this run level
and have to power cycle to be able to boot. I tried vanilla -rc4, -rc5
and -rc4-mm1 which all worked just fine. But all 3 of the -RT versions
I have on hand (08,10,13) showed the same symptom.
couldn't see the beginning of the oops but at the end was
Init: no more processes left in this run level
and have to power cycle to be able to boot. I tried vanilla -rc4, -rc5
and -rc4-mm1 which all worked just fine. But all 3 of the -RT versions
I have on hand (08,10,13) showed the same symptom.
6 matches
Mail list logo
