From: Pavel Vasilyev <pavel@pavlinux.ru>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.2.52-rt73
Date: Fri, 22 Nov 2013 00:44:37 +0400 [thread overview]
Message-ID: <528E70B5.5010603@pavlinux.ru> (raw)
In-Reply-To: <20131116194633.GD11518@linutronix.de>
[-- 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 --]
next prev parent reply other threads:[~2013-11-21 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 19:46 [ANNOUNCE] 3.12.0-rt2 Sebastian Andrzej Siewior
2013-11-16 21:26 ` Pavel Vasilyev
2013-11-19 7:38 ` Sami Pietikäinen
2013-11-22 14:23 ` Sebastian Andrzej Siewior
2013-11-24 10:15 ` Michael Langfinger
2013-11-25 8:23 ` Sami Pietikäinen
2013-11-25 13:21 ` Sami Pietikäinen
2013-11-29 16:13 ` Sebastian Andrzej Siewior
2013-11-21 20:44 ` Pavel Vasilyev [this message]
2013-11-22 14:56 ` [ANNOUNCE] 3.2.52-rt73 Sebastian Andrzej Siewior
2013-11-22 21:11 ` [ANNOUNCE] 3.12.1-rt4 Sebastian Andrzej Siewior
2013-12-01 22:25 ` Pavel Vasilyev
2013-12-02 8:43 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2013-11-20 19:46 [ANNOUNCE] 3.2.52-rt73 Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=528E70B5.5010603@pavlinux.ru \
--to=pavel@pavlinux.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.