| View previous topic :: View next topic |
| Author |
Message |
bent
n00b
Joined: 26 Mar 2003
Posts: 62
Location: New Zealand
|
 Posted: Wed Jul 04, 2012 8:37 pm Post subject: Cores other than 0 won't start if key pressed during startup |
 |
|
I recently added a vga= parameter to my kernel command line to experiment with different resolutions. The video mode is not recognised, so the kernel prompts me for a video mode shortly after being loaded. This prompt times out after 30 seconds, and the machine boots with the default video mode. I'm usually not around to answer this prompt; my machine takes a very long time to POST so I normally just switch it on and walk away, eventually the kernel boots, vga prompt appears and times out, and the kernel boots normally.
I problem occurs whenever this prompt is not allowed to time out. For example, if I press <SPACE> to continue with the default video mode, the boot carries on and fails to start CPUs 1-7, with "CPU%d: Not responding.". CPU0 is the only core that starts. Boot then continues to the point the PCI bus is scanned, and the machine suddenly restarts so I can't scroll back to see more messages.
The same fault occurs no matter what I type at the VGA prompt, the machine only boots correctly if this prompt is allowed to time out. It seems only to happen when arch/x86/boot/tty.c/getchar() has been called, though I appreciate I may be barking up the wrong tree completely.
The bug is easy enough to work around for me, just remove the vga=xxx argument that I don't even need anyway, but before I do I'd like to see if I can help narrow this little bug down. Any suggestions?
_________________
amd64, x86, ppc. Gave away my mips, broke my foot on the alpha, someone stole my sparc :'( |
|
| Back to top |
|
 |
bent
n00b
Joined: 26 Mar 2003
Posts: 62
Location: New Zealand
|
| Posted: Wed Jul 04, 2012 9:27 pm Post subject: |
|
|
Here is CPU information from a successful boot:
| Code: | [ 0.006560] CPU: Physical Processor ID: 0
[ 0.006619] CPU: Processor Core ID: 0
[ 0.006680] mce: CPU supports 9 MCE banks
[ 0.006747] CPU0: Thermal monitoring enabled (TM1)
[ 0.006813] using mwait in idle threads.
[ 0.006926] ACPI: Core revision 20110623
[ 0.010413] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.020466] CPU0: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz stepping 05
[ 0.121776] Performance Events: PEBS fmt1+, erratum AAJ80 worked around, Nehalem events, Intel PMU driver.
[ 0.122019] ... version: 3
[ 0.122078] ... bit width: 48
[ 0.122138] ... generic registers: 4
[ 0.122197] ... value mask: 0000ffffffffffff
[ 0.122259] ... max period: 000000007fffffff
[ 0.122320] ... fixed-purpose events: 3
[ 0.122380] ... event mask: 000000070000000f
[ 0.122582] Booting Node 0, Processors #1
[ 0.122670] smpboot cpu 1: start_ip = 99000
[ 0.213810] #2
[ 0.213854] smpboot cpu 2: start_ip = 99000
[ 0.304696] #3
[ 0.304740] smpboot cpu 3: start_ip = 99000
[ 0.395577] #4
[ 0.395621] smpboot cpu 4: start_ip = 99000
[ 0.486434] #5
[ 0.486479] smpboot cpu 5: start_ip = 99000
[ 0.577326] #6
[ 0.577371] smpboot cpu 6: start_ip = 99000
[ 0.668220] #7 Ok.
[ 0.668279] smpboot cpu 7: start_ip = 99000
[ 0.759012] Brought up 8 CPUs
[ 0.759072] Total of 8 processors activated (43173.05 BogoMIPS).
|
_________________
amd64, x86, ppc. Gave away my mips, broke my foot on the alpha, someone stole my sparc :'( |
|
| Back to top |
|
|
pidsley
n00b
Joined: 09 Jun 2012
Posts: 63
|
| Posted: Thu Jul 05, 2012 12:43 am Post subject: |
|
|
| Is there some reason you don't want to use KMS? Do you know why your machine takes so long to POST? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
