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