List Info

Thread: ahd problems in dom0 with Xen3 with dmesg




ahd problems in dom0 with Xen3 with dmesg
user name
2006-07-25 18:34:42
Hi all,

I encounter the same problem when booting Dom0 from a SATA
drive :

piixide1:0:0 lost interrupt
type: ata tc_bcount: 0 tc_skip:0

The kernel goes into a loop with this error message ...

I've tried to use some options in grub/menu.lst like  
"ignorebiostables" or "noapic" ...
But the problem is still there :(

I've rebuild all my kernels from the latest sources
because, I use an  
athlon64x2 to build the netbsd-current ... no effects ...

My computer is an HP d530 / Céléron 2.4GHz ...

Any idea ?

Best regards

Le 10 juil. 06 à 14:53, John R. Shannon a écrit :

> John R. Shannon wrote:
>> John R. Shannon wrote:
>>> Pavel Cahyna wrote:
>>>> On Sun, Jul 09, 2006 at 06:27:00AM -0600,
John R. Shannon wrote:
>>>>> dom0 goes into a loop, on boot, where
it dumps the SCSI controller
>>>>> state. Computer has dual Xeon
processors and dual SCSI drives.
>>>>
>>>> Almost certainly lost interrupts. See http://permalink.gmane.or
g/ 
>>>> gmane.os.netbsd.ports.xen/1546
>>>>
>>>> Pavel
>>>
>>> "nosmp" is specified as a Xen boot
parameter in /grub/menu.lst
>>>
>>> Should this be specified differently?
>>>
>> With nosmp, dmesg does not show the other CPU. I
did not post it  
>> as it otherwise looks the same.
>
> It does boot, without this error, if I specify
"noapic".
>
> -- 
> John R. Shannon, CISSP
> johnjohnrshannon.com
> jshannondsci-usa.com
> john.r.shannonus.army.mil
> shannonjrNetBSD.org
>

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )