| 1 |
Andrew Finley wrote: |
| 2 |
> Hi Steve (didn't know if this should go to the list or not), |
| 3 |
> |
| 4 |
> I have had a few crashes with the fallowing kernel error (this is the |
| 5 |
> binary kernel you sent me): |
| 6 |
> |
| 7 |
> [<ffffffffffffff8045d758>]_set_up_early_setup_test+0xfffffeefef0000.... |
| 8 |
> Code: a400000 .... |
| 9 |
> kernel panic - not syncing: Aiee, killing interrupt handler! |
| 10 |
|
| 11 |
I have not seen this even once with my kernel. Perhaps you have a |
| 12 |
really old prom version that is doing something funky, but I just don't |
| 13 |
know. You didn't try to do something funky with objcopy to change the |
| 14 |
address or something did you? |
| 15 |
|
| 16 |
> |
| 17 |
> I noticed some funny things during the boot sequence: |
| 18 |
> |
| 19 |
> 1) |
| 20 |
> *Setting system clock to hardware clock [UTC]... |
| 21 |
> |
| 22 |
> FATAL: Could not load /lib/modules/2.6.10-rc1/modules.dep: No such file |
| 23 |
> or directory |
| 24 |
> |
| 25 |
> *Failed to set system clock to hardware clock |
| 26 |
|
| 27 |
This is a known problem. The O2 rtc has been broken since 2.6.9 |
| 28 |
somehow. I've talked to somebody that said they haven't seen this |
| 29 |
problem at all. I'm wondering if it is a result of a) the gentoo |
| 30 |
toolchain or b) a patch I'm using. |
| 31 |
|
| 32 |
Also, my kernel wasn't compiled with module support at all...in fact, I |
| 33 |
think mine is 2.6.10-rc2. I know why you are getting the error (kernel |
| 34 |
looking to autoload rtc module probably), but I don't know why it is |
| 35 |
looking for the module at all. |
| 36 |
|
| 37 |
> |
| 38 |
> 2) |
| 39 |
> "ERROR: Problem starting needed services. "bootmisc" was not started" |
| 40 |
> |
| 41 |
|
| 42 |
Not sure what the deal is here without more information, but it isn't |
| 43 |
fatal. You probably have some service set up to start which isn't |
| 44 |
installed or is broken. Check your boot logs. |
| 45 |
|
| 46 |
> |
| 47 |
> I tried several other precompiled kernels (for the o2), but none have |
| 48 |
> DEVFS support, which I understand gentoo requires. |
| 49 |
|
| 50 |
Gentoo most certainly doesn't require devfs. Our stages ship with a |
| 51 |
static /dev directory. You can boot with "gentoo=nodevfs" to avoid an |
| 52 |
annoying error about devfs on boot. However, what is even better is |
| 53 |
udev. Just "emerge udev" and boot a 2.6 kernel...and Gentoo's init |
| 54 |
scripts take care of the rest. |
| 55 |
|
| 56 |
> |
| 57 |
> Do you know what the problem might be? If so how might I fix it, short |
| 58 |
> of compiling my own kernel. |
| 59 |
|
| 60 |
You really should learn to build your own kernel anyway. I would |
| 61 |
recommend the latest mips-sources-2.6.9 ebuild instead of being thrown |
| 62 |
into the fire right away with checking cvs out and tracking down the |
| 63 |
right patches. You can't just use the standard kernel.org tarball for |
| 64 |
mips machines really. You should also stop by our irc channel |
| 65 |
(#gentoo-mips, irc.freenode.net) sometime if you haven't already. |
| 66 |
|
| 67 |
> |
| 68 |
> Thanks again for your help. |
| 69 |
> Regards- |
| 70 |
> Andy |
| 71 |
> |
| 72 |
> |
| 73 |
|
| 74 |
|
| 75 |
-- |
| 76 |
gentoo-mips@g.o mailing list |
Archives