Re: ahd problems in dom0 with Xen3 with dmesg

[KlinT <klint%klintcentral.net@localhost>]

Yes I've tried it ...

But, I think it's not "noapic" but "noacpi" instead ... ( but I've  
tried both )

I've also tried "nosmp" and "ignorebiostables".

I've allready play with these options when I ran Xen 2.0.7 on my  
Athlon64.X2 ( dual core ) ... It's fixed right now with Xen 3.0.2.2 ...

Just for information, I have encountered the same problem on this  
Athlon64 based computer ( nVidia chipset ) when trying to boot Dom0  
on SATA HDD. But, if I run the Dom0 from a standard IDE drive ( as  
wd0 ) and with my DomUs on the SATA drive, it works fine ...

Thanks for helping ...

Best Regards,

Arnaud

Le 25 juil. 06 à 21:20, John R. Shannon a écrit :

> Did you try "noapic"?
>
> KlinT wrote:
> > 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.org/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
> > > john%johnrshannon.com@localhost
> > > jshannon%dsci-usa.com@localhost
> > > john.r.shannon%us.army.mil@localhost
> > > shannonjr%NetBSD.org@localhost
>
>
> --
> John R. Shannon, CISSP
> Chief Scientist
> DSCI, Information Assurance Division
> jshannon%dsci-usa.com@localhost
> john.r.shannon%us.army.mil@localhost
> shannonjr%NetBSD.org@localhost
> (208)522-4506