Bug#416210: linux-image-2.6.18-4-686: Hangs at initrd boot state dual PentiumIII chipset ServerWorks OSB4
On Sun, Mar 25, 2007 at 07:05:12PM +0200, Grzegorz Szyszlo wrote:
> Package: linux-image-2.6.18-4-686
> Version: 2.6.18.dfsg.1-11
> Severity: critical
> Justification: breaks the whole system
> System: fresh pure install, all tasks from tasksel. On install state
> I hadn't any problems, but next boot cause any big problem for me:
> Kernel 2.6.18-4-486 works ok, but it has only ONE processor support and
> is slower.
> Kernel 2.6.18-4-686 hangs at boot. I don't know how switch off SMP at
> boot for tests.
> both install selections SMP & nonSMP uses both installed processors.
> I had this problem with -3- kernel version. Previous I don't remember,
> because I had not much time for tests, and I reinstalled system many times
> to find stable system.
> I didn't try remove one processor for test. I'll do it if it will be needed.
> System hanging is very strange.
> I can do ctrl+alt+del, I can scroll shift+pgup/pgdown. Maybe one
> thread is hang, and don't allow second thread (second processor)
> to continue boot process.
> After about 45 minutes system boot, but .... hangs on another step.
> Finally system start up, but is very unstable. A lot of processes
> have <zombie> status. It is impossible to down system properly.
> shutdown -h now didn't down the system for about 3 hours,
> but started this process corectly - changed init state i succesfully
> stopped some of daemons.
> To install correctly fresh system, I must look out for selecting 486
> kernel version, because 686 strange hang at initrd/boot state.
> Bootloader is grub, booted as (hd0,1) or /dev/ida/c0d0p2,
> because on p1 is configuration partition. Making boot sector on c0d0
> cause config partition unusable. Really config partition is DOS partition,
> accessed by BIOS. c0d0p2 has bootable flag. Booting cause no problems.
> Kernel & initrd file are loaded & initialized correctly.
> My needs:
> 1. I have two computers. Give me scheme for RS232 cable to save
> all startup log, and command for kernel to switch output to RS232.
> I can use minicom for getting messages.
> 2. I want temporarly switch off SMP on -686, & try boot.
> 3. Maybe use 486 kernel version with SMP support
> If it don't take any effect, please help me remove kernel module by
> module, to find one that cause problem.
> I think, it's possible 3 ways for resolving:
> 1. SMP cause problem
> 2. 686 cause problem
> 3. Problem is in any kernel module compiled as SMP or 680 or both.
Does this error still occur with more recent kernel versions?
If you're running Etch, could you try to reproduce this bug
with the 2.6.24 based kernel added in 4.0r4?
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org