[ANNOUNCE] 3.2.52-rt73

[ANNOUNCE] 3.2.52-rt73

[Steven Rostedt]

Dear RT Folks,

I'm pleased to announce the 3.2.52-rt73 stable release.


This release is just an update to the new stable 3.2.52 version
and no RT specific changes have been made.


You can get this release via the git tree at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git

  branch: v3.2-rt
  Head SHA1: 8f50d792dcaf70f762c271a9722a83704abf3e0f


Or to build 3.2.52-rt73 directly, the following patches should be applied:

  http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.2.tar.xz

  http://www.kernel.org/pub/linux/kernel/v3.x/patch-3.2.52.xz

  http://www.kernel.org/pub/linux/kernel/projects/rt/3.2/patch-3.2.52-rt73.patch.xz




Enjoy,

-- Steve

Re: [ANNOUNCE] 3.2.52-rt73

[Sebastian Andrzej Siewior]

* Pavel Vasilyev | 2013-11-22 00:44:37 [+0400]:

>
>Fine, killed 3.12 now decided to finish 3.2.x. Good job guys!
>
>Not configuration, not hardware, not software has not been updated or changed.

No I am a bit confused. On 16th you write:
|3.2.52-rt72 - work

and now you say that we killed v3.2. There was no v3.2.52-rt72 but
v3.2.51-rt72. So did -rt72 work and -rt73 does no more?

I saw your earlier screenshots and there is nothing I can say. I can't
tell based on the screenshot what is wrong. Sorry.

This time you managed to include a backtrace. Better! However would you
mind to enable frame pointers? The backtrace 

>BUG: scheduling while atomic: irq/74-sata_nv/57/0x00000002
>Modules linked in: cls_u32 sch_sfq sch_htb
>Pid: 57, comm: irq/74-sata_nv Tainted: G           O 3.2.52-rt73 #10
>Call Trace:
> [<ffffffff814bdef4>] ? __schedule+0x314/0x344
> [<ffffffff81081b77>] ? task_blocks_on_rt_mutex+0x1e7/0x280
> [<ffffffff814be741>] ? schedule+0x21/0xa0
> [<ffffffff814c0d88>] ? rt_spin_lock_slowlock+0x128/0x280
> [<ffffffff81204d01>] ? blk_update_request+0x11/0x450
> [<ffffffff812a6976>] ? add_timer_randomness+0x86/0x1e0
> [<ffffffff81206eac>] ? blk_end_request+0x9c/0xc0
> [<ffffffff812c629a>] ? scsi_io_completion+0x9a/0x770
> [<ffffffff8120d4ab>] ? blk_done_softirq+0x6b/0x80
> [<ffffffff8104a805>] ? __do_softirq_common+0xa5/0x1d0
> [<ffffffff81094ec0>] ? irq_thread_fn+0x50/0x50
> [<ffffffff8104ad77>] ? local_bh_enable+0x127/0x150
> [<ffffffff81094f08>] ? irq_forced_thread_fn+0x48/0x70
> [<ffffffff81094d80>] ? irq_thread+0x150/0x240
> [<ffffffff81094c30>] ? disable_irq_nosync+0x60/0x60
> [<ffffffff81067150>] ? kthread+0x80/0x90
> [<ffffffff814c3174>] ? kernel_thread_helper+0x4/0x10
> [<ffffffff810670d0>] ? kthread_bind+0x80/0x80
> [<ffffffff814c3170>] ? gs_change+0xb/0xb

shows now random functions which were on stack before the accident. What
happens is that something on the system tries to take a sleeping long
while beeing most likely in a preempt disable region. With lockdep on it
might even throw some additional information here.

Sebastian

Re: [ANNOUNCE] 3.2.52-rt73

[Pavel Vasilyev]

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


Fine, killed 3.12 now decided to finish 3.2.x. Good job guys!

Not configuration, not hardware, not software has not been updated or changed.

BUG: scheduling while atomic: irq/74-sata_nv/57/0x00000002
Modules linked in: cls_u32 sch_sfq sch_htb
Pid: 57, comm: irq/74-sata_nv Tainted: G           O 3.2.52-rt73 #10
Call Trace:
 [<ffffffff814bdef4>] ? __schedule+0x314/0x344
 [<ffffffff81081b77>] ? task_blocks_on_rt_mutex+0x1e7/0x280
 [<ffffffff814be741>] ? schedule+0x21/0xa0
 [<ffffffff814c0d88>] ? rt_spin_lock_slowlock+0x128/0x280
 [<ffffffff81204d01>] ? blk_update_request+0x11/0x450
 [<ffffffff812a6976>] ? add_timer_randomness+0x86/0x1e0
 [<ffffffff81206eac>] ? blk_end_request+0x9c/0xc0
 [<ffffffff812c629a>] ? scsi_io_completion+0x9a/0x770
 [<ffffffff8120d4ab>] ? blk_done_softirq+0x6b/0x80
 [<ffffffff8104a805>] ? __do_softirq_common+0xa5/0x1d0
 [<ffffffff81094ec0>] ? irq_thread_fn+0x50/0x50
 [<ffffffff8104ad77>] ? local_bh_enable+0x127/0x150
 [<ffffffff81094f08>] ? irq_forced_thread_fn+0x48/0x70
 [<ffffffff81094d80>] ? irq_thread+0x150/0x240
 [<ffffffff81094c30>] ? disable_irq_nosync+0x60/0x60
 [<ffffffff81067150>] ? kthread+0x80/0x90
 [<ffffffff814c3174>] ? kernel_thread_helper+0x4/0x10
 [<ffffffff810670d0>] ? kthread_bind+0x80/0x80
 [<ffffffff814c3170>] ? gs_change+0xb/0xb


BUG: scheduling while atomic: ksoftirqd/3/27/0x00000002
Pid: 3, comm: ksoftirqd/0 Tainted: G           O 3.2.52-rt73 #10
...
BUG: scheduling while atomic: ksoftirqd/0/3/0x00000002
Pid: 27, comm: ksoftirqd/3 Tainted: G           O 3.2.52-rt73 #10
....
BUG: scheduling while atomic: ksoftirqd/0/3/0x00000002
Pid: 27, comm: ksoftirqd/3 Tainted: G           O 3.2.52-rt73 #10



-- 

                                                         Pavel.




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]