From: Georgiewskiy Yuriy <bottleman@icf.org.ru>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.0.14-rt31
Date: Thu, 22 Dec 2011 18:00:25 +0400 (MSK) [thread overview]
Message-ID: <alpine.DEB.2.02.1112221759480.6601@icf.org.ru> (raw)
In-Reply-To: <1324525237.5916.114.camel@gandalf.stny.rr.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 3494 bytes --]
On 2011-12-21 22:40 -0500, Steven Rostedt wrote LKML and RT:
there is steel a bug in acpi:
[ 251.152035] BUG: scheduling while atomic: irq/9-acpi/14/0x00000002
[ 251.152038] Modules linked in: xt_TCPMSS xt_tcpudp iptable_mangle ip_tables x_tables ipv6 pci_slot pktcdvd tcp_cubic microcode fuse hso pata_pcmcia firewire_net firewire_ohci firewire_core crc_itu_t tcp_hybla cdc_acm usbmouse usb_storage usb_libusual usbhid uhci_hcd ohci_hcd ehci_hcd usbcore snd_mpu401_uart snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_seq_device cpufreq_userspace acpi_cpufreq mperf msr cpuid nvram arc4 joydev snd_intel8x0m mousedev 8250_pci 8250_pnp snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer psmouse snd_page_alloc serio_raw pcmcia radeon ttm drm_kms_helper drm backlight i2c_algo_bit ath9k mac80211 ath9k_common ath9k_hw ath cfg80211 i2c_core cfbcopyarea cfbimgblt rfkill cfbfillrect processor pcspkr battery ac intel_agp intel_gtt agpgart yenta_socket pcmcia_rsrc pcmcia_core button power_supply 8250 serial_core evdev raid0 btrfs crc32c libcrc32c sr_mod cdrom atkbd thermal thermal_sys hwmon 8139too [last unloaded: scsi_wait_scan]
[ 251.152105] Pid: 14, comm: irq/9-acpi Not tainted 3.0.14-rt31-r235 #1
[ 251.152108] Call Trace:
[ 251.152112] [<792d784d>] ? 0x792d784d
[ 251.152114] [<79022284>] ? 0x79022284
[ 251.152116] [<79020547>] ? 0x79020547
[ 251.152117] [<7902253e>] ? 0x7902253e
[ 251.152119] [<79022e59>] ? 0x79022e59
[ 251.152121] [<792d7a4f>] ? 0x792d7a4f
[ 251.152123] [<792d8a55>] ? 0x792d8a55
[ 251.152125] [<79020bfc>] ? 0x79020bfc
[ 251.152127] [<7918d60c>] ? 0x7918d60c
[ 251.152128] [<79196f09>] ? 0x79196f09
[ 251.152130] [<7919e374>] ? 0x7919e374
[ 251.152132] [<791971ab>] ? 0x791971ab
[ 251.152134] [<79195c33>] ? 0x79195c33
[ 251.152136] [<79188cb7>] ? 0x79188cb7
[ 251.152137] [<7905dab0>] ? 0x7905dab0
[ 251.152139] [<7905d92d>] ? 0x7905d92d
[ 251.152141] [<7905da90>] ? 0x7905da90
[ 251.152143] [<7905d810>] ? 0x7905d810
[ 251.152144] [<7903eb24>] ? 0x7903eb24
[ 251.152146] [<7903eab0>] ? 0x7903eab0
[ 251.152148] [<792d9e3e>] ? 0x792d9e3e
SR>
SR>Dear RT Folks,
SR>
SR>I'm pleased to announce the 3.0.14-rt31 stable release.
SR>
SR>
SR>This release is just an update to the new stable 3.0.14 version
SR>and no RT specific changes have been made.
SR>
SR>
SR>You can get this release via the git tree at:
SR>
SR> git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
SR>
SR> Head SHA1: 6aaac97b2b5e0750a2739c3a247d79d4fadac43e
SR>
SR>
SR>Or to build 3.0.14-rt31 directly, the following patches should be applied:
SR>
SR> http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.0.tar.xz
SR>
SR> http://www.kernel.org/pub/linux/kernel/v3.0/patch-3.0.14.xz
SR>
SR> http://www.kernel.org/pub/linux/kernel/projects/rt/3.0/patch-3.0.14-rt31.patch.xz
SR>
SR>
SR>The broken out patches are available at:
SR>
SR> http://www.kernel.org/pub/linux/kernel/projects/rt/3.0/patches-3.0.14-rt31.tar.xz
SR>
SR>Enjoy,
SR>
SR>-- Steve
SR>
SR>
SR>
C уважением With Best Regards
Георгиевский Юрий. Georgiewskiy Yuriy
+7 4872 711666 +7 4872 711666
факс +7 4872 711143 fax +7 4872 711143
Компания ООО "Ай Ти Сервис" IT Service Ltd
http://nkoort.ru http://nkoort.ru
JID: GHhost@icf.org.ru JID: GHhost@icf.org.ru
YG129-RIPE YG129-RIPE
next prev parent reply other threads:[~2011-12-22 14:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 3:40 [ANNOUNCE] 3.0.14-rt31 Steven Rostedt
2011-12-22 11:08 ` Raz
2011-12-22 11:50 ` Steven Rostedt
2011-12-22 14:00 ` Georgiewskiy Yuriy [this message]
2011-12-22 14:44 ` Steven Rostedt
2011-12-22 15:29 ` Georgiewskiy Yuriy
2011-12-22 16:23 ` Steven Rostedt
2011-12-22 16:35 ` Georgiewskiy Yuriy
2011-12-24 0:02 ` Karsten Wiese
2011-12-24 14:13 ` Steven Rostedt
2011-12-24 16:16 ` Clark Williams
2012-01-10 18:53 ` Steven Rostedt
2012-01-10 23:56 ` Karsten Wiese
2012-01-04 15:19 ` Georgiewskiy Yuriy
2012-01-11 11:10 ` Karsten Wiese
2012-01-11 15:39 ` Steven Rostedt
2012-01-12 10:18 ` Tim Sander
2012-01-12 13:54 ` Steven Rostedt
2012-01-12 16:57 ` Tim Sander
2012-01-13 9:42 ` Tim Sander
2012-01-13 18:45 ` Bernardo Barros
2012-01-13 20:30 ` Tim Sander
2012-01-13 23:51 ` Steven Rostedt
2012-01-17 14:27 ` [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame? Tim Sander
2012-01-17 14:42 ` Steven Rostedt
2012-01-17 17:40 ` Mike Galbraith
2012-01-18 11:11 ` [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame? Yep Tim Sander
2012-01-18 13:54 ` Mike Galbraith
2012-01-18 15:37 ` Steven Rostedt
2012-01-24 10:52 ` Tim Sander
2012-01-25 9:31 ` Tim Sander
2012-02-01 20:27 ` Steven Rostedt
2012-02-01 23:11 ` Tim Sander
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=alpine.DEB.2.02.1112221759480.6601@icf.org.ru \
--to=bottleman@icf.org.ru \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).