Re: kern/53492: nouveau panics with booting from 8.0 amd64 CD

[Greg Oster <oster%netbsd.org@localhost>]

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

From: Greg Oster <oster%netbsd.org@localhost>
To: scole_mail <scole_mail%gmx.com@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/53492: nouveau panics with booting from 8.0 amd64 CD
Date: Fri, 3 Aug 2018 13:20:55 -0600

 On Fri,  3 Aug 2018 03:35:00 +0000 (UTC)
 scole_mail <scole_mail%gmx.com@localhost> wrote:
 
 > The following reply was made to PR kern/53492; it has been noted by
 > GNATS.
 > 
 > From: scole_mail <scole_mail%gmx.com@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: 
 > Subject: Re: kern/53492: nouveau panics with booting from 8.0 amd64 CD
 > Date: Thu, 02 Aug 2018 20:33:32 -0700
 > 
 >  Martin Husemann <martin%duskware.de@localhost> writes:
 >  >
 >  >  Hmm, tricky - could you (I know this is asking for much) try to
 >  > extract the firmware from base.tgz manually, then extract the
 >  > kernel set somewhere else and move the kernel as (say) netbsd.80
 >  > into your existing / ? 
 >  >  Then boot that kernel, hope it panics, and get a crash dump?
 >  >    
 >  
 >  I not sure if I'll have time and access to try all that.  If I do,
 > could I use a USB thumbdrive or external USB drive for this?  Or
 > could I use a CD with the right kernel and debug info burned on disk,
 > or does the crash dump need to record on disk somewhere?
 >  
 >  I got a little more info from dmesg, don't know if it will help or
 >  should be trusted.  But when I booted the CD normally (with nouveau
 >  enabled), waited til the screen stopped updating, then hit the reset
 >  button, then booted with nouveau disabled, then went to Utility Menu
 > -> /bin/sh and typed 'dmesg', I seemed to get the both dmesg record
 > from both boots.
 >  
 >  If the dmesg can be belived, it seems like the system booted, and
 > maybe the screen stopped updating?  
 
 I've seen that with a GT520:
 
 ...
 nouveau0 at pci1 dev 0 function 0: vendor 10de product 1040 (rev. 0xa1)
 drm kern info: nouveau  [  DEVICE][nouveau0] BOOT0  : 0x0d9000a1
 drm kern info: nouveau  [  DEVICE][nouveau0] Chipset: GF119 (NVD9)
 drm kern info: nouveau  [  DEVICE][nouveau0] Family : NVD0
 drm kern info: nouveau  [   VBIOS][nouveau0] checking PRAMIN for
 image... 
 drm kern info: nouveau  [   VBIOS][nouveau0] ... appears to be
 valid 
 drm kern info: nouveau  [   VBIOS][nouveau0] using image from
 PRAMIN 
 drm kern info: nouveau  [   VBIOS][nouveau0] BIT signature found
 drm kern info: nouveau  [   VBIOS][nouveau0] version 75.19.1b.00.01
 nouveau0: interrupting at ioapic0 pin 16 (nouveau)
 drm kern warning: nouveau
 W[     PFB][nouveau0][0x00000000][0xfffffe811d4a9808] reclocking of
 this ram type unsupported 
 drm kern info: nouveau  [     PFB][nouveau0]
 RAM type: DDR3 
 drm kern info: nouveau  [     PFB][nouveau0] RAM size:
 1024 MiB 
 drm kern info: nouveau  [     PFB][nouveau0]    ZCOMP: 0 tags
 drm kern info: nouveau  [    VOLT][nouveau0] GPU voltage: 900000uv 
 drm kern info: nouveau  [  PTHERM][nouveau0] FAN control: PWM 
 drm kern info: nouveau  [  PTHERM][nouveau0] fan management: automatic 
 drm kern info: nouveau  [  PTHERM][nouveau0] internal sensor: yes 
 drm kern info: nouveau  [     CLK][nouveau0] 07: core 270 MHz memory
 405 MHz 
 drm kern info: nouveau  [     CLK][nouveau0] 0f: core 810 MHz memory
 500 MHz 
 drm kern info: nouveau  [     CLK][nouveau0] --: core 270 MHz memory 405
 MHz Zone  kernel: Available graphics memory: 5498678 kiB Zone   dma32:
 Available graphics memory: 2097152 kiB 
 drm kern info: nouveau [     DRM] VRAM: 1024 MiB 
 drm kern info:nouveau  [     DRM] GART: 1048576 MiB 
 drm kern info: nouveau [     DRM] TMDS table version 2.0 
 drm kern info: nouveau [     DRM] DCB version 4.0 
 drm kern info: nouveau [     DRM] DCB outp 00: 02000300 00000000 
 drm kern info: nouveau [     DRM] DCB outp 01: 01000302 00020030 
 drm kern info: nouveau [     DRM] DCB outp 02: 02011362 00020010 
 drm kern info: nouveau [     DRM] DCB outp 03: 04022310 00000000 
 drm kern info: nouveau [     DRM] DCB conn 00: 00001030 
 drm kern info: nouveau [     DRM] DCB conn 01: 00002161 
 drm kern info: nouveau  [     DRM] DCB conn 02: 00000200 
 drm: Supports vblank timestamp caching Rev 2 (21.10.2013). 
 drm: Driver supports precise vblank timestamp query. 
 drm kern info: nouveau [     DRM] MM: using COPY0 for buffer copies
 nouveau0: info: No connectors reported connected with modes 
 drm: Cannot find any crtc or sizes - going 1024x768 
 nouveaufb0 at nouveau0 nouveau0: info: registered panic notifier
 
 The above is what shows up on the display.... in /var/log/messages it
 continues on with:
 
 nouveaufb0: framebuffer at 0xffff80013fa42000, size 1024x768, depth 32,
 stride 4096 
 wsdisplay0 at nouveaufb0 kbdmux 1: console (default, vt100 emulation)
 
 I havn't debugged it any further, other than to note that the GT520 has
 dual outputs, and my guess is it's picking the 'other one' for the
 display.
 
 Later...
 
 Greg Oster