linux-kernel - Re: 2.6.18-rt1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5bdc1c8b0609201238te67affcne7bb21d50bda3a69@mail.gmail.com>
Date:	Wed, 20 Sep 2006 12:38:55 -0700
From:	"Mark Knecht" <markknecht@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"John Stultz" <johnstul@...ibm.com>,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	"Dipankar Sarma" <dipankar@...ibm.com>,
	"Arjan van de Ven" <arjan@...radead.org>
Subject: Re: 2.6.18-rt1

On 9/20/06, Ingo Molnar <mingo@...e.hu> wrote:
> I'm pleased to announce the 2.6.18-rt1 tree, which can be downloaded
> from the usual place:
>
>    http://redhat.com/~mingo/realtime-preempt/
>

Hi Ingo,
   I gave 2.6.18-rt2 a quick try. It compiled fine but crashed on
boot. I've no way to copy the screen. I can send along a digital photo
if the following isn't enough info.

QUESTION: Should I be able to run ati-drivers-8.28.8 with this kernel
or would I have to wait for ATI to put out a 2.6.18 compatible driver?
The current version does not emerge with 2.6.18-rt2.

CRASH INFO:

Unable to handle kernel null pointer derefernce at 0000000000000000 RIP
[< ffffffff80228ae4 >] __wake_up_common+0x24/0x68
PGD 3d6e7067 PUD 3d638067 PMD 0
Oops: 0000 [1] PREEMPT SMP
CPU
Modules linked in:
Pid: 5, comm:softirq-timer/0 Not tainted 2.6.18-rt2 #2

There is a bunch of debug stuff that follows and then finally a trace:

__wake_up
hrt_time_run_queue
run_timer_softirq
kthread
child_rip
DWARF2 unwinder stuck at child_rip

more stuff......

preempt count: 00000001
1-level deep critical nesting:

__spin_trylock

Not sure how much that will help you. Been awhile since I've sent
along crash reports. I'll have to ge a second Linux machine running to
do the console boot capture thing if you need it.

Hope this helps,
Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/