linux-kernel - Hard crash with 2.6.17-rt8

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>] [day] [month] [year] [list]

Date:	Thu, 3 Aug 2006 14:00:31 -0700
From:	"Mark Knecht" <markknecht@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Steven Rostedt" <rostedt@...dmis.org>,
	"hui Bill Huey" <billh@...ppy.monkey.org>
Subject: Hard crash with 2.6.17-rt8

Hi,
   Two things:

1) While compiling some code this morning on my AMD64 machine using
2.6.17-rt8 I had a hard crash. Everything was hung  - the compile,
Gnome, everything - and I didn't seem to be able to get out with and
key combination so I did a hard reset.

2) I tried rebooting into 2.6.17-rt8 and hung during the boot process.
I managed to catch one not-so-good photo (the flash was on) showing
the "3-level deep critical section nesting". Let me know who to send
it to off list. The end shows something like:

__sched_text_start+0x3b/0x58f...[<00000000>] <=0x0
rt_lock_slowclock_)x30/0x23e...[<00000000>] <=0x0
rt_lock_slowclock_)x30/0x23e...[<00000000>] <=0x0

Up above there is some stuff like:

rt_lock_slowdown
get_page_from_freelist
get_zeroed_page
pte_alloc
__handle_mm_fault.
do_(something I cannot read)
do_(somethign I cannot read)
debug_(something)_mutex_unlock
error_exit

Unfortunately stuff in there is blanked out by the flash reflecting on
the screen. (Stupid me! Sorry!)

   I've gone back to 2.6.17-rt5 for now which has been running great
and never crashed on me.

   I hope this little bit helps confirm some of what you all are
debuggin in your other threads.

Cheers,
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/