Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Mark_H_Johnson]

Florian Schmidt <mista.tapas@gmx.net> wrote:

>ok, this new build still hangs at the same spot.

Me too. The serial console output follows at the end. Will try a
few boot alternatives and let you know if I can get this to run.
>From what I can tell, it was attempting to test the NMI watchdog
when it failed.

  --Mark

-----

Linux version 2.6.10-rc2-mm1-RT-V0.7.27-4 (root@dws77) (gcc version 3.3.3
20040412 (Red Hat Linux 3.3.3-7)) #1 SMP Tue Nov 16 09:18:20 CST 2004
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
 BIOS-e820: 000000001fff0000 - 000000001fff8000 (ACPI data)
 BIOS-e820: 000000001fff8000 - 0000000020000000 (ACPI NVS)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
511MB LOWMEM available.
found SMP MP-table at 000fb170
DMI 2.3 present.
Using APIC driver default
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 6:8 APIC version 17
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 6:8 APIC version 17
Using ACPI for processor (LAPIC) configuration information
Intel MultiProcessor Specification v1.1
    Virtual Wire compatibility mode.
OEM ID: VIA      Product ID: VT3075       APIC at: 0xFEE00000
I/O APIC #2 Version 17 at 0xFEC00000.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Processors: 2
Real-Time Preemption Support (c) Ingo Molnar
Built 1 zonelists
Initializing CPU#0
Kernel command line: ro root=LABEL=/ nmi_watchdog=1 single
console=ttyS0,9600n8r profile=2
kernel CPU profiling enabled
kernel profiling shift: 2
PID hash table entries: 2048 (order: 11, 32768 bytes)
Detected 864.206 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 511224k/524224k available (2231k kernel code, 12612k reserved, 658k
data, 232k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Security Framework v1.0.0 initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
CPU0: Intel Pentium III (Coppermine) stepping 06
per-CPU timeslice cutoff: 730.77 usecs.
task migration cache decay timeout: 1 msecs.
Booting processor 1/1 eip 2000
Initializing CPU#1
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel Pentium III (Coppermine) stepping 06
Total of 2 processors activated (3411.96 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 pin1=2 pin2=0
t<

[from a good boot of -V0.7.26-4...]
testing NMI watchdog ... OK.
checking TSC synchronization across 2 CPUs: passed.
IRQ#0 thread RT prio: 49.
spawn_desched_task(00000000)
desched cpu_callback 3/00000000
ksoftirqd started up.
softirq RT prio: 24.
desched cpu_callback 2/00000000
desched thread 0 started up.
desched cpu_callback 3/00000001
desched cpu_callback 2/00000001
ksoftirqd started up.
softirq RT prio: 24.
Brought up 2 CPUs
... and so on ...

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* Mark_H_Johnson@raytheon.com <Mark_H_Johnson@raytheon.com> wrote:

> Florian Schmidt <mista.tapas@gmx.net> wrote:
> 
> >ok, this new build still hangs at the same spot.
> 
> Me too. The serial console output follows at the end. Will try a few
> boot alternatives and let you know if I can get this to run.
> >From what I can tell, it was attempting to test the NMI watchdog
> when it failed.

i've uploaded -5 with a fix in profile_tick() - does it boot fine for
you now?

Btw., a good way to catch such early bootup bugs is to activate
early-printk over the serial console:

 earlyprintk=serial,ttyS0,38400 console=ttyS0,38400 console=tty0

and in this particular case the most effective serial logging method is:

 earlyprintk=serial,ttyS0,38400,keep console=ttyS0,38400 console=tty0

the 'keep' tells the kernel to keep the early console a bit longer -
which in this particular timer-interrupt crash case produces a more
usable log. (the 'keep' parameter makes the serial console a bit less
useful as a regular console later on, so it should only be used for
crashes that the normal early console doesnt catch.)

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[K.R. Foley]

Ingo Molnar wrote:
> * Mark_H_Johnson@raytheon.com <Mark_H_Johnson@raytheon.com> wrote:
> 
> 
>>Florian Schmidt <mista.tapas@gmx.net> wrote:
>>
>>
>>>ok, this new build still hangs at the same spot.
>>
>>Me too. The serial console output follows at the end. Will try a few
>>boot alternatives and let you know if I can get this to run.
>>>From what I can tell, it was attempting to test the NMI watchdog
>>when it failed.
> 
> 
> i've uploaded -5 with a fix in profile_tick() - does it boot fine for
> you now?
> 

This one boots for me now.

kr

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[K.R. Foley]

Ingo Molnar wrote:
> * Mark_H_Johnson@raytheon.com <Mark_H_Johnson@raytheon.com> wrote:
> 
> 
>>Florian Schmidt <mista.tapas@gmx.net> wrote:
>>
>>
>>>ok, this new build still hangs at the same spot.
>>
>>Me too. The serial console output follows at the end. Will try a few
>>boot alternatives and let you know if I can get this to run.
>>>From what I can tell, it was attempting to test the NMI watchdog
>>when it failed.
> 
> 
> i've uploaded -5 with a fix in profile_tick() - does it boot fine for
> you now?
> 

I now have both of my SMP systems booted on -V0.7.27-6 now without any 
problems.

kr

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* K.R. Foley <kr@cybsft.com> wrote:

> >i've uploaded -5 with a fix in profile_tick() - does it boot fine for
> >you now?
> >
> 
> I now have both of my SMP systems booted on -V0.7.27-6 now without any
> problems.

great. The current release is meanwhile at -V0.7.27-10, which includes
other minor updates:

 - two fixes to the wakeup timing code - this should resolve some of the
   weird traces reported by Mark H. Johnson.

 - two minor tweaks to the wakeup/reschedule path which should improve
   wakeup latencies.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 22:24:01 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> great. The current release is meanwhile at -V0.7.27-10, which includes
> other minor updates:
> 

Ok, this one boots fine again for me (didn't test the ones betwen my last
report and this one).

I have not yet tried to get this kernel to lock up yet, but i made another
interesting observation:

irq 8 at prio 98 (only irq 1 with higher prio 99). running rtc_wakeup in the
console (it runs SCHED_FIFO allright). Switching consoles (different text
consoles - not swithcing to X, though this basically produces similar
results) produces large jitters (around 1 ms) and occasional missed irq's
and piggy messages. This is completely reproducable here. The rtc histogram
doesn't show any large wakeup latencies.

/proc/latency_trace doesn't show that high latencies either on console
switch:

preemption latency trace v1.0.7 on 2.6.10-rc2-mm1-RT-V0.7.27-10
-------------------------------------------------------
 latency: 63 us, entries: 22 (22)   |   [VP:0 KP:1 SP:1 HP:1 #CPUS:1]
    -----------------
    | task: IRQ 8/13, uid:0 nice:-5 policy:1 rt_prio:98
    -----------------
 => started at: try_to_wake_up+0x51/0x170 <c010f3a1>
 => ended at:   finish_task_switch+0x51/0xb0 <c010f911>
=======>
    5 80010004 0.000ms (+0.000ms): trace_start_sched_wakeup (try_to_wake_up)
    5 80010003 0.000ms (+0.000ms): (1) ((98))
    5 80010003 0.000ms (+0.000ms): (13) ((5))
    5 80010003 0.000ms (+0.000ms): try_to_wake_up (wake_up_process)
    5 80010003 0.000ms (+0.000ms): (0) ((1))
    5 80010002 0.000ms (+0.000ms): preempt_schedule (try_to_wake_up)
    5 80010002 0.000ms (+0.000ms): wake_up_process (redirect_hardirq)
    5 80010001 0.000ms (+0.000ms): preempt_schedule (__do_IRQ)
    5 80010001 0.000ms (+0.000ms): irq_exit (do_IRQ)
    5 80000002 0.000ms (+0.000ms): do_softirq (irq_exit)
    5 80000002 0.001ms (+0.061ms): __do_softirq (do_softirq)
    5 00000000 0.062ms (+0.000ms): preempt_schedule (_mmx_memcpy)
    5 90000000 0.062ms (+0.000ms): __schedule (preempt_schedule)
    5 90000000 0.062ms (+0.000ms): profile_hit (__schedule)
    5 90000001 0.062ms (+0.000ms): sched_clock (__schedule)
   13 80000002 0.062ms (+0.000ms): __switch_to (__schedule)
   13 80000002 0.062ms (+0.000ms): (5) ((13))
   13 80000002 0.062ms (+0.000ms): (98) ((1))
   13 80000002 0.062ms (+0.000ms): finish_task_switch (__schedule)
   13 80000001 0.062ms (+0.000ms): trace_stop_sched_switched (finish_task_switch)
   13 80000001 0.063ms (+0.003ms): (13) ((1))
   13 80000001 0.066ms (+0.000ms): trace_stop_sched_switched (finish_task_switch)

I sometimes do get large values in /proc/latency_trace, but they seem to be
unrelated to the console switching.

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 22:20:39 +0100
Florian Schmidt <mista.tapas@gmx.net> wrote:

> /proc/latency_trace doesn't show that high latencies either on console
> switch:
> 

correction: now i do see large wakeup latencies in /proc/latency_trace, but
only when rtc_wakeup is not running [??? :)]. something's fishy..

(IRQ 1/18/CPU#0): new 2 us maximum-latency wakeup.
(IRQ 1/18/CPU#0): new 3 us maximum-latency wakeup.
(syslogd/302/CPU#0): new 4 us maximum-latency wakeup.
(ksoftirqd/0/3/CPU#0): new 4 us maximum-latency wakeup.
(ksoftirqd/0/3/CPU#0): new 5 us maximum-latency wakeup.
(IRQ 0/2/CPU#0): new 857 us maximum-latency wakeup.
(IRQ 0/2/CPU#0): new 891 us maximum-latency wakeup.
(IRQ 0/2/CPU#0): new 976 us maximum-latency wakeup.
(IRQ 0/2/CPU#0): new 1117 us maximum-latency wakeup.

It seems this excerpt from below trace is characteristic for all the long
traces:

   5 80000002 0.001ms (+1.114ms): __do_softirq (do_softirq)
   5 00000000 1.115ms (+0.000ms): preempt_schedule (_mmx_memcpy)

preemption latency trace v1.0.7 on 2.6.10-rc2-mm1-RT-V0.7.27-10
-------------------------------------------------------
 latency: 1117 us, entries: 22 (22)   |   [VP:0 KP:1 SP:1 HP:1 #CPUS:1]
    -----------------
    | task: IRQ 0/2, uid:0 nice:0 policy:1 rt_prio:50
    -----------------
 => started at: try_to_wake_up+0x51/0x170 <c010f3a1>
 => ended at:   finish_task_switch+0x51/0xb0 <c010f911>
=======>
    5 80010004 0.000ms (+0.000ms): trace_start_sched_wakeup (try_to_wake_up)
    5 80010003 0.000ms (+0.000ms): (49) ((98))
    5 80010003 0.000ms (+0.000ms): (2) ((5))
    5 80010003 0.000ms (+0.000ms): try_to_wake_up (wake_up_process)
    5 80010003 0.000ms (+0.000ms): (0) ((1))
    5 80010002 0.000ms (+0.000ms): preempt_schedule (try_to_wake_up)
    5 80010002 0.000ms (+0.000ms): wake_up_process (redirect_hardirq)
    5 80010001 0.000ms (+0.000ms): preempt_schedule (__do_IRQ)
    5 80010001 0.000ms (+0.000ms): irq_exit (do_IRQ)
    5 80000002 0.000ms (+0.000ms): do_softirq (irq_exit)
    5 80000002 0.001ms (+1.114ms): __do_softirq (do_softirq)
    5 00000000 1.115ms (+0.000ms): preempt_schedule (_mmx_memcpy)
    5 90000000 1.115ms (+0.000ms): __schedule (preempt_schedule)
    5 90000000 1.115ms (+0.000ms): profile_hit (__schedule)
    5 90000001 1.116ms (+0.000ms): sched_clock (__schedule)
    2 80000002 1.116ms (+0.000ms): __switch_to (__schedule)
    2 80000002 1.116ms (+0.000ms): (5) ((2))
    2 80000002 1.116ms (+0.000ms): (98) ((49))
    2 80000002 1.116ms (+0.000ms): finish_task_switch (__schedule)
    2 80000001 1.116ms (+0.000ms): trace_stop_sched_switched (finish_task_switch)
    2 80000001 1.116ms (+0.003ms): (2) ((49))
    2 80000001 1.120ms (+0.000ms): trace_stop_sched_switched (finish_task_switch)

Ah, and one more thing: When i boot up the computer my init script sets irq
3 to prio 98. But it seems the irq handler's priority changes actually when
the soundcard is used the first time. So i need to re-set the irq prio
_after_ i have  used the soundcard for the first time..

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* Florian Schmidt <mista.tapas@gmx.net> wrote:

> It seems this excerpt from below trace is characteristic for all the long
> traces:
> 
>    5 80000002 0.001ms (+1.114ms): __do_softirq (do_softirq)
>    5 00000000 1.115ms (+0.000ms): preempt_schedule (_mmx_memcpy)

i've seen this before, it's still unsolved. This trace shows it nicely:

>     5 80010002 0.000ms (+0.000ms): wake_up_process (redirect_hardirq)
>     5 80010001 0.000ms (+0.000ms): preempt_schedule (__do_IRQ)
>     5 80010001 0.000ms (+0.000ms): irq_exit (do_IRQ)
>     5 80000002 0.000ms (+0.000ms): do_softirq (irq_exit)
>     5 80000002 0.001ms (+1.114ms): __do_softirq (do_softirq)
>     5 00000000 1.115ms (+0.000ms): preempt_schedule (_mmx_memcpy)
>     5 90000000 1.115ms (+0.000ms): __schedule (preempt_schedule)
>     5 90000000 1.115ms (+0.000ms): profile_hit (__schedule)

this is either a false positive, or we missed a preemption. To see which
one, could you apply the attached patch and try to reproduce this long
trace? The new trace will tell us whether need_resched is set during
that ~1 msec window.

	Ingo

--- linux/kernel/latency.c.orig
+++ linux/kernel/latency.c
@@ -184,6 +184,7 @@ ____trace(struct cpu_trace *tr, unsigned
 		 * Encode irqs-off into the preempt count:
 		 */
 			 + (irqs_disabled() ? 0x80000000 : 0)
+			 + (need_resched() ?  0x08000000 : 0)
 #endif
 				;
 	}

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 23:42:57 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> this is either a false positive, or we missed a preemption. To see which
> one, could you apply the attached patch and try to reproduce this long
> trace? The new trace will tell us whether need_resched is set during
> that ~1 msec window.

hmm, the output doens't look so much different (or am i just blind?). maybe
i need to do make clean before building with this patch applied?

flo


preemption latency trace v1.0.7 on 2.6.10-rc2-mm1-RT-V0.7.27-10
-------------------------------------------------------
 latency: 992 us, entries: 22 (22)   |   [VP:0 KP:1 SP:1 HP:1 #CPUS:1]
    -----------------
    | task: IRQ 0/2, uid:0 nice:0 policy:1 rt_prio:49
    -----------------
 => started at: try_to_wake_up+0x51/0x170 <c010f3a1>
 => ended at:   finish_task_switch+0x51/0xb0 <c010f911>
=======>
    5 80010004 0.000ms (+0.000ms): trace_start_sched_wakeup (try_to_wake_up)
    5 88010003 0.000ms (+0.000ms): (50) ((98))
    5 88010003 0.000ms (+0.000ms): (2) ((5))
    5 88010003 0.000ms (+0.000ms): try_to_wake_up (wake_up_process)
    5 88010003 0.000ms (+0.000ms): (0) ((1))
    5 88010002 0.000ms (+0.000ms): preempt_schedule (try_to_wake_up)
    5 88010002 0.000ms (+0.000ms): wake_up_process (redirect_hardirq)
    5 88010001 0.000ms (+0.000ms): preempt_schedule (__do_IRQ)
    5 88010001 0.000ms (+0.000ms): irq_exit (do_IRQ)
    5 88000002 0.000ms (+0.000ms): do_softirq (irq_exit)
    5 88000002 0.001ms (+0.990ms): __do_softirq (do_softirq)
    5 08000000 0.991ms (+0.000ms): preempt_schedule (_mmx_memcpy)
    5 98000000 0.991ms (+0.000ms): __schedule (preempt_schedule)
    5 98000000 0.991ms (+0.000ms): profile_hit (__schedule)
    5 98000001 0.991ms (+0.000ms): sched_clock (__schedule)
    2 80000002 0.991ms (+0.000ms): __switch_to (__schedule)
    2 80000002 0.991ms (+0.000ms): (5) ((2))
    2 80000002 0.992ms (+0.000ms): (98) ((50))
    2 80000002 0.992ms (+0.000ms): finish_task_switch (__schedule)
    2 80000001 0.992ms (+0.000ms): trace_stop_sched_switched (finish_task_switch)
    2 80000001 0.992ms (+0.001ms): (2) ((50))
    2 80000001 0.993ms (+0.000ms): trace_stop_sched_switched (finish_task_switch)

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* Florian Schmidt <mista.tapas@gmx.net> wrote:

> hmm, the output doens't look so much different (or am i just blind?).
> maybe i need to do make clean before building with this patch applied?

the trace is fine, note the extra 0x08000000:

>     5 88010003 0.000ms (+0.000ms): try_to_wake_up (wake_up_process)
>     5 88010003 0.000ms (+0.000ms): (0) ((1))
>     5 88010002 0.000ms (+0.000ms): preempt_schedule (try_to_wake_up)
>     5 88010002 0.000ms (+0.000ms): wake_up_process (redirect_hardirq)
         ^--- this one
>     5 88010001 0.000ms (+0.000ms): preempt_schedule (__do_IRQ)
>     5 88010001 0.000ms (+0.000ms): irq_exit (do_IRQ)
>     5 88000002 0.000ms (+0.000ms): do_softirq (irq_exit)
>     5 88000002 0.001ms (+0.990ms): __do_softirq (do_softirq)
>     5 08000000 0.991ms (+0.000ms): preempt_schedule (_mmx_memcpy)
>     5 98000000 0.991ms (+0.000ms): __schedule (preempt_schedule)

it was zero before - indeed hard to notice optically :-|

found the reason for this latency meanwhile: it's kernel_fpu_begin() and
kernel_fpu_end() disabling/enabling preemption. (these are used by the
mmx memcpy's)

i've uploaded the -11 patch with a preliminary fix:

    http://redhat.com/~mingo/realtime-preempt/

which turns off the FPU-based ops if PREEMPT_RT is specified. The speed
difference should be small but the latency difference is large ...

could you try -11, do you still see these large latencies?

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Wed, 17 Nov 2004 00:11:45 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> >     5 88010002 0.000ms (+0.000ms): wake_up_process (redirect_hardirq)
>          ^--- this one
> 
> it was zero before - indeed hard to notice optically :-|

nah, i just didn't know what to look for :)

> i've uploaded the -11 patch with a preliminary fix:
> 
> which turns off the FPU-based ops if PREEMPT_RT is specified. The speed
> difference should be small but the latency difference is large ...
> 
> could you try -11, do you still see these large latencies?

yes, this seems to fix it. no more extra jitter or large latencies on
console switches. 

Now, on to trying to lock up the machine ;)

Ah, btw: one thing i observed with my soundcard. I load the module at bootup
and chrt its IRQ handler to prio 98 (a check with chrt shows this prio
allright). Now it seems that the first time the soundcard is actually used
the thread gets back its original prio (from dmesg):

IRQ#3 thread RT prio: 42.

Maybe the sounddriver (snd-cs46xx) i use never initializes its irq before
the first time it gets used to play something. Well anyways, the workaround
is to change its prio after the first time it is used and not directly after
module loading..

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 23:55:35 +0100
Florian Schmidt <mista.tapas@gmx.net> wrote:

> yes, this seems to fix it. no more extra jitter or large latencies on
> console switches. 
> 
> Now, on to trying to lock up the machine ;)
> 

Arr, it did lock up again. This time i was in X, so i couldn't use any sysrq
stuff to see something. Will try tomorrow again..

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[john cooper]

Florian Schmidt wrote:
> On Tue, 16 Nov 2004 23:55:35 +0100
> Florian Schmidt <mista.tapas@gmx.net> wrote:
> 
> 
>>yes, this seems to fix it. no more extra jitter or large latencies on
>>console switches. 
>>
>>Now, on to trying to lock up the machine ;)
>>
> 
> 
> Arr, it did lock up again. This time i was in X, so i couldn't use any sysrq
> stuff to see something. Will try tomorrow again..

Was this random or under some particular stress/load?


-- 
john.cooper@timesys.com

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 19:06:50 -0500
john cooper <john.cooper@timesys.com> wrote:

> > Arr, it did lock up again. This time i was in X, so i couldn't use any sysrq
> > stuff to see something. Will try tomorrow again..
> 
> Was this random or under some particular stress/load?

I had rtc_wakeup running with a rtc frequency of 8192 hz at the time plus
some general usage (reading mails, etc..) In earlier kernels it seemed that
the lock fell together with the rtc IRQ being piggy. will try to reproduce
now with the freshest RP kernel.

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* Florian Schmidt <mista.tapas@gmx.net> wrote:

> > Was this random or under some particular stress/load?
> 
> I had rtc_wakeup running with a rtc frequency of 8192 hz at the time
> plus some general usage (reading mails, etc..) In earlier kernels it
> seemed that the lock fell together with the rtc IRQ being piggy. will
> try to reproduce now with the freshest RP kernel.

i've just uploaded the -28-0 kernel with a couple of robustness updates,
could you try that one?

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* Florian Schmidt <mista.tapas@gmx.net> wrote:

> > Was this random or under some particular stress/load?
> 
> I had rtc_wakeup running with a rtc frequency of 8192 hz at the time
> plus some general usage (reading mails, etc..) In earlier kernels it
> seemed that the lock fell together with the rtc IRQ being piggy. will
> try to reproduce now with the freshest RP kernel.

could you send me the latest .config you are using on this box?

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

[-- Attachment #1: Type: text/plain, Size: 4290 bytes --]

On Wed, 17 Nov 2004 14:02:36 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Florian Schmidt <mista.tapas@gmx.net> wrote:
> 
> > > Was this random or under some particular stress/load?
> > 
> > I had rtc_wakeup running with a rtc frequency of 8192 hz at the time
> > plus some general usage (reading mails, etc..) In earlier kernels it
> > seemed that the lock fell together with the rtc IRQ being piggy. will
> > try to reproduce now with the freshest RP kernel.

I am not all certain that there really is a correlation like this. It might
have been coincidence. This boot locked again when i was in X for 1 minute
for checking mails. So again no console output.

I will change the keyboard IRQ handler back to prio 99. Maybe sysrq is
usable then..

Will stay on the console from now until next lockup to see if i get anything
out of sysrq (although the 50 lines vga console is probably of limited use
here).

> 
> could you send me the latest .config you are using on this box?

sure. attached. 

flo

p.s.: some more system info:

~$ cat /proc/cpuinfo 
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 4
model name      : AMD Athlon(tm) Processor
stepping        : 2
cpu MHz         : 1195.144
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr pni syscall mmxext 3dnowext 3dnow
bogomips        : 2359.29


0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 735 Host (rev 01)
	Flags: bus master, medium devsel, latency 32
	Memory at d0000000 (32-bit, non-prefetchable) [size=256M]
	Capabilities: <available only to root>

0000:00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 64
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
	Memory behind bridge: cdc00000-cfcfffff
	Prefetchable memory behind bridge: bd900000-cdafffff

0000:00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
	Flags: bus master, medium devsel, latency 0

0000:00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016
	Flags: medium devsel
	I/O ports at 0c00 [size=32]

0000:00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master])
	Subsystem: Silicon Integrated Systems [SiS] SiS5513 EIDE Controller (A,B step)
	Flags: bus master, fast devsel, latency 128
	I/O ports at ff00 [size=16]

0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0)
	Subsystem: Elitegroup Computer Systems: Unknown device 0a14
	Flags: bus master, medium devsel, latency 64, IRQ 10
	I/O ports at dc00 [size=256]
	I/O ports at d800 [size=64]
	Capabilities: <available only to root>

0000:00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
	Subsystem: Elitegroup Computer Systems: Unknown device 0a14
	Flags: bus master, medium devsel, latency 64, IRQ 5
	I/O ports at d400 [size=256]
	Memory at cfffe000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at cffc0000 [disabled] [size=128K]
	Capabilities: <available only to root>

0000:00:0f.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
	Subsystem: TERRATEC Electronic GmbH: Unknown device 112e
	Flags: bus master, medium devsel, latency 64, IRQ 3
	Memory at cfffd000 (32-bit, non-prefetchable) [size=4K]
	Memory at cfe00000 (32-bit, non-prefetchable) [size=1M]
	Capabilities: <available only to root>

0000:01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti 200] (rev a3) (prog-if 00 [VGA])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 8503
	Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
	Memory at ce000000 (32-bit, non-prefetchable) [size=16M]
	Memory at c0000000 (32-bit, prefetchable) [size=128M]
	Memory at cda80000 (32-bit, prefetchable) [size=512K]
	Expansion ROM at cfcf0000 [disabled] [size=64K]
	Capabilities: <available only to root>

what else would be interesting for you?

flo

[-- Attachment #2: .config --]
[-- Type: application/octet-stream, Size: 26386 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.10-rc2-mm1-RT-V0.7.28-0
# Wed Nov 17 12:35:09 2004
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=17
# CONFIG_HOTPLUG is not set
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
# CONFIG_SMP is not set
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_BKL=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y

#
# Performance-monitoring counters support
#
# CONFIG_PERFCTR is not set
CONFIG_KERN_PHYS_OFFSET=1
# CONFIG_KEXEC is not set

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BLACKLIST_YEAR=0

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_MISC=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_DEBUG_DRIVER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
# CONFIG_CDROM_PKTCDVD is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
CONFIG_BLK_DEV_SIS5513=y
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=32
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLOGIC_1280_1040 is not set
CONFIG_SCSI_QLA2XXX=m
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
# CONFIG_IP_MULTIPLE_TABLES is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
# CONFIG_IP_ROUTE_VERBOSE is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IP_TCPDIAG=y
# CONFIG_IP_TCPDIAG_IPV6 is not set

#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set

#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CONNTRACK_MARK is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
# CONFIG_IP_NF_FTP is not set
# CONFIG_IP_NF_IRC is not set
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_MATCH_ADDRTYPE=m
CONFIG_IP_NF_MATCH_REALM=m
# CONFIG_IP_NF_MATCH_SCTP is not set
# CONFIG_IP_NF_MATCH_COMMENT is not set
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
# CONFIG_IP_NF_NAT_LOCAL is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
# CONFIG_IP_NF_RAW is not set
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
# CONFIG_IP_NF_COMPAT_IPCHAINS is not set
# CONFIG_IP_NF_COMPAT_IPFWADM is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CLK_JIFFIES=y
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
# CONFIG_NET_SCH_HFSC is not set
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
# CONFIG_NET_SCH_NETEM is not set
CONFIG_NET_SCH_INGRESS=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
# CONFIG_CLS_U32_PERF is not set
# CONFIG_NET_CLS_IND is not set
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
# CONFIG_NET_CLS_ACT is not set
CONFIG_NET_CLS_POLICE=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_KGDBOE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
# CONFIG_ETHERTAP is not set

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
CONFIG_SIS900=m
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PPP=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPPOE=m
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
CONFIG_GAMEPORT=m
CONFIG_SOUND_GAMEPORT=m
# CONFIG_GAMEPORT_NS558 is not set
# CONFIG_GAMEPORT_L4 is not set
# CONFIG_GAMEPORT_EMU10K1 is not set
# CONFIG_GAMEPORT_VORTEX is not set
# CONFIG_GAMEPORT_FM801 is not set
# CONFIG_GAMEPORT_CS461x is not set
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# CONFIG_INPUT_UINPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
CONFIG_NVRAM=y
CONFIG_RTC=y
CONFIG_RTC_HISTOGRAM=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_INTEL_MCH is not set
# CONFIG_AGP_NVIDIA is not set
CONFIG_AGP_SIS=m
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HANGCHECK_TIMER=m

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
# CONFIG_I2C_ALGOPCA is not set

#
# I2C Hardware Bus support
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
# CONFIG_I2C_AMD756_S4882 is not set
CONFIG_I2C_AMD8111=m
CONFIG_I2C_I801=m
CONFIG_I2C_I810=m
CONFIG_I2C_ISA=m
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_PROSAVAGE=m
CONFIG_I2C_SAVAGE4=m
CONFIG_SCx200_ACB=m
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
# CONFIG_I2C_STUB is not set
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
CONFIG_I2C_VOODOO3=m
# CONFIG_I2C_PCA_ISA is not set

#
# Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_FSCHER=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_IT87=m
# CONFIG_SENSORS_LM63 is not set
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
# CONFIG_SENSORS_LM87 is not set
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_MAX1619=m
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m

#
# Other I2C Chip support
#
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_RTC8564=m
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_I2C_DEBUG_CHIP is not set

#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
CONFIG_VIDEO_SELECT=y

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
# CONFIG_SND_VERBOSE_PRINTK is not set
CONFIG_SND_DEBUG=y
# CONFIG_SND_DEBUG_MEMORY is not set
# CONFIG_SND_DEBUG_DETECT is not set

#
# Generic devices
#
CONFIG_SND_DUMMY=m
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# PCI devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
CONFIG_SND_CS46XX=m
CONFIG_SND_CS46XX_NEW_DSP=y
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
# CONFIG_USB is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISER4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
CONFIG_ROMFS_FS=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y

#
# Caches
#
# CONFIG_FSCACHE is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
CONFIG_DEVPTS_FS_XATTR=y
# CONFIG_DEVPTS_FS_SECURITY is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_XATTR is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
CONFIG_CRAMFS=m
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
CONFIG_AFS_FS=m
CONFIG_RXRPC=m

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
CONFIG_NLS_CODEPAGE_1250=y
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
CONFIG_WAKEUP_TIMING=y
CONFIG_PREEMPT_TRACE=y
CONFIG_CRITICAL_PREEMPT_TIMING=y
CONFIG_CRITICAL_IRQSOFF_TIMING=y
CONFIG_CRITICAL_TIMING=y
CONFIG_LATENCY_TIMING=y
CONFIG_LATENCY_TRACE=y
CONFIG_MCOUNT=y
CONFIG_RT_DEADLOCK_DETECT=y
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_INFO is not set
CONFIG_FRAME_POINTER=y
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set
# CONFIG_KGDB is not set

#
# Security options
#
# CONFIG_KEYS is not set
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
CONFIG_SECURITY_CAPABILITIES=m
# CONFIG_SECURITY_SECLVL is not set
CONFIG_SECURITY_REALTIME=m
# CONFIG_SECURITY_SELINUX is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_AES_586 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_TEST is not set

#
# Library routines
#
CONFIG_CRC_CCITT=m
CONFIG_CRC32=m
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* Florian Schmidt <mista.tapas@gmx.net> wrote:

> > could you send me the latest .config you are using on this box?
> 
> sure. attached. 

> what else would be interesting for you?

have you kicked the latency tracer by clearing preempt_max_latency, or
is it at the default (off) value?

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Wed, 17 Nov 2004 14:41:50 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Florian Schmidt <mista.tapas@gmx.net> wrote:
> 
> > > could you send me the latest .config you are using on this box?
> > 
> > sure. attached. 
> 
> > what else would be interesting for you?
> 
> have you kicked the latency tracer by clearing preempt_max_latency, or
> is it at the default (off) value?

I didn't touch it.

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Paul Ma]

Hi,

After I finished using my USB HDD, I umount it.
When unplug from my computer, there are the following output:

Nov 17 21:13:11 magf1 kernel: usb 1-5: USB disconnect, address 2
Nov 17 21:13:11 magf1 kernel: slab error in kmem_cache_destroy(): cache
`scsi_cmd_cache': Can't free all objects
Nov 17 21:13:11 magf1 kernel:  [<c0104164>] dump_stack+0x23/0x27 (20)
Nov 17 21:13:11 magf1 kernel:  [<c0151ba5>] kmem_cache_destroy+0x106/0x194
(28)
Nov 17 21:13:11 magf1 kernel:  [<c02c99b5>]
scsi_destroy_command_freelist+0x53/0x81 (28)
Nov 17 21:13:11 magf1 kernel:  [<c02ca866>] scsi_host_dev_release+0x43/0x164
(172)
Nov 17 21:13:11 magf1 kernel:  [<c0295b4d>] device_release+0x7c/0x80 (32)
Nov 17 21:13:11 magf1 kernel:  [<c0226b94>] kobject_cleanup+0x94/0x96 (32)
Nov 17 21:13:11 magf1 kernel:  [<c02276ba>] kref_put+0x46/0xf0 (40)
Nov 17 21:13:11 magf1 kernel:  [<c0226bd2>] kobject_put+0x25/0x29 (16)
Nov 17 21:13:11 magf1 kernel:  [<d8880146>]
usb_stor_release_resources+0x7e/0x133 [usb_storage] (24)
Nov 17 21:13:11 magf1 kernel:  [<d88806d6>] storage_disconnect+0x9a/0xa8
[usb_storage] (16)
Nov 17 21:13:11 magf1 kernel:  [<d88a118c>] usb_unbind_interface+0x8b/0x8d
[usbcore] (28)
Nov 17 21:13:11 magf1 kernel:  [<c0296d92>] device_release_driver+0x86/0x88
(28)
Nov 17 21:13:11 magf1 kernel:  [<c0296f98>] bus_remove_device+0x56/0x86 (20)
Nov 17 21:13:11 magf1 kernel:  [<c0295f91>] device_del+0x4f/0x88 (20)
Nov 17 21:13:11 magf1 kernel:  [<d88a947c>] usb_disable_device+0xd1/0x172
[usbcore] (44)
Nov 17 21:13:11 magf1 kernel:  [<d88a3c97>] usb_disconnect+0xb0/0x187
[usbcore] (44)
Nov 17 21:13:11 magf1 kernel:  [<d88a5309>]
hub_port_connect_change+0x471/0x4a0 [usbcore] (72)
Nov 17 21:13:11 magf1 kernel:  [<d88a5779>] hub_events+0x441/0x52d [usbcore]
(76)
Nov 17 21:13:11 magf1 kernel:  [<d88a589c>] hub_thread+0x37/0x120 [usbcore]
(96)
Nov 17 21:13:11 magf1 kernel:  [<c0101329>] kernel_thread_helper+0x5/0xb
(690024468)
Nov 17 21:13:11 magf1 kernel: ---------------------------
Nov 17 21:13:11 magf1 kernel: | preempt count: 00000001 ]
Nov 17 21:13:11 magf1 kernel: | 1-level deep critical section nesting:
Nov 17 21:13:11 magf1 kernel: ----------------------------------------
Nov 17 21:13:11 magf1 kernel: .. [<c013ce8c>] .... print_traces+0x1d/0x56
Nov 17 21:13:11 magf1 kernel: .....[<c0104164>] ..   ( <=
dump_stack+0x23/0x27)
Nov 17 21:13:11 magf1 kernel:

On linux-2.6.6/2.6.7 and Fedora Core 2, My USB HDD is working properly. On
realtime preempt kernel, I
have such problem.

Paul


----- Original Message -----
From: "Florian Schmidt" <mista.tapas@gmx.net>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "john cooper" <john.cooper@timesys.com>; "K.R. Foley" <kr@cybsft.com>;
<Mark_H_Johnson@raytheon.com>; <linux-kernel@vger.kernel.org>; "Lee Revell"
<rlrevell@joe-job.com>; "Rui Nuno Capela" <rncbc@rncbc.org>; "Bill Huey"
<bhuey@lnxw.com>; "Adam Heath" <doogie@debian.org>; "Thomas Gleixner"
<tglx@linutronix.de>; "Michal Schmidt" <xschmi00@stud.feec.vutbr.cz>;
"Fernando Pablo Lopez-Lezcano" <nando@ccrma.Stanford.EDU>; "Karsten Wiese"
<annabellesgarden@yahoo.de>; "Gunther Persoons"
<gunther_persoons@spymac.com>; <emann@mrv.com>; "Shane Shrybman"
<shrybman@aei.ca>; "Amit Shah" <amit.shah@codito.com>; "Stefan Schweizer"
<sschweizer@gmail.com>
Sent: Wednesday, November 17, 2004 8:59 PM
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3


> On Wed, 17 Nov 2004 14:41:50 +0100
> Ingo Molnar <mingo@elte.hu> wrote:
>
> >
> > * Florian Schmidt <mista.tapas@gmx.net> wrote:
> >
> > > > could you send me the latest .config you are using on this box?
> > >
> > > sure. attached.
> >
> > > what else would be interesting for you?
> >
> > have you kicked the latency tracer by clearing preempt_max_latency, or
> > is it at the default (off) value?
>
> I didn't touch it.
>
> flo
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* Florian Schmidt <mista.tapas@gmx.net> wrote:

> > > I had rtc_wakeup running with a rtc frequency of 8192 hz at the time
> > > plus some general usage (reading mails, etc..) In earlier kernels it
> > > seemed that the lock fell together with the rtc IRQ being piggy. will
> > > try to reproduce now with the freshest RP kernel.
> 
> I am not all certain that there really is a correlation like this. It
> might have been coincidence. This boot locked again when i was in X
> for 1 minute for checking mails. So again no console output.

managed to reproduce the lockup on my testbox, using your .config,
running rtc_wakeup -f 8192 and starting X. Hard hang and i had IRQ1 at
prio 99. Will turn on the NMI watchdog now, hopefully this lockup will
stay easy to reproduce.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Wed, 17 Nov 2004 14:45:09 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Florian Schmidt <mista.tapas@gmx.net> wrote:
> 
> > > > I had rtc_wakeup running with a rtc frequency of 8192 hz at the time
> > > > plus some general usage (reading mails, etc..) In earlier kernels it
> > > > seemed that the lock fell together with the rtc IRQ being piggy. will
> > > > try to reproduce now with the freshest RP kernel.
> > 
> > I am not all certain that there really is a correlation like this. It
> > might have been coincidence. This boot locked again when i was in X
> > for 1 minute for checking mails. So again no console output.
> 
> managed to reproduce the lockup on my testbox, using your .config,
> running rtc_wakeup -f 8192 and starting X. Hard hang and i had IRQ1 at
> prio 99. Will turn on the NMI watchdog now, hopefully this lockup will
> stay easy to reproduce.

Hi,

i experienced another one. But as i stayed on the console sysrq was
available, so i can send you the last locks listed by sysrq-t.

The scenario was this:

rtc_wakeup -f 8192 in one console
some find /'s in another

Now i changed to a third console and put some load on the system my doing
make clean bzImage in some kernel source dir.

right after hitting enter after typing "make clean bziage" i got another
piggy message and the machine locked. It seems (to my uneducated mind) cc1
and rtc_wakeup both are involved with this as the list of held locks (or the
part of the list which i can see) shows them.

there were 5 locks of the following form

&drive-gendev_rel_sem
init
init_hwif_data

2 locks of this form:

&tty->atomic_read
getty
reasd_char

and these:

&mm->page_table_lock
cc1
exit_mmap

&mm->mmap_sem
rtc_wakeup
do_page_fault

&mm->page_table_lock
rtc_wakeup
handle_mm_fault

&serio_lock
IRQ 1
serio_interrupt

sysrq_table_lock
IRQ 1
__handle_sysrq

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* Florian Schmidt <mista.tapas@gmx.net> wrote:

> > managed to reproduce the lockup on my testbox, using your .config,
> > running rtc_wakeup -f 8192 and starting X. Hard hang and i had IRQ1 at
> > prio 99. Will turn on the NMI watchdog now, hopefully this lockup will
> > stay easy to reproduce.
> 
> Hi,
> 
> i experienced another one. But as i stayed on the console sysrq was
> available, so i can send you the last locks listed by sysrq-t.

i can now reproduce it at will. It's some sort of MM deadlock (infinite
pagefaults in rtc_wakeup), i'm debugging it now.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-11

[???]

Hi,

I have one USB removable HDD.  After plugging it to my usb ports, I can
mount FS and read/write,
but if I unmount it and unplug it , the system gives so many errors. Even
though I do not mount and umount FS,
only plug and  then unplug USB HDD,  the errors occur as well. The following
is my syslog after unplug and plug
this USB HDD:


Nov 17 13:56:28 magf1 kernel: usb 1-5: USB disconnect, address 2
Nov 17 13:56:29 magf1 kernel: slab error in kmem_cache_destroy(): cache
`scsi_cmd_cache': Can't free all objects
Nov 17 13:56:29 magf1 kernel:  [<c0104164>] dump_stack+0x23/0x27 (20)
Nov 17 13:56:29 magf1 kernel:  [<c0151ba5>] kmem_cache_destroy+0x106/0x194
(28)
Nov 17 13:56:29 magf1 kernel:  [<c02c99b5>]
scsi_destroy_command_freelist+0x53/0x81 (28)
Nov 17 13:56:29 magf1 kernel:  [<c02ca866>] scsi_host_dev_release+0x43/0x164
(172)
Nov 17 13:56:29 magf1 kernel:  [<c0295b4d>] device_release+0x7c/0x80 (32)
Nov 17 13:56:29 magf1 kernel:  [<c0226b94>] kobject_cleanup+0x94/0x96 (32)
Nov 17 13:56:29 magf1 kernel:  [<c02276ba>] kref_put+0x46/0xf0 (40)
Nov 17 13:56:29 magf1 kernel:  [<c0226bd2>] kobject_put+0x25/0x29 (16)
Nov 17 13:56:29 magf1 kernel:  [<d8880146>]
usb_stor_release_resources+0x7e/0x133 [usb_storage] (24)
Nov 17 13:56:29 magf1 kernel:  [<d88806d6>] storage_disconnect+0x9a/0xa8
[usb_storage] (16)
Nov 17 13:56:29 magf1 kernel:  [<d88a118c>] usb_unbind_interface+0x8b/0x8d
[usbcore] (28)
Nov 17 13:56:29 magf1 kernel:  [<c0296d92>] device_release_driver+0x86/0x88
(28)
Nov 17 13:56:29 magf1 kernel:  [<c0296f98>] bus_remove_device+0x56/0x86 (20)
Nov 17 13:56:29 magf1 kernel:  [<c0295f91>] device_del+0x4f/0x88 (20)
Nov 17 13:56:29 magf1 kernel:  [<d88a947c>] usb_disable_device+0xd1/0x172
[usbcore] (44)
Nov 17 13:56:29 magf1 kernel:  [<d88a3c97>] usb_disconnect+0xb0/0x187
[usbcore] (44)
Nov 17 13:56:29 magf1 kernel:  [<d88a5309>]
hub_port_connect_change+0x471/0x4a0 [usbcore] (72)
Nov 17 13:56:29 magf1 kernel:  [<d88a5779>] hub_events+0x441/0x52d [usbcore]
(76)
Nov 17 13:56:29 magf1 kernel:  [<d88a589c>] hub_thread+0x37/0x120 [usbcore]
(96)
Nov 17 13:56:29 magf1 kernel:  [<c0101329>] kernel_thread_helper+0x5/0xb
(691048468)
Nov 17 13:56:29 magf1 kernel: ---------------------------
Nov 17 13:56:29 magf1 kernel: | preempt count: 00000001 ]
Nov 17 13:56:29 magf1 kernel: | 1-level deep critical section nesting:
Nov 17 13:56:29 magf1 kernel: ----------------------------------------
Nov 17 13:56:29 magf1 kernel: .. [<c03cceee>] .... _raw_spin_lock+0x22/0x78
Nov 17 13:56:29 magf1 kernel: .....[<c014737b>] ..   ( <=
__do_IRQ+0x9c/0x159)
Nov 17 13:56:29 magf1 kernel:
Nov 17 13:56:29 magf1 kernel: (IRQ 0/2/CPU#0): new 192 us maximum-latency
wakeup.
Nov 17 13:56:59 magf1 kernel: usb 1-5: new high speed USB device using
ehci_hcd and address 3
Nov 17 13:56:59 magf1 kernel: usb 1-5: config 1 descriptor has 1 excess
byte, ignoring
Nov 17 13:56:59 magf1 kernel: usb 1-5: Product: USB TO IDE
Nov 17 13:56:59 magf1 kernel: kmem_cache_create: duplicate cache
scsi_cmd_cache
Nov 17 13:56:59 magf1 kernel: BUG at mm/slab.c:1447!
Nov 17 13:56:59 magf1 kernel: ------------[ cut here ]------------
Nov 17 13:56:59 magf1 kernel: kernel BUG at mm/slab.c:1447!
Nov 17 13:56:59 magf1 kernel: invalid operand: 0000 [#1]
Nov 17 13:56:59 magf1 kernel: PREEMPT SMP
Nov 17 13:56:59 magf1 kernel: Modules linked in: usb_storage uhci_hcd
ehci_hcd usbcore video asus_acpi rtc
Nov 17 13:56:59 magf1 kernel: CPU:    0
Nov 17 13:56:59 magf1 kernel: EIP:    0060:[<c0151628>]    Not tainted VLI
Nov 17 13:56:59 magf1 kernel: EFLAGS: 00010282
(2.6.10-rc2-mm1-RT-V0.7.27-11)
Nov 17 13:56:59 magf1 kernel: EIP is at kmem_cache_create+0x441/0x66e
Nov 17 13:56:59 magf1 kernel: eax: 00000017   ebx: c91df780   ecx: c0119911
edx: c013aa88
Nov 17 13:56:59 magf1 kernel: esi: c0402af0   edi: c0402af0   ebp: d6cf6c98
esp: d6cf6c5c
Nov 17 13:56:59 magf1 kernel: ds: 007b   es: 007b   ss: 0068   preempt:
00000001
Nov 17 13:56:59 magf1 kernel: Process khubd (pid: 1327, threadinfo=d6cf6000
task=d76f47d0)
Nov 17 13:56:59 magf1 kernel: Stack: c03e4ee2 c03ea285 000005a7 00000565
d6cf6c88 c91df7d8 00000007 c0000000
Nov 17 13:56:59 magf1 kernel:        d7856948 ffffff80 00000000 00000180
d77e0000 c0491dc0 d77e0048 d6cf6cc4
Nov 17 13:56:59 magf1 kernel:        c02c98e2 c0402ae1 00000200 00000080
00002000 00000000 00000000 d77e00f0
Nov 17 13:56:59 magf1 kernel: Call Trace:
Nov 17 13:56:59 magf1 kernel:  [<c010412b>] show_stack+0x85/0x9b (28)
Nov 17 13:56:59 magf1 kernel:  [<c01042d7>] show_registers+0x16f/0x1d3 (56)
Nov 17 13:56:59 magf1 kernel:  [<c01044e5>] die+0x10c/0x192 (64)
Nov 17 13:56:59 magf1 kernel:  [<c0104a8c>] do_invalid_op+0x123/0x125 (192)
Nov 17 13:56:59 magf1 kernel:  [<c0103d87>] error_code+0x2b/0x30 (120)
Nov 17 13:56:59 magf1 kernel:  [<c02c98e2>]
scsi_setup_command_freelist+0x94/0x114 (44)
Nov 17 13:56:59 magf1 kernel:  [<c02cac4e>] scsi_host_alloc+0x2c7/0x3d9
(180)
Nov 17 13:56:59 magf1 kernel:  [<d8880013>]
usb_stor_acquire_resources+0x6f/0x124 [usb_storage] (28)
Nov 17 13:56:59 magf1 kernel:  [<d8880595>] storage_probe+0x1cb/0x272
[usb_storage] (36)
Nov 17 13:56:59 magf1 kernel:  [<d88a10df>] usb_probe_interface+0xc7/0xe9
[usbcore] (48)
Nov 17 13:56:59 magf1 kernel:  [<c0296ba4>] driver_probe_device+0x36/0x73
(24)
Nov 17 13:57:00 magf1 kernel:  [<c0296c31>] device_attach+0x50/0xa3 (40)
Nov 17 13:57:00 magf1 kernel:  [<c0296f03>] bus_add_device+0x51/0x90 (28)
Nov 17 13:57:00 magf1 kernel:  [<c0295e57>] device_add+0xbc/0x134 (40)
Nov 17 13:57:00 magf1 kernel:  [<d88a9c3a>]
usb_set_configuration+0x31c/0x476 [usbcore] (88)
Nov 17 13:57:00 magf1 kernel:  [<d88a4004>] usb_new_device+0x11e/0x225
[usbcore] (52)
Nov 17 13:57:00 magf1 kernel:  [<d88a514b>]
hub_port_connect_change+0x2b3/0x4a0 [usbcore] (72)
Nov 17 13:57:00 magf1 kernel:  [<d88a5779>] hub_events+0x441/0x52d [usbcore]
(76)
Nov 17 13:57:00 magf1 kernel:  [<d88a589c>] hub_thread+0x37/0x120 [usbcore]
(96)
Nov 17 13:57:00 magf1 kernel:  [<c0101329>] kernel_thread_helper+0x5/0xb
(691048468)
Nov 17 13:57:00 magf1 kernel: ---------------------------
Nov 17 13:57:00 magf1 kernel: | preempt count: 00000002 ]
Nov 17 13:57:00 magf1 kernel: | 2-level deep critical section nesting:
Nov 17 13:57:00 magf1 kernel: ----------------------------------------
Nov 17 13:57:00 magf1 kernel: .. [<c03ccf66>] ....
_raw_spin_lock_irqsave+0x22/0x87
Nov 17 13:57:00 magf1 kernel: .....[<c010441d>] ..   ( <= die+0x44/0x192)
Nov 17 13:57:00 magf1 kernel: .. [<c013ce8c>] .... print_traces+0x1d/0x56
Nov 17 13:57:00 magf1 kernel: .....[<c010412b>] ..   ( <=
show_stack+0x85/0x9b)
Nov 17 13:57:00 magf1 kernel:
Nov 17 13:57:00 magf1 kernel: Code: e8 33 04 fd ff b8 a0 48 67 c0 e8 c8 93
fe ff c7 44 24 08 a7 05 00 00 c7 44 24 04 85 a2 3e c0 c7 04 24 e2 4e 3e c0
e8 0d 04 fd ff <0f> 0b a7 05 85 a2 3e c0 8b 45 e4 8b 08 e9 4d ff ff ff 8b 47
50
Nov 17 13:57:00 magf1 kernel:  BUG: khubd/1327, lock held at task exit time!
Nov 17 13:57:00 magf1 kernel:  [d88bb940] {usb_all_devices_rwsem.lock}
Nov 17 13:57:00 magf1 kernel: .. held by:             khubd: 1327 [d76f47d0,
115]
Nov 17 13:57:00 magf1 kernel: ... acquired at:  usb_lock_device+0x16/0x20
[usbcore]
Nov 17 13:57:00 magf1 kernel: BUG: khubd/1327, lock held at task exit time!
Nov 17 13:57:00 magf1 kernel:  [d6852028] {&dev->serialize}
Nov 17 13:57:00 magf1 kernel: .. held by:             khubd: 1327 [d76f47d0,
115]
Nov 17 13:57:00 magf1 kernel: ... acquired at:  locktree+0x84/0x88 [usbcore]
Nov 17 13:57:00 magf1 kernel: BUG: khubd/1327, lock held at task exit time!
Nov 17 13:57:00 magf1 kernel:  [d7683428] {&dev->serialize}
Nov 17 13:57:00 magf1 kernel: .. held by:             khubd: 1327 [d76f47d0,
115]
Nov 17 13:57:00 magf1 kernel: ... acquired at:
hub_port_connect_change+0x1c4/0x4a0 [usbcore]
Nov 17 13:57:00 magf1 kernel: BUG: env/3928, lock held at task exit time!
Nov 17 13:57:00 magf1 kernel:  [d88bba6c] {&s->rwsem}
Nov 17 13:57:00 magf1 kernel: .. held by:               env: 3928 [d76f47d0,
116]
Nov 17 13:57:00 magf1 kernel: ... acquired at:  bus_add_device+0x30/0x90
Nov 17 13:57:00 magf1 kernel: BUG: env/3928, lock held at task exit time!
Nov 17 13:57:00 magf1 kernel:  [c0491e04] {host_cmd_pool_mutex.lock}
Nov 17 13:57:00 magf1 kernel: .. held by:               env: 3928 [d76f47d0,
116]
Nov 17 13:57:00 magf1 kernel: ... acquired at:
scsi_setup_command_freelist+0x4c/0x114

My USB HDD is OK on FC2 and ON RP kernel V0.7.18, V0.7.25-1,V0.7.27-11 all
have this problem.

Paul Ma
magf@bitland.com.cn

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[K.R. Foley]

Florian Schmidt wrote:
> On Tue, 16 Nov 2004 22:24:01 +0100
> Ingo Molnar <mingo@elte.hu> wrote:
> 
> 
>>great. The current release is meanwhile at -V0.7.27-10, which includes
>>other minor updates:
>>
> 
> 
> Ok, this one boots fine again for me (didn't test the ones betwen my last
> report and this one).
> 
> I have not yet tried to get this kernel to lock up yet, but i made another
> interesting observation:
> 
> irq 8 at prio 98 (only irq 1 with higher prio 99). running rtc_wakeup in the
> console (it runs SCHED_FIFO allright). Switching consoles (different text
> consoles - not swithcing to X, though this basically produces similar
> results) produces large jitters (around 1 ms) and occasional missed irq's
> and piggy messages. This is completely reproducable here. The rtc histogram
> doesn't show any large wakeup latencies.

Just a thought. What priority are you running rtc_wakup at? If you are 
doing something like:

schp.sched_priority = sched_get_priority_max(SCHED_FIFO); // which 
equates to a priority of 99

Then you it is actually running at a higher priority than the rtc, and 
it won't work very well. I tend to run rtc (IRQ 8) at 99 and the 
programs accessing it at 98 which seems to work reasonably well.

> 
> /proc/latency_trace doesn't show that high latencies either on console
> switch:
> 
> preemption latency trace v1.0.7 on 2.6.10-rc2-mm1-RT-V0.7.27-10
> -------------------------------------------------------
>  latency: 63 us, entries: 22 (22)   |   [VP:0 KP:1 SP:1 HP:1 #CPUS:1]
>     -----------------
>     | task: IRQ 8/13, uid:0 nice:-5 policy:1 rt_prio:98
>     -----------------
>  => started at: try_to_wake_up+0x51/0x170 <c010f3a1>
>  => ended at:   finish_task_switch+0x51/0xb0 <c010f911>
> =======>
>     5 80010004 0.000ms (+0.000ms): trace_start_sched_wakeup (try_to_wake_up)
>     5 80010003 0.000ms (+0.000ms): (1) ((98))
>     5 80010003 0.000ms (+0.000ms): (13) ((5))
>     5 80010003 0.000ms (+0.000ms): try_to_wake_up (wake_up_process)
>     5 80010003 0.000ms (+0.000ms): (0) ((1))
>     5 80010002 0.000ms (+0.000ms): preempt_schedule (try_to_wake_up)
>     5 80010002 0.000ms (+0.000ms): wake_up_process (redirect_hardirq)
>     5 80010001 0.000ms (+0.000ms): preempt_schedule (__do_IRQ)
>     5 80010001 0.000ms (+0.000ms): irq_exit (do_IRQ)
>     5 80000002 0.000ms (+0.000ms): do_softirq (irq_exit)
>     5 80000002 0.001ms (+0.061ms): __do_softirq (do_softirq)
>     5 00000000 0.062ms (+0.000ms): preempt_schedule (_mmx_memcpy)
>     5 90000000 0.062ms (+0.000ms): __schedule (preempt_schedule)
>     5 90000000 0.062ms (+0.000ms): profile_hit (__schedule)
>     5 90000001 0.062ms (+0.000ms): sched_clock (__schedule)
>    13 80000002 0.062ms (+0.000ms): __switch_to (__schedule)
>    13 80000002 0.062ms (+0.000ms): (5) ((13))
>    13 80000002 0.062ms (+0.000ms): (98) ((1))
>    13 80000002 0.062ms (+0.000ms): finish_task_switch (__schedule)
>    13 80000001 0.062ms (+0.000ms): trace_stop_sched_switched (finish_task_switch)
>    13 80000001 0.063ms (+0.003ms): (13) ((1))
>    13 80000001 0.066ms (+0.000ms): trace_stop_sched_switched (finish_task_switch)
> 
> I sometimes do get large values in /proc/latency_trace, but they seem to be
> unrelated to the console switching.
> 
> flo
> 

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 15:42:52 -0600
"K.R. Foley" <kr@cybsft.com> wrote:

> Just a thought. What priority are you running rtc_wakup at? If you are 
> doing something like:
> 
> schp.sched_priority = sched_get_priority_max(SCHED_FIFO); // which 
> equates to a priority of 99
> 
> Then you it is actually running at a higher priority than the rtc, and 
> it won't work very well. I tend to run rtc (IRQ 8) at 99 and the 
> programs accessing it at 98 which seems to work reasonably well.

yah, the default for rtc_wakeup is 91 for the read() thread and 90 for the
reporting thread. So rtc's prio is above that.

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* Florian Schmidt <mista.tapas@gmx.net> wrote:

> I have not yet tried to get this kernel to lock up yet, but i made
> another interesting observation:
> 
> irq 8 at prio 98 (only irq 1 with higher prio 99). running rtc_wakeup
> in the console (it runs SCHED_FIFO allright). Switching consoles
> (different text consoles - not swithcing to X, though this basically
> produces similar results) produces large jitters (around 1 ms) and
> occasional missed irq's and piggy messages. This is completely
> reproducable here. The rtc histogram doesn't show any large wakeup
> latencies.

interesting, i'll try to reproduce this.

btw., for best rtc_wakeup results you should chrt IRQ#0 to prio 99 too,
because it uses rtc_lock, otherwise it's an extra PI pass to undo the
lock inversion, which adds another 10 usecs or so to the worst-case
path.

and i'd suggest to chrt irq 1 back to below prio 90, maybe this explains
the console-switching latency? If you do a console-switch via the
keyboard then its priority 99 can get inherited by events/0 which then
does the quite expensive VGA console clearing/copying with priority 99,
possibly delaying rtc_wakeup quite significantly, easily for a
millisecond or so. So what you are seeing might be priority inheritance
handling at work!

> I sometimes do get large values in /proc/latency_trace, but they seem
> to be unrelated to the console switching.

could you post such a large latency trace? Are they like the bad traces
Mark is occasionally seeing, with some ridiculously large latency and a
ridiculously short execution trace?

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 23:31:35 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> and i'd suggest to chrt irq 1 back to below prio 90, maybe this explains
> the console-switching latency? If you do a console-switch via the
> keyboard then its priority 99 can get inherited by events/0 which then
> does the quite expensive VGA console clearing/copying with priority 99,
> possibly delaying rtc_wakeup quite significantly, easily for a
> millisecond or so. So what you are seeing might be priority inheritance
> handling at work!
> 

ah, will try this right away..

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 22:33:12 +0100
Florian Schmidt <mista.tapas@gmx.net> wrote:

> On Tue, 16 Nov 2004 23:31:35 +0100
> Ingo Molnar <mingo@elte.hu> wrote:
> 
> > and i'd suggest to chrt irq 1 back to below prio 90, maybe this explains
> > the console-switching latency? If you do a console-switch via the
> > keyboard then its priority 99 can get inherited by events/0 which then
> > does the quite expensive VGA console clearing/copying with priority 99,
> > possibly delaying rtc_wakeup quite significantly, easily for a
> > millisecond or so. So what you are seeing might be priority inheritance
> > handling at work!
> > 
> 
> ah, will try this right away..

now, doesn't seem to make a difference.. i gave IRQ 1 prio 40 and the
behaviour is the same.. BTW: what about IRQ 0? I tried at different prios
[40 and 99]. Doesn't make a difference either. As far as i understand it, it
really shouldn't make a difference either as in the interesting cases (app
woken up by irq) the scheduler is explicitly run anyways, right?

Here's another trace:

preemption latency trace v1.0.7 on 2.6.10-rc2-mm1-RT-V0.7.27-10
-------------------------------------------------------
 latency: 1056 us, entries: 22 (22)   |   [VP:0 KP:1 SP:1 HP:1 #CPUS:1]
    -----------------
    | task: IRQ 0/2, uid:0 nice:0 policy:1 rt_prio:99
    -----------------
 => started at: try_to_wake_up+0x51/0x170 <c010f3a1>
 => ended at:   finish_task_switch+0x51/0xb0 <c010f911>
=======>
    5 80010004 0.000ms (+0.000ms): trace_start_sched_wakeup (try_to_wake_up)
    5 80010003 0.000ms (+0.000ms): (0) ((98))
    5 80010003 0.000ms (+0.000ms): (2) ((5))
    5 80010003 0.000ms (+0.000ms): try_to_wake_up (wake_up_process)
    5 80010003 0.000ms (+0.000ms): (0) ((1))
    5 80010002 0.000ms (+0.000ms): preempt_schedule (try_to_wake_up)
    5 80010002 0.000ms (+0.000ms): wake_up_process (redirect_hardirq)
    5 80010001 0.000ms (+0.000ms): preempt_schedule (__do_IRQ)
    5 80010001 0.000ms (+0.000ms): irq_exit (do_IRQ)
    5 80000002 0.000ms (+0.000ms): do_softirq (irq_exit)
    5 80000002 0.001ms (+1.054ms): __do_softirq (do_softirq)
    5 00000000 1.055ms (+0.000ms): preempt_schedule (_mmx_memcpy)
    5 90000000 1.055ms (+0.000ms): __schedule (preempt_schedule)
    5 90000000 1.055ms (+0.000ms): profile_hit (__schedule)
    5 90000001 1.055ms (+0.000ms): sched_clock (__schedule)
    2 80000002 1.056ms (+0.000ms): __switch_to (__schedule)
    2 80000002 1.056ms (+0.000ms): (5) ((2))
    2 80000002 1.056ms (+0.000ms): (98) ((0))
    2 80000002 1.056ms (+0.000ms): finish_task_switch (__schedule)
    2 80000001 1.056ms (+0.000ms): trace_stop_sched_switched (finish_task_switch)
    2 80000001 1.056ms (+0.003ms): (2) ((0))
    2 80000001 1.060ms (+0.000ms): trace_stop_sched_switched (finish_task_switch)

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

ah, it's a missed reschedule:

>     5 80010004 0.000ms (+0.000ms): trace_start_sched_wakeup (try_to_wake_up)
>     5 80010003 0.000ms (+0.000ms): (0) ((98))
>     5 80010003 0.000ms (+0.000ms): (2) ((5))
>     5 80010003 0.000ms (+0.000ms): try_to_wake_up (wake_up_process)
>     5 80010003 0.000ms (+0.000ms): (0) ((1))
>     5 80010002 0.000ms (+0.000ms): preempt_schedule (try_to_wake_up)
>     5 80010002 0.000ms (+0.000ms): wake_up_process (redirect_hardirq)
>     5 80010001 0.000ms (+0.000ms): preempt_schedule (__do_IRQ)
>     5 80010001 0.000ms (+0.000ms): irq_exit (do_IRQ)
>     5 80000002 0.000ms (+0.000ms): do_softirq (irq_exit)
>     5 80000002 0.001ms (+1.054ms): __do_softirq (do_softirq)
>     5 00000000 1.055ms (+0.000ms): preempt_schedule (_mmx_memcpy)
>     5 90000000 1.055ms (+0.000ms): __schedule (preempt_schedule)

note this entry:

>     5 80010003 0.000ms (+0.000ms): (0) ((1))

this was generated by:

                __trace(0, need_resched());

so need_resched() is definite set. The kernel should have rescheduled. 

The other trace entries corroborate this:

>     5 80010003 0.000ms (+0.000ms): (0) ((98))
>     5 80010003 0.000ms (+0.000ms): (2) ((5))

these two entries mean that PID 2 got woken up by PID 5, and that PID 2
has a priority of 0, which is much higher than PID 5's prio 98 [the
kernel-internal priority scale is inverted], so no wonder need_resched() 
is set.

	Ingo

BUG with 0.7.27-11, with KGDB

[Amit Shah]

Initializing Cryptographic API
kgdb <20030915.1651.33> : port =3f8, IRQ=4, divisor =1
BUG: scheduling while atomic: swapper/0x00000001/1
caller is schedule+0x3f/0x13c
 [<c01041f4>] dump_stack+0x23/0x27 (20)
 [<c02ce307>] __sched_text_start+0xc97/0xce7 (116)
 [<c02ce396>] schedule+0x3f/0x13c (36)
 [<c02ce60a>] wait_for_completion+0x95/0x137 (96)
 [<c0138cd8>] kthread_create+0x22a/0x22c (368)
 [<c0145a30>] start_irq_thread+0x4f/0x83 (32)
 [<c01453ec>] setup_irq+0x55/0x140 (36)
 [<c0145655>] request_irq+0x90/0x107 (44)
 [<c01e1bc1>] kgdb_enable_ints_now+0xa5/0xb0 (28)
 [<c03bfb89>] kgdb_enable_ints+0x2c/0x63 (16)
 [<c03a8a23>] do_initcalls+0x31/0xc6 (32)
 [<c01003bb>] init+0x87/0x19a (28)
 [<c0101329>] kernel_thread_helper+0x5/0xb (1047322644)
---------------------------
| preempt count: 00000002 ]
| 2-level deep critical section nesting:
----------------------------------------
.. [<c02cfd66>] .... _raw_spin_trylock+0x1c/0x57
.....[<c01e1b31>] ..   ( <= kgdb_enable_ints_now+0x15/0xb0)
.. [<c013dbe3>] .... print_traces+0x1d/0x56
.....[<c01041f4>] ..   ( <= dump_stack+0x23/0x27)

-- 
Amit Shah
Codito Technologies Pvt. Ltd.

Re: BUG with 0.7.27-11, with KGDB

[Bill Huey]

On Wed, Nov 17, 2004 at 01:29:33PM +0530, Amit Shah wrote:
> Initializing Cryptographic API
> kgdb <20030915.1651.33> : port =3f8, IRQ=4, divisor =1
> BUG: scheduling while atomic: swapper/0x00000001/1
> caller is schedule+0x3f/0x13c
>  [<c01041f4>] dump_stack+0x23/0x27 (20)
>  [<c02ce307>] __sched_text_start+0xc97/0xce7 (116)
>  [<c02ce396>] schedule+0x3f/0x13c (36)
>  [<c02ce60a>] wait_for_completion+0x95/0x137 (96)
>  [<c0138cd8>] kthread_create+0x22a/0x22c (368)
>  [<c0145a30>] start_irq_thread+0x4f/0x83 (32)
>  [<c01453ec>] setup_irq+0x55/0x140 (36)
>  [<c0145655>] request_irq+0x90/0x107 (44)
>  [<c01e1bc1>] kgdb_enable_ints_now+0xa5/0xb0 (28)
>  [<c03bfb89>] kgdb_enable_ints+0x2c/0x63 (16)
>  [<c03a8a23>] do_initcalls+0x31/0xc6 (32)
>  [<c01003bb>] init+0x87/0x19a (28)
>  [<c0101329>] kernel_thread_helper+0x5/0xb (1047322644)

Woops, it means that KGDB needs a direct irq and not an irq-thread.
Let me see if I can work up something tonight before I head to bed.

bill

Re: BUG with 0.7.27-11, with KGDB

[Bill Huey]

[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]

On Wed, Nov 17, 2004 at 12:26:20AM -0800, Bill Huey wrote:
> On Wed, Nov 17, 2004 at 01:29:33PM +0530, Amit Shah wrote:
> > Initializing Cryptographic API
> > kgdb <20030915.1651.33> : port =3f8, IRQ=4, divisor =1
> > BUG: scheduling while atomic: swapper/0x00000001/1
> > caller is schedule+0x3f/0x13c
> >  [<c01041f4>] dump_stack+0x23/0x27 (20)
> >  [<c02ce307>] __sched_text_start+0xc97/0xce7 (116)
> >  [<c02ce396>] schedule+0x3f/0x13c (36)
> >  [<c02ce60a>] wait_for_completion+0x95/0x137 (96)
> >  [<c0138cd8>] kthread_create+0x22a/0x22c (368)
> >  [<c0145a30>] start_irq_thread+0x4f/0x83 (32)
> >  [<c01453ec>] setup_irq+0x55/0x140 (36)
> >  [<c0145655>] request_irq+0x90/0x107 (44)
> >  [<c01e1bc1>] kgdb_enable_ints_now+0xa5/0xb0 (28)
> >  [<c03bfb89>] kgdb_enable_ints+0x2c/0x63 (16)
> >  [<c03a8a23>] do_initcalls+0x31/0xc6 (32)
> >  [<c01003bb>] init+0x87/0x19a (28)
> >  [<c0101329>] kernel_thread_helper+0x5/0xb (1047322644)
> 
> Woops, it means that KGDB needs a direct irq and not an irq-thread.
> Let me see if I can work up something tonight before I head to bed.

It could be horribly wrong for a number of reasons (wait for Ingo
for a proper irq code fix and additional support), but try this:

[attachment]

It should be a good hint as to how to fix this problem.

bill


[-- Attachment #2: t2 --]
[-- Type: text/plain, Size: 1238 bytes --]

diff -rwu linux.voluntary.virgin/kernel/irq/manage.c linux.voluntary/kernel/irq/manage.c
--- linux.voluntary.virgin/kernel/irq/manage.c	2004-11-16 16:39:24.000000000 -0800
+++ linux.voluntary/kernel/irq/manage.c	2004-11-17 00:39:46.000000000 -0800
@@ -362,6 +363,11 @@
 	}
 #endif
 
+	if (irqflags & SA_NODELAYFORCED) {
+		irqflags &= ~SA_NODELAYFORCED;
+		irqflags |= SA_NODELAY;
+	}
+
 	action = kmalloc(sizeof(struct irqaction), GFP_ATOMIC);
 	if (!action)
 		return -ENOMEM;
--- linux.voluntary.virgin/arch/i386/lib/kgdb_serial.c	2004-11-16 16:39:24.000000000 -0800
+++ linux.voluntary/arch/i386/lib/kgdb_serial.c	2004-11-17 00:40:04.000000000 -0800
@@ -435,7 +435,7 @@
 #endif
 		ints_disabled = request_irq(gdb_async_info->state->irq,
 					    gdb_interrupt,
-					    IRQ_T(gdb_async_info),
+					    IRQ_T(gdb_async_info) | SA_NODELAYFORCED,
 					    "KGDB-stub", NULL);
 		intprintk(("KGDB: request_irq returned %d\n", ints_disabled));
 	}

--- linux.voluntary.virgin/include/linux/irq.h	2004-11-16 16:39:24.000000000 -0800
+++ linux.voluntary/include/linux/irq.h	2004-11-17 00:27:29.000000000 -0800
@@ -42,6 +42,7 @@
  */
 #ifndef SA_NODELAY
 # define SA_NODELAY 0x01000000
+# define SA_NODELAYFORCED 0x02000000
 #endif
 
 /*

Re: BUG with 0.7.27-11, with KGDB

[Ingo Molnar]

* Bill Huey <bhuey@lnxw.com> wrote:

> +	if (irqflags & SA_NODELAYFORCED) {
> +		irqflags &= ~SA_NODELAYFORCED;
> +		irqflags |= SA_NODELAY;

i've removed the SA_NODELAY-clearing hack from manage.c, that makes
things much cleaner.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Mark_H_Johnson]

>great. The current release is meanwhile at -V0.7.27-10, which includes
>other minor updates:

A kernel built with -V0.7.27-10 had the following BUG early in the
boot sequence. All boot messages prior to this point were basically
the same as I sent in the previous report.
  --Mark


[this is where -4 died...]
testing NMI watchdog ... OK.
checking TSC synchronization across 2 CPUs: passed.
IRQ#0 thread RT prio: 49.
BUG at kernel/softirq.c:514!
------------[ cut here ]------------
kernel BUG at kernel/softirq.c:514!
invalid operand: 0000 [#1]
PREEMPT SMP
Modules linked in:
CPU:    0
EIP:    0060:[<c012751e>]    Not tainted VLI
EFLAGS: 00010286   (2.6.10-rc2-mm1-RT-V0.7.27-10)
EIP is at cpu_callback+0xfe/0x130
eax: 0000001d   ebx: 00000000   ecx: c032ab6e   edx: dff82000
esi: 00000000   edi: 00000000   ebp: dff83fb0   esp: dff83f98
ds: 007b   es: 007b   ss: 0068   preempt: 00000001
Process swapper (pid: 1, threadinfo=dff82000 task=dff81460)
Stack: c033cefe c033f16e 00000202 c013b924 00000000 00000000 dff83fc8
c03eb7ee
       c037843c 00000003 00000000 c0100350 dff83fd0 c0100302 dff83fec
c0100387
       00000008 00000000 0000007b c0100350 00000000 00000000 c0102019
00000000
Call Trace:
 [<c0104e3f>] show_stack+0x8f/0xb0 (28)
 [<c0104fff>] show_registers+0x16f/0x1e0 (56)
 [<c0105236>] die+0x106/0x190 (64)
 [<c0105810>] do_invalid_op+0x130/0x140 (192)
 [<c0104a7f>] error_code+0x2b/0x30 (84)
 [<c03eb7ee>] spawn_ksoftirqd+0x2e/0x60 (24)
 [<c0100302>] do_pre_smp_initcalls+0x12/0x20 (8)
 [<c0100387>] init+0x37/0x1b0 (28)
 [<c0102019>] kernel_thread_helper+0x5/0xc (537378836)
---------------------------
| preempt count: 00000002 ]
| 2-level deep critical section nesting:
----------------------------------------
.. [<c032c702>] .... _raw_spin_lock_irqsave+0x22/0x90
.....[<c0105174>] ..   ( <= die+0x44/0x190)
.. [<c013dfbd>] .... print_traces+0x1d/0x60
.....[<c0104e3f>] ..   ( <= show_stack+0x8f/0xb0)

Code: 0f 0b 03 02 6e f1 33 c0 e9 77 ff ff ff c7 04 24 fe ce 33 c0 b8 02 02
00 00 89 44 24 08 b8 6e f1 33 c0 89 44 24 04 e8 62 9c ff ff <0f> 0b 02 02
6e f1 33 c0 8b 14 b5 20 20 41 c0 e9 39 ff ff ff 8b
 <0>Kernel panic - not syncing: Attempted to kill init!

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Mark_H_Johnson]

>From what I can tell, it was attempting to test the NMI watchdog
>when it failed.

Confirmed, clean boot when I removed
  nmi_watchdog=1 profile=2
from the boot parameters. Will be doing some tests without it.

   --Mark

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[K.R. Foley]

Mark_H_Johnson@raytheon.com wrote:
>>From what I can tell, it was attempting to test the NMI watchdog
> 
>>when it failed.
> 
> 
> Confirmed, clean boot when I removed
>   nmi_watchdog=1 profile=2
> from the boot parameters. Will be doing some tests without it.
> 
>    --Mark
> 
> 
I have no such boot parameters and I still couldn't get it to boot on my 
SMP workstation at the office.

kr

[patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.3

[Ingo Molnar]

i have released the -V0.3 Real-Time Preemption patch, which can be
downloaded from:

	http://redhat.com/~mingo/realtime-preempt/

this is a fixes-only release, but still experimental.

this release should fix a number of bugs that were reported for the V0
series: the futex.c assert, the lockups and the 'slowdown problem'.

The slowdown problem was an architectural issue that surfaced sometime
around U10 and increased in prominence as the the number of mutexes
increased and the number of spinlocks decreased. The futex.c assert was
related to this architectural issue as well, and most of the lockups
reported were i believe livelocks caused by the same issue. Also, the
scheduler path had an easy-to-trigger deadlock that often just silently
locked up.

some of the networking lockups might be related to this issue too, but i
think PREEMPT_REALTIME still has separate lock odering issues within the
networking code. Please re-report any deadlock-tracer asserts that you
might encounter.

Changes since -V0.2:

 - HEAP_SIZE fix from Karsten Wiese

 - fix hdparm-triggered debugging message reported by Mark H Johnson

 - fixed mutex related preemption to not impact the task state, just 
   like a normal spinlock does. This necessiated the introduction of
   TASK_RUNNING_MUTEX handling and related kernel infrastructure. This 
   framework avoids spurious wakeups done by mutex handling by isolating
   the state changes done by normal wakeups vs. the state changes caused
   by the mutex code.

 - added per-CPU deschedule threads. This fixes a deadlock scenario and
   it is also much faster than keventd.

 - fix debugging message upon console unblanking

to create a -V0.3 tree from scratch, the patching order is:

   http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
 + http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.9/2.6.9-mm1/2.6.9-mm1.bz2
 + http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.9-mm1-V0.3

	Ingo

[patch] Real-Time Preemption, -RT-2.6.10-rc1-mm2-V0.7.1

[Ingo Molnar]

i have released the -V0.7.1 Real-Time Preemption patch, which can be
downloaded from:

    http://redhat.com/~mingo/realtime-preempt/

this release is mainly a merge of -V0.6.9 to 2.6.10-rc2-mm2.

I havent done a proper changelog for a couple of days so here is a list
of bigger changes since -V0.4:

 - implemented a first version of the priority inheritance handling and
   priority inversion avoidance logic. This feature, after some initial
   stability problems, solved the jackd and rtc_wakeup latencies that
   were introduced by the ultra-finegrained locking in the -V series.

   (the -T/U series had a coarser locking scheme triggered much lower
   levels of priority inversion scenarios. The locking in the -V series
   was clearly the tipping point.)

   The new PI code covers all synchronization objects in Linux (on
   PREEMPT_REALTIME): spinlocks, rwlocks, semaphores and rwsems. 
   Feedback on the design of this code would be welcome, and patches as
   well, if you have a better scheme. The code is pretty modular so feel 
   free to experiment with alternative schemes.

 - completely reworked the debugging framework. All lock types
   (spinlocks, rwlocks, semaphores and rwsems) are now tracked, both
   their symbolic name and their place of acquire are traced and printed
   out upon detection of a deadlock. More and better information is
   printed upon a deadlock. Got rid of the 'semaphore owners array' in
   debugging mode, this reduces the footprint of semaphores quite
   significantly and speeds up deadlock detection.

 - got rid of the separate 'counted semaphores' implementation, it was
   too intrusive. Made the core 'generic semaphores' implementation
   compatible with vanilla Linux counted semaphore semantics. This also
   enabled the unrolling of the completion-handling cleanups which,
   while being very nice, were getting intrusive as well.

 - countless build and driver related reports/fixes from lots of people

 - more latency breaks in the remaining critical sections. A
   particularly important one was the irqs-off latency bugfix from
   Thomas Gleixner.

 - sped up the i8259 PIC and the PIT timer hardirq handling routines -
   these are now in the path of the longest latency.

 - cleaned up IRQ and signal preemption - there were missed
   check-rescheds and possibilities for IRQ recursion.

 - made ALSA's ioctl()s not use the BKL - this fixes more jackd
   latencies.

to create a -V0.7.1 tree from scratch, the patching order is:

   http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
   http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc1.bz2
   http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm2/2.6.10-rc1-mm2.bz2
   http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc1-mm2-V0.7.1

	Ingo

[patch] Real-Time Preemption, -RT-2.6.10-rc1-mm3-V0.7.18

[Ingo Molnar]

i have released the -V0.7.18 Real-Time Preemption patch, which can be
downloaded from:

   http://redhat.com/~mingo/realtime-preempt/

this release includes fixes and cleanups.

Changes between -V0.7.12 and -V0.7.18:

 - merged to 2.6.10-rc1-mm3

 - fixed the e1000 xmit warnings reported by Amit Shah. Same fix for tg3
   too.

 - added irq-latency fix from Thomas Gleixner: re-enable interrupts
   before adding timings to the entropy pool.

 - fixed excessive ksoftirqd overhead during outgoing TCP traffic. 
   ksoftirqd kept getting re-woken while it had no way to progress.

 - added upstream fix from Andi Kleen for the vmalloc bug causing module
   load problems/crashes. Added ipc/shm fix too.

Changes between -V0.7.1 and -V0.7.12:

 - big source level cleanups: completely rearranged the mutex type
   definitions and source files, to make it reflect the code. Made
   all locking objects based on a new, central lock type: struct
   rt_mutex. This type is never exposed externally, it is internal to
   the RT code. Unified all the RT locking code in kernel/rt.c, this 
   also simplified and sped things up. Undid collateral damage to the
   generic rwsem code - it is now untouched and independent of the RT
   code.

 - rearranged the way spinlocks interact with the RT code and cleaned 
   up the RT spinlock definitions. Found and fixed a bug in the process:
   rwlocks were dropping the BKL upon contention.

 - small x86 speedup: call __schedule not preempt_schedule_irq from
   work_resched.

 - ported PREEMPT_RT to x64. This resulted in the generalization of some
   of the x86 changes.

 - hopefully fixed fbcon kernel logging

 - hacked reiser4 to make it work on PREEMPT_REALTIME.

 - dropped the swap-layout-improvements patch. While it was working fine 
   it's not necessary for latencies anymore under the PREEMPT_REALTIME
   approach, and the swap-patch was getting intrusive.

 - fixed preemption-bug in drain_cpu_caches() on SMP [bug introduced by
   PREEMPT_REALTIME]

 - new attempt at getting rid of the networking related deadlocks

 - selinux deadlock fix and RCU-code conversion to RT semantics

to create a -V0.7.18 tree from scratch, the patching order is:

   http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
   http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc1.bz2
   http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm3/2.6.10-rc1-mm3.bz2
   http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc1-mm3-V0.7.18

	Ingo

[patch] Real-Time Preemption, -RT-2.6.10-rc1-mm3-V0.7.19

[Ingo Molnar]

i have released the -V0.7.19 Real-Time Preemption patch, which can be
downloaded from the usual place:

   http://redhat.com/~mingo/realtime-preempt/

this release includes fixes only.

Changes since -V0.7.18:

 - fixed a merge bug introduced in -V0.7.18, breaking bit-spinlocks used
   by ext3's journalling code. This could/should fix the kjournald crash
   reported by Adam Heath, Gunther Persoons and Eran Mann. Bug triggered
   on !SMP kernels only.

 - added upstream patch to fix a crash in bttv/btcx_riscmem_free(), 
   reported by Shane Shrybman.

 - made modlist_lock raw again - this could fix the /proc/acpi related
   asserts reported by Karsten Wiese.

 - fixed -RT locking bug in zap_completion_queue(), this could fix the 
   asserts reported by Shane Shrybman and others.

to create a -V0.7.19 tree from scratch, the patching order is:

   http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
   http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc1.bz2
   http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm3/2.6.10-rc1-mm3.bz2
   http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc1-mm3-V0.7.19

	Ingo

[patch] Real-Time Preemption, -RT-2.6.10-rc1-mm3-V0.7.21

[Ingo Molnar]

i have released the -V0.7.21 Real-Time Preemption patch, which can be
downloaded from the usual place:

   http://redhat.com/~mingo/realtime-preempt/

this release includes fixes and debugging-improvements.

Changes since -V0.7.20:

 - reverted the modlist_lock change - it caused more problems than it 
   solved.

 - implemented irqs-off critical section timing/tracing, inspired by the 
   positive results Thomas Gleixner got with a different kind of cli/sti
   tracer. To activate it, enable CONFIG_CRITICAL_TIMING and 
   CONFIG_CRITICAL_IRQSOFF_TIMING and cli/sti latencies will be reported
   'integrated' into the preempt on/off latencies.

 - sped up tracing in a number of ways. Performance of the tracer slowly
   eroded in the past week or two, it needed alignment and size fixes ,
   inlining/branch-prediction updates and i got rid of unnecessary code.
   The max latency is now traced in cycles - this got rid of an
   expensive 64-bit division in the fastpath. (the /proc/sys tunables
   are still in usecs so userspace should not notice anything.) It's
   still not cheap but roughly 5 times faster than -V0.7.20's tracer, on
   a fast desktop box.

 - renamed CONFIG_PREEMPT_REALTIME to CONFIG_PREEMPT_RT - it's shorter.

 - renamed CONFIG_PREEMPT_TIMING to CONFIG_CRITICAL_TIMING and 
   introduced CONFIG_CRITICAL_IRQSOFF_TIMING to enable cli/sti timing.

to create a -V0.7.21 tree from scratch, the patching order is:

   http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
   http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc1.bz2
   http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm3/2.6.10-rc1-mm3.bz2
   http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc1-mm3-V0.7.21

	Ingo

[patch] Real-Time Preemption, -RT-2.6.10-rc1-mm3-V0.7.23

[Ingo Molnar]

i have released the -V0.7.23 Real-Time Preemption patch, which can be
downloaded from the usual place:

    http://redhat.com/~mingo/realtime-preempt/

this release includes fixes, development/debugging improvements and
latency improvements and other speedups.

the biggest change is the reworked timing/tracing framework. Wakeup
timing became a compile-time thing and can be selected independently of
the preemption mode - i.e. it can now be used on near-vanilla !PREEMPT
kernels too, providing good wakeup-latency comparison of the various
preemption models.

irqs-off and preempt-off critical section timing/tracing can be selected
if wakeup timing is disabled, the two options can be selected separately
or together as well.

another improvement is that wakeup-timing now works correctly on SMP too
- the tracer 'follows' the highest-priority task in the system as it
gets bounced between CPUs and always traces the CPU where the task is
pending.

other changes since -V0.7.22:

 - semaphore livelock fix: feedback from Mark H. Johnson pinpointed a 
   bug in the down_trylock() semaphore code: if preempted in the wrong
   moment a lower-prio task could cause a higher-prio task to livelock
   indefinitely. This fix could solve the 'keventd looping' problem 
   reported by Mark.

   the fix is to make the down_trylock() code a bit simpler, but this
   also introduces the potential for down_trylock() to get 'spurious' 
   locking-rejects. Hopefully this wont be a big problem - we dont 
   really guarantee that down_trylock() succeeds - but code using higher
   semaphore counts to track resources could be negatively impacted by
   this. We'll see.

 - console assert fix: implemented a different type of fbcon
   RT-preemption handling variant, this could solve the assert reported
   by Amit Shah.

 - debugging improvement: implemented a sequence counter for max latency 
   traces. This has the advantage of solving the 'slow console on SMP
   problem': the latency-timing code used to get confused by another CPU 
   printing a timing message to a slow console and thus delaying that 
   other CPU. Now any latency that gets generated while a maximum is 
   printed is skipped.

 - further shrunk the non-debug size of struct rt_mutex by moving the 
   save_state logic into the debug paths - size is now 4 machine-words.

 - fixed CONFIG_HIGHMEM latencies: all atomic-kmap APIs are now wrapped 
   seemlessly and in a preemptible way.

 - implemented an IO-APIC register cache to speed up the IRQ-redirection
   latency hotpath. Also, made the POST flush a bit faster.

 - disable KGDB if PREEMPT_RT - it's broken for now.

 - move some runtime checks to under DEBUG_PREEMPT - this speeds up 
   CRITICAL_PREEMPT_TIMING.

to create a -V0.7.23 tree from scratch, the patching order is:

   http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
   http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc1.bz2
   http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm3/2.6.10-rc1-mm3.bz2
   http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc1-mm3-V0.7.23

	Ingo

[patch] Real-Time Preemption, -RT-2.6.10-rc1-mm3-V0.7.25-0

[Ingo Molnar]

i have released the -V0.7.25-0 Real-Time Preemption patch, which can be
downloaded from the usual place:

    http://redhat.com/~mingo/realtime-preempt/

this release includes fixes, new features and latency improvements.

the biggest change is the threading of the lone remaining non-threaded
external interrupt: the timer interrupt (IRQ#0).

It was not threaded until now because unlike device interrupts the timer
interrupt is quite deeply attached to Linux's architecture, driving
process timing, profiling and the scheduler. I separated these into
stuff that can be done from a thread context and stuff that needs to
execute directly.

Fortunately most of the expensive and latency-generating stuff could be
pushed into the irq thread. As a side-effect this enabled the turning of
rtc_lock and xtime_lock into a mutex. Also, it removed some ugly hacks
from rtc.c and should improve worst-case latencies.

the other bigger change is the reworking of the .config space. Instead
of the deep hierarchy of hard-to-understand technical PREEMPT options,
there's now a flattened out choice of 4 preemption models:

                ( ) No Forced Preemption (Server)
                ( ) Voluntary Kernel Preemption (Desktop)
                ( ) Preemptible Kernel (Low-Latency Desktop)
                (X) Complete Preemption (Real-Time)

and updated help texts. Plus for the preemption models where it can be
freely turned off, softirq and hardirq threading is an additional
option.

the third bigger change is the reworking of the tracer to make it easier
to drive it from user-space. There are 3 runtime flags now:

 /proc/sys/kernel/trace_enabled           (default: 1)
 /proc/sys/kernel/trace_user_triggered    (default: 0)
 /proc/sys/kernel/trace_freerunning       (default: 0)

semantics of user-triggered tracing: if enabled then any active tracing
of wakeup and/or critical sections stops and userspace drives start/stop
events via gettimeofday(0,1)/gettimeofday(0,0). The latter saves the
current trace into /proc/latency_trace, the former clears the trace
buffer and starts tracing anew. Doing another gettimeofday(0,1) on an
already running tracer clears the trace and restarts it without saving
the current trace into /proc/latency_trace. Doing a gettimeofday(0,0) on
an already stopped tracer has no effect (i.e. /proc/latency_trace wont
be saved a second time). The tracer does timing for userspace
automatically the same way it does it for the built-in timing
mechanisms, and it can be configured via the preempt_max_latency and
preempt_tresh tunables.

also, wakeup-timing, irq-off and preempt-off critical section timing can
now be done at once again, the /proc/sys/kernel/preempt_wakeup_timing
flag switches between the modes. (default: 1)

other changes since -V0.7.24:

 - debug feature: added the RTC-debug patch sanitized by K.R. Foley,
   plus further cleanups.

 - added upstream fix for kobject related crash, pointed out by Shane 
   Shrybman.

 - cleanup: Kconfig help text fixes from Amit Shah

 - latency improvement: on UP-IOAPIC, when redirecting an interrupt, do
   not ack the APIC. This is the method used for direct interrupts and
   on UP it might as well work out fine. It is certainly faster than
   masking/unmasking, making UP-IOAPIC the fastest PIC mode again.

 - livelock fix: the timer-irq threading unearthed a seqlock related
   livelock scenario, which triggered in do_gettimeoffset() big-time. 
   The solution is to serialize seqlock readers with writers _iff_ the 
   seqlock status is 'invalid'. This is a rare event, but when it
   happens it saves the day.

 - debugging helper: the /proc/sys/kernel/debug_direct_keyboard flag 
   (default: 0) will hack the keyboard IRQ into being direct. NOTE: the 
   keyboard in this mode should only be used to access SysRq 
   functionality that is not possible via the threaded keyboard handler. 
   The direct keyboard IRQ can crash the system.

 - new kernel profiling features: added profile=preempt to profile 
   whether interrupts hit the kernel in preemptible mode or in a 
   critical section. Added /proc/sys/kernel/prof_pid to profile a
   specific PID only. (default: -1, meaning all tasks profiled) Added
   /proc/irq/prof_cpu_mask back.

 - robustness improvement: do not report atomicity-warnings during
   kernel oopses - it's more important to get the oops out to the
   console.

to create a -V0.7.25-0 tree from scratch, the patching order is:

   http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
   http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc1.bz2
   http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm3/2.6.10-rc1-mm3.bz2
   http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc1-mm3-V0.7.25-0

	Ingo

[patch] Real-Time Preemption, -RT-2.6.10-rc1-mm3-V0.7.25-1

[Ingo Molnar]

i have released the -V0.7.25-1 Real-Time Preemption patch, which can be
downloaded from the usual place:

    http://redhat.com/~mingo/realtime-preempt/

this is a fixes-only release that resolves a couple of bugs that slipped
into -V0.7.25-0:

 - lockup/deadlock fix: make debug_direct_keyboard default to 0. It is
   only a debug helper to be used for development, it was never intended
   to be enabled. This fix should resolve the bugs reported by Gunther
   Persoons and Mark H. Johnson.

 - fix symbol export problems in rtc.ko, reported by Remi Colinet, based
   on the patch from K.R. Foley.

 - make preempt_wakeup_timing default to 1 if enabled in the .config, as 
   originally intended.

to create a -V0.7.25-1 tree from scratch, the patching order is:

   http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
   http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc1.bz2
   http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm3/2.6.10-rc1-mm3.bz2
   http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc1-mm3-V0.7.25-1

	Ingo

[patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-0

[Ingo Molnar]

i have released the -V0.7.27-0 Real-Time Preemption patch, which can be
downloaded from the usual place:

	http://redhat.com/~mingo/realtime-preempt/

this is a pure merge of -V0.7.26-5 to 2.6.10-rc2-mm1, there are no other
changes.

to create a -V0.7.27-0 tree from scratch, the patching order is:

  http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
  http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc2.bz2
  http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc2/2.6.10-rc2-mm1/2.6.10-rc2-mm1.bz2
  http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-0

	Ingo

[patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-1

[Ingo Molnar]

i have released the -V0.7.27-1 Real-Time Preemption patch, which can be
downloaded from the usual place:

	http://redhat.com/~mingo/realtime-preempt/

this quick update fixes a couple of build bugs.

Changes since a -V0.7.27-0:

 - fix iptables compilation error

 - fix selinux compilation error

to create a -V0.7.27-1 tree from scratch, the patching order is:

  http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
  http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc2.bz2
  http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc2/2.6.10-rc2-mm1/2.6.10-rc2-mm1.bz2
  http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-1

	Ingo

[patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

i have released the -V0.7.27-3 Real-Time Preemption patch, which can be
downloaded from the usual place:

	http://redhat.com/~mingo/realtime-preempt/

this is another quick update to fix a couple of bugs. Sorry about the
fast pace of updates but these fixes are worth having ASAP:

Changes since a -V0.7.27-1:

 - fix module-put BKL count bug - this could explain/fix the lockups
   reported by Rui Nuno Capela.

 - fixed a netfilter related networking deadlock reported by Mark H. 
   Johnson two weeks ago, it triggered on my testbox today. This (rare)
   bug could potentially explain some of the other lockup reports that
   are still open.

 - fix load average constant +1.0 offset when PREEMPT_RT is enabled. 
   This was an artifact of the IRQ-threading of the timer interrupt.

to create a -V0.7.27-3 tree from scratch, the patching order is:

  http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
  http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc2.bz2
  http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc2/2.6.10-rc2-mm1/2.6.10-rc2-mm1.bz2
  http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 14:40:27 +0100
Ingo Molnar <mingo@elte.hu> wrote:

 
> i have released the -V0.7.27-3 Real-Time Preemption patch, which can be
> downloaded from the usual place:
> 
> 	http://redhat.com/~mingo/realtime-preempt/
> 
> this is another quick update to fix a couple of bugs. Sorry about the
> fast pace of updates but these fixes are worth having ASAP:

Hi,

i built a 27-4 kernel and tried to boot into it. It hangs after:

Uncompressing linux.. Ok, booting the kernel

Will try plain 2.6.10-rc2-mm1 and 2.6.10-rc2

.config is here:

http://affenbande.org/~tapas/config

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 15:20:21 +0100
Florian Schmidt <mista.tapas@gmx.net> wrote:

> i built a 27-4 kernel and tried to boot into it. It hangs after:
> 
> Uncompressing linux.. Ok, booting the kernel
> 
> Will try plain 2.6.10-rc2-mm1 and 2.6.10-rc2
> 
> .config is here:
> 
> http://affenbande.org/~tapas/config

Ok, both 2.6.10-rc2 and 2.6.10-rc2-mm1 boot fine.. Rebuilding 27-4 kernel to
see if i can still reproduce above mentioned hang..

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Florian Schmidt]

On Tue, 16 Nov 2004 16:08:22 +0100
Florian Schmidt <mista.tapas@gmx.net> wrote:

> On Tue, 16 Nov 2004 15:20:21 +0100
> Florian Schmidt <mista.tapas@gmx.net> wrote:
> 
> > i built a 27-4 kernel and tried to boot into it. It hangs after:
> > 
> > Uncompressing linux.. Ok, booting the kernel
> > 
> > Will try plain 2.6.10-rc2-mm1 and 2.6.10-rc2
> > 
> > .config is here:
> > 
> > http://affenbande.org/~tapas/config
> 
> Ok, both 2.6.10-rc2 and 2.6.10-rc2-mm1 boot fine.. Rebuilding 27-4 kernel to
> see if i can still reproduce above mentioned hang..

ok, this new build still hangs at the same spot.

flo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Stefan Schweizer]

On Tue, 16 Nov 2004 16:29:24 +0100, Florian Schmidt <mista.tapas@gmx.net> wrote:
> ok, this new build still hangs at the same spot.

same problem here

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Marcos D. Marado Torres]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 16 Nov 2004, Ingo Molnar wrote:

> to create a -V0.7.27-3 tree from scratch, the patching order is:
>
>  http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2
>  http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.10-rc2.bz2
>  http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc2/2.6.10-rc2-mm1/2.6.10-rc2-mm1.bz2
>  http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3
>

root@Atlantis:/usr/src# wget http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3
- --18:43:08--  http://redhat.com/%7Emingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3
            => `realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3'
Resolving redhat.com... 209.132.177.50
Connecting to redhat.com[209.132.177.50]:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3 [following]
- --18:43:11--  http://www.redhat.com/%7Emingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3
            => `realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3'
Resolving www.redhat.com... 209.132.177.50
Connecting to www.redhat.com[209.132.177.50]:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://people.redhat.com/mingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3 [following]
- --18:43:12--  http://people.redhat.com/mingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3
            => `realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3'
Resolving people.redhat.com... 66.187.233.237
Connecting to people.redhat.com[66.187.233.237]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
18:43:12 ERROR 404: Not Found.


Mind Booster Noori

- -- 
/* *************************************************************** */
    Marcos Daniel Marado Torres	     AKA	Mind Booster Noori
    http://student.dei.uc.pt/~marado   -	  marado@student.dei.uc.pt
    () Join the ASCII ribbon campaign against html email, Microsoft
    /\ attachments and Software patents.   They endanger the World.
    Sign a petition against patents:  http://petition.eurolinux.org
/* *************************************************************** */
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFBmkpqmNlq8m+oD34RAv3VAJ0Xk4PVQuKmxbWGS9BKCyTj/b3pUACg7H5W
hvMBsDXBU/3xSOJOI4jU7fA=
=AyKN
-----END PGP SIGNATURE-----

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Lee Revell]

On Tue, 2004-11-16 at 18:43 +0000, Marcos D. Marado Torres wrote:
> HTTP request sent, awaiting response... 404 Not Found
> 18:43:12 ERROR 404: Not Found.

Usually means a bug was found and Ingo is uploading a new version.

Lee

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Ingo Molnar]

* Marcos D. Marado Torres <marado@student.dei.uc.pt> wrote:

> root@Atlantis:/usr/src# wget 
> http://redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.10-rc2-mm1-V0.7.27-3

> 18:43:12 ERROR 404: Not Found.

yes. If you get a 404 then a newer patch has been uploaded - check the
home directory for the latest patch. Old patches are in the older/
subdirectory.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.27-3

[Bill Huey]

[-- Attachment #1: Type: text/plain, Size: 234 bytes --]

On Tue, Nov 16, 2004 at 02:40:27PM +0100, Ingo Molnar wrote:
> i have released the -V0.7.27-3 Real-Time Preemption patch, which can be
> downloaded from the usual place:

Against some version of V0.7.25... that I just deleted.

bill


[-- Attachment #2: t --]
[-- Type: application/x-troff, Size: 42963 bytes --]