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]
Message-ID: <5da0588e0806091116l31344cdfp90b3407abdaea345@mail.gmail.com>
Date:	Mon, 9 Jun 2008 14:16:03 -0400
From:	Rince <rincebrain@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: [BUG] rt_worker_func panics on my Asus motherboard

Hi LKML,
I've got an Asus P5BV-C/4L motherboard - somewhat badly supported
pre-2.6.25. Debian and Ubuntu stable refused to boot their install CDs
on it...but I digress.

I couldn't run 2.6.24 on it - it hung forever on initializing the SATA
ports. So I booted a GIT kernel (Git from May 31st at around 10 PM),
and hurray, it worked correctly.

Unfortunately, recently, the server went down. I turned on the
monitor, and a wonderful panic greeted me (scrolled a few lines off
the top, "of course"). I did not have a good camera handy, but I can
transcribe it in parts as requested. Below is the call trace:

[<ffffffff803b8582>]rt_worker_func+0x0/0x16c
[<ffffffff8023dc95>]run_workqueue+0x7b/0x103
[<ffffffff8023e533>]worker_thread+0xd5/0xe0
[<ffffffff80240d19>]autoremove_wake_function+0x0/0x2e
[<ffffffff8023e45e>]worker_thread+0x0/0xe0
[...]

My kernel config can be found on acm.jhu.edu/~rercola/astrolabe-config.gz

Any additional information I can provide, I will be more than willing
to. I've linked this to one or two questionable pieces of networking
hardware I have laying around, so I can reproduce it freely.

Thanks to anyone who can shed light on this!
- Rich
-- 
Wrinkles should merely indicate where smiles have been. -- Mark Twain
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ