From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: john stultz <johnstul@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodm
Cc: Bernardo Barros <bernardobarros2@gmail.com>,
William Blackburn <bill_-@hotmail.com>,
nando@ccrma.Stanford.EDU
Subject: BUG: [PlanetCCRMA] update: new kernel for fc13 (2.6.33.6 + rt28)
Date: Sat, 07 Aug 2010 17:44:11 -0700 [thread overview]
Message-ID: <1281228251.17527.13.camel@localhost.localdomain> (raw)
Here's a report from of one of the users of my rt28 build for 2.6.33.6
(for Planet CCRMA)... Another user (William) is also having freezes but
with no clues left behind in /var/log/messages...
-- Fernando
-------- Forwarded Message --------
From: Bernardo Barros <bernardobarros2@gmail.com>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: William Blackburn <bill_-@hotmail.com>,
planetccrma@ccrma.Stanford.EDU
Subject: Re: [PlanetCCRMA] update: new kernel for fc13 (2.6.33.6 +
rt28)(William Blackburn)
Date: Sat, 7 Aug 2010 18:06:01 -0300
Hi,
I'm also getting oops and freezes with the new rt-kernel. No
experimental mesa drivers now, but still I only get 3d accelerations
with the experimental mesa drivers. I also get some errors on startup
about nouveau driver (on both kernels) and a error about a USB device
file with the rt-kernel.
I was using supercollider, jack and ardour. The oops bug report is here:
Package: kernel
Latest Crash: Sat 07 Aug 2010 05:14:44 PM
Command: not_applicable
Reason: BUG: unable to handle kernel NULL pointer dereference at
0000000000000048
Comment: None
Bug Reports:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000048
IP: [<ffffffffa0070e25>] ttm_tt_swapout+0x92/0x1c9 [ttm]
PGD 11009b067 PUD 10ce2f067 PMD 0
Oops: 0000 [#1] PREEMPT SMP
last sysfs file: /sys/devices/system/cpu/cpu7/cache/index2/shared_cpu_map
CPU 1
Pid: 326, comm: ttm_swap Not tainted
2.6.33.6-147.2.4.rt28.1.fc13.ccrma.x86_64.rt #1 43192PU/43192PU
RIP: 0010:[<ffffffffa0070e25>] [<ffffffffa0070e25>]
ttm_tt_swapout+0x92/0x1c9 [ttm]
RSP: 0018:ffff88012b3afcb0 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8800b0f20640 RCX: 0000000000000000
RDX: ffff88012b3b8780 RSI: ffff88010e9375c0 RDI: ffff8800b0f20640
RBP: ffff88012b3afd10 R08: 0000000000000022 R09: 0000000000000002
R10: ffff8800b0f20640 R11: 0000000000000004 R12: ffff88010e9375c0
R13: ffff88010e9375c0 R14: ffff88010ce42090 R15: ffff88012ac623c0
FS: 0000000000000000(0000) GS:ffff880006240000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000048 CR3: 0000000129516000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process ttm_swap (pid: 326, threadinfo ffff88012b3ae000, task ffff88012b3b8780)
Stack:
0000000000105ee0 0000000000105eef ffff88012a143108 000000000000bdc7
0000000100000000 ffff88010ce42000 ffff88010ce42044 ffff88010ce42000
ffff88010ce42044 0000000000000000 ffff88010ce42090 ffff88012ac623c0
Call Trace:
[<ffffffffa007255a>] ttm_bo_swapout+0x1ee/0x22e [ttm]
[<ffffffffa0070385>] ttm_shrink+0x9d/0xc4 [ttm]
[<ffffffffa00703c0>] ttm_shrink_work+0x14/0x16 [ttm]
[<ffffffff81062b56>] worker_thread+0x1d8/0x275
[<ffffffffa00703ac>] ? ttm_shrink_work+0x0/0x16 [ttm]
[<ffffffff81066c23>] ? autoremove_wake_function+0x0/0x34
[<ffffffff8106297e>] ? worker_thread+0x0/0x275
[<ffffffff8106689e>] kthread+0x7a/0x82
[<ffffffff8100aa24>] kernel_thread_helper+0x4/0x10
[<ffffffff81066824>] ? kthread+0x0/0x82
[<ffffffff8100aa20>] ? kernel_thread_helper+0x0/0x10
Code: e8 26 00 06 e1 48 3d 00 f0 ff ff 49 89 c4 76 16 48 c7 c7 66 7c
07 a0 31 c0 45 89 e6 e8 6c b7 3c e1 e9 2a 01 00 00 49 8b 44 24 18 <48>
8b 40 48 4c 8b b8 50 01 00 00 c7 45 c4 00 00 00 00 65 48 8b
RIP [<ffffffffa0070e25>] ttm_tt_swapout+0x92/0x1c9 [ttm]
RSP <ffff88012b3afcb0>
CR2: 0000000000000048
reply other threads:[~2010-08-08 0:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1281228251.17527.13.camel@localhost.localdomain \
--to=nando@ccrma.stanford.edu \
--cc=bernardobarros2@gmail.com \
--cc=bill_-@hotmail.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodm \
--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;
as well as URLs for NNTP newsgroup(s).