Re: [ANNOUNCE] 2.6.31-rt11

[Darren Hart]

Thomas Gleixner wrote:
> We are pleased to announce the next update to our new preempt-rt
> series.
>
>    - latencytop fix
>
>    - disable SPARSE_IRQ, DMAR, IRQ_REMAP for -rt
>
> Known issues:
>    - ARM highmem
>    - scheduler load balancing oddities. Peter is working on it.
>    - timer_interrupt hang check (still working on somthing useful)
>
> The planned "add back MIPS support" is postponed to rt12.
>
> Download locations:
>
>     http://rt.et.redhat.com/download/
>     http://www.kernel.org/pub/linux/kernel/projects/rt/
>
> Git release branch:
>     git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.31
>   
> Git development branch:
>     git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head
>
> Gitweb:
>     http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.31
>
> Information on the RT patch can be found at:
>
>     http://rt.wiki.kernel.org/index.php/Main_Page
>
> to build the 2.6.31-rt11 tree, the following patches should be
> applied:
>
>     http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.31.tar.bz2
>     http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.31-rt11.bz2
>
> Enjoy !
>
>       tglx
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hitting a repeating BUG at boot on my Thinkpad T60p:

[    2.861699] BUG: sleeping function called from invalid context at 
kernel/rtmutex.c:684
[    2.861839] in_atomic(): 1, irqs_disabled(): 0, pid: 777, name: sleep
[    2.861967] Pid: 777, comm: sleep Not tainted 2.6.31-rc4-rt1-dvh01 #1
[    2.862092] Call Trace:
[    2.862217]  [<c012d881>] __might_sleep+0xe1/0x100
[    2.862343]  [<c056ccba>] rt_spin_lock+0x2a/0x70
[    2.862468]  [<c018243a>] res_counter_uncharge+0x2a/0x50
[    2.862593]  [<c01e6e23>] __mem_cgroup_uncharge_common+0x93/0x190
[    2.862720]  [<c01e6fb8>] mem_cgroup_uncharge_page+0x28/0x30
[    2.862845]  [<c01d6b87>] page_remove_rmap+0x47/0x50
[    2.862969]  [<c01cf2d9>] unmap_vmas+0x349/0x6b0
[    2.863093]  [<c01d45e5>] exit_mmap+0xc5/0x1c0
[    2.863217]  [<c0140481>] mmput+0x51/0xc0
[    2.863339]  [<c0146465>] exit_mm+0x105/0x140
[    2.863462]  [<c01465b5>] do_exit+0x115/0x760
[    2.863584]  [<c0146cc4>] sys_exit+0x14/0x20
[    2.863707]  [<c0103025>] syscall_call+0x7/0xb

I'm looking for a problem with preempt_disable() between LinuxCon 
seesions now.  But if someone already knows the problem, thought I'd post.

Thanks,

--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/