GuixSD kernel panic on linux-libre 3.18.7

GuixSD kernel panic on linux-libre 3.18.7

[Daniel Pimentel]

Hi Guix,

I installed GuixSD on Lenovo X200 Tablet with success (Linux-Libre 
3.18.4), but after upgrade (# guix pull; guix system reconfigure 
/etc/config.scm) there is a kernel panic with kernel higher than 3.18.4 
(last line):
kernel panic - not syncing: Attempted to kill init! exit code=0x00000100

P.S.: With old kernel (Linux-Libre 3.18.4) it's work.

Thanks,

-- 
Daniel Pimentel (d4n1)

Re: GuixSD kernel panic on linux-libre 3.18.7

[Daniel Pimentel]

On 2015-02-26 08:35, Daniel Pimentel wrote:
> Hi Guix,
> 
> I installed GuixSD on Lenovo X200 Tablet with success (Linux-Libre
> 3.18.4), but after upgrade (# guix pull; guix system reconfigure
> /etc/config.scm) there is a kernel panic with kernel higher than
> 3.18.4 (last line):
> kernel panic - not syncing: Attempted to kill init! exit 
> code=0x00000100
> 
> P.S.: With old kernel (Linux-Libre 3.18.4) it's work.
> 
> Thanks,
In other motherboard GuixSD work but if Thinkpad X200 Tablet not.

Sorry for forget put Thinkpad X200 in subject.
-- 
Daniel Pimentel (d4n1)

Re: GuixSD kernel panic on linux-libre 3.18.7

[Adam Pribyl]

On Thu, 26 Feb 2015, Daniel Pimentel wrote:

> Hi Guix,
>
> I installed GuixSD on Lenovo X200 Tablet with success (Linux-Libre 3.18.4), 
> but after upgrade (# guix pull; guix system reconfigure /etc/config.scm) 
> there is a kernel panic with kernel higher than 3.18.4 (last line):
> kernel panic - not syncing: Attempted to kill init! exit code=0x00000100

This may a or may not be related to kernel, the message is too common to 
find what is going on. guix pull and reconfigure is too invasive to say 
this is a kernel fault. It could be the initramfs is not build, root 
device not set properly etc...

> P.S.: With old kernel (Linux-Libre 3.18.4) it's work.
>
> Thanks,
>
> -- 
> Daniel Pimentel (d4n1)

Adam Pribyl

Re: GuixSD kernel panic on linux-libre 3.18.7

[Ludovic Courtès]

Daniel Pimentel <d4n1@openmailbox.org> skribis:

> I installed GuixSD on Lenovo X200 Tablet with success (Linux-Libre
> 3.18.4), but after upgrade (# guix pull; guix system reconfigure
> /etc/config.scm) there is a kernel panic with kernel higher than
> 3.18.4 (last line):
> kernel panic - not syncing: Attempted to kill init! exit code=0x00000100

Could you see if there’s a more meaningful error before that?

Thanks,
Ludo’.

Re: GuixSD kernel panic on linux-libre 3.18.7

[Mark H Weaver]

Daniel Pimentel <d4n1@openmailbox.org> writes:

> I installed GuixSD on Lenovo X200 Tablet with success (Linux-Libre
> 3.18.4), but after upgrade (# guix pull; guix system reconfigure
> /etc/config.scm) there is a kernel panic with kernel higher than
> 3.18.4 (last line):
> kernel panic - not syncing: Attempted to kill init! exit code=0x00000100
>
> P.S.: With old kernel (Linux-Libre 3.18.4) it's work.

You haven't given enough information, but the line above suggests that
the initialization program failed to boot the system.  This can happen
due to problems in your OS configuration.  Is your OS config exactly the
same now as it was when you installed the working system.

Anyway, to debug the problem further, it would be useful to see:

* More of the messages printed before the last line.

* Your OS config, along with any memories you have about what you might
  have changed since it last worked.

      Mark

Re: GuixSD kernel panic on linux-libre 3.18.7

[Daniel Pimentel]

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

On 2015-02-26 15:31, Mark H Weaver wrote:
> Daniel Pimentel <d4n1@openmailbox.org> writes:
> 
>> I installed GuixSD on Lenovo X200 Tablet with success (Linux-Libre
>> 3.18.4), but after upgrade (# guix pull; guix system reconfigure
>> /etc/config.scm) there is a kernel panic with kernel higher than
>> 3.18.4 (last line):
>> kernel panic - not syncing: Attempted to kill init! exit 
>> code=0x00000100
>> 
>> P.S.: With old kernel (Linux-Libre 3.18.4) it's work.
> 
> You haven't given enough information, but the line above suggests that
> the initialization program failed to boot the system.  This can happen
> due to problems in your OS configuration.  Is your OS config exactly 
> the
> same now as it was when you installed the working system.
> 
> Anyway, to debug the problem further, it would be useful to see:
> 
> * More of the messages printed before the last line.
> 
> * Your OS config, along with any memories you have about what you might
>   have changed since it last worked.
> 
>       Mark
Attached a image with kernel panic (maybe I send Log too). Sorry for my 
late.

Thanks,
-- 
Daniel Pimentel (d4n1)

[-- Attachment #2: IMG_20150226_082554.jpg --]
[-- Type: image/jpeg, Size: 341681 bytes --]