Andrew Vasquez <[email protected]> writes:
>> A couple more tidbits of information on this problem.
>>
>> 1) I have seen this on two different boards
>> a Tyan S4882 and a Arima HDAMA, with and without linuxbios.
>> In just messing around adding "debug" on the kernel command line
>> or changing Dprintk in smpboot.c:smp_callin() to printk,
>> avoids this boot lock up for me.
>
> All,
>
> Has there been any resolution to this problem. I've just tried
> 2.6.13-rc1 on a Dell PowerEdge 2850 (dual-proc em64t) and am running
> into what appears to be a similar case where cpu initialization never
> completes. I'll attach my .config, boot-up messages, and the output
> of lspci.
>
> I've also tried the s/Dprintk/printk/ hack with no success.
I can confirm that I am seeing this on Xeons as well with my problem
2.6.12 kernel. And specifying debug does cause it to go away, for me.
As for which debug messages cause the bug not to be trigger I am
logging to the serial console which may be part of the difference.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
