Subject: Re: port-amd64/37198: Limited hardware support for IBM x3755
To: None <port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Quentin Garnier <cube@cubidou.net>
List: netbsd-bugs
Date: 10/24/2007 19:00:08
The following reply was made to PR port-amd64/37198; it has been noted by GNATS.

From: Quentin Garnier <cube@cubidou.net>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-amd64/37198: Limited hardware support for IBM x3755
Date: Wed, 24 Oct 2007 20:58:56 +0200

 --OFj+1YLvsEfSXdCH
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Wed, Oct 24, 2007 at 06:40:00PM +0000, oster@netbsd.org wrote:
 > >Number:         37198
 > >Category:       port-amd64
 > >Synopsis:       NetBSD has limited hardware support for IBM x3755
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    port-amd64-maintainer
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Wed Oct 24 18:40:00 +0000 2007
 > >Originator:     oster@netbsd.org
 > >Release:        NetBSD 4.99.31 - Oct 4, 2007
 > >Organization:
 > Sometimes
 > >Environment:
 > =09
 > =09
 > System: NetBSD 4.99.31 (INSTALL) #1: Thu Oct  4 15:44:25 CST 2007
 >         oster@quadrapus:/u1/builds/build138/src/sys/arch/amd64/compile/IN=
 STALL
 > Architecture: amd64
 > Machine: amd64
 > >Description:
 > 	NetBSD/amd64 has limited support for the hardware on an=20
 > IBM x3755 with quad 3.0GHz dual-core Opterons (8222) and 128GB RAM.
 >=20
 > In particular, USB doesn't work, networking doesn't work, and no
 > hard drives were recognized on this particular box.
 >=20
 > >How-To-Repeat:
 > 	Attempt to boot NetBSD on an IBM x3755.  Assuming you get
 > around the pmap panic because of the amount of RAM, watch it come=20
 > up to sysinst.  Be disappointed when your USB keyboard doesn't work.
 > Reboot with PS/2 keyboard.  Be further disappointed when you discover
 > that bnx0 doesn't work.  Figure out how to get the remote management
 > console working.  Get boot messages from there (below):
 
 =46rom dmesg output, bus_dmamap_create() is returning an error (for bnx
 it's certain, for ohci it's very likely, or at least one of the
 bus_dma(9) API is returning an error).  With a PCI bus, the only way
 bus_dmamap_create can error out is if malloc() fails.  How could that
 happen?=20
 
 --=20
 Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
 "See the look on my face from staying too long in one place
 [...] every time the morning breaks I know I'm closer to falling"
 KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
 
 --OFj+1YLvsEfSXdCH
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.6 (NetBSD)
 
 iQEVAwUBRx+V8NgoQloHrPnoAQKuqggApFrh9+QUJPuLQP1C8OSd17FKF1gFVQd/
 1opXxpcFrrRZ31VBmfCqCScrQUWPll0l64oszIFKtNx78U5qAC8nphxBLI76K7am
 xoFIydDScjOfxxGU5BoTWuZClyg8E3Jiduivlu44Wp29jk61si/momhrf5SkemiM
 rRRtuz3wvd6rGS2gZ2HPXqLLhtJz3zTMACBOviWp1m91Tm3Laa7blnCgnTNk5q7k
 o3D7rkk/PBGmkzLzi5fecfo5odZvzRxeehFWh5hZiKUJg5eMQaqrtBbHhV6qzrRH
 B02TJA+JbWKdoSf6QrHucMTw5jtquPmUNKiCNRCUt2DtTMTykrpprw==
 =nPUB
 -----END PGP SIGNATURE-----
 
 --OFj+1YLvsEfSXdCH--