linux-kernel - Re: linux-2.6.23-mm1 crashed

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: <2a382c6e0710141224n2b8a47c8v1346f1a9dedc7943@mail.gmail.com>
Date:	Sun, 14 Oct 2007 23:24:39 +0400
From:	"Dave Milter" <davemilter@...il.com>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-2.6.23-mm1 crashed

By the way, because of oops happens on early stage of boot,
you not need any image to reproduce this bug:
something like this will be enough:
1)cd /tmp/ && qemu-img create hda.img 10M
2)cd linux/mm/source/code
3)qemu -kernel arch/i386/boot/bzImage -hda /tmp/hda.img

if you add "-s" to qemu options you can after that do:
gdb vmlinux
$target remote localhost:1234
$br gth_timeout
$continue

On 10/14/07, Dave Milter <davemilter@...il.com> wrote:
> I build linux-2.6.23-mm1 and try to boot it using qemu,
> and it crashed with trace like this:
> do_page_fault
> error_code
> lock_acquire
> _spin_lock_irqsave
> gdth_timeout
> run_timer_softirq
> __do_softirq
> do_softirq
>
> I have screenshot, but have no idea, is it legal to include it, if I
> sent copy to lkml.
> config of kernel in attachment,
> I apply all three patches from hot-fixes.
>
>
-
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/