NetBSD Problem Report #52131

From  Mon Apr  3 08:02:16 2017
Return-Path: <>
Received: from ( [])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "", Issuer "Postmaster" (verified OK))
	by (Postfix) with ESMTPS id 0D61C7A234
	for <>; Mon,  3 Apr 2017 08:02:16 +0000 (UTC)
Message-Id: <>
Date: Mon,  3 Apr 2017 10:02:07 +0200 (CEST)
Subject: Machine needs SSH connection to wake up properly
X-Send-Pr-Version: 3.95

>Number:         52131
>Category:       kern
>Synopsis:       Machine needs SSH connection to wake up properly
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          feedback
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 03 08:05:00 +0000 2017
>Last-Modified:  Sat Jun 20 08:50:01 +0000 2020
>Originator:     Reinoud Zandijk
>Release:        NetBSD 7.99.58


System: NetBSD 7.99.58 NetBSD 7.99.58 (GENERIC) #1: Fri Jan 13 14:39:40 CET 2017 amd64
Architecture: x86_64
Machine: amd64

Explicitly set:
hw.acpi.sleep.vbios = 2
hw.acpi.wake.* =1

Slept when using X by typing in commands in an Xterm.

radeon0 at pci2 dev 0 function 0: vendor 1002 product 9440 (rev. 0x00)
radeon0: info: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M
radeon0: info: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
drm: radeon: 1024M of VRAM memory ready
drm: radeon: 1024M of GTT memory ready.
radeon0: info: WB enabled
radeon0: info: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu
addr 0x0xffff8000d9739c00
radeon0: info: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu
addr 0x0xffff8000d9739c0c
radeon0: interrupting at ioapic1 pin 0 (radeon)
drm: radeon: irq initialized.
radeondrmkmsfb0 at radeon0
radeon0: info: registered panic notifier
radeondrmkmsfb0: framebuffer at 0xffff8000d9b70000, size 1600x1200, depth 32,
stride 6400
wsdisplay0 at radeondrmkmsfb0 kbdmux 1: console (default, vt100 emulation),
using wskbd0


After I put the machine to sleep using "sync; sysctl -w hw.acpi.sleep.state=3"
the machine only wakes up by pressing the power button even though it ought to
work by keyboard, but thats another minor issue.

After pressing the power key, the machine wakes up, reinits the display and
starts up generally fine. However the display is displaying random static
noise. The keyboard works fine but is not echoing as expecting but there are
no screen modifications either even though the xterm ought to update. TTY
swiching has no effect.

Even though the machine pings fine, its display is ONLY restored by SSH-ing
into the machine. The login is not needed, just the mere act of setting up an
SSH connection restores the screen.

Start X,
execute "sync; sysctl -w hw.acpi.sleep.state=3"
press power button
notice that screen is filled with static noise
Start setting up an SSH from any remote machine and its display gets restored

Start an SSH connection from a remote machine to get a usable screen again.



State-Changed-From-To: open->feedback
State-Changed-When: Sun, 03 Jun 2018 06:48:59 +0000
We changed vbios=0 in your case. Is this enough to resolve the problem? (in -8 and -current)

From: Reinoud Zandijk <>
Subject: Re: kern/52131
Date: Thu, 5 Sep 2019 16:09:30 +0200

 Tested it out with a newer kernel, NetBSD-8.99.43. On resuming, the machine
 still displays noise on the screen but VT switching to either one of the text
 consoles or the X screen will redraw all! I couldn't reproduce the requirement
 of ssh-ing to the machine. In stead it reports on waking up:

 [   790.731845] msk1: autoconfiguration error: phy failed to come ready
 ... (repeated quite a lot, msk1 is not in use)
 [   790.731845] msk1: autoconfiguration error: phy failed to come ready
 [   790.741850] fwohci0: BUS reset
 [   790.741850] fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
 [   790.741850] ieee1394if0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me)
 [   790.741850] ieee1394if0: bus manager 0
 [   790.741850] fwohci0: autoconfiguration error: unrecoverable error
 [   808.520363] nfs server nas:/home: not responding
 [   809.941044] nfs server nas:/home: not responding
 [   861.233919] nfs server nas:/var/mail: not responding
 [   870.778061] msk0: autoconfiguration error: watchdog timeout

 But with the msk0 not working. After the timeout the network is fine again. I
 don't have any firewire peripherals.

From: Reinoud Zandijk <>
Subject: Re: kern/52131
Date: Sat, 20 Jun 2020 10:48:37 +0200

 I tested it with stock NetBSD-9.0 and a different ATI video card but the
 problem persists. I think it might be that the X server is waiting on NFS.

 The original suggestion for the SSH connection might have had a side effect of
 waking the msk0 interface up and would explain the observed.

 So basically, its the msk0 not waking up and the fsohci not being recoverable.
 Maybe close this one and open a separate PR on these device drivers
 suspend/resume code?



NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.46 2020/01/03 16:35:01 leot Exp $
$NetBSD:,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2020 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.