Hi!
Thanks to Steven's Kconfig fixes I was able to compile 2.6.15-rc5 with
Ingo's rt2-patch just fine.
I have two small problem with it, however. One is the following Oops during
boot which didn't seem to affect the bootup process, however.
Greetings,
Gunter
Oops: 0000 [#1]
PREEMPT
Modules linked in: eepro100 fuse
CPU: 0
EIP: 0060:[retrigger_next_event+87/480] Not tainted VLI
EFLAGS: 00010082 (2.6.15-rc5-rt2.zb.20051214.1)
EIP is at retrigger_next_event+0x57/0x1e0
eax: c031ebbc ebx: 00000000 ecx: 00000000 edx: c031ebdc
esi: f093713c edi: 00000004 ebp: 0000008c esp: dea49ef8
ds: 007b es: 007b ss: 0068 preempt: 00000003
Process hwclock (pid: 1117, threadinfo=dea48000 task=de481730
stack_left=7876 worst_left=-1)
Stack: dea48000 f093713c 00000004 f092f753 00000004 00000001 dea48000
c031ebc4
c031ebdc c031eb90 c031ebbc 81201eea 0fbecd02 f093713c 00000004
00000086
00fa0000 00000000 dea48000 c0132b4e c0135ff6 7035d1b8 0fbecd07
023c9da0
Call Trace:
[clock_was_set+46/64] clock_was_set+0x2e/0x40 (80)
[do_settimeofday+422/480] do_settimeofday+0x1a6/0x1e0 (4)
[sys_settimeofday+81/192] sys_settimeofday+0x51/0xc0 (72)
[syscall_call+7/11] syscall_call+0x7/0xb (40)
Code: 44 24 1c 8b 6a 08 85 ed 0f 84 96 00 00 00 8b 54 24 28 8b 44 24 28 8b
74 24 04 8b 7c 24 08 83 c2 20 89 54 24 20 8b 48 20 8b 58 24 <8b
> 55 14 8b 45 10 01 ce 11 df 39 fa 7f 4b 7d 3d 89 f6 8d bc 27
<6>note: hwclock[1117] exited with preempt_count 2
BUG: scheduling while atomic: hwclock/0x00000002/1117
caller is do_exit+0x25b/0x480
[__schedule+1292/1680] __schedule+0x50c/0x690 (8)
[do_exit+603/1152] do_exit+0x25b/0x480 (72)
[die+366/368] die+0x16e/0x170 (40)
[do_page_fault+536/1503] do_page_fault+0x218/0x5df (52)
[do_page_fault+0/1503] do_page_fault+0x0/0x5df (60)
[error_code+79/84] error_code+0x4f/0x54 (8)
[check_clock+43/176] check_clock+0x2b/0xb0 (36)
[retrigger_next_event+87/480] retrigger_next_event+0x57/0x1e0 (8)
[clock_was_set+46/64] clock_was_set+0x2e/0x40 (88)
[do_settimeofday+422/480] do_settimeofday+0x1a6/0x1e0 (4)
[sys_settimeofday+81/192] sys_settimeofday+0x51/0xc0 (72)
[syscall_call+7/11] syscall_call+0x7/0xb (40)
[email protected] wrote:
> I have two small problem with it, however. One is the following Oops
> during boot which didn't seem to affect the bootup process, however.
I'm currently not able to reproduce this, so it may be benign.
Greetings,
Gunter