NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/53492: nouveau panics with booting from 8.0 amd64 CD
The following reply was made to PR kern/53492; it has been noted by GNATS.
From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc:
Subject: Re: kern/53492: nouveau panics with booting from 8.0 amd64 CD
Date: Fri, 03 Aug 2018 20:57:17 +0700
Date: Fri, 3 Aug 2018 03:35:00 +0000 (UTC)
From: scole_mail <scole_mail%gmx.com@localhost>
Message-ID: <20180803033500.CE6FF7A1D7%mollari.NetBSD.org@localhost>
| or does the crash dump need to record on disk somewhere?
It would, but it does not look like you will need that.
| I got a little more info from dmesg, don't know if it will help or
| should be trusted.
It does, and can.
| I seemed to get the both dmesg record from both boots.
Yes, if power is not lost (so RAM is preserved) the message buffer
contents are not lost, and you can see exactly that.
| If the dmesg can be belived, it seems like the system booted, and maybe
| the screen stopped updating?
Yes, that is what it looks like to me - the display driver simply could not handle
graphics card properly (but does not crash or hang.)
In that case, you should continue with graphics disabled for now, get the
system set up, and networking functioning so you can ssh into the system
(or telnet or something if you must...)
Then boot again with the nv driver not disabled - when the boot has had
time to complete, ssh in, and see what happens. You might even be able
to "blind" login on the console (you know there's a login prompt, just assume
it is there and type at it ... if that works, you might even be able to try
starting X and see what happens.)
Meanwhile, someone (not me) who knows at least something about nouveau
might be able to disgnose all those drm errors from your dmesg.
kre
Home |
Main Index |
Thread Index |
Old Index