Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: nouveau reboot
On Fri, Jul 21, 2017 at 08:17:44AM +0100, Patrick Welche wrote:
> On Fri, Jul 21, 2017 at 07:53:09AM +0100, Patrick Welche wrote:
> > On Thu, Jul 20, 2017 at 09:06:16PM +0000, coypu%sdf.org@localhost wrote:
> > > On Thu, Jul 13, 2017 at 09:49:32AM +0100, Patrick Welche wrote:
> > > > or "new" reboot: just updated a working 3rd July amd64
> > > > kernel with this morning's source, and the computer reboots after
> > > > printing nouveau, but before drm. Haven't had a chance to dig (won't
> > > > until tonight) - any first guesses?
> > >
> > > Must be unrelated to nouveau. no changes in sys/external/bsd/drm2 since
> > > June 1.
> >
> > In the meantime it is getting even more confusing: I bisected to
> >
> > http://mail-index.netbsd.org/source-changes/2017/07/11/msg086253.html
> >
> > lm(4): Add suport for NCT5174D, NCT6775F, NCT6779D and NCT679[1235]D.
> > wbsio(4): Add support for NCT6795D.
> >
> > but then rebooting with disable wbsio (which didn't switch anything off)
> > and disable lm still failed. Now moving the modules which I haven't kept
> > in synch during the bisection away.
>
> Moving the modules out of the way now gets consistent results:
> - unsuccessful boot with the above patch
> - successful boot with the above patch and "disable lm"
>
> I have no idea what chip is in this box(!)
Serial console to the rescue:
Kernel lock error: _kernel_lock,216: spinout
lock address : 0xffffffff8108bdc0 type : spin
initialized : 0xffffffff80a9daf1
shared holds : 0 exclusive: 1
shares wanted: 0 exclusive: 16
current cpu : 14 last held: 7
current lwp : 0xffffe4013af4b5e0 last held: 0xffffe4013af19180
last locked* : 0xffffffff8074c92b unlocked : 0xffffffff80243a3c
curcpu holds : 0 wanted by: 0xffffe4013af4b5e0
uhub5: 4 ports with 4 removable, self powered
acpicpu15: ACPI CPUs started
panic: LOCKDEBUG: Kernel lock error: _kernel_lock,216: spinout
last held by:
PID LID S CPU FLAGS STRUCT LWP * NAME WAIT
0 124 2 7 200 ffffe4013af19180 configintr
bus_space_read_1() at netbsd:bus_space_read_1+0xf
putchar() at netbsd:putchar+0x128
kprintf() at netbsd:kprintf+0xc01
aprint_error_internal() at netbsd:aprint_error_internal+0x77
aprint_error() at netbsd:aprint_error+0x41
ahci_do_reset_drive() at netbsd:ahci_do_reset_drive+0x428
ahci_probe_drive() at netbsd:ahci_probe_drive+0x1ae
atabusconfig() at netbsd:atabusconfig+0x1c0
atabus_thread() at netbsd:atabus_thread+0x7a
wanted by:
PID LID S CPU FLAGS STRUCT LWP * NAME WAIT
0 > 129 7 14 200 ffffe4013af4b5e0 configintr
breakpoint() at netbsd:breakpoint+0x5
vpanic() at netbsd:vpanic+0x16f
snprintf() at netbsd:snprintf
lockdebug_more() at netbsd:lockdebug_more
_kernel_lock() at netbsd:_kernel_lock+0x1cb
db{14}> show proc /a 0xffffe4013af4b5e0
lwp_t ffffe4013af4b5e0
system: pid 0 proc ffffffff810511e0 vmspace/map ffffffff81107b80 flags 20002
> lwp 129 [configintr] ffffe4013af4b5e0 pcb ffffe4013af45000
stat 7 flags 200 cpu 14 pri 96
> lwp 128 [configintr] ffffe4013af4ba00 pcb ffffe4013af41000
stat 7 flags 200 cpu 1 pri 96
> lwp 127 [configintr] ffffe4013af0a1a0 pcb ffffe4013af3a000
stat 7 flags 200 cpu 12 pri 96
...
no sign of lm nor wbsio, just plenty of ahci / sata_reset_interface - there
are 7 sata devices.
Cheers,
Patrick
Home |
Main Index |
Thread Index |
Old Index