Re: ThinkPad - suspend-to-RAM intel-x86 issues and tests

2018-11-20 Thread David H. Gutteridge
On Tue, 2018-11-20 at 16:25 +0100, Riccardo Mottola wrote:
> Hi David,
> 
> David H. Gutteridge wrote:
> > FWIW, I'm able to get suspend and resume to work reliably on a
> > Lenovo
> > T420 with NetBSD-8.0_STABLE. (With 8.99.x, it doesn't work as
> > reliably
> > because the SATA driver seems to have issues after resumption which
> > don't occur with 8.0.) I didn't have to do anything of note to get
> > it
> > to work, it just does, assuming there's nothing extra attached.
> > (Read
> > on below.)
> 
> The T420 is a lot newer and is amd64 instead of x86.

True. What I can also say is that I tested the i386 port with it too
(see kern/53658), and it worked too. I've also tested i386 with an LG
X110 that I used to run NetBSD 5.x and then 7.x on. I could never get
it to suspend. With 8.0, it doesn't resume successfully, because of an
issue with the i915 DRM driver, but with the newer DRM code base that
was pulled into HEAD, I've found 8.99.25 did successfully resume, so
there may be hope.

I have access to a Toshiba Satellite Pro that's a roughly similar
vintage to your T43; I'll see how it behaves when I have a chance.

> > On the other hand, I cannot get it to work on a Lenovo x131e (the
> > AMD
> > CPU version, with Radeon graphics). With that machine, it resumes,
> > but
> > the display stays dark. (This behaviour is consistent with most
> > Linux
> > kernels I've tried as well, so there's something tricky about it.)
> 
> Yes, I have this issue on the T43 with ATI graphics, however it often 
> does work and come back (but takes several secons) it is unreliable,
> but 
> the only ThinkPad I have NetBSD on which sometimes suspends/resumes 
> correctly.
> 
> Did you try disabling video in configure and then trying to 
> suspend/resume after a clean boot?

I haven't tried that yet, no. I'll add it to the list.

> Christos suggested to me disabling video and audio (things in my 
> experience cause issue too).
> I tried also fine-grained disabling based on dmesg devices.
> 
> However, I went down to bare-bones, leaving just internal hard disk
> and 
> keyboard - disabling everything which I could (but perhaps I missed 
> something) and yet it fails!
> 
> > One other thing to consider is whether you have anything extra
> > plugged
> > into the USB stack when you're trying to suspend. I've found having
> > pretty much anything plugged in (including a mouse) causes my T420
> > to
> > fail to completely suspend.
> 
> Indeed, I did all the test with a just clean-booted machine with no
> USB 
> mouse, keybord, dongles or else.
> 
> It did not help.

Hopefully, we'll figure this out.

Dave




daily CVS update output

2018-11-20 Thread NetBSD source update


Updating src tree:
P src/crypto/external/bsd/openssl/dist/crypto/armcap.c
P src/crypto/external/bsd/openssl/dist/crypto/ppccap.c
P src/external/bsd/nsd/dist/server.c
P src/lib/libcurses/cchar.c
P src/sys/arch/aarch64/include/pmap.h
P src/sys/arch/ia64/ia64/genassym.cf
P src/sys/arch/ia64/ia64/locore.S
P src/sys/coda/coda_vnops.c
P src/sys/dev/ic/ahcisata_core.c
P src/sys/dev/pci/ahcisata_pci.c
P src/sys/dev/pci/files.pci
P src/sys/dev/pci/if_wm.c
P src/sys/uvm/uvm_bio.c
P src/usr.sbin/sysinst/bsddisklabel.c
P src/usr.sbin/sysinst/label.c
P src/usr.sbin/sysinst/mbr.c
P src/usr.sbin/sysinst/partman.c
P src/usr.sbin/sysinst/run.c
P src/usr.sbin/tprof/tprof.8

Updating xsrc tree:


Killing core files:



Updating release-7 src tree (netbsd-7):

Updating release-7 xsrc tree (netbsd-7):



Updating release-8 src tree (netbsd-8):
U doc/CHANGES-8.1
P external/bsd/nsd/dist/server.c
P sys/dev/usb/usb_quirks.c
P sys/dev/usb/usb_quirks.h
P sys/dev/usb/usbdi.c

Updating release-8 xsrc tree (netbsd-8):




Updating file list:
-rw-rw-r--  1 srcmastr  netbsd  52365000 Nov 21 03:11 ls-lRA.gz


Automated report: NetBSD-current/i386 build success

2018-11-20 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again.

The following commits were made between the last failed build and the
successful build:

2018.11.20.15.16.43 prlw1 src/sys/dev/pci/ahcisata_pci.c,v 1.45

Log files can be found at:


http://releng.NetBSD.org/b5reports/i386/commits-2018.11.html#2018.11.20.15.16.43


Re: ThinkPad - suspend-to-RAM intel-x86 issues and tests

2018-11-20 Thread maya
On Tue, Nov 20, 2018 at 06:02:36PM +0100, Riccardo Mottola wrote:
> Hi,
> 
> m...@netbsd.org wrote:
> > For general context, suspend does work on -current. I tried on an older
> > amd64.http://netbsd.org/~maya/n4030-suspend
> > (No driver disabled, but I tried from r/o root in an installer)
> > 
> > Unfortunately my shinier machine is a pain to suspend. I might end up
> > giving up.
> 
> at least it works for somebody :) It works for me (mostly) also on my amd64
> Laptop. However, except for video issues, suspend works also on my T43, so
> basically suspend works also on x86.
> 
> I am confused that disabling drivers does not help. One of the few drivers I
> did not disable (of course) are pci and ide! ANd I need a keyboard too for
> minimal tests...
> 
> Other possible suspects?
> 
> Riccardo
> 
> PS: Do the install CDs or netinst CD's have ACPI enabled? Or do we have some
> sort of Live CD? Since using an USB key to boot proved not feasible to test
> without isntalling, if I had a CD image, Ic ould try at least on one or two
> devices more where I could even compare against another OS.

I was using a USB image to suspend, I dropped to boot prompt and ran
'boot -s' to boot to single user without a mounted rw filesystem.


Re: ThinkPad - suspend-to-RAM intel-x86 issues and tests

2018-11-20 Thread Riccardo Mottola

Hi,

m...@netbsd.org wrote:

For general context, suspend does work on -current. I tried on an older
amd64.http://netbsd.org/~maya/n4030-suspend
(No driver disabled, but I tried from r/o root in an installer)

Unfortunately my shinier machine is a pain to suspend. I might end up
giving up.


at least it works for somebody :) It works for me (mostly) also on my 
amd64 Laptop. However, except for video issues, suspend works also on my 
T43, so basically suspend works also on x86.


I am confused that disabling drivers does not help. One of the few 
drivers I did not disable (of course) are pci and ide! ANd I need a 
keyboard too for minimal tests...


Other possible suspects?

Riccardo

PS: Do the install CDs or netinst CD's have ACPI enabled? Or do we have 
some sort of Live CD? Since using an USB key to boot proved not feasible 
to test without isntalling, if I had a CD image, Ic ould try at least on 
one or two devices more where I could even compare against another OS.


Re: ThinkPad - suspend-to-RAM intel-x86 issues and tests

2018-11-20 Thread Riccardo Mottola



Hi David,

David H. Gutteridge wrote:

FWIW, I'm able to get suspend and resume to work reliably on a Lenovo
T420 with NetBSD-8.0_STABLE. (With 8.99.x, it doesn't work as reliably
because the SATA driver seems to have issues after resumption which
don't occur with 8.0.) I didn't have to do anything of note to get it
to work, it just does, assuming there's nothing extra attached. (Read
on below.)


The T420 is a lot newer and is amd64 instead of x86.



On the other hand, I cannot get it to work on a Lenovo x131e (the AMD
CPU version, with Radeon graphics). With that machine, it resumes, but
the display stays dark. (This behaviour is consistent with most Linux
kernels I've tried as well, so there's something tricky about it.)


Yes, I have this issue on the T43 with ATI graphics, however it often 
does work and come back (but takes several secons) it is unreliable, but 
the only ThinkPad I have NetBSD on which sometimes suspends/resumes 
correctly.


Did you try disabling video in configure and then trying to 
suspend/resume after a clean boot?


Christos suggested to me disabling video and audio (things in my 
experience cause issue too).

I tried also fine-grained disabling based on dmesg devices.

However, I went down to bare-bones, leaving just internal hard disk and 
keyboard - disabling everything which I could (but perhaps I missed 
something) and yet it fails!




One other thing to consider is whether you have anything extra plugged
into the USB stack when you're trying to suspend. I've found having
pretty much anything plugged in (including a mouse) causes my T420 to
fail to completely suspend.


Indeed, I did all the test with a just clean-booted machine with no USB 
mouse, keybord, dongles or else.


It did not help.

Riccardo


Automated report: NetBSD-current/i386 build failure

2018-11-20 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386
build failure.

The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2018.11.20.12.23.01.

An extract from the build.sh output follows:

counts[PCI_INTR_TYPE_MSI] = 1;,
  ^
--- kern-INSTALL ---
ca/dist/include   -c
/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/compat/common/sysv_sem_50.c 
-o sysv_sem_50.o
--- kern-XEN3PAE_DOM0 ---

/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/dev/pci/ahcisata_pci.c:329:34:
 error: left-hand operand of comma expression has no effect 
[-Werror=unused-value]
--- kern-INSTALL_XEN3PAE_DOMU ---
--- kern_tc.o ---
/tmp/bracket/build/2018.11.20.12.23.01-i386/tools/bin/nbctfconvert -g -L 
VERSION kern_tc.o
--- kern-LEGACY ---
rnal/bsd/drm2/nouveau -DCONFIG_NOUVEAU_DEBUG=5 
-DCONFIG_NOUVEAU_DEBUG_DEFAULT=3 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/external/bsd/acpica/dist/include
  
/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/external/bsd/drm2/dist/drm/nouveau/nvkm/engine/disp/nouveau_nvkm_engine_disp_hdmig84.c
--- kern-INSTALL_XEN3PAE_DOMU ---
--- kern_todr.o ---
#   compile  INSTALL_XEN3PAE_DOMU/kern_todr.o
/tmp/bracket/build/2018.11.20.12.23.01-i386/tools/bin/i486--netbsdelf-gcc 
-msoft-float -mno-mmx -mno-sse -mno-avx -ffreestanding 
-fno-zero-initialized-in-bss -fno-delete-null-pointer-checks -O2 
-fno-omit-frame-pointer -fstack-protector -Wstack-protector --param 
ssp-buffer-size=1 -fno-strict-aliasing -fno-common -std=gnu99 -Werror -Wall 
-Wno-main -Wno-format-zero-length -Wpointer-arith -Wmissing-prototypes 
-Wstrict-prototypes -Wold-style-definition -Wswitch -Wshadow -Wcast-qual 
-Wwrite-strings -Wno-unreachable-code -Wno-pointer-sign -Wno-attributes 
-Wno-sign-compare -march=i686 
--sysroot=/tmp/bracket/build/2018.11.20.12.23.01-i386/destdir -Di386 -I. 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/obj/sys/arch/i386/compile/INSTALL_XEN3PAE_DOMU/xen-ma
 -I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/external/bsd/acpica/dist 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/external/bsd/libnv/dist 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/../common/lib/libx86emu -I
 /tmp/bracket/build/2018.11.20.--- kern-LEGACY ---
mv -f nouveau_nvkm_engine_disp_hdmig84.d.tmp 
nouveau_nvkm_engine_disp_hdmig84.d
--- kern-INSTALL_XEN3PAE_DOMU ---
12.23.01-i386/src/sys/../common/lib/libc/misc 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/../common/include 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/arch 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys -nostdinc -DDIAGNOSTIC 
-DCOMPAT_44 -DMAXPHYS=32768 -D_KERNEL -D_KERNEL_OPT -std=gnu99 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/lib/libkern/../../../common/lib/libc/quad
 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/lib/libkern/../../../common/lib/libc/string
 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/lib/libkern/../../../common/lib/libc/arch/i386/string
 -D_FORTIFY_SOURCE=2 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/external/bsd/libnv/dist 
-c /tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/kern/kern_todr.c -o 
kern_todr.o
--- kern-LEGACY ---
--- nouveau_nvkm_engine_disp_hdmigf119.d ---
#create  LEGACY/nouveau_nvkm_engine_disp_hdmigf119.d

CC=/tmp/bracket/build/2018.11.20.12.23.01-i386/tools/bin/i486--netbsdelf-gcc 
/tmp/bracket/build/2018.11.20.12.23.01-i386/tools/bin/nbmkdep -f 
nouveau_nvkm_engine_disp_hdmigf119.d.tmp --  -msoft-float -mno-mmx -mno-sse 
-mno-avx -mindirect-branch=thunk -mindirect-branch-register -ffreestanding 
-fno-zero-initialized-in-bss  -fno-delete-null-pointer-checks   -O2 
-fno-omit-frame-pointer -fstack-protector -Wstack-protector   --param 
ssp-buffer-size=1  -fno-strict-aliasing -fno-common -std=gnu99   -Werror 
-Wall -Wno-main -Wno-format-zero-length -Wpointer-arith -Wmissing-prototypes 
-Wstrict-prototypes -Wold-style-definition -Wswitch -Wshadow -Wcast-qual 
-Wwrite-strings -Wno-unreachable-code -Wno-pointer-sign -Wno-attributes -Wextra 
-Wno-unused-parameter -Wold-style-definition -Wno-sign-compare  
--sysroot=/tmp/bracket/build/2018.11.20.12.23.01-i386/destdir -Di386 -I. 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/external/bsd/acpica/dist 
-I/tmp/bracket/build/2018.11.20.12.2
 3.01-i386/src/sys/external/bsd/libnv/dist 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/../common/lib/libx86emu 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/../common/lib/libc/misc 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/../common/include 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/arch  
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys -nostdinc -DDIAGNOSTIC  
-DCOMPAT_44 -D_KERNEL -D_KERNEL_OPT -std=gnu99 
-I/tmp/bracket/build/2018.11.20.12.23.01-i386/src/sys/lib/libkern/../../../common/lib/libc/quad

Re: ThinkPad - suspend-to-RAM intel-x86 issues and tests

2018-11-20 Thread Paul Goyette

On Tue, 20 Nov 2018, David H. Gutteridge wrote:


FWIW, I'm able to get suspend and resume to work reliably on a Lenovo
T420 with NetBSD-8.0_STABLE. (With 8.99.x, it doesn't work as reliably
because the SATA driver seems to have issues after resumption which
don't occur with 8.0.)


Jaromir Dolocek did a lot of work on ahcisata recently.  You might try 
to coordninate with him to see if his changes have affected the suspend 
and resume stuff.



+--+--++
| Paul Goyette | PGP Key fingerprint: | E-mail addresses:  |
| (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee dot com   |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd dot org |
+--+--++


Re: Brightness buttons don't work in current

2018-11-20 Thread Fekete Zoltán

 Eredeti üzenet 
Tárgy: Re: Brightness buttons don't work in current
Dátum: 2018-09-26 21:51
Feladó: Fekete Zoltán 
Címzett: tech-k...@netbsd.org
Válaszcím: fekete.zol...@minux.hu

2018-09-26 21:37 időpontban Cág ezt írta:

Fekete Zoltán wrote:


Anybody experienced similar thing? Should I set something new in
kernel config?


Do you mean on the console or in X11? They never worked for me in 
either

case. Manually changing hw.acpi.acpiout entry doesn't change the
brightness, and xbacklight, to which I map the brightness keys, reports
`No outputs have backlight property`.

--
caóc


In X11. I have an i915 integrated chip. NetBSD8 release handles this as 
expected.

hw.acpi.acpiout worked also. Now it doesn't.
Something happened in the recent weeks I assume.



FeZ


Hi There,

I wanted to recall this report. I know it's not a major thing, but as it 
has been working formerly, and very convenient, so why not to mention 
again.


I think the brightness button handler disappeared after the huge changes 
were committed  for i915 into the current branch last summer.

The NetBSD8 kernel is still perfect. Only current lacks the feature.

Isn't there a possibility to reimplement it based on the working 
NetBSD8?


Thank you:

FeZ


undefined reference to `logf@GLIBCXX_3.4' fix

2018-11-20 Thread coypu
If you are seeing this error, which affects only -current, it is because
the libstdc++ configuration was slightly wrong for a few months.
Fixing involved removing a symbol, so you get an undefined reference.

If you see:
/usr/pkgobj/graphics/gimp/work/.buildlink/lib/libexiv2.so: undefined reference 
to `logf@GLIBCXX_3.4'

Do:
pkg_info -Fe /usr/pkg/lib/libexiv2.so
To find which package is affected by the ABI breakage, and rebuild it to
get correct references.