Boot error SMP
Hans van Leest
hvleest at signet.nl
Tue Jun 28 15:45:39 GMT 2005
I had problems with the serial console.
XP said that COM1 was busy. For the rest I followed this guideline:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html
To give you the output, I typed it over and checked it twice!
So here is the output.
Waiting 15 seconds for SCSI devices to settle
da0 at iir0 bus 2 target 0 lun 0
da0: <Intel Host Drive #oo > Fixed Direct Access SCSI-2 device
da0: Tagged Queueing Enabled
da0: 152562MB (312448185 512 byte sectors: 255H 63S/T 19449C)
SMP: AP CPU #1 Launched!
Fatal trap 12:page fault while in kernel mode
cpuid = 1; apic id = 06
fault virtual addres = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc044b9e7
stack pointer = 0x10:0xe4d9ece0
frame pointer = 0x10:0xe4d9ecf4
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 66 (swi3: cambio)
trap number = 12
panic: page fault
cpuid = 1
boot() called on cpu#o
Uptime: 16s
John Baldwin wrote:
>On Monday 27 June 2005 04:36 pm, Hans van Leest wrote:
>
>
>>John Baldwin wrote:
>>
>>
>>>On Monday 27 June 2005 03:58 pm, Hans van Leest wrote:
>>>
>>>
>>>>I can boot boot from a SMP a 5.3 stable kernel when loader.conf
>>>>contains: kern.smp.disabled=1.
>>>>Otherwise it's crashing.
>>>>But how do I continue?
>>>>I've tried CURRENT, only I've got a problem with booting in single user.
>>>>Proberbly it's the iir driver.
>>>>Thanx in advance
>>>>
>>>>
>>>Can you get details of the crash? For example, can you boot over a serial
>>>console and provide the output when it crashes? Also, can you compile the
>>>debugger into the kernel and get a stack trace?
>>>
>>>
>>I've tried to use dumpdir and dumpdev to save the dump. With no succes.
>>I'm not that familair with kernel debugging.
>>I putted : dumpdev="/dev/ad0s1b" and dumpdir="YES" in my rc.conf. Only,
>>when I boot, I get the message: Wrong dump device or directory.
>>I will use the dev-handbook to try to get a dump of the crash.
>>Is CURRENT an option? Or can I stick with 5.3 STABLE?
>>
>>
>> Thx
>>
>>
>
>5.x is fine. You don't have to get a dump. If you can setup a serial console
>you can just cut and paste the panic messages.
>
>
>
More information about the freebsd-smp
mailing list