1 |
On Sat, Nov 27, 2010 at 9:17 AM, Mick <michaelkintzios@×××××.com> wrote: |
2 |
> On Saturday 27 November 2010 15:17:43 Mark Knecht wrote: |
3 |
>> On Sat, Nov 27, 2010 at 6:59 AM, Mick <michaelkintzios@×××××.com> wrote: |
4 |
>> > I haven't had much luck with the 2.6.35 version of kernels - they have |
5 |
>> > cause panics on two different x86 boxen. |
6 |
>> > |
7 |
>> > Now that 2.6.35 has gone stable so I tried it again and I'm getting a |
8 |
>> > kernel panic complaining about VFS unable to mount root fs: |
9 |
>> > ================================== |
10 |
>> > VFS: Cannot open root device "sda3" or unknown-block(0,0) |
11 |
>> > Please append a correct "root=" boot option; here are the available |
12 |
>> > partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on |
13 |
>> > unknown-block(0,0) Pid: 1, comm: swapper Not tainted 2.6.35-gentoo-r12 |
14 |
>> > #2 |
15 |
>> > Call Trace: |
16 |
>> > [<c14b3530>] ? panic+0x5f/0xc6 |
17 |
>> > [<c1693c68>] ? mount_block_root+0x1c2/0x245 |
18 |
>> > [<c1002930>] ? do_signal+0x766/0x7f2 |
19 |
>> > [<c1693d31>] ? mount_root+0x46/0x5a |
20 |
>> > [<c1693e8b>] ? prepare_namespace+0x146/0x182 |
21 |
>> > [<c1093203>] ? sys_access+0x1f/0x23 |
22 |
>> > [<c16933f1>] ? kernel_init+0x1a9/0x1b7 |
23 |
>> > [<c1693248>] ? kernel_init+0x0/0x1b7 |
24 |
>> > [<c10030b6>] ? kernel_thread_helper+0x6/0x10 |
25 |
>> > panic occurred, switching back to text console |
26 |
>> > ================================== |
27 |
>> |
28 |
>> <SNIP> |
29 |
>> |
30 |
>> > Am I missing something obvious to make the 2.6.35 series work with my |
31 |
>> > boxen? |
32 |
> |
33 |
>> OK, there's so many possibilities for what causes this. Basic |
34 |
>> confusion ensues... |
35 |
>> |
36 |
>> 1) When booting, if you look carefully, is the initial kernel seeing |
37 |
>> _any_ disks? Sometimes they fly bye and are hard to catch. If it is |
38 |
>> then is it showing sda3? |
39 |
> |
40 |
> The moment the monitor comes on it's already crashed - the first line under |
41 |
> the penguins shows: |
42 |
> |
43 |
> Initializing USB Mass Storage driver... |
44 |
> |
45 |
> so I assume that any probing of drives has already happened. |
46 |
> |
47 |
>> 2) What sort of file system did you put on sda3? I assume this is |
48 |
>> built into the kernel if this is an upgrade? |
49 |
> |
50 |
> reiserfs built into the kernel and unchanged for the last umpteen kernel |
51 |
> series. |
52 |
> |
53 |
>> 3) Post the appropriate part of grub.conf to show how you are booting. |
54 |
> |
55 |
> title=Gentoo Linux 2.6.35-r12 |
56 |
> root (hd0,5) |
57 |
> kernel /kernel-2.6.35-gentoo-r12 root=/dev/sda3 |
58 |
> |
59 |
> The 2.6.34-r12 uses the same stanza except for *.35 being replaced with *.34 |
60 |
> |
61 |
>> 4) Post fstab |
62 |
> |
63 |
> /dev/sda6 /boot ext2 noauto,noatime 1 1 |
64 |
> /dev/sda3 / reiserfs noatime 0 1 |
65 |
> /dev/sda2 none swap sw 0 0 |
66 |
> [snip] |
67 |
> |
68 |
> I'll now build the kernel on the second x86 box and see what happens there. |
69 |
> -- |
70 |
> Regards, |
71 |
> Mick |
72 |
> |
73 |
|
74 |
Yeah, all makes sense what you've done and I can only offer one more |
75 |
thing for you to look at. |
76 |
|
77 |
I skipped from 2.6.33 to 2.6.36 so I cannot say anything specific |
78 |
about the *.35 series, but one thing I've suffered with on my 2.6.36 |
79 |
build is that if I have a specific USB hub hooked up my machine won't |
80 |
complete a boot. I have to disconnect this USB hub prior to boot and |
81 |
then hook it back up after the boot completes. |
82 |
|
83 |
I've not had time to look for the cause so I only hook it up to use |
84 |
it. After boot there are no other problems I've seen. |
85 |
|
86 |
I was assuming that maybe there's some difference in the USB stuff |
87 |
that I hadn't discovered yet, and since you see a crash at a USB step |
88 |
possibly it's similar and I never saw it at *.35 because I never used |
89 |
that series? |
90 |
|
91 |
Good luck and I wish I could be of more help. |
92 |
|
93 |
Cheers, |
94 |
Mark |