Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Mark_H_Johnson]

>i've uploaded a fixed kernel (-V0.6.8) to:
>
>  http://redhat.com/~mingo/realtime-preempt/

This build appears to run OK and then in the middle of the real time
tests stops doing useful work (during network test).

 - can move mouse & switch displays
 - script checking latency hangs (no errors, apparently stuck in sleep)
 - ps is OK, but top does not work (no display, Ctrl-C gives prompt again)
 - cannot ping the test system from another system (don't get the "no route
message, just no response)
 - Alt-SysRq keys still work
 - eventually the mouse would not switch displays

Rebooted with Alt-SysRq-B.

Sending serial console results separately.
  --Mark

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

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

> This build appears to run OK and then in the middle of the real time
> tests stops doing useful work (during network test).

weird, the deadlock detector did not trigger, although it is a clear
circular deadlock:

R     ksoftirqd/0/    3 [dffe8020, 105] blocked on: [dfcafc20] {r:0,a:-1,&((sk)->sk_lock.slock)}
.. held by:               rcp/ 4791 [d84bd910, 118]
... acquired at:  ip_send_reply+0x12b/0x250

D             rcp/ 4791 [d84bd910, 118] blocked on: [c03cb900] {r:0,a:-1,ptype_lock}
.. held by:       ksoftirqd/0/    3 [dffe8020, 105]
... acquired at:  netif_receive_skb+0xae/0x330

i.e. ksoftirqd blocked on rcp and rcp blocked on ksoftirqd, cleanly
deadlocking each other.

anyway, does the patch below, ontop of -V0.6.8, fix this type of hang?

	Ingo

--- linux/net/core/dev.c.orig
+++ linux/net/core/dev.c
@@ -1916,7 +1916,9 @@ static void net_rx_action(struct softirq
 		dev = list_entry(queue->poll_list.next,
 				 struct net_device, poll_list);
 
+		rcu_read_lock_read(&ptype_lock);
 		if (dev->quota <= 0 || dev->poll(dev, &budget)) {
+			rcu_read_unlock_read(&ptype_lock);
 			local_irq_disable();
 			list_del(&dev->poll_list);
 			list_add_tail(&dev->poll_list, &queue->poll_list);
@@ -1926,6 +1928,7 @@ static void net_rx_action(struct softirq
 				dev->quota = dev->weight;
 		} else {
 			dev_put(dev);
+			rcu_read_unlock_read(&ptype_lock);
 			local_irq_disable();
 		}
 

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> > This build appears to run OK and then in the middle of the real time
> > tests stops doing useful work (during network test).
> 
> weird, the deadlock detector did not trigger, although it is a clear
> circular deadlock:

ah ... found it - a fair portion of spinlocks and rwlocks had deadlock
detection turned off in -V0.6.6 - amongst them ptype_lock. I've uploaded
-V0.6.9 that fixes this.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[K.R. Foley]

Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> 
>>>This build appears to run OK and then in the middle of the real time
>>>tests stops doing useful work (during network test).
>>
>>weird, the deadlock detector did not trigger, although it is a clear
>>circular deadlock:
> 
> 
> ah ... found it - a fair portion of spinlocks and rwlocks had deadlock
> detection turned off in -V0.6.6 - amongst them ptype_lock. I've uploaded
> -V0.6.9 that fixes this.
> 
> 	Ingo
> 
I probably shouldn't say this, but I have yet to have -V0.6.9 die on me. 
And at least right now, the peppiness is back in the X interface, the 
menus, etc.

kr

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.9

[Rui Nuno Capela]

Ingo Molnar wrote:
>
> ah ... found it - a fair portion of spinlocks and rwlocks had deadlock
> detection turned off in -V0.6.6 - amongst them ptype_lock. I've uploaded
> -V0.6.9 that fixes this.
>

OK. Already tested RT-V0.6.9 and things are really good, so far. Got it
under the jackd-R + 9*fluidsynth workload test, and the comparison to
2.6.9 (vanilla) is getting kind of humiliating :)

                                   2.6.9   RT-V0.6.9
                                 --------- ---------
 XRUN Rate   . . . . . . . . . :    415         0    /hour
 Delay Rate (>spare time)  . . :    493         0    /hour
 Delay Rate (>1000 usecs)  . . :    913         1    /hour
 Delay Maximum . . . . . . . . :   6877       864    usecs
 Cycle Maximum . . . . . . . . :   1440      1552    usecs
 Average DSP Load. . . . . . . :     38.9      40.5  %
 Average Interrupt Rate  . . . :   1337      1338    /sec
 Average Context-Switch Rate . :   7488      9048    /sec

As before, these stats were taken by running jackd -v -dalsa -dhw:0
-r44100 -p128 -n2 -S -P, loaded with 9 (nine) fluidsynth instances, on a
P4@2.533Ghz laptop, against the onboard sound device (snd-ali5451).
The results were averaged for 12 consecutive runs of 5 minutes each.

On the RT kernel, the IRQ 5 handler thread, that serves the ali5451 sound
device, has been chrt'ed to SCHED_FIFO and to priority=60 (chrt -p -f 60
`pidof "IRQ 5"`). This time thought, I haven't touched the ksoftirqd/0
scheduling policy nor priority.

I am also rehearsing these same tests on my P4/SMT desktop. I'll post
those a bit later today.

As a personal comment, I've never, never seen so good figures in any other
kernel I've came across in the last couple of years. I hope this can only
go to the better ;)

See ya.
-- 
rncbc aka Rui Nuno Capela
rncbc@rncbc.org

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.9

[Bill Huey]

On Tue, Nov 02, 2004 at 11:21:43PM -0000, Rui Nuno Capela wrote:
> As a personal comment, I've never, never seen so good figures in any other
> kernel I've came across in the last couple of years. I hope this can only
> go to the better ;)

Hard RT guarantees is the goal of this project afterall. It's absolutely
going to happen. You can bet on it.

bill

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.9

[Rui Nuno Capela]

Rui Nuno Capela wrote:
>
> I am also rehearsing these same tests on my P4/SMT desktop.
> I'll post those a bit later today.
>

So here they are. This machine is a P4 2.80C@3.366GHz, HT enabled on a
Asus P4P800 mobo, Intel 82801EB onboard sound device (snd-intel8x0).

                                   2.6.9smp   RT-V0.6.9smp
                                 ------------ ------------
 XRUN Rate   . . . . . . . . . :       0            0      /hour
 Delay Rate (>spare time)  . . :       0            0      /hour
 Delay Rate (>1000 usecs)  . . :       0            0      /hour
 Delay Maximum . . . . . . . . :     346          166      usecs
 Cycle Maximum . . . . . . . . :     986         1028      usecs
 Average DSP Load. . . . . . . :      25.0         25.7    %
 Average Interrupt Rate  . . . :    1717         1718      /sec
 Average Context-Switch Rate . :   10082        15793      /sec

As you can see, the results here aren't so disparate as on my UP laptop.

I guess that I can stress this out and lower the period size on jackd -R,
to -p64. And even increase the workload with more client instances (from 9
to 18 ?) to let the RT show it's potential, if that makes sense at all.

Bye now.
-- 
rncbc aka Rui Nuno Capela
rncbc@rncbc.org

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.9

[Ingo Molnar]

* Rui Nuno Capela <rncbc@rncbc.org> wrote:

> Rui Nuno Capela wrote:
> >
> > I am also rehearsing these same tests on my P4/SMT desktop.
> > I'll post those a bit later today.
> >
> 
> So here they are. This machine is a P4 2.80C@3.366GHz, HT enabled on a
> Asus P4P800 mobo, Intel 82801EB onboard sound device (snd-intel8x0).
> 
>                                    2.6.9smp   RT-V0.6.9smp
>                                  ------------ ------------
>  XRUN Rate   . . . . . . . . . :       0            0      /hour
>  Delay Rate (>spare time)  . . :       0            0      /hour
>  Delay Rate (>1000 usecs)  . . :       0            0      /hour
>  Delay Maximum . . . . . . . . :     346          166      usecs
>  Cycle Maximum . . . . . . . . :     986         1028      usecs
>  Average DSP Load. . . . . . . :      25.0         25.7    %
>  Average Interrupt Rate  . . . :    1717         1718      /sec
>  Average Context-Switch Rate . :   10082        15793      /sec
> 
> As you can see, the results here aren't so disparate as on my UP
> laptop.

i suspect it has to do with the different load - the UP laptop had 40%
utilization, this box is 25% utilized.

> I guess that I can stress this out and lower the period size on jackd
> -R, to -p64. And even increase the workload with more client instances
> (from 9 to 18 ?) to let the RT show it's potential, if that makes
> sense at all.

yeah, it would really be nice to see how much it can take and to see the
point where the -RT kernel starts to suffer from xruns too.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.9

[Ingo Molnar]

* Rui Nuno Capela <rncbc@rncbc.org> wrote:

> OK. Already tested RT-V0.6.9 and things are really good, so far. Got
> it under the jackd-R + 9*fluidsynth workload test, and the comparison
> to 2.6.9 (vanilla) is getting kind of humiliating :)
> 
>                                    2.6.9   RT-V0.6.9
>                                  --------- ---------
>  XRUN Rate   . . . . . . . . . :    415         0    /hour
>  Delay Rate (>spare time)  . . :    493         0    /hour
>  Delay Rate (>1000 usecs)  . . :    913         1    /hour
>  Delay Maximum . . . . . . . . :   6877       864    usecs
>  Cycle Maximum . . . . . . . . :   1440      1552    usecs
>  Average DSP Load. . . . . . . :     38.9      40.5  %
>  Average Interrupt Rate  . . . :   1337      1338    /sec
>  Average Context-Switch Rate . :   7488      9048    /sec

cool, good numbers. May i have a stats suggestion for future runs? Could
you monitor the system (kernel) CPU overhead and userspace overhead as
well?

> As before, these stats were taken by running jackd -v -dalsa -dhw:0
> -r44100 -p128 -n2 -S -P, loaded with 9 (nine) fluidsynth instances, on
> a P4@2.533Ghz laptop, against the onboard sound device (snd-ali5451).
> The results were averaged for 12 consecutive runs of 5 minutes each.
> 
> On the RT kernel, the IRQ 5 handler thread, that serves the ali5451
> sound device, has been chrt'ed to SCHED_FIFO and to priority=60 (chrt
> -p -f 60 `pidof "IRQ 5"`). This time thought, I haven't touched the
> ksoftirqd/0 scheduling policy nor priority.
> 
> I am also rehearsing these same tests on my P4/SMT desktop. I'll post
> those a bit later today.
> 
> As a personal comment, I've never, never seen so good figures in any
> other kernel I've came across in the last couple of years. I hope this
> can only go to the better ;)

i hope so too :) There's no reason why the performance of the current
-RT kernel couldnt be maintained, there are no corners cut.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Fernando Pablo Lopez-Lezcano]

On Tue, 2004-11-02 at 11:27, Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
> > > This build appears to run OK and then in the middle of the real time
> > > tests stops doing useful work (during network test).
> > 
> > weird, the deadlock detector did not trigger, although it is a clear
> > circular deadlock:
> 
> ah ... found it - a fair portion of spinlocks and rwlocks had deadlock
> detection turned off in -V0.6.6 - amongst them ptype_lock. I've uploaded
> -V0.6.9 that fixes this.

This happens with V0.6.9 running on an Athlon64:

r8169 Gigabit Ethernet driver 1.6LK loaded
ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 16 (level, low) -> IRQ 16
divert: allocating divert_blk for eth0
eth0: Identified chip type is 'RTL8169s/8110s'.
eth0: RTL8169 at 0xf88a0f00, 00:0c:76:b3:c2:43, IRQ 16
BUG: atomic counter underflow at:
 [<c0108153>] dump_stack+0x23/0x30 (20)
 [<c02f5e91>] qdisc_destroy+0xe1/0xf0 (28)
 [<c02f60ad>] dev_shutdown+0x3d/0xa0 (28)
 [<c02e6ffb>] unregister_netdevice+0x12b/0x2a0 (36)
 [<c0273ffe>] unregister_netdev+0x1e/0x30 (16)
 [<f8b0b8b5>] rtl8169_remove_one+0x25/0x50 [r8169] (32)
 [<c01f55a6>] pci_device_remove+0x76/0x80 (24)
 [<c025f15d>] device_release_driver+0x6d/0x70 (24)
 [<c025f18b>] driver_detach+0x2b/0x40 (20)
 [<c025f5ff>] bus_remove_driver+0x3f/0x70 (20)
 [<c025fb0c>] driver_unregister+0x1c/0x30 (16)
 [<c01f586c>] pci_unregister_driver+0x1c/0x30 (16)
 [<f8b0d357>] rtl8169_cleanup_module+0x17/0x1b [r8169] (12)
 [<c013fdb1>] sys_delete_module+0x121/0x150 (96)
 [<c010729d>] sysenter_past_esp+0x52/0x71 (-8124)
---------------------------
| preempt count: 00000001 ]
| 1-level deep critical section nesting:
----------------------------------------
.. [<c013dc3d>] .... print_traces+0x1d/0x60
.....[<c0108153>] ..   ( <= dump_stack+0x23/0x30)
                                                                                
divert: freeing divert_blk for eth0
ip_tables: (C) 2000-2002 Netfilter core team

-- Fernando

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[K.R. Foley]

Fernando Pablo Lopez-Lezcano wrote:
> On Tue, 2004-11-02 at 11:27, Ingo Molnar wrote:
> 
>>* Ingo Molnar <mingo@elte.hu> wrote:
>>
>>>>This build appears to run OK and then in the middle of the real time
>>>>tests stops doing useful work (during network test).
>>>
>>>weird, the deadlock detector did not trigger, although it is a clear
>>>circular deadlock:
>>
>>ah ... found it - a fair portion of spinlocks and rwlocks had deadlock
>>detection turned off in -V0.6.6 - amongst them ptype_lock. I've uploaded
>>-V0.6.9 that fixes this.
> 
> 
> This happens with V0.6.9 running on an Athlon64:
> 
> r8169 Gigabit Ethernet driver 1.6LK loaded
> ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 16 (level, low) -> IRQ 16
> divert: allocating divert_blk for eth0
> eth0: Identified chip type is 'RTL8169s/8110s'.
> eth0: RTL8169 at 0xf88a0f00, 00:0c:76:b3:c2:43, IRQ 16
> BUG: atomic counter underflow at:
>  [<c0108153>] dump_stack+0x23/0x30 (20)
>  [<c02f5e91>] qdisc_destroy+0xe1/0xf0 (28)
>  [<c02f60ad>] dev_shutdown+0x3d/0xa0 (28)
>  [<c02e6ffb>] unregister_netdevice+0x12b/0x2a0 (36)
>  [<c0273ffe>] unregister_netdev+0x1e/0x30 (16)
>  [<f8b0b8b5>] rtl8169_remove_one+0x25/0x50 [r8169] (32)
>  [<c01f55a6>] pci_device_remove+0x76/0x80 (24)
>  [<c025f15d>] device_release_driver+0x6d/0x70 (24)
>  [<c025f18b>] driver_detach+0x2b/0x40 (20)
>  [<c025f5ff>] bus_remove_driver+0x3f/0x70 (20)
>  [<c025fb0c>] driver_unregister+0x1c/0x30 (16)
>  [<c01f586c>] pci_unregister_driver+0x1c/0x30 (16)
>  [<f8b0d357>] rtl8169_cleanup_module+0x17/0x1b [r8169] (12)
>  [<c013fdb1>] sys_delete_module+0x121/0x150 (96)
>  [<c010729d>] sysenter_past_esp+0x52/0x71 (-8124)
> ---------------------------
> | preempt count: 00000001 ]
> | 1-level deep critical section nesting:
> ----------------------------------------
> .. [<c013dc3d>] .... print_traces+0x1d/0x60
> .....[<c0108153>] ..   ( <= dump_stack+0x23/0x30)
>                                                                                 
> divert: freeing divert_blk for eth0
> ip_tables: (C) 2000-2002 Netfilter core team
> 
> -- Fernando
> 
> 
> 
Several of us get this. I believe this bug exists in upstream kernels 
also, it just doesn't get caught without the detection Ingo has added.

kr

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Mark_H_Johnson]

>Does this also happen if you chrt ksoftirqd to FIFO prio 1?
>Does the 'LOC' count increase for both cpus in /proc/interrupts?

With -V0.6.9, I got some slightly different symptoms. I did the change
chrt change (though I looked up the PID by hand, my attempt to use
pidof with 'ksoftirqd/0' did not work).

The LOC count did increase on both CPU's during my test (up until
I got the deadlock listed below). I also noticed that almost all
interrupts were processed by CPU0; should have checked before starting
the real time test to see if that was consistent when the system
was idle. I was about to send you a message from the test system with
that data when the system locked up.

The crash sequence was...

 - boot to single user (uneventful)
 - telnet 5 (uneventful)
 - X and top tests (uneventful)
 - network test started (and did not finish)
 - 2343 usec latency dumped
 - 55962 usec latency dumped
 - 74229 usec latency dumped
 - 83374 usec latency dumped
 - deadlock
 - long string of other BUG messages

I tried to Sync & reboot with Alt-SysRq keys at this point and was
unable to do so. Hard reset to reboot. Serial console output to
follow separately.
  --Mark

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

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

> The crash sequence was...
> 
>  - boot to single user (uneventful)
>  - telnet 5 (uneventful)
>  - X and top tests (uneventful)
>  - network test started (and did not finish)
>  - 2343 usec latency dumped
>  - 55962 usec latency dumped
>  - 74229 usec latency dumped
>  - 83374 usec latency dumped
>  - deadlock

yeah, this is yet another networking deadlock, nicely detected and
logged. Since the deadlock locks up ksoftirqd, timer handling (also
driven by ksoftirqd) wont work - i think this explains the followup
symptoms you got.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> yeah, this is yet another networking deadlock, nicely detected and
> logged. Since the deadlock locks up ksoftirqd, timer handling (also
> driven by ksoftirqd) wont work - i think this explains the followup
> symptoms you got.

the patch below should fix this deadlock but there might be others
around ...

	Ingo

--- linux/include/net/sock.h.orig2	
+++ linux/include/net/sock.h	
@@ -706,8 +706,8 @@ extern void FASTCALL(lock_sock(struct so
 extern void FASTCALL(release_sock(struct sock *sk));
 
 /* BH context may only use the following locking interface. */
-#define bh_lock_sock(__sk)	spin_lock(&((__sk)->sk_lock.slock))
-#define bh_unlock_sock(__sk)	spin_unlock(&((__sk)->sk_lock.slock))
+#define bh_lock_sock(__sk)	do { rcu_read_lock_read(&ptype_lock); spin_lock(&((__sk)->sk_lock.slock)); } while (0)
+#define bh_unlock_sock(__sk)	do { spin_unlock(&((__sk)->sk_lock.slock)); rcu_read_unlock_read(&ptype_lock); } while (0)
 
 extern struct sock *		sk_alloc(int family, int priority, int zero_it,
 					 kmem_cache_t *slab);

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> > yeah, this is yet another networking deadlock, nicely detected and
> > logged. Since the deadlock locks up ksoftirqd, timer handling (also
> > driven by ksoftirqd) wont work - i think this explains the followup
> > symptoms you got.
> 
> the patch below should fix this deadlock but there might be others
> around ...

the patch doesnt work. Working on a better solution.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

> > the patch below should fix this deadlock but there might be others
> > around ...
> 
> the patch doesnt work. Working on a better solution.

this hopefully better solution is included in -V0.7.1.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Florian Schmidt]

On Wed, 3 Nov 2004 13:39:35 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> 
> > > the patch below should fix this deadlock but there might be others
> > > around ...
> > 
> > the patch doesnt work. Working on a better solution.
> 
> this hopefully better solution is included in -V0.7.1.

Hi, 

i tried V0.7.7 and since all other RP kernels locked for me in X, i decided
to go to the console and try to see if i get some debugging output. Well i
put the usual stress on the system but besides some higher rtc_wakeup
jitters [up to 60%] which didn't show during the earlier runs that locked
when in X, the system ran fine. i wasn't able to lock the system from within
the console (X was started but idling at gdm).

Ok, so i suspected, maybe the locks i see got to do with X, so i changed to
the X console, logged in and quicklky switched back to the console. and no
surprise 10seconds later or so it locked (i suppose gnome was still loading
at that point in time). Without any console output. Does it matter which
virtual text console one is on? i thought not.

anyways. i might just get myself a serial console in a few days (old pc
froma buddy). but i thought a serial console would be mostly useful to
capture more of the debug messages. if none shows at all it won't help
either right?

flo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Adam Heath]

On Wed, 3 Nov 2004, Florian Schmidt wrote:

> i tried V0.7.7 ...

I can't use 0.7.7.  I have the known problem with ide+lvm.  Backing out
dio-handle-eof.patch fixes it for me, at least on 2.6.9-mm1.  Haven't tried
against 2.6.10-rc1-mm2(which is still broken).

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Mark_H_Johnson]

>was this already in the default bootup, or only after the crash
>happened?
Not quite a "crash", but definitely after I noticed the system no
longer doing any useful work. As I said before, it was as if anything
to do with timers was not working (e.g., sleep 1s).

>Does this also happen if you chrt ksoftirqd to FIFO prio 1?
>Does the 'LOC' count increase for both cpus in /proc/interrupts?

It will be an hour or so before I can try either of these,
I have a build in progress. I can check both of these with the new
build (or the old one if you want that too).

  --Mark

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Mark_H_Johnson]

>hm, this one is an extremely weird deadlock - the NMI watchdog detected
>a _user-space_ deadlock - i.e. the "cpu_burn" user-space code disabled
>interrupts for more than ~5 seconds? Sounds quite unlikely and the
>EFLAGS register also directly contradicts it, it has 0x200 set so
>interrupts are enabled!

Very unlikely - cpu_burn.c (all of it...)

int main() {
  while (1) {  }
  return 1;
}

No - it did not disable interrupts.

>The only other way for the NMI watchdog to
>trigger is if for whatever reason the local APIC timer interrupts are
>not getting through and the NMI ticks (which come via a different
>interrupt pin) get through.

The other symptoms I was seeing appeared to be timer related
 - never returned from "sleep 1s" in the shell script
 - "ps -fe" worked fine, but "top" did not
You may be on to something here.

  --Mark

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

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

> >The only other way for the NMI watchdog to
> >trigger is if for whatever reason the local APIC timer interrupts are
> >not getting through and the NMI ticks (which come via a different
> >interrupt pin) get through.
> 
> The other symptoms I was seeing appeared to be timer related
>  - never returned from "sleep 1s" in the shell script
>  - "ps -fe" worked fine, but "top" did not
> You may be on to something here.

was this already in the default bootup, or only after the crash
happened? Does this also happen if you chrt ksoftirqd to FIFO prio 1? 
Does the 'LOC' count increase for both cpus in /proc/interrupts?

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Mark_H_Johnson]

>i've uploaded a fixed kernel (-V0.6.8) to:
>
>  http://redhat.com/~mingo/realtime-preempt/

OK. Will step up shortly but have some test results from -V0.6.7
that I just collected. The system crashed with LOCKUP messages during
both runs but I did get some real time tests run. No build problems.

First run

[1] boot to single user was uneventful.

[2] telinit 5 was also OK, no atomic underflow warnings.

[3] Logged in, set up my RT settings (udma2, IRQ priorities) and
did a quick sample of wakeup timing. Still appear to have the false
positives, even on an otherwise idle system. For example:

(get_ltrace.sh/3502/CPU#0): new 936 us maximum-latency wakeup.
(kdeinit/3198/CPU#0): new 971 us maximum-latency wakeup.
(cat/3504/CPU#0): new 1776 us maximum-latency wakeup.
(cat/3504/CPU#0): new 5286 us maximum-latency wakeup.
(cat/3504/CPU#0): new 71828 us maximum-latency wakeup.
(cupsd/2061/CPU#1): new 341 us maximum-latency wakeup.
(ksoftirqd/0/3/CPU#0): new 64940 us maximum-latency wakeup.
(get_ltrace.sh/3554/CPU#1): new 1299 us maximum-latency wakeup.
(cat/3556/CPU#1): new 4361 us maximum-latency wakeup.
(cat/3556/CPU#1): new 68847 us maximum-latency wakeup.
(get_ltrace.sh/3582/CPU#1): new 963 us maximum-latency wakeup.
(cat/3584/CPU#1): new 2273 us maximum-latency wakeup.
(cat/3584/CPU#1): new 66211 us maximum-latency wakeup.

At this point, the system locked up and a little bit later dumped
a LOCKUP on the serial console (at end of message).

Second run.

[1] Booting to single user and telinit 5 was uneventful.

[2] Logged in and used
  echo 0 > /proc/sys/kernel/preempt_wakeup_timing
to go back to tracking the long latency locks. Set up RT environment
as well.

[3] Started to collect latency timing data; no false positives during
a few minutes of "idle" time.

[4] Started the real time stress test.
 - X - data looks generally OK with huge (max 13 msec) spikes near
the start and end.
 - top - data is noisy; had a number of periods (up to 1 second) where
the CPU loop was delayed up to a millisecond or so (about 100% overhead)
and some spikes even longer than above (max 22 msec).
 - network output - machine crashed again, a similar lockup problem
to the first run. (dump at end of message)

Something I noticed during these runs. If I moved the mouse up / down, the
audio seemed to change (slightly lower tone). Mouse movements left / right
did not seem to cause such a noticeable change. This may be related to the
spikes in the measured top stress test.

  --Mark

First LOCKUP

NMI Watchdog detected LOCKUP
Pid: 3933, comm:             cpu_burn
EIP: 0073:[<08048340>] CPU: 0
EIP is at 0x8048340
 ESP: 007b:bffffa40 EFLAGS: 00200282    Not tainted  (2.6.9-mm1-RT-V0.6.7)
EAX: 00000000 EBX: 00711ffc ECX: bffffadc EDX: bffffad4
ESI: 00000001 EDI: 007140fc EBP: bffffa48 DS: 007b ES: 007b
CR0: 8005003b CR2: 00681400 CR3: 015735e0 CR4: 000006f0
 [<c0105bec>] show_regs+0x14c/0x174 (36)
 [<c0115f4f>] nmi_watchdog_tick+0x12f/0x140 (28)
 [<c0109c0c>] default_do_nmi+0x6c/0x110 (96)
 [<c0109d2d>] do_nmi+0x6d/0x70 (24)
 [<c0108735>] nmi_stack_correct+0x1e/0x2e (-196314476)
---------------------------
| preempt count: 00010002 ]
| 2-level deep critical section nesting:
----------------------------------------
.. [<c0326a8f>] .... _spin_lock+0x1f/0x70
.....[<c0115f47>] ..   ( <= nmi_watchdog_tick+0x127/0x140)
.. [<c013d7dd>] .... print_traces+0x1d/0x60
.....[<c0105bec>] ..   ( <= show_regs+0x14c/0x174)

 on CPU1, eip c013be90, registers:
Modules linked in: snd_pcm_oss snd_mixer_oss snd_ens1371 snd_rawmidi
snd_seq_d
evice snd_ac97_codec snd_pcm snd_timer snd_page_alloc gameport snd
soundcore ipv
6 parport_pc lp parport autofs4 sunrpc 8139too mii floppy sg scsi_mod
microcode
dm_mod uhci_hcd ext3 jbd
CPU:    1
EIP:    0060:[<c013be90>]    Not tainted VLI
EFLAGS: 00200002   (2.6.9-mm1-RT-V0.6.7)
EIP is at ___trace+0x40/0x170
eax: 00017780   ebx: c0445180   ecx: c01e24ea   edx: c0326a81
esi: 00000001   edi: 00200002   ebp: cad35d48   esp: cad35d18
ds: 007b   es: 007b   ss: 0068   preempt: 00010004
Process sleep (pid: 4185, threadinfo=cad34000 task=cb3c2a90)
Stack: c0109cc0 00200002 cad35d54 c0372424 00200002 cad35d44 c0109d2d
cad34000

       c0372420 c0372424 cb3c2a90 00200046 cad35d58 c013bfed c0326a81
c01e2308
       cad35d6c c0114fd8 00000003 c01e24ea c0372428 cad35d80 c0326a81
00000001

Call Trace:
 [<c0108a1f>] show_stack+0x8f/0xb0 (28)
 [<c0108bdf>] show_registers+0x16f/0x1e0 (56)
 [<c0109b5f>] die_nmi+0x5f/0xa0 (24)
 [<c0115f0f>] nmi_watchdog_tick+0xef/0x140 (28)
 [<c0109c0c>] default_do_nmi+0x6c/0x110 (96)
 [<c0109d2d>] do_nmi+0x6d/0x70 (24)
 [<c0108735>] nmi_stack_correct+0x1e/0x2e (116)
 [<c013bfed>] __mcount+0x1d/0x30 (16)
 [<c0114fd8>] mcount+0x14/0x18 (20)
 [<c0326a81>] _spin_lock+0x11/0x70 (20)
 [<c01e2308>] _down_write_trylock+0x58/0x290 (52)
 [<c01e3325>] down_trylock+0x45/0x180 (52)
 [<c0123f95>] vprintk+0xf5/0x170 (36)
 [<c0123e8d>] printk+0x1d/0x30 (16)
 [<c0108945>] show_trace+0x95/0xe0 (32)
 [<c0108a63>] dump_stack+0x23/0x30 (20)
 [<c013c98e>] check_preempt_timing+0x16e/0x300 (76)
 [<c013ce7f>] sub_preempt_count+0x7f/0xf0 (32)
 [<c01147ba>] flush_tlb_mm+0x5a/0x110 (36)
 [<c015965e>] unmap_vmas+0x10e/0x1c0 (56)
 [<c015e60c>] exit_mmap+0x5c/0x130 (56)
 [<c0120c39>] mmput+0x49/0x160 (28)
 [<c0126bf3>] do_exit+0x183/0x5c0 (40)
 [<c0127170>] do_group_exit+0x40/0xe0 (40)
 [<c0107b89>] sysenter_past_esp+0x52/0x71 (-8124)
---------------------------
| preempt count: 00010005 ]
| 5-level deep critical section nesting:
----------------------------------------
.. [<c0114783>] .... flush_tlb_mm+0x23/0x110
.....[<c015965e>] ..   ( <= unmap_vmas+0x10e/0x1c0)
.. [<c0326aff>] .... _spin_lock_irqsave+0x1f/0x80
.....[<c0123ecb>] ..   ( <= vprintk+0x2b/0x170)
.. [<c0326a8f>] .... _spin_lock+0x1f/0x70
.....[<c01e24ea>] ..   ( <= _down_write_trylock+0x23a/0x290)
.. [<c0326a8f>] .... _spin_lock+0x1f/0x70
.....[<c0109b22>] ..   ( <= die_nmi+0x22/0xa0)
.. [<c013d7dd>] .... print_traces+0x1d/0x60
.....[<c0108a1f>] ..   ( <= show_stack+0x8f/0xb0)

Code: b8 00 e0 ff ff 89 fe c1 ee 09 21 e0 89 45 ec 83 f6 01 8b 40 10 83 e6
01
69 c0 80 77 01 00 8d 98 00 da 42 c0 f0 ff 80 00 da 42 c0 <8b> 80 00 da 42
c0 48
74 0d f0 ff 0b 57 9d 83 c4 24 5b 5e 5f 5d
console shuts up ...


Second LOCKUP

NMI Watchdog detected LOCKUP
Pid: 3933, comm:             cpu_burn
EIP: 0073:[<08048340>] CPU: 0
EIP is at 0x8048340
 ESP: 007b:bffffa40 EFLAGS: 00200282    Not tainted  (2.6.9-mm1-RT-V0.6.7)
EAX: 00000000 EBX: 00711ffc ECX: bffffadc EDX: bffffad4
ESI: 00000001 EDI: 007140fc EBP: bffffa48 DS: 007b ES: 007b
CR0: 8005003b CR2: 00681400 CR3: 015735e0 CR4: 000006f0
 [<c0105bec>] show_regs+0x14c/0x174 (36)
 [<c0115f4f>] nmi_watchdog_tick+0x12f/0x140 (28)
 [<c0109c0c>] default_do_nmi+0x6c/0x110 (96)
 [<c0109d2d>] do_nmi+0x6d/0x70 (24)
 [<c0108735>] nmi_stack_correct+0x1e/0x2e (-196314476)
---------------------------
| preempt count: 00010002 ]
| 2-level deep critical section nesting:
----------------------------------------
.. [<c0326a8f>] .... _spin_lock+0x1f/0x70
.....[<c0115f47>] ..   ( <= nmi_watchdog_tick+0x127/0x140)
.. [<c013d7dd>] .... print_traces+0x1d/0x60
.....[<c0105bec>] ..   ( <= show_regs+0x14c/0x174)

 on CPU1, eip c013be90, registers:
Modules linked in: snd_pcm_oss snd_mixer_oss snd_ens1371 snd_rawmidi
snd_seq_d
evice snd_ac97_codec snd_pcm snd_timer snd_page_alloc gameport snd
soundcore ipv
6 parport_pc lp parport autofs4 sunrpc 8139too mii floppy sg scsi_mod
microcode
dm_mod uhci_hcd ext3 jbd
CPU:    1
EIP:    0060:[<c013be90>]    Not tainted VLI
EFLAGS: 00200002   (2.6.9-mm1-RT-V0.6.7)
EIP is at ___trace+0x40/0x170
eax: 00017780   ebx: c0445180   ecx: c01e24ea   edx: c0326a81
esi: 00000001   edi: 00200002   ebp: cad35d48   esp: cad35d18
ds: 007b   es: 007b   ss: 0068   preempt: 00010004
Process sleep (pid: 4185, threadinfo=cad34000 task=cb3c2a90)
Stack: c0109cc0 00200002 cad35d54 c0372424 00200002 cad35d44 c0109d2d
cad34000

       c0372420 c0372424 cb3c2a90 00200046 cad35d58 c013bfed c0326a81
c01e2308

       cad35d6c c0114fd8 00000003 c01e24ea c0372428 cad35d80 c0326a81
00000001

Call Trace:
 [<c0108a1f>] show_stack+0x8f/0xb0 (28)
 [<c0108bdf>] show_registers+0x16f/0x1e0 (56)
 [<c0109b5f>] die_nmi+0x5f/0xa0 (24)
 [<c0115f0f>] nmi_watchdog_tick+0xef/0x140 (28)
 [<c0109c0c>] default_do_nmi+0x6c/0x110 (96)
 [<c0109d2d>] do_nmi+0x6d/0x70 (24)
 [<c0108735>] nmi_stack_correct+0x1e/0x2e (116)
 [<c013bfed>] __mcount+0x1d/0x30 (16)
 [<c0114fd8>] mcount+0x14/0x18 (20)
 [<c0326a81>] _spin_lock+0x11/0x70 (20)
 [<c01e2308>] _down_write_trylock+0x58/0x290 (52)
 [<c01e3325>] down_trylock+0x45/0x180 (52)
 [<c0123f95>] vprintk+0xf5/0x170 (36)
 [<c0123e8d>] printk+0x1d/0x30 (16)
 [<c0108945>] show_trace+0x95/0xe0 (32)
 [<c0108a63>] dump_stack+0x23/0x30 (20)
 [<c013c98e>] check_preempt_timing+0x16e/0x300 (76)
 [<c013ce7f>] sub_preempt_count+0x7f/0xf0 (32)
 [<c01147ba>] flush_tlb_mm+0x5a/0x110 (36)
 [<c015965e>] unmap_vmas+0x10e/0x1c0 (56)
 [<c015e60c>] exit_mmap+0x5c/0x130 (56)
 [<c0120c39>] mmput+0x49/0x160 (28)
 [<c0126bf3>] do_exit+0x183/0x5c0 (40)
 [<c0127170>] do_group_exit+0x40/0xe0 (40)
 [<c0107b89>] sysenter_past_esp+0x52/0x71 (-8124)
---------------------------
| preempt count: 00010005 ]
| 5-level deep critical section nesting:
----------------------------------------
.. [<c0114783>] .... flush_tlb_mm+0x23/0x110
.....[<c015965e>] ..   ( <= unmap_vmas+0x10e/0x1c0)
.. [<c0326aff>] .... _spin_lock_irqsave+0x1f/0x80
.....[<c0123ecb>] ..   ( <= vprintk+0x2b/0x170)
.. [<c0326a8f>] .... _spin_lock+0x1f/0x70
.....[<c01e24ea>] ..   ( <= _down_write_trylock+0x23a/0x290)
.. [<c0326a8f>] .... _spin_lock+0x1f/0x70
.....[<c0109b22>] ..   ( <= die_nmi+0x22/0xa0)
.. [<c013d7dd>] .... print_traces+0x1d/0x60
.....[<c0108a1f>] ..   ( <= show_stack+0x8f/0xb0)

Code: b8 00 e0 ff ff 89 fe c1 ee 09 21 e0 89 45 ec 83 f6 01 8b 40 10 83 e6
01
69 c0 80 77 01 00 8d 98 00 da 42 c0 f0 ff 80 00 da 42 c0 <8b> 80 00 da 42
c0 48
74 0d f0 ff 0b 57 9d 83 c4 24 5b 5e 5f 5d
console shuts up ...

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

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

> (cat/3504/CPU#0): new 5286 us maximum-latency wakeup.
> (cat/3504/CPU#0): new 71828 us maximum-latency wakeup.

ok - wakeup-latency timing is completely unreliable on SMP and will
produce bogus results.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

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

> NMI Watchdog detected LOCKUP
> Pid: 3933, comm:             cpu_burn
> EIP: 0073:[<08048340>] CPU: 0
> EIP is at 0x8048340
>  ESP: 007b:bffffa40 EFLAGS: 00200282    Not tainted  
> (2.6.9-mm1-RT-V0.6.7)
> EAX: 00000000 EBX: 00711ffc ECX: bffffadc EDX: bffffad4
> ESI: 00000001 EDI: 007140fc EBP: bffffa48 DS: 007b ES: 007b
> CR0: 8005003b CR2: 00681400 CR3: 015735e0 CR4: 000006f0
>  [<c0105bec>] show_regs+0x14c/0x174 (36)
>  [<c0115f4f>] nmi_watchdog_tick+0x12f/0x140 (28)
>  [<c0109c0c>] default_do_nmi+0x6c/0x110 (96)
>  [<c0109d2d>] do_nmi+0x6d/0x70 (24)
>  [<c0108735>] nmi_stack_correct+0x1e/0x2e (-196314476)

hm, this one is an extremely weird deadlock - the NMI watchdog detected
a _user-space_ deadlock - i.e. the "cpu_burn" user-space code disabled
interrupts for more than ~5 seconds? Sounds quite unlikely and the
EFLAGS register also directly contradicts it, it has 0x200 set so
interrupts are enabled! The only other way for the NMI watchdog to
trigger is if for whatever reason the local APIC timer interrupts are
not getting through and the NMI ticks (which come via a different
interrupt pin) get through.

this is what's happening on the other CPU:

>  [<c0109b5f>] die_nmi+0x5f/0xa0 (24)
>  [<c0115f0f>] nmi_watchdog_tick+0xef/0x140 (28)
>  [<c0109c0c>] default_do_nmi+0x6c/0x110 (96)
>  [<c0109d2d>] do_nmi+0x6d/0x70 (24)
>  [<c0108735>] nmi_stack_correct+0x1e/0x2e (116)
>  [<c013bfed>] __mcount+0x1d/0x30 (16)
>  [<c0114fd8>] mcount+0x14/0x18 (20)
>  [<c0326a81>] _spin_lock+0x11/0x70 (20)
>  [<c01e2308>] _down_write_trylock+0x58/0x290 (52)
>  [<c01e3325>] down_trylock+0x45/0x180 (52)
>  [<c0123f95>] vprintk+0xf5/0x170 (36)
>  [<c0123e8d>] printk+0x1d/0x30 (16)
>  [<c0108945>] show_trace+0x95/0xe0 (32)
>  [<c0108a63>] dump_stack+0x23/0x30 (20)
>  [<c013c98e>] check_preempt_timing+0x16e/0x300 (76)
>  [<c013ce7f>] sub_preempt_count+0x7f/0xf0 (32)
>  [<c01147ba>] flush_tlb_mm+0x5a/0x110 (36)

flush_tlb_mm sends an IPI to the other CPU - maybe there's a connection.

	Ingo

Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

[Lee Revell]

On Sun, 2004-10-31 at 13:48 +0100, Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > ok, could you try the -RT-V0.6.0 patch i've just uploaded? It could i
> > believe improve these latencies.
> 
> hm, CONFIG_PARPORT_1284 seems broken, and USB too, it locks up during
> bootup. Investigating ...
> 

FWIW with V0.5.16 I had several hard lockups when running Florian's test
app at 2048 Hz.

Lee

Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

[Ingo Molnar]

* Lee Revell <rlrevell@joe-job.com> wrote:

> > > ok, could you try the -RT-V0.6.0 patch i've just uploaded? It could i
> > > believe improve these latencies.
> > 
> > hm, CONFIG_PARPORT_1284 seems broken, and USB too, it locks up during
> > bootup. Investigating ...
> > 
> 
> FWIW with V0.5.16 I had several hard lockups when running Florian's
> test app at 2048 Hz.

please check out V0.6.1, i made the semaphore code more robust and more
compatible. The V0.6 series could also fix the XFS and reiserfs problems
reported.

	Ingo

Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> > FWIW with V0.5.16 I had several hard lockups when running Florian's
> > test app at 2048 Hz.
> 
> please check out V0.6.1, i made the semaphore code more robust and
> more compatible. The V0.6 series could also fix the XFS and reiserfs
> problems reported.

i've just uploaded V0.6.2 that fixes a console-unblanking-timer thinko. 
This bug was present for quite some time, but this is the first time it 
triggered on my testbox - might be more common on others.

	Ingo

Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

[Florian Schmidt]

On Sun, 31 Oct 2004 14:40:16 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > > FWIW with V0.5.16 I had several hard lockups when running Florian's
> > > test app at 2048 Hz.
> > 
> > please check out V0.6.1, i made the semaphore code more robust and
> > more compatible. The V0.6 series could also fix the XFS and reiserfs
> > problems reported.
> 
> i've just uploaded V0.6.2 that fixes a console-unblanking-timer thinko. 
> This bug was present for quite some time, but this is the first time it 
> triggered on my testbox - might be more common on others.

V0.6.2 works pretty good. max jitter until now 21% [205us]. still fiddling
with the output formatting for rtc_wakeup.

flo

Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

[Florian Schmidt]

On Sun, 31 Oct 2004 16:20:59 +0100
Florian Schmidt <mista.tapas@gmx.net> wrote:

> 
> V0.6.2 works pretty good. max jitter until now 21% [205us]. still fiddling
> with the output formatting for rtc_wakeup.
> 

i got a deadlock though. it was a weird one. mouse and keyboard [including
sysrq] froze. but the find / i started kept on running in an xterm. had to
press reset due to lack of second machine..

flo

p.s. new rtc_wakeup version uploaded, which shows the percentage converted
to usecs (always positive, you need the sign?). btw: with V0.6.2 i sometimes
see jitter > 100% but still no lost irq (/dev/rtc still reports only 1
delivered irq on next wakeup). I cannot provke lost irqs with -f up to 2048.
With -f 8192 i do get lost irq's [not amazing though].

Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

[Florian Schmidt]

On Sun, 31 Oct 2004 16:59:13 +0100
Florian Schmidt <mista.tapas@gmx.net> wrote:

> p.s. new rtc_wakeup version uploaded, which shows the percentage converted
> to usecs (always positive, you need the sign?). btw: with V0.6.2 i sometimes
> see jitter > 100% but still no lost irq (/dev/rtc still reports only 1
> delivered irq on next wakeup). I cannot provke lost irqs with -f up to 2048.
> With -f 8192 i do get lost irq's [not amazing though].

another update upped. small bugfix (still depended on jack, should work now
w/o jack installed) plus minor cosmetic corrections. Here's example output
for 2.6.8.1-P9 (under heavy load (multiple finds plus kernel compile plus UI
artistics):

~/source/my_projects/rtc_wakeup$ ./rtc_wakeup 
rtc_wakeup - press ctrl-c to stop
freq:             1024
max # of irqs:    0 (run until stopped)
jitter threshold: 5% (48 usec)
output filename:  /dev/null
rt priority:      90(91)
getting cpu speed
1194913254.155 Hz (1194.913 MHz)
# of cycles for "perfect" period: 1166907 (976 usec)
setting up ringbuffer
setting up consumer thread
setting up /dev/rtc
locking memory
turning irq on, beginning measurement
new max. jitter: 1.6% (15 usec)
new max. jitter: 1.9% (18 usec)
new max. jitter: 2.6% (25 usec)
new max. jitter: 2.9% (28 usec)
new max. jitter: 3.2% (31 usec)
new max. jitter: 3.3% (31 usec)
new max. jitter: 3.3% (32 usec)
new max. jitter: 3.5% (34 usec)
new max. jitter: 3.5% (34 usec)
new max. jitter: 3.7% (35 usec)
new max. jitter: 4.3% (41 usec)
new max. jitter: 4.9% (47 usec)
threshold violated: 5.6% (54usec)
new max. jitter: 5.6% (54 usec)
threshold violated: 5.3% (51usec)
done.
total # of irqs:      168072
missed irqs:          0
threshold violations: 2
max jitter:           5.6% (54 usec)

So basically like lee said, 7% seems to be a normal upper limit for VP
boxes (there might be spikes though). 

V0.6.2 looked good, too, until it locked up again (under heavy load with
rtc_wakeup running) ;) Will build one with debugging enabled tomorrow. 

flo

Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

[Ingo Molnar]

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

> new max. jitter: 4.3% (41 usec)
> new max. jitter: 4.9% (47 usec)

a couple of conceptual questions: why does rtc_wakeup poll() on
/dev/rtc? Shouldnt a read() be enough?

i'm seeing some weird traces, which show rtc_wakeup doing this cycle:

	[~900 usecs pass]

	hardirq 8 comes in, wakes IRQ 8 thread
	IRQ 8 thread wakes up rtc_wakeup

	rtc_wakeup fast-thread returns from sys_read()
	rtc_wakeup fast-thread enters sys_poll() and returns immediately
	rtc_wakeup fast-thread enters sys_read() and blocks

	rtc_wakeup slow-thread runs and does the calculations.

	[repeat]

this i think shows that the logic is wrong somewhere and that read()
will achieve the blocking. This also means that the sys_read()-return +
sys_poll() overhead is added to the 'IRQ wakeup' overhead!

removing the poll() lines doesnt seem to impact the quality of the data,
but i still see roughly 50 usecs added to the 'real' latency that i see
in traces.

	Ingo

Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> removing the poll() lines doesnt seem to impact the quality of the
> data, but i still see roughly 50 usecs added to the 'real' latency
> that i see in traces.

this i think is related to what Thomas observed, that there's a new
irqs-off critical section somewhere. (it's in the new priority handling
code i think.)

	Ingo

Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

[Ingo Molnar]

* Ingo Molnar <mingo@elte.hu> wrote:

> > removing the poll() lines doesnt seem to impact the quality of the
> > data, but i still see roughly 50 usecs added to the 'real' latency
> > that i see in traces.
> 
> this i think is related to what Thomas observed, that there's a new
> irqs-off critical section somewhere. (it's in the new priority
> handling code i think.)

ah, found it. Only RT tasks were supposed to get special priority
handling, while in fact all tasks got it - so when Thomas ran hackbench
(Thomas, you did, right?) it created an O(nr_hackbench) overhead within
the mutex code ... I've uploaded -V0.6.5 to the usual place:

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

Thomas, can you confirm that this kernel fixes the irqs-off latencies? 
(the priority loop indeed was done with irqs turned off.)

i'm not sure this fix is related to the deadlocks reported though.

	Ingo

Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4]

[Thomas Gleixner]

On Mon, 2004-11-01 at 15:06 +0100, Ingo Molnar wrote:
> ah, found it. Only RT tasks were supposed to get special priority
> handling, while in fact all tasks got it - so when Thomas ran hackbench
> (Thomas, you did, right?) it created an O(nr_hackbench) overhead within
> the mutex code ... I've uploaded -V0.6.5 to the usual place:

Yes, I was running hackbench as usual

>   http://redhat.com/~mingo/realtime-preempt/
> 
> Thomas, can you confirm that this kernel fixes the irqs-off latencies? 
> (the priority loop indeed was done with irqs turned off.)

The latencies are still there. I have the feeling it's worse than 0.6.2.

It's definitely irq-off. I have a card with a controller, which produces
an 2ms interrupt. The controller busy loops until the second level ack
is done. The time is measured from raising the irq to the 2nd level ack.

The irqhandler is using NODELAY and keeps irqs disabled. So the measured
time in the controller is the irqs disabled time + the irq latency
(which is ~7µs). The testrun on 0.6.5 showed latencies up to 600µs
within 10 minutes.

After 15 Mintes the keyboard was dead. 

I'm porting some of the Libertos debugging stuff into 0.6.5, so I can
instrument the problem. 

More later.

tglx

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

[Ingo Molnar]

* Thomas Gleixner <tglx@linutronix.de> wrote:

> > Thomas, can you confirm that this kernel fixes the irqs-off latencies? 
> > (the priority loop indeed was done with irqs turned off.)
> 
> The latencies are still there. I have the feeling it's worse than 0.6.2.

update to others: Thomas debugged this problem today and found the place
that kept irqs disabled for a long time: it was update_process_times(). 
(which i recently touched to break latencies there - but forgot that the
lock is an irqs-off lock!)

i've uploaded a fixed kernel (-V0.6.8) to:

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

(this kernel also has the module-put-unlock-kernel fix that should solve
the other warning reported by Thomas and Bill.)

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[K.R. Foley]

Ingo Molnar wrote:
> * Thomas Gleixner <tglx@linutronix.de> wrote:
> 
> 
>>>Thomas, can you confirm that this kernel fixes the irqs-off latencies? 
>>>(the priority loop indeed was done with irqs turned off.)
>>
>>The latencies are still there. I have the feeling it's worse than 0.6.2.
> 
> 
> update to others: Thomas debugged this problem today and found the place
> that kept irqs disabled for a long time: it was update_process_times(). 
> (which i recently touched to break latencies there - but forgot that the
> lock is an irqs-off lock!)
> 
> i've uploaded a fixed kernel (-V0.6.8) to:
> 
>   http://redhat.com/~mingo/realtime-preempt/
> 
> (this kernel also has the module-put-unlock-kernel fix that should solve
> the other warning reported by Thomas and Bill.)
> 
> 	Ingo
> 

This one initially booted fine on my SMP workstation at the office. Ran 
for about 1 hr. 10 mins. then locked with no indications as to why. Then 
failed reboot after hitting the reset switch. The last thing that I saw 
on the console seems to match the following that I found in the log:

Nov  2 11:21:49 swdev14 rc: Starting readahead:  succeeded
Nov  2 11:21:50 swdev14 messagebus: messagebus startup succeeded
Nov  2 11:21:50 swdev14 rhnsd[3245]: Red Hat Network Services Daemon 
starting up
.
Nov  2 11:21:50 swdev14 rhnsd: rhnsd startup succeeded
Nov  2 11:21:51 swdev14 kernel: (rc/2112/CPU#2): new 912 us 
maximum-latency wake
up.
Nov  2 11:21:51 swdev14 kernel: (ksoftirqd/1/6/CPU#1): new 3147 us 
maximum-laten
cy wakeup.
Nov  2 11:21:51 swdev14 kernel: (mingetty/3251/CPU#1): new 3916 us 
maximum-laten
cy wakeup.
Nov  2 11:21:51 swdev14 kernel: (init/3253/CPU#2): new 4321 us 
maximum-latency w
akeup.
Nov  2 11:21:51 swdev14 kernel: (init/1/CPU#0): new 5332 us 
maximum-latency wake
up.
Nov  2 11:21:51 swdev14 kernel: (init/1/CPU#0): new 5819 us 
maximum-latency wake
up.
Nov  2 11:21:51 swdev14 kernel: (hotplug/3259/CPU#2): new 6847 us 
maximum-latenc
y wakeup.
Nov  2 11:21:51 swdev14 kernel: (hotplug/3274/CPU#2): new 7378 us 
maximum-latenc
y wakeup.
Nov  2 11:31:12 swdev14 syslogd 1.4.1: restart.

After the failed reboot a subsequent reboot went fine. This behavior 
seems to be pretty much the same for a while now.

My SMP system at home has been running for for 1 hr. 23 mins. so far. No 
signs of problems.

kr

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

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

> This one initially booted fine on my SMP workstation at the office.
> Ran for about 1 hr. 10 mins. then locked with no indications as to
> why.  [...]

soft hang or hard hang? In any case, the freshly uploaded -V0.6.9 kernel
both fixes one more deadlock and extends deadlock-detection to virtually
every locking object in Linux so it would be nice to check whether you
are getting a silent hang again, or perhaps something more verbose.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[K.R. Foley]

Ingo Molnar wrote:
> * K.R. Foley <kr@cybsft.com> wrote:
> 
> 
>>This one initially booted fine on my SMP workstation at the office.
>>Ran for about 1 hr. 10 mins. then locked with no indications as to
>>why.  [...]
> 
> 
> soft hang or hard hang? In any case, the freshly uploaded -V0.6.9 kernel
> both fixes one more deadlock and extends deadlock-detection to virtually
> every locking object in Linux so it would be nice to check whether you
> are getting a silent hang again, or perhaps something more verbose.
> 
> 	Ingo
> 

Doh! Sorry. Hard hang. Building -V0.6.9 already.

kr

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Norberto Bensa]

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

Hello Ingo,

Ingo Molnar wrote:
> i've uploaded a fixed kernel (-V0.6.8) to:
>
>   http://redhat.com/~mingo/realtime-preempt/

Doesn't compile:

  CC [M]  fs/lockd/svc.o
fs/lockd/svc.c:49: warning: type defaults to `int' in declaration of 
`DECLARE_MUTEX_NOCHECK'
fs/lockd/svc.c:49: warning: parameter names (without types) in function 
declaration
fs/lockd/svc.c: In function `lockd':
fs/lockd/svc.c:112: error: `lockd_start' undeclared (first use in this 
function)
fs/lockd/svc.c:112: error: (Each undeclared identifier is reported only once
fs/lockd/svc.c:112: error: for each function it appears in.)
fs/lockd/svc.c: In function `lockd_up':
fs/lockd/svc.c:261: error: `lockd_start' undeclared (first use in this 
function)
fs/lockd/svc.c: In function `init_nlm':
fs/lockd/svc.c:426: error: `lockd_start' undeclared (first use in this 
function)
fs/lockd/svc.c: At top level:
fs/lockd/svc.c:49: warning: 'DECLARE_MUTEX_NOCHECK' declared `static' but 
never defined
make[2]: *** [fs/lockd/svc.o] Error 1
make[1]: *** [fs/lockd] Error 2
make: *** [fs] Error 2

Regards,
Norberto

[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 30641 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.9-mm1-RT-V0.6.8
# Tue Nov  2 16:20:44 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

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_AS is not set
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_IOSCHED_CFQ=y
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
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=y
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# 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=y
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# 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=5
CONFIG_ASM_SEMAPHORES=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=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=y
CONFIG_HPET_EMULATE_RTC=y
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
# CONFIG_PREEMPT_REALTIME is not set
# CONFIG_SPINLOCK_BKL is not set
CONFIG_PREEMPT_BKL=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_X86_MCE_P4THERMAL 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_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM is not set

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

#
# Power management options (ACPI, APM)
#
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
# CONFIG_ACPI_SLEEP is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
# CONFIG_ACPI_BUTTON is not set
# CONFIG_ACPI_FAN is not set
# CONFIG_ACPI_PROCESSOR is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_THINKPAD is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_X86_PM_TIMER is not set

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set

#
# 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_MMCONFIG=y
CONFIG_PCI_MSI=y
CONFIG_PCI_LEGACY_PROC=y
# CONFIG_PCI_NAMES is not set
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set

#
# PC-card bridges
#
CONFIG_PCMCIA_PROBE=y

#
# PCI Hotplug Support
#
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_FAKE is not set
# CONFIG_HOTPLUG_PCI_COMPAQ is not set
# CONFIG_HOTPLUG_PCI_IBM is not set
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_PCIE is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y

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

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y
CONFIG_PNPBIOS_PROC_FS=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# 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=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=2048
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
CONFIG_CDROM_PKTCDVD=y
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set

#
# 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=y
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# 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 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_ARM is not set
# CONFIG_IDE_CHIPSETS 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=y
CONFIG_SCSI_PROC_FS=y

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

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# 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_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_IN2000 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_DTC3280 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_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS 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=y
# 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_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
# CONFIG_MD_LINEAR is not set
CONFIG_MD_RAID0=y
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_RAID6 is not set
CONFIG_MD_MULTIPATH=y
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
CONFIG_DM_ZERO=y

#
# 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=m
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=m
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE 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_IPV6 is not set
# CONFIG_NETFILTER 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
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set

#
# 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 is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 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
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA 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_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 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=m
CONFIG_8139TOO_PIO=y
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_NET_POCKET 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 is not set
# 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=2048
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=2048
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=y

#
# 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 is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC 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 is not set

#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set

#
# 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_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=y
# 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 is not set
# CONFIG_AGP_SWORKS is not set
CONFIG_AGP_VIA=y
# CONFIG_AGP_EFFICEON is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_CHARDEV=y

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

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

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

#
# Other I2C Chip support
#
# CONFIG_SENSORS_EEPROM is not set
# CONFIG_SENSORS_PCF8574 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_SENSORS_RTC8564 is not set
# 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=y

#
# Video For Linux
#

#
# Video Adapters
#
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_PMS is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_TUNER_3036 is not set
# CONFIG_VIDEO_STRADIS is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_DPC is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_OVCAMCHIP is not set

#
# Radio Adapters
#
# CONFIG_RADIO_CADET is not set
# CONFIG_RADIO_RTRACK is not set
# CONFIG_RADIO_RTRACK2 is not set
# CONFIG_RADIO_AZTECH is not set
# CONFIG_RADIO_GEMTEK is not set
# CONFIG_RADIO_GEMTEK_PCI is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_MAESTRO is not set
# CONFIG_RADIO_SF16FMI is not set
# CONFIG_RADIO_SF16FMR2 is not set
# CONFIG_RADIO_TERRATEC is not set
# CONFIG_RADIO_TRUST is not set
# CONFIG_RADIO_TYPHOON is not set
# CONFIG_RADIO_ZOLTRIX 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_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
CONFIG_SOUND=y

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

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# 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

#
# ISA devices
#
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set

#
# PCI devices
#
CONFIG_SND_AC97_CODEC=y
# 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 is not set
# CONFIG_SND_CS4281 is not set
CONFIG_SND_EMU10K1=y
# 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 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_OHCI_HCD is not set
CONFIG_USB_UHCI_HCD=y

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_STORAGE is not set

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_DSBR is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set

#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_TEST is not set

#
# USB ATM/DSL drivers
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=m
# CONFIG_XFS_RT is not set
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_MINIX_FS=m
# CONFIG_ROMFS_FS is not set
CONFIG_QUOTA=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# Caches
#
# CONFIG_FSCACHE is not set

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

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=850
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-15"
# CONFIG_NTFS_FS 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=y
CONFIG_TMPFS=y
CONFIG_TMPFS_XATTR=y
CONFIG_TMPFS_SECURITY=y
# 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 is not set
# 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=m
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
CONFIG_NFS_DIRECTIO=y
# CONFIG_NFSD is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
# CONFIG_EXPORTFS is not set
CONFIG_SUNRPC=m
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 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 is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set

#
# Native Language Support
#
CONFIG_NLS=m
CONFIG_NLS_DEFAULT="utf8"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
# 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 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
# CONFIG_NLS_ISO8859_1 is not set
# 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=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_PREEMPT_TIMING is not set
# CONFIG_USE_FRAME_POINTER is not set
# CONFIG_EARLY_PRINTK is not set
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

#
# Security options
#
# CONFIG_KEYS is not set
CONFIG_SECURITY=y
# CONFIG_SECURITY_NETWORK is not set
CONFIG_SECURITY_CAPABILITIES=y
# CONFIG_SECURITY_ROOTPLUG is not set
# CONFIG_SECURITY_SECLVL is not set
# 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_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 is not set
CONFIG_CRC32=m
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

* Norberto Bensa <norberto+linux-kernel@bensa.ath.cx> wrote:

> Ingo Molnar wrote:
> > i've uploaded a fixed kernel (-V0.6.8) to:
> >
> >   http://redhat.com/~mingo/realtime-preempt/
> 
> Doesn't compile:
> 
>   CC [M]  fs/lockd/svc.o
> fs/lockd/svc.c:49: warning: type defaults to `int' in declaration of 
> `DECLARE_MUTEX_NOCHECK'

ok - the reason was this:

> # CONFIG_PREEMPT_REALTIME is not set

i fixed these build problems in the -V0.6.9 patch i just uploaded.

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Karsten Wiese]

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

Am Dienstag 02 November 2004 16:06 schrieb Ingo Molnar:
> i've uploaded a fixed kernel (-V0.6.8) to:
>
>   http://redhat.com/~mingo/realtime-preempt/
>
> (this kernel also has the module-put-unlock-kernel fix that should solve
> the other warning reported by Thomas and Bill.)
>
> 	Ingo

Fixed a deadlock in snd-es1968 with attached patch.

Just for information, the error messages on V0.6.9 were:
===============================================
[ BUG: semaphore recursion deadlock detected! |
-----------------------------------------------
already locked:  [c91ea080] {r:0,a:-1,&chip->reg_lock}
.. held by:            insmod/ 3185 [cf6c2750, 118]
... acquired at:  es1968_measure_clock+0x3b6/0x640 [snd_es1968]

------------------------------
| showing all locks held by: |  (insmod/3185 [cf6c2750, 118]):
------------------------------

#001:             [c036a4ec] {r:0,a:-1,&s->rwsem}
... acquired at:  bus_add_driver+0x8a/0xc0

#002:             [c91ea080] {r:0,a:-1,&chip->reg_lock}
... acquired at:  es1968_measure_clock+0x3b6/0x640 [snd_es1968]

-{current task's backtrace}----------------->
 [<c0107923>] dump_stack+0x23/0x30 (20)
 [<c01bae36>] check_deadlock+0x276/0x2a0 (44)
 [<c01bb455>] task_blocks_on_sem+0x195/0x1d0 (56)
 [<c02de4d3>] down_write_mutex+0x283/0x3c0 (88)
 [<c0134bc4>] __mutex_lock+0x44/0x60 (24)
 [<c0134c8d>] _mutex_lock_irqsave+0x1d/0x30 (16)
 [<d099266e>] snd_es1968_bob_start+0xbe/0x160 [snd_es1968] (44)
 [<d0994a1a>] es1968_measure_clock+0x3ca/0x640 [snd_es1968] (72)
 [<d0996318>] snd_es1968_probe+0x1f8/0x340 [snd_es1968] (60)
 [<c01ca5b2>] pci_device_probe_static+0x52/0x70 (28)
 [<c01ca60d>] __pci_device_probe+0x3d/0x50 (24)
 [<c01ca651>] pci_device_probe+0x31/0x50 (24)
 [<c021c1b5>] bus_match+0x45/0x80 (28)
 [<c021c31c>] driver_attach+0x6c/0xb0 (36)
 [<c021c802>] bus_add_driver+0x92/0xc0 (36)
 [<c01ca969>] pci_register_driver+0x99/0xc0 (36)
 [<d0861017>] alsa_card_es1968_init+0x17/0x1b [snd_es1968] (12)
 [<c013ab29>] sys_init_module+0x169/0x220 (28)
 [<c01072ed>] sysenter_past_esp+0x52/0x71 (-8124)
---------------------------
| preempt count: 00000002 ]
| 2-level deep critical section nesting:
----------------------------------------
.. [<c02de604>] .... down_write_mutex+0x3b4/0x3c0
.....[<c0134bc4>] ..   ( <= __mutex_lock+0x44/0x60)
.. [<c01368dd>] .... print_traces+0x1d/0x60
.....[<c0107923>] ..   ( <= dump_stack+0x23/0x30)


showing all tasks:
s            init/    1 [c1271370, 116] (not blocked)
s     ksoftirqd/0/    2 [c1270d00, 105] (not blocked)
s       desched/0/    3 [c1270690, 105] (not blocked)
s        events/0/    4 [c1270020,  98] (not blocked)
s         khelper/    5 [cff27390, 105] (not blocked)
s         kthread/   10 [cff26d20, 105] (not blocked)
s          kacpid/   18 [cff266b0, 105] (not blocked)
s           IRQ 9/   19 [cff26040,  50] (not blocked)
s       kblockd/0/   86 [cfec93b0, 105] (not blocked)
s           khubd/   94 [cfec8d40, 115] (not blocked)
s         pdflush/  141 [cfec86d0, 120] (not blocked)
s         pdflush/  142 [cfec8060, 116] (not blocked)
s           aio/0/  144 [c1304d60, 110] (not blocked)
s         kswapd0/  143 [c13053d0, 125] (not blocked)
s           IRQ 8/  732 [c13046f0,  56] (not blocked)
s          IRQ 12/  740 [c13cf3f0,  54] (not blocked)
s           IRQ 6/  753 [c13ced80,  51] (not blocked)
s         kseriod/  734 [c1304080, 124] (not blocked)
s          IRQ 14/  776 [c13ce710,  53] (not blocked)
s          IRQ 15/  778 [c13ce0a0,  52] (not blocked)
s           IRQ 1/  796 [c13fd410,  55] (not blocked)
s       kjournald/  838 [c13fc730, 116] (not blocked)
s         portmap/ 2013 [c13fcda0, 116] (not blocked)
s            sshd/ 2074 [ceac2970, 124] (not blocked)
s             xfs/ 2343 [ceed03e0, 119] (not blocked)
s           IRQ 5/ 2411 [cefa6220, 106] (not blocked)
s        mingetty/ 2485 [ce88a8d0, 118] (not blocked)
s        mingetty/ 2498 [cebfa5a0, 118] (not blocked)
s        mingetty/ 2499 [ce6298b0, 118] (not blocked)
s        mingetty/ 2500 [cebfb280, 118] (not blocked)
s        mingetty/ 2501 [cea8afc0, 122] (not blocked)
s        mingetty/ 2610 [cebfb8f0, 122] (not blocked)
s             kdm/ 2611 [ce88b5b0, 117] (not blocked)
s               X/ 2698 [ce628bd0, 115] (not blocked)
s             kdm/ 2699 [cf6c2dc0, 121] (not blocked)
s          IRQ 11/ 2792 [ceac2fe0,  57] (not blocked)
s        startkde/ 2796 [ceac2300, 117] (not blocked)
s       ssh-agent/ 2855 [cea8a950, 116] (not blocked)
s         kdeinit/ 2889 [cddd8c30, 117] (not blocked)
s         kdeinit/ 2892 [cefa7570, 116] (not blocked)
s         kdeinit/ 2894 [cea8a2e0, 116] (not blocked)
s         kdeinit/ 2897 [ce88af40, 115] (not blocked)
s         kdeinit/ 2908 [ce88a260, 116] (not blocked)
s         kdeinit/ 2982 [ceed10c0, 117] (not blocked)
s        kwrapper/ 2985 [ceed1730, 116] (not blocked)
s         kdeinit/ 2987 [ceed0a50, 115] (not blocked)
s         kdeinit/ 2989 [cddd85c0, 116] (not blocked)
s         kdeinit/ 2993 [ce629240, 116] (not blocked)
s         kdeinit/ 2995 [cebfac10, 116] (not blocked)
s         kdeinit/ 2997 [cefa6890, 116] (not blocked)
s         kdeinit/ 3004 [c13fc0c0, 116] (not blocked)
s         kdeinit/ 3007 [ce628560, 116] (not blocked)
s         kdeinit/ 3009 [cddd9910, 116] (not blocked)
s         kdeinit/ 3011 [cf6c20e0, 116] (not blocked)
s            bash/ 3080 [cddd92a0, 117] (not blocked)
s              su/ 3136 [cefa6f00, 119] (not blocked)
s            bash/ 3139 [cea8b630, 118] (not blocked)
R          insmod/ 3185 [cf6c2750, 118] (not blocked)

---------------------------
| showing all locks held: |
---------------------------

#001:             [c04445c0] {r:0,a:-1,&hwif->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x9d/0x190

#002:             [c04441b8] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#003:             [c04443a0] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#004:             [c0444c64] {r:0,a:-1,&hwif->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x9d/0x190

#005:             [c044485c] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#006:             [c0444a44] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#007:             [c0445308] {r:0,a:-1,&hwif->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x9d/0x190

#008:             [c0444f00] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#009:             [c04450e8] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#010:             [c04459ac] {r:0,a:-1,&hwif->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x9d/0x190

#011:             [c04455a4] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#012:             [c044578c] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#013:             [c0446050] {r:0,a:-1,&hwif->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x9d/0x190

#014:             [c0445c48] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#015:             [c0445e30] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#016:             [c04466f4] {r:0,a:-1,&hwif->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x9d/0x190

#017:             [c04462ec] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#018:             [c04464d4] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#019:             [c0446d98] {r:0,a:-1,&hwif->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x9d/0x190

#020:             [c0446990] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#021:             [c0446b78] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#022:             [c044743c] {r:0,a:-1,&hwif->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x9d/0x190

#023:             [c0447034] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#024:             [c044721c] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#025:             [c0447ae0] {r:0,a:-1,&hwif->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x9d/0x190

#026:             [c04476d8] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#027:             [c04478c0] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#028:             [c0448184] {r:0,a:-1,&hwif->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x9d/0x190

#029:             [c0447d7c] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#030:             [c0447f64] {r:0,a:-1,&drive->gendev_rel_sem}
.. held by:              init/    1 [c1271370, 116]
... acquired at:  init_hwif_data+0x172/0x190

#031:             [cfc24d20] {r:0,a:-1,&tty->atomic_read}
.. held by:          mingetty/ 2485 [ce88a8d0, 118]
... acquired at:  read_chan+0x716/0x770

#032:             [cf624d20] {r:0,a:-1,&tty->atomic_read}
.. held by:          mingetty/ 2499 [ce6298b0, 118]
... acquired at:  read_chan+0x716/0x770

#033:             [cefe2d20] {r:0,a:-1,&tty->atomic_read}
.. held by:          mingetty/ 2498 [cebfa5a0, 118]
... acquired at:  read_chan+0x716/0x770

#034:             [ce0bcd20] {r:0,a:-1,&tty->atomic_read}
.. held by:          mingetty/ 2500 [cebfb280, 118]
... acquired at:  read_chan+0x716/0x770

#035:             [cfb26d20] {r:0,a:-1,&tty->atomic_read}
.. held by:          mingetty/ 2610 [cebfb8f0, 122]
... acquired at:  read_chan+0x716/0x770

#036:             [cfb2bd20] {r:0,a:-1,&tty->atomic_read}
.. held by:          mingetty/ 2501 [cea8afc0, 122]
... acquired at:  read_chan+0x716/0x770

#037:             [c036a4ec] {r:0,a:-1,&s->rwsem}
.. held by:            insmod/ 3185 [cf6c2750, 118]
... acquired at:  bus_add_driver+0x8a/0xc0

#038:             [c91ea080] {r:0,a:-1,&chip->reg_lock}
.. held by:            insmod/ 3185 [cf6c2750, 118]
... acquired at:  es1968_measure_clock+0x3b6/0x640 [snd_es1968]

#039:             [c032d360] {r:0,a:-1,tasklist_lock}
.. held by:            insmod/ 3185 [cf6c2750, 118]
... acquired at:  show_all_locks+0x30/0x130
=============================================

[ turning off deadlock detection. Please report this trace. ]

Karsten

[-- Attachment #2: snd-es1968.patch --]
[-- Type: text/x-diff, Size: 1186 bytes --]

--- sound/pci/es1968.c~	2004-11-02 23:51:56.504888304 +0100
+++ sound/pci/es1968.c	2004-11-02 23:51:12.375596976 +0100
@@ -837,23 +837,19 @@
 static void snd_es1968_bob_stop(es1968_t *chip)
 {
 	u16 reg;
-	unsigned long flags;
 
-	spin_lock_irqsave(&chip->reg_lock, flags);
 	reg = __maestro_read(chip, 0x11);
 	reg &= ~ESM_BOB_ENABLE;
 	__maestro_write(chip, 0x11, reg);
 	reg = __maestro_read(chip, 0x17);
 	reg &= ~ESM_BOB_START;
 	__maestro_write(chip, 0x17, reg);
-	spin_unlock_irqrestore(&chip->reg_lock, flags);
 }
 
 static void snd_es1968_bob_start(es1968_t *chip)
 {
 	int prescale;
 	int divide;
-	unsigned long flags;
 
 	/* compute ideal interrupt frequency for buffer size & play rate */
 	/* first, find best prescaler value to match freq */
@@ -882,13 +878,11 @@
 	} else if (divide > 1)
 		divide--;
 
-	spin_lock_irqsave(&chip->reg_lock, flags);
 	__maestro_write(chip, 6, 0x9000 | (prescale << 5) | divide);	/* set reg */
 
 	/* Now set IDR 11/17 */
 	__maestro_write(chip, 0x11, __maestro_read(chip, 0x11) | 1);
 	__maestro_write(chip, 0x17, __maestro_read(chip, 0x17) | 1);
-	spin_unlock_irqrestore(&chip->reg_lock, flags);
 }
 
 /* call with substream spinlock */

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Ingo Molnar]

* Karsten Wiese <annabellesgarden@yahoo.de> wrote:

> Am Dienstag 02 November 2004 16:06 schrieb Ingo Molnar:
> > i've uploaded a fixed kernel (-V0.6.8) to:
> >
> >   http://redhat.com/~mingo/realtime-preempt/
> >
> > (this kernel also has the module-put-unlock-kernel fix that should solve
> > the other warning reported by Thomas and Bill.)
> >
> > 	Ingo
> 
> Fixed a deadlock in snd-es1968 with attached patch.

thanks. This is a (SMP-only) bug in the vanilla driver too, correct?

	Ingo

Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8

[Karsten Wiese]

Am Mittwoch 03 November 2004 02:12 schrieb Ingo Molnar:
> 
> * Karsten Wiese <annabellesgarden@yahoo.de> wrote:
> 
> > Am Dienstag 02 November 2004 16:06 schrieb Ingo Molnar:
> > > i've uploaded a fixed kernel (-V0.6.8) to:
> > >
> > >   http://redhat.com/~mingo/realtime-preempt/
> > >
> > > (this kernel also has the module-put-unlock-kernel fix that should solve
> > > the other warning reported by Thomas and Bill.)
> > >
> > > 	Ingo
> > 
> > Fixed a deadlock in snd-es1968 with attached patch.
> 
> thanks. This is a (SMP-only) bug in the vanilla driver too, correct?

Yes. I sent the patch to alsa-devel too.

Karsten