From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Subject: Re: [ANNOUNCE] 3.0.6-rt16
Date: Wed, 05 Oct 2011 12:22:22 -0700 [thread overview]
Message-ID: <4E8CAE6E.8020905@localhost> (raw)
In-Reply-To: <alpine.LFD.2.02.1110042139350.18778@ionos>
[-- Attachment #1: Type: text/plain, Size: 2524 bytes --]
On 10/04/2011 01:19 PM, Thomas Gleixner wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.0.6-rt16 release.
Thanks!!
Still seeing some problems:
[ 92.591009] ------------[ cut here ]------------
[ 92.591022] WARNING: at kernel/hrtimer.c:391
hrtimer_fixup_activate+0x41/0x45()
[ 92.591025] Hardware name: 6463CTO
[ 92.591028] Modules linked in: fuse ppdev parport_pc lp parport
sunrpc rfcomm bnep ip6t_REJECT nf_conntrack_ipv4 nf_defrag_ipv4
nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter
ip6_tables snd_hda_codec_analog arc4 snd_hda_intel snd_hda_codec
snd_hwdep r852 sm_common snd_seq snd_seq_device iwl3945 iwl_legacy btusb
nand nand_ids snd_pcm mac80211 cfg80211 r592 snd_timer nand_ecc
thinkpad_acpi bluetooth snd i2c_i801 mtd iTCO_wdt memstick joydev
microcode snd_page_alloc rfkill iTCO_vendor_support soundcore e1000e
binfmt_misc sdhci_pci sdhci firewire_ohci mmc_core firewire_core
yenta_socket crc_itu_t i915 drm_kms_helper drm i2c_algo_bit i2c_core
video [last unloaded: scsi_wait_scan]
[ 92.591097] Pid: 0, comm: kworker/0:0 Tainted: G W
3.0.6-1.rt16.1.fc15.ccrma.i686.rtPAE #1
[ 92.591099] Call Trace:
[ 92.591106] [<c085ac69>] ? printk+0x2d/0x2f
[ 92.591111] [<c0447cb7>] warn_slowpath_common+0x7c/0x91
[ 92.591115] [<c046642f>] ? hrtimer_fixup_activate+0x41/0x45
[ 92.591119] [<c046642f>] ? hrtimer_fixup_activate+0x41/0x45
[ 92.591122] [<c04663ee>] ? hrtimer_init_on_stack+0x2d/0x2d
[ 92.591126] [<c0447cee>] warn_slowpath_null+0x22/0x24
[ 92.591130] [<c046642f>] hrtimer_fixup_activate+0x41/0x45
[ 92.591135] [<c060086d>] debug_object_fixup+0x17/0x23
[ 92.591140] [<c0600e1d>] debug_object_activate+0xc5/0xcc
[ 92.591143] [<c046649e>] enqueue_hrtimer+0x19/0xa0
[ 92.591148] [<c046714b>] __hrtimer_start_range_ns+0x1b2/0x253
[ 92.591153] [<c046723f>] hrtimer_start_range_ns+0x26/0x2c
[ 92.591158] [<c0472dee>] hrtimer_start_expires.constprop.1+0x28/0x2e
[ 92.591163] [<c04732b8>] tick_nohz_restart_sched_tick+0x109/0x148
[ 92.591167] [<c04085d2>] cpu_idle+0x90/0x97
[ 92.591172] [<c08540e1>] start_secondary+0x250/0x252
[ 92.591175] ---[ end trace 000000000000006f ]---
[ 93.288005] ------------[ cut here ]------------
Full dmesg and complete config attached.
Regretfully it does not stay up and running for long. Eventually the
whole machine freezes and has to be power cycled (a T61 laptop, used to
work with previous 3.x rty releases - sorry, don't know when it broke).
-- Fernando
[-- Attachment #2: dmesg-3.0.6.bz2 --]
[-- Type: application/x-bzip, Size: 6851 bytes --]
[-- Attachment #3: config-3.0.6.bz2 --]
[-- Type: application/x-bzip, Size: 28838 bytes --]
prev parent reply other threads:[~2011-10-05 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 20:19 [ANNOUNCE] 3.0.6-rt16 Thomas Gleixner
2011-10-05 2:44 ` Frank Rowand
2011-10-05 19:22 ` Fernando Lopez-Lezcano [this message]
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=4E8CAE6E.8020905@localhost \
--to=nando@ccrma.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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