Mark Knecht wrote:
On 6/27/06, krgn <k.gebbert@xxxxxxxxx> wrote:
hi Mark,
thanks, that was already very helpful, I saw now actually how different
things are from .16 to .17 so luckily I ended up with a newer,
different
error which is now more complicated to show, since I don't reach a
stage
anymore, where I can grab a log or so.
Bascially, when reaching something like this stage here,
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096
bytes)
..........
VFS: Mounted root (ext2 filesystem) readonly.
Time: tsc clocksource has been installed.
the newer kernel tells me something like it can't mount my root
partition and that 'block(0,0)' is unknown. I double checked against my
old config, changed the new one to the old settings and recompiled, but
no joy. I appended the new config so maybe someone who might have a
clue
what this might be, can have a look.
normally, my root partition is mounted like this:
/dev/hda5 on / type ext3 (rw,noatime,user_xattr)
and I also checked again grub settings and the fstab file, but there
was
nothing strange, so must assume its something about the configuration,
or the kernel again (since my old one boots fine with the same grub
settings)
any idea about VFS?
thanks,
KArsten
Hi Karsten,
(Or is it actually KArsten with two capitals? Please excuse my
confusion there. I'd very much like to address you properly. Thanks.)
I don't really have a clue exactly what this problem is but I took a
look around on web using Google. A few things came up:
1) Did you remember to build ext3 support into the kernel? Note how
mine below says it's mounting ext3.
2) It seems that someone might have had an issue like this caused by
ACPI. You could try acpi=off on your boot command line edited in by
hand or added in grub.
When my AMD64 machine boots I see this:
<SNIP>
ACPI wakeup devices:
HUB0 XVR0 XVR1 XVR2 XVR3 USB0 USB2 MMAC MMCI UAR1
ACPI: (supports S0 S1 S3 S4 S5)
Time: tsc clocksource has been installed.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
*****************************************************************************
*
*
* REMINDER, the following debugging options are turned on in your
.config: *
*
*
*
CONFIG_DEBUG_RT_MUTEXES *
*
CONFIG_DEBUG_PREEMPT *
*
*
* they may increase runtime overhead and
latencies. *
*
*
*****************************************************************************
Freeing unused kernel memory: 188k freed
input: AT Translated Set 2 keyboard as /class/input/input0
input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
Adding 2008084k swap on /dev/sda10. Priority:-1 extents:1
across:2008084k
EXT3 FS on sda2, internal journal
[drm] Initialized drm 1.0.1 20051102
<SNIP>
Since there is ACPI stuff immediately before and after it seems
worth looking at.
I suppose you don't have a second Linux box to do the null modem
cable trick where you can capture the boot stuff on a different
machine? Helpful during times like these.
Write back with more info and we can keep trying. At least that's
two ideas for now.
Cheers,
Mark
Hey Mark,
I have tried to boot completely without acpi, with the same result. :(
But, searching the forum took me to this thread:
http://forums.gentoo.org/viewtopic-t-473602-highlight-kernel+panic+syncing+vfs.html
in which the moderator posts:
The meanings are
| Code: |
| unknown block (0,0) |
The kernel
cannot talk to
the drive at all. Its missing the high level disk driver, the low level
disk driver (for the chipset), or the Partition table code.
which is exactly, what I keep getting all the time. So, it must have to
do with EXT-3 driver not being loaded and I had a look when booting the
kernel again: hte ext-3 driver was not loaded at all! Normally, with
the functioning kernel it looks like what you posted. Now, with the
working kernel I also get somehitng strange:
zikkezakke linux-2.6.16-rt23 # dmesg |grep EXT
EXT2-fs warning (device hda5): ext2_fill_super: mounting ext3
filesystem as ext2
EXT3 FS on hda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS on hda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
which does not look really good either, does it? At least, it works,
and for the root partition I don't really need a journalled FS. Anyway,
at the moment my kernel config is that I compile the ext-fs (2&3)
into the kernel, which I didn't for the one I am using now. My plan is
to modularise them and make an initrd, and see if the driver gets
loaded then. Maybe I am on the wrong track though, but its worth a try
:)
greets,
Karsten
ps: KArsten is only a frequent typo I make ;)
|