Port-amd64 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

RE: BETA6.0 - AMD Opetron 6272 (16 core) multiprocessor config crashes



Finally got this to work.. Although not sure if this is still related to
irq on driver issues on the network card..

But I was able to insert a PCI express network card and got this going .. 

The issues still stays if I use both ports on the dual network card.. i.e
to make this work I had to configure one network on the motherboard and
the other on the pciexpress network card.. the server crashes if I use
both nics on the motherboard or the pciexpress network card.. 

Regards
Derrick

-----Original Message-----
From: Manuel Bouyer [mailto:bouyer%antioche.eu.org@localhost] 
Sent: Tuesday, December 25, 2012 3:38 PM
To: Derrick Lobo
Cc: port-amd64%netbsd.org@localhost
Subject: Re: BETA6.0 - AMD Opetron 6272 (16 core) multiprocessor config
crashes

On Mon, Dec 24, 2012 at 03:28:16PM -0500, Derrick Lobo wrote:
> Manuel
> 
> A funny thing happened today.. we were trying to replicate this issue 
> in our lab and were never able to reproduce it.. however in the lab 
> once we connected a network cable and enabled the 2nd nic .. the 
> server crashed in minutes..
> 
> 
> So seems like having one network interface connected makes this work.. 
> I can have all 16 cores running and processing with no error and any
work load..
> however the moment I connect and activate the second nic.. (even if no 
> data flows on the second nic) the server crashs.. keep the second nic 
> and reboot netbsd in SMB mode and it works..
>

Does it hang immediatly after enabling the second nic, or some time later
? if you can enter ddb, does 'show events' report interrupts for this nic
? 

> 
> So theres something related to the 2nd nic that causing this issue..
> 
> Hope this helps.. I can live by disabling the second nic, but if a 
> solution is possible it would be great..

It looks like an interrupt routing issue. I'm not an expert in this area;
a PR with the dmesg and ACPI infos would probably be the best way to get
this handled.

--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--


Home | Main Index | Thread Index | Old Index