re: install/57774: Old Nvidia card with Nouveau causes kernel panic on boot

[xuser <xuser%sdf.org@localhost>]

The following reply was made to PR install/57774; it has been noted by GNATS.

From: xuser <xuser%sdf.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: install-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
        huskers2012%outlook.com@localhost
Subject: re: install/57774: Old Nvidia card with Nouveau causes kernel panic
 on boot
Date: Thu, 14 Dec 2023 20:48:55 -0500 (EST)

 Unsupported card??
 
 xuser%sdf.org@localhost
 SDF Public Access UNIX System - http://sdf.org
 
 On Fri, 15 Dec 2023, matthew green wrote:
 
 > The following reply was made to PR install/57774; it has been noted by GNATS.
 >
 > From: matthew green <mrg%eterna23.net@localhost>
 > To: gnats-bugs%netbsd.org@localhost, huskers2012%outlook.com@localhost
 > Cc: install-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 >    netbsd-bugs%netbsd.org@localhost
 > Subject: re: install/57774: Old Nvidia card with Nouveau causes kernel panic on boot
 > Date: Fri, 15 Dec 2023 10:58:22 +1100
 >
 > > nouveau0: NVIDIA NV44(044300b2)_
 > > nouveau0: bios: version 04.44.02.45.00
 > > nouveau0: error: imem: unable to map PRAMIN BAR 2: -35
 > > nouveau0: error: imem: imem ctor failed, -35
 > > nouveau0: unable to create nouveau device: 35
 > > panic: cnopen: no console device
 >
 > this message comes from a netbsd-only code segment:
 >
 > 300         imem->iomemt =3D device->func->resource_tag(device, bar);
 > 301         iomembase =3D device->func->resource_addr(device, bar);
 > 302         iomemsz =3D device->func->resource_size(device, bar);
 > 303         /* XXX errno NetBSD->Linux */
 > 304         ret =3D -bus_space_map(imem->iomemt, iomembase, iomemsz,
 > 305             BUS_SPACE_MAP_LINEAR|BUS_SPACE_MAP_PREFETCHABLE, &imem->io=
 > memh);
 > 306         if (ret) {
 > 307                 nvkm_error(&imem->base.subdev, "unable to map PRAMIN B=
 > AR %d"
 > 308                     ": %d\n", bar, ret);
 >
 > error 35 =3D EAGAIN.  that's probably coming from x86/bus_space.c:
 >
 > 249 bus_space_reserve(bus_space_tag_t t,
 > ...
 > 283         error =3D extent_alloc_region(ex, bpa, size,
 > 284             EX_NOWAIT | (ioport_malloc_safe ? EX_MALLOCOK : 0));
 >
 > which seems to imply the address is already mapped, so we'd need
 > to figure out what is doing this.  can you post the full dmesg
 > from before it panics?  (even if just some pictures or video?)
 >
 > thanks.
 >
 >
 > .mrg.
 >
 >