[LITMUS^RT] [NOOB] Cannot boot using "default" compiled kernel
John Gamboa
vaulttech at gmail.com
Wed Aug 15 16:06:01 CEST 2012
Hello,
I was recommended to get the code from the litmus-rt repository, instead of
using the patched kernel (as in [1]). I issued "make bzImage" using the
provided configuration file in [2], just as before, getting a brand new
kernel.
I've downloaded the image from [3] and I'm running the following line
(strongly based in the suggestion given in [3]) to start the virtual
machine:
qemu-system-x86_64 \
-enable-kvm \
-smp 2 \
-hda ../images/ubuntu.backing.qcow2.img \
-m 1024 \
-name "ubuntu-qemu-cjk" \
-nographic \
-kernel ./bzImage \
-append "console=ttyS0,115200 root=/dev/hda1"
( As you can see, I've taken the "-gdb tcp::12345 -net nic -net
user,hostfwd=::2222-:22" out from the end.
I also took the "-cpu host" part: when I tried using it, I've got a panic
in the very beginning. I couldn't find in the documentation what was the
"default" cpu (when not specified), but it went "farther" without that. )
Unfortunately, I'm not able to boot. When trying to boot, I get, at some
point, the following lines:
[...]
[ 4.426853] BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
> [ 4.606310] input: ImExPS/2 Generic Explorer Mouse as
> /devices/platform/i8042/serio1/input/input2
> [ 4.612020] EXT4-fs (hda1): couldn't mount as ext3 due to feature
> incompatibilities
> [ 4.620340] EXT4-fs (hda1): couldn't mount as ext2 due to feature
> incompatibilities
> [ 4.636304] EXT4-fs (hda1): mounted filesystem with ordered data mode.
> Opts: (null)
> [ 4.637116] VFS: Mounted root (ext4 filesystem) readonly on device 3:1.
> [ 4.637116] Freeing unused kernel memory: 520k freed
> udevd[882]: mknod '/dev/fd0' 2:0 060660' failed: Read-only file system
> udevd[880]: mknod '/dev/.tmp-block-3:0' 3:0 060600' failed: Read-only file
> system
> udevd[866]: mknod '/dev/hdc' 22:0 060660' failed: Read-only file system
> udevd[806]: mknod '/dev/input/event0' 13:64 020640' failed: Read-only file
> system
> udevd[869]: mknod '/dev/ttyS1' 4:65 020660' failed: Read-only file system
> udevd[866]: mknod '/dev/ttyS2' 4:66 020660' failed: Read-only file system
> udevd[880]: mknod '/dev/hda' 3:0 060660' failed: Read-only file system
> udevd[870]: mknod '/dev/ttyS3' 4:67 020660' failed: Read-only file system
[...] (many many more lines like this)
I tested the sha256sum of the downloaded image and it was right (the same
as in [3]). I compiled the kernel using gcc 4.4.3 and I am sure that the
file downloaded in [2] is not corrupted/bad in any way. I've compiled the
kernel in two different machines using independently downloaded git
repositories (to assure that the problem wasn't related to any corruption
in my git files tree). I tried to search the "Read-only file system"
message in Google, but it didn't help much.
Since I was able to boot (it gets stuck for around 2min in the lines below,
but it boots) using the kernel compiled using the "patched kernel"
(following the steps in [1]), I feel sure that the problem is not related
to the image (even though I'm seeing these "Read-only file system"
messages).
[ 4.122115] EXT4-fs (hda1): recovery complete
> [ 4.123293] EXT4-fs (hda1): mounted filesystem with ordered data mode.
> Opts: (null)
> [ 4.123977] VFS: Mounted root (ext4 filesystem) readonly on device 3:1.
> [ 4.124929] devtmpfs: mounted
> [ 4.125923] Freeing unused kernel memory: 516k freed
> [ 4.289938] init: ureadahead main process (686) terminated with status 5
> mountall: Disconnected from Plymouth
> fsck from util-linux 2.19.1
> /dev/hda1: clean, 55350/327680 files, 352276/1310208 blocks
I'm running out of ideas. Any help would be very very welcome!
Thanks in advance.
[1]: https://wiki.litmus-rt.org/litmus/InstallationInstructions
[2]: http://www.litmus-rt.org/releases/2012.2/x86_64-config
[3]: https://wiki.litmus-rt.org/litmus/VirtualMachineImages
--
John Gamboa
rabanetescebolas.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20120815/524f2998/attachment.html>
More information about the litmus-dev
mailing list