public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
* kexec 2.0.4-rc1 won't work on an ARM kernel without device-tree
@ 2012-11-24  9:00 Sven Neumann
  2012-11-28  8:42 ` Sven Neumann
  0 siblings, 1 reply; 2+ messages in thread
From: Sven Neumann @ 2012-11-24  9:00 UTC (permalink / raw)
  To: kexec

Hi,

I am trying to use kexec-2.0.4-rc1 on an ARM device running Linux 3.0.4.
This old kernel does obviously not have device-tree support. Here's the
error message I get:

# uname -a
Linux speaker 3.0.4 #1 PREEMPT Fri Nov 23 09:15:39 CET 2012 armv5tel GNU/Linux

# kexec --append="console=ttyS0,115200 root=ubi0:RootFS rootfstype=ubifs rw ubi.mtd=3" /boot/uImage --force
unrecoverable error: could not scan "/proc/device-tree/": No such file or directory


Looks like the release candidate depends on the very latest kernel
features and won't work on older kernels? Is that intentional?


Regards,
Sven

-- 
Sven Neumann <s.neumann@raumfeld.com>
Raumfeld by Teufel


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: kexec 2.0.4-rc1 won't work on an ARM kernel without device-tree
  2012-11-24  9:00 kexec 2.0.4-rc1 won't work on an ARM kernel without device-tree Sven Neumann
@ 2012-11-28  8:42 ` Sven Neumann
  0 siblings, 0 replies; 2+ messages in thread
From: Sven Neumann @ 2012-11-28  8:42 UTC (permalink / raw)
  To: kexec; +Cc: Matthew Leach

Hi,

On Sat, 2012-11-24 at 10:00 +0100, Sven Neumann wrote:

> I am trying to use kexec-2.0.4-rc1 on an ARM device running Linux 3.0.4.
> This old kernel does obviously not have device-tree support. Here's the
> error message I get:
> 
> # uname -a
> Linux speaker 3.0.4 #1 PREEMPT Fri Nov 23 09:15:39 CET 2012 armv5tel GNU/Linux
> 
> # kexec --append="console=ttyS0,115200 root=ubi0:RootFS rootfstype=ubifs rw ubi.mtd=3" /boot/uImage --force
> unrecoverable error: could not scan "/proc/device-tree/": No such file or directory
> 
> 
> Looks like the release candidate depends on the very latest kernel
> features and won't work on older kernels? Is that intentional?

OK, in the meantime I figured out that I can use kexec-2.0.4-rc1 if I
use the --atags command-line parameter. But unless I missed something,
this change in behavior is nowhere documented and thus should be
considered a severe regression. I am somewhat puzzled that no one here
even cared about my email.

IMO the behavior should be changed so that kexec, if called on ARM
without the --dtb or --atags parameters, checks if the running kernel
provides /proc/device-tree. If it doesn't, then this should not be a
fatal error, but it should assume --atags. That would restore the old
behavior for kernels that don't use device-tree.


Regards,
Sven


-- 
Sven Neumann
Head of RAUMFELD Software Development

Lautsprecher Teufel GmbH
Gewerbehof Bülowbogen - Aufgang D1
Bülowstr. 66 - 10783 Berlin - Germany

Registernummer HRB 20271 beim Amtsgericht Berlin-Charlottenburg
Geschäftsführer: Thomas Stiegler, Edgar van Velzen

Tel. +49 (0)30 - 300 930 - 0, Direkt -153
neumann@teufel.de  

www.teufel.de  www.teufelaudio.com  http://blog.teufel.de


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-11-28  8:42 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-24  9:00 kexec 2.0.4-rc1 won't work on an ARM kernel without device-tree Sven Neumann
2012-11-28  8:42 ` Sven Neumann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox