Re: Problem booting T2000 with own kernel (2.6.39) and included initrd

[Denny Schierz <linuxmail@4lin.net>]

Am 24.02.2012 um 23:31 schrieb Jurij Smakov:

> On Fri, Feb 24, 2012 at 10:38:15PM +0100, Denny Schierz wrote:
>> [   61.144119] Kernel panic - not syncing: Attempted to kill init!
>> [   61.144242] Call Trace:
>> [   61.144294]  [000000000045b8f8] do_exit+0xa8/0x6bc
>> [   61.144344]  [000000000045bf7c] do_group_exit+0x70/0xa8
>> [   61.144405]  [000000000045bfcc] SyS_exit_group+0x18/0x28
>> [   61.144472]  [0000000000405fd4] linux_sparc_syscall32+0x34/0x40
>> [   61.144583] Press Stop-A (L1-A) to return to the boot prom
> 
> Ok, now I actually read the backtrace :-), so I have another theory.
> 
> It appears that your init (or whatever is used in place of init on the 
> initrd) is simply exiting (by doing the exit() syscall, seen in the 
> backtrace)

I have the same problem with a monolith kernel, without any initrd. Worst:

  ┌────────────────────┤ Loading additional components ├────────────────────┐
  │                                                                         │
  │                                   16%                                   │
  │                                                                         │
  │ [  248.791900] Unable to handle kernel paging request at virtual address 000000f203204000
[  248.792085] tsk->{mm,active_mm}->context = 0000000000001686              │
[  248.792187] tsk->{mm,active_mm}->pgd = fffff801fd624000──────────────────┘
[  248.792735] Kernel panic - not syncing: Aiee, killing interrupt handler!
[  248.793200] Press Stop-A (L1-A) to return to the boot prom

that's from the Debian installer :-/

cu denny