| 1 |
Ok, I went back and found what looks like a glaring error. The old |
| 2 |
config had the CONFIG_PHYSICAL_START=0x1000000 under processor |
| 3 |
options, the new one was missing a zero. A ha! sez I and "fixed" it. |
| 4 |
Nope. I get the exact same panic. |
| 5 |
|
| 6 |
Setting CONFIG_EXT2_FS_XATTR=y doesn't help either. |
| 7 |
|
| 8 |
On a related note, I see that CONFIG_NR_CPUS only allows for 8 in the |
| 9 |
30 kernel. Trying any other number leads to an error "Invalid Number" |
| 10 |
, whereas for the 29 kernel, 64 seems to be the default. |
| 11 |
|
| 12 |
|
| 13 |
|
| 14 |
On 10/21/09, Maxim Wexler <maxim.wexler@×××××.com> wrote: |
| 15 |
>> To me, that looks like /dev/sda1 (which is what the kernel is using as |
| 16 |
>> root=) doesn't contain any of the following: |
| 17 |
>> /sbin/init |
| 18 |
>> /etc/init |
| 19 |
>> /bin/init |
| 20 |
>> /bin/sh |
| 21 |
>> |
| 22 |
>> Noting that the kernel output implied that it was an ext2 filesystem, |
| 23 |
>> that looks like it mounted your /boot as /, which fails as there isn't |
| 24 |
>> any init available on it. |
| 25 |
> |
| 26 |
> The partitioning scheme and fs hasn't changed. Just the kernel. It |
| 27 |
> wasn't a problem before. Also, I don't think the fs id is significant |
| 28 |
> since, if you look at the photo attached to the bug report, ext3 is |
| 29 |
> involved in that case. In the new config have CONFIG_EXT2_FS_XATTR is |
| 30 |
> not set, whereas it's set 'y' in the old. Maybe that's it. The |
| 31 |
> <help> page says choose N if unsure, which is what I did this time. |
| 32 |
> I'll wait to hear back from the group and give it another try. |
| 33 |
> |
| 34 |
> mw |
| 35 |
> |
Archives