Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #59862 > unrolled thread

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node  #0, CPUs:    #1" Yves-Alexis Perez <corsac@debian.org> - 2018-01-06 18:50 +0100
    Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node  #0, CPUs:    #1" "LJ" <ljdebbug@ljay.org.uk> - 2018-01-06 19:40 +0100
      Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node  #0, CPUs:    #1" "LJ" <ljdebbug@ljay.org.uk> - 2018-01-06 20:00 +0100
        Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node  #0, CPUs:    #1" "LJ" <ljdebbug@ljay.org.uk> - 2018-01-07 11:00 +0100

#59862 — Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[Multipart message — attachments visible in raw view] — view raw

On Sat, 2018-01-06 at 15:46 +0000, LJ wrote:
> Booting in recovery mode the final lines are:
> 
> [   0.058600] x86: Booting SMP configuration:
> [   0.058632] .... node  #0, CPUs:      :1
> 
> The cursor is flashing after the "#1" and the system hangs at that point.
> 
> I have video and a screenshot of boot if that helps.

Looking at the lspci output you have a Xeon E3 from the 1200 series, but you
could provide your full /proc/cpuinfo?

You're running the system in 32bit mode, which KAISER/KPTI doesn't touch (so
meltdown is *not* fixed), so I guess it comes from the preparation patches for
 KAISER rather than KAISER itself.

Regards,
-- 
Yves-Alexis

[toc] | [next] | [standalone]

#59865

> Looking at the lspci output you have a Xeon E3 from the 1200 series, but
> you
> could provide your full /proc/cpuinfo?

Hi, sure...

root@sam:~# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 60
model name      : Intel(R) Celeron(R) CPU G1840 @ 2.80GHz
stepping        : 3
microcode       : 0x22
cpu MHz         : 1097.680
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer
xsave rdrand lahf_lm abm tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust erms invpcid xsaveopt dtherm arat pln pts
bugs            :
bogomips        : 5587.41
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 60
model name      : Intel(R) Celeron(R) CPU G1840 @ 2.80GHz
stepping        : 3
microcode       : 0x22
cpu MHz         : 1199.877
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 2
initial apicid  : 2
fdiv_bug        : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer
xsave rdrand lahf_lm abm tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust erms invpcid xsaveopt dtherm arat pln pts
bugs            :
bogomips        : 5587.41
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

Thanks,
LJ

[toc] | [prev] | [next] | [standalone]

#59866

> Try also booting without 'quiet' and with 'debug earlyprintk'.

Happy to try, but not sure how to do that - do I edit
/boot/config-4.9.0-5-686-pae ?  Couldn't see "QUIET" in there?

> If you manage to get a kernel log (using a
> serial port or maybe netconsole if it's not too early in the boot) it'd
> help I guess.

The box has a serial port, but not sure I've got anything to plug into it!
I might have an old Debian box somewhere... :)

Thanks,
LJ

[toc] | [prev] | [next] | [standalone]

#59880

>> Try also booting without 'quiet' and with 'debug earlyprintk'.
>
> Happy to try, but not sure how to do that

Worked out how to do it...  Edited /etc/default/grub removed "quiet" and
added "earlyprintk=vga debug" to GRUB_CMDLINE_LINUX_DEFAULT and ran
update-grub.

The bad news is that it hangs at the same point:

[    0.058517] CPU 1 irqstacks, hard=f75be000 soft=f75c0000
[    0.058551] x86: Booting SMP configuration:
[    0.058583] .... node  #0, CPUs:      #1

I had a look in the BIOS and the only thing that looked vaguely
interesting was "Execute Disable Bit" - "Intel Extreme Disable Bit
Function.  Supported CPUs can help protect from virus and malicious buffer
overflow attacks", but that didn't make any difference.

Had a read through the link Ben Hutchings sent
(https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html)
and ended up with:

GRUB_CMDLINE_LINUX_DEFAULT="earlyprintk=vga,keep debug udbg-immortal
ekgdboc=kbd"

But that didn't give any more info. :(

Thanks,
LJ

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web