From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.24-rc7-rt2
Date: Wed, 16 Jan 2008 12:11:22 +0200 [thread overview]
Message-ID: <200801161211.25948.caglar@pardus.org.tr> (raw)
In-Reply-To: <200801160912.37814.caglar@pardus.org.tr>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
Hi Again;
16 Oca 2008 Çar tarihinde, S.Çağlar Onur şunları yazmıştı:
> 16 Oca 2008 Çar tarihinde, Steven Rostedt şunları yazmıştı:
> > On Tue, 15 Jan 2008, [utf-8] S.Ã^GaÄ^_lar Onur wrote:
> > > 2.6.24-rc7-rt2 (-rt2 patchset on top of Linus's current git commit
> > > 031f2dcd7075e218e74dd7f942ad015cf82dffab) starts to complain like
> > > following (full dmesg can be found @ [1]) when try to login from
> > > console (the other acpi related errors also existed in 2.6.24-rc5-rt1)
> > > and FYI, plain 2.6.24-rc7 (again commit
> > > 031f2dcd7075e218e74dd7f942ad015cf82dffab) has no issues.
> >
> > Do you get the same issues if you add to -rc7 and not git.
>
> I'll try after trying -rt3.
-rt3 on top of 2.6.24-rc8 works fine without that sysfs problem (acpi warnings
still there and full dmesg can be found from [1]), whatever causes this seems
solved :)
[1] http://cekirdek.pardus.org.tr/~caglar/dmesg.rt3
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-16 10:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 18:41 2.6.24-rc7-rt2 Steven Rostedt
2008-01-14 20:02 ` 2.6.24-rc7-rt2 Mark Knecht
2008-01-14 22:16 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-14 22:30 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 17:10 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-17 2:07 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-17 17:11 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-17 17:25 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-17 17:57 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-15 0:37 ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-16 3:50 ` 2.6.24-rc7-rt2 Valdis.Kletnieks
2008-01-16 4:04 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 6:23 ` 2.6.24-rc7-rt2 Valdis.Kletnieks
2008-01-16 14:12 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 16:22 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-21 11:31 ` 2.6.24-rc7-rt2 Esben Nielsen
2008-01-21 12:49 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-27 21:51 ` 2.6.24-rc7-rt2 Esben Nielsen
2008-01-28 2:32 ` 2.6.24-rc7-rt2 Stefan Monnier
2008-01-16 13:17 ` 2.6.24-rc7-rt2 Alan Cox
2008-01-16 4:01 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 7:12 ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-16 10:11 ` S.Çağlar Onur [this message]
2008-01-17 2:20 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 3:44 ` 2.6.24-rc7-rt2: WARNING: at include/linux/rcupreempt.h:110 rcu_enter_nohz() Mike Galbraith
2008-01-15 16:27 ` 2.6.24-rc7-rt2 Luotao Fu
2008-01-15 18:06 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 20:04 ` 2.6.24-rc7-rt2 Luotao Fu
2008-01-16 12:03 ` 2.6.24-rc7-rt2 [PATCH] latency tracer fix for ppc32 Luotao Fu
2008-01-17 3:26 ` 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=200801161211.25948.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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