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]
Date:	Sun, 26 Apr 2009 12:25:51 +0000 (UTC)
From:	Jeffrey Cao <jcao.linux@...il.com>
To:	linux-kernel@...r.kernel.org
Subject:  Re: Kernel locks up when idle on VIA-nano U2300 with VIA VX800 on
 Jetway JNF76-N1GL-LF mainboard

On 2009-04-26, Martin Mueller <mm@...21.net> wrote:
> Hi all,
>
> last Thursday my mini-ITX board in my home-server died and I had to
> get a replacement board. I got an fanless Jetway JNF76-N1GL-LF from a
> local Dealer. The board uses a 1GHz U2300 VIA-nano CPU[1] and an VIA
> VX800 chipset. After replacing the board, the adventure actually
> started:
>
> Booting my installed debian with kernel 2.6.29-1-686 (debian kernel) failed.
> The system just hang when detecting the harddisks during the boot
> process, no oops, no messages, just no reaction any more. 
>
> Fortunatelly I had an old 2.6.23-1-686 (debian kernel) still hanging around
> in the grub menu. This kernel works flawlessly on the board (aside
> from not recognizing the VIA HD-audio, which doesn't bother me at the
> moment).
>
> Next, I downloaded linux-2.6.30-rc3, compiled a minimal version with
> just initrd. I left out PCI-support, ACPI and almost everything else
> menuconfig allowed me to unselect except the VGA text console. This
> kernel locked up after giving me the initial prompt from busybox in
> the initrd.
>
> When adding the following lines in the script executed by the kernel
> after booting in the initrd, the system actually works:
>
>   while true; do true; done &
>   /bin/sh
>
> As soon as I kill the shell loop, the system freezes again.
>
> So my conclusion is: the kernel locks up the first time the CPU
> is idle.
>
> Any hints on how to proceed from here?
>

This seems something to do with the board and the hard disk drive.
Do you attach the hard disk to the board correctly? Is there any jumper settings
on the board? Is there any additional module needed by your new board? You can
boot a live CD (Ubuntu is a nice one, it is built with most latest kernel and 
modules) and try to mount your hard disk to make sure the hardware is OK. If this
works, then try to figure out which module is missing in your old kernel.

Jeffrey

--
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