Reboot on resume from suspend

[Carsten Kunze]

Hello,

after suspend from console (X not running) the laptop boots when pressing the 
power button in sleep state. (I did not test with X.)

How can this be debugged or is it already clear from dmesg that resume from 
suspend is not supported for this laptop?

Carsten

13)
ACPI: LPIT 0xC8FE4E38 5C (v01 DELL   CBX3  AMI. 
0005)
ACPI: SSDT 0xC8FE4E98 000228 (v01 INTEL  sensrhub  INTL 
20120711)
ACPI: SSDT 0xC8FE50C0 000160 (v01 Intel  zpodd1000 INTL 
20120711)
ACPI: SSDT 0xC8FE5220 00051F (v01 PmRef  Cpu0Ist  3000 INTL 
20120711)
ACPI: SSDT 0xC8FE5740 000AD8 (v01 PmRef  CpuPm3000 INTL 
20120711)
ACPI: HPET 0xC8FE6218 38 (v01 DELL   CBX3 01072009 AMI. 
0005)
ACPI: SSDT 0xC8FE6250 0003D2 (v01 SataRe SataTabl 1000 INTL 
20120711)
ACPI: MCFG 0xC8FE6628 3C (v01 DELL   CBX3 01072009 MSFT 
0097)
ACPI: SSDT 0xC8FE6668 001044 (v01 SgRef  SgPeg1000 INTL 
20120711)
ACPI: ASF! 0xC8FE76B0 A5 (v32 INTEL   HCG 0001 TFSM 
000F4240)
ACPI: SSDT 0xC8FE7758 000589 (v01 AMITCG PROC 0001 INTL 
20120711)
ACPI: DMAR 0xC8FE7CE8 B0 (v01 INTEL  HSW  0001 INTL 
0001)
ACPI: SSDT 0xC8FE7D98 00109B (v01 AmdRef AmdTabl  1000 INTL 
20120711)
ACPI: TCPA 0xC8FE8E38 32 (v02 APTIO4 NAPAASF  0001 MSFT 
0113)
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: 9 ACPI AML tables successfully acquired and loaded
ioapic0 at mainbus0 apid 8: pa 0xfec0, version 0x20, 24 pins
cpu0 at mainbus0 apid 0
cpu0: Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz, id 0x306c3
cpu1 at mainbus0 apid 2
cpu1: Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz, id 0x306c3
cpu2 at mainbus0 apid 1
cpu2: Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz, id 0x306c3
cpu3 at mainbus0 apid 3
cpu3: Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz, id 0x306c3
acpi0 at mainbus0: Intel ACPICA 20160930
acpi0: X/RSDT: OemId , AslId 
acpi0: MCFG: segment 0, bus 0-63, address 0xf800
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFE822CC35810 0003D3 (v01 PmRef  Cpu0Cst  3001 INTL 
20120711)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFE810E7E3810 0005AA (v01 PmRef  ApIst3000 INTL 
20120711)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT 0xFE810E72FA50 000119 (v01 PmRef  ApCst3000 INTL 
20120711)
acpi0: SCI interrupting at int 9
timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
hpet0 at acpi0: high precision event timer (mem 0xfed0-0xfed00400)
timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000
acpiec0 at acpi0 (ECDV, PNP0C09-0)
: io 0x930,0x934
FWHD (INT0800) at acpi0 not configured
LDRC (PNP0C02) at acpi0 not configured
attimer1 at acpi0 (TIMR, PNP0100): io 0x40-0x43,0x50-0x53 irq 0
CWDT (INT3F0D) at acpi0 not configured
RMSC (PNP0C02) at acpi0 not configured
pckbc1 at acpi0 (PS2K, DLLK05BE) (kbd port): io 0x60,0x64 irq 1
pckbc2 at acpi0 (PS2M, DLL05BE) (aux port): irq 12
ACD0 (INT33CA) at acpi0 not configured
DFUD (INT33D7) at acpi0 not configured
acpivga0 at acpi0 (PEGP): ACPI Display Adapter
acpivga0: connected output devices:
acpivga0:   0x0100: Ext. Monitor, head 0
acpivga0:   0x0400: Unknown Output Device, head 0
acpivga0:   0x0302: Unknown Output Device, head 0
acpivga0:   0x0303: Unknown Output Device, head 0
acpivga0:   0x0300: Unknown Output Device, head 0
acpivga0:   0x0301: Unknown Output Device, head 0
acpivga0:   0x0304: Unknown Output Device, head 0
acpivga0:   0x0305: Unknown Output Device, head 0
acpivga1 at acpi0 (GFX0): ACPI Display Adapter
acpiout0 at acpivga1 (CRT, 0x0100): ACPI Display Output Device
acpiout1 at acpivga1 (LCD, 0x0400): ACPI Display Output Device
acpiout1: brightness levels: [5-100]
acpiout2 at acpivga1 (DVI, 0x0302): ACPI Display Output Device
acpiout3 at acpivga1 (DVI2, 0x0303): ACPI Display Output Device
acpiout4 at acpivga1 (DVI3, 0x0304): ACPI Display Output Device
acpiout5 at acpivga1 (DP, 0x0300): ACPI Display Output Device
acpiout6 at acpivga1 (DP2, 0x0301): ACPI Display Output Device
acpiout7 at acpivga1 (DP3, 0x0305): ACPI Display Output Device
acpivga1: connected output devices:
acpivga1:   0x0100 (acpiout0): Ext. Monitor, head 0
acpivga1:   0x0400 (acpiout1): Unknown Output Device, head 0
acpivga1:   0x0302 (acpiout2): Unknown Output Device, head 0
acpivga1:   0x0303 (acpiout3): Unknown Output Device, head 0
acpivga1:   0x0300 (acpiout5): Unknown Output Device, head 0
acpivga1:   0x0301 (acpiout6): Unknown Output Device, head 0
acpivga1:   0x0304 (acpiout4): Unknown Output Device, head 0
acpivga1:   0x0305 (acpiout7): Unknown Output Device, head 0
PDRC (PNP0C02) at acpi0 not configured
A_CC (SMO8810) at acpi0 not configured
acpiwmi0 at acpi0 (AMW0, PNP0C14-0): ACPI WMI Interface
wmidell0 at acpiwmi0: Dell WMI mappings
acpilid0 at acpi0 (LID0, PNP0C0D): ACPI Lid Switch

Aw: Re: Setting mtime doesn't work after copying a file with mmap

[Carsten Kunze]

Brett Lymn  wrote:

> Try using msync with the invalidate option, that should push the pages
> out to disk.

That works, thank you!

The msync does now block and hence slow down the application, but the sync is 
an advantage in the special case I use it.
But in general a sync should not be mandatory (for performance reasons). So 
isn't it a kernel bug that mtime is updated when pages are written back?

Carsten

Aw: Re: Aw: Re: Setting mtime doesn't work after copying a file with mmap

[Carsten Kunze]

chris...@astron.com (Christos Zoulas) wrote:

> How often should it be updated?

Only once on munmap?  If it is updated at an unpredictable time it makes 
something like utime(2) senseless (since it is changed anyway).  Always use 
msync is a performance issue for e.g. "cp -p ..." (so I think cp(1) doesn't use 
mmap for copying).

If the current behaviour is 4.4BSD derived it is ok, but if it's "only" NetBSD 
specific it is maybe not optimal.

Carsten

Aw: Re: Setting mtime doesn't work after copying a file with mmap

[Carsten Kunze]

> >Yes. I open the files, then do many mmap->munmap in a loop (for large
> >files--I don't map the whole file at once), then use futimes then close.
> 
> Can't you use fsync() then?

But fsync also does an immediate physical write and hence blocks the process.

But msync with MS_ASYNC seems to do the job.  So the kernel is POSIX here which 
is perfect.

Carsten

Setting mtime doesn't work after copying a file with mmap

[Carsten Kunze]

Hello,

when I copy a file with mmap:

- open both files
- mmap both files
- copy with memcpy
- setting mtime with futimes
- close both files

the time is set correctly and stays correctly for several seconds. But when I 
do a sync(1) the time is updated to the current time! Also when I first close 
the files and then use utimensat or utime the time is set correctly but changes 
again after a sync(1). If I don't use sync(1) the time is updated automatically 
within a minute.

When I copy the files with read(2)/write(2) instead of mmap this bug does *not* 
occur. Also when I mount the NetBSD file system to Linux via fuse/sshfs and 
then use mmap on Linux it works correctly.

I think the a mmap-mapping is written back with some delay and this delayed 
write back updates mtime.

Carsten

Aw: Re: Aw: Re: /var/db/entropy-file not present

[carsten . kunze]

... random_seed start/stop works perfectly when called manually.  So the 
question is why it isn't called on shutdown (I always use "halt -p" to stop the 
system, rarly I use "reboot").

Carsten

Aw: Re: Aw: Re: Aw: Re: /var/db/entropy-file not present

[carsten . kunze]

My reply mails did arrive in wrong order 

> For normal use, always use shutdown(8) ("shutdown -p now" to power
> off the system as close to immediately as is consistent with a clean
> shutdown).

Oops, thank you, that's it!  I can't test it now but this will solve the issue.

Thanks,
Carsten

Aw: Re: Aw: Re: /var/db/entropy-file not present

[carsten . kunze]

> That happens when the seed is loaded, rndctl -L deletes the file when
> it extracts the seed from it (you really only want to use it once.)
> See rndctl(8)

Ok, then it's "random_seed start" that deletes it, that makes sense.

I'm using NetBSD-CURRENT amd64 from October 30th.  So is your other mail 
applicable then?  I remember that I have seen this message since a long time, 
about half a year (with previous CURRENT snapshots).

Carsten

/var/db/entropy-file not present

[carsten . kunze]

Hello,

during boot I always get the message "random_seed: /var/db/entropy-file: Not 
present".  random_seed is (of course) enabled in /etc/default/rc.conf.  When I 
type "/etc/rc.d/random_seed stop" the file /var/db/entropy-file is written and 
found on the next boot.  But later the file is deleted (likely by random_seed 
itself).  /var/db is directly in the / filesystem (not mounted).
Unfortunately the messages from random_seed to not seem to be recorded in any 
log file.

Carsten

Aw: Re: /var/db/entropy-file not present

[carsten . kunze]

> Do you happen to have do_rcshutdown=NO in rc.conf ?
> 
> random_seed needs the rc.d script to run at system shutdown to save the
> seed for the next boot.   You wouldn't want the file just left there 
> unchanged, or it would not be very random (after a while anyway...)

No, rcshutdown is only set to YES in /etc/default/rc.conf.  And I think 
random_seed is run at shutdown--who else is deleting the file?  I think the 
script thinks the /var/db is an unsafe filesystem.  As said I don't find a log 
entry unfortunately.  I see the message at boot time but on shutdown one can't 
read anything

Carsten

USB stick image for snapshots

[carsten . kunze]

Hello,

on ftp://nyftp.netbsd.org/pub/NetBSD-daily ISO images of snapshots (e.g. named 
boot.iso) can be found. Would it be possible to also add something like 
boot.img which can be copied to a USB stick? If one often installs new snaphots 
on bare metal it is more comfortable to use a USB stick than burning a CD 
every time.
Or is there a script which converts the ISO image to a USB image? I did follow 
the instructions on
https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/
but it didn't work. E.g. there is no file named netbsd-INSTALL.gz and no 
directory named sets on the CD image.

Carsten

Aw: Re: USB stick image for snapshots

[carsten . kunze]

 On most machines it works to just dd the .iso to the usb stick.

Unfortunately it does not work on my machine. It does recognize the USB stick 
as a floppy disk, then fails to boot it.

So again--could a boot.img could be provided e.g. for some mainstream ports 
like amd64? Or a conversion script?

Carsten

Aw: Re: USB stick image for snapshots

[carsten . kunze]

Hi Travis and Joachim,

 If you're ok to download the full installation sets, e.g. you could use
 these ones:
 
 ftp://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201505031900Z/images/NetBSD
 -7.0_BETA-amd64-install.img.gz
 ftp://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201505041130Z/images/NetBSD-7.9
 9.15-amd64-install.img.gz
 
 In the past, they worked for me on a USB stick.

I've overlooked the directory images. When I opened .../HEAD/201505041130Z I 
saw amd64 and searched there for the image.

Thank you for the correct link!

Carsten

Resume from suspend does not work on a DELL LATITUDE E6540

[carsten . kunze]

Hello,

resume from suspend does not work on a DELL LATITUDE E6540
with NetBSD 7.99.9 (GENERIC.201504161510Z).

Independend of the value of hw.acpi.sleep.vbios the laptop
reboots on resume. dmesg is:

ACPI Display Output Device
acpiout1: brightness levels: [5-100]
acpiout2 at acpivga1 (DVI, 0x0302): ACPI Display Output Device
acpiout3 at acpivga1 (DVI2, 0x0303): ACPI Display Output Device
acpiout4 at acpivga1 (DVI3, 0x0304): ACPI Display Output Device
acpiout5 at acpivga1 (DP, 0x0300): ACPI Display Output Device
acpiout6 at acpivga1 (DP2, 0x0301): ACPI Display Output Device
acpiout7 at acpivga1 (DP3, 0x0305): ACPI Display Output Device
acpivga1: connected output devices:
acpivga1:   0x0100 (acpiout0): Ext. Monitor, head 0
acpivga1:   0x0400 (acpiout1): Unknown Output Device, head 0
acpivga1:   0x0302 (acpiout2): Unknown Output Device, head 0
acpivga1:   0x0303 (acpiout3): Unknown Output Device, head 0
acpivga1:   0x0300 (acpiout5): Unknown Output Device, head 0
acpivga1:   0x0301 (acpiout6): Unknown Output Device, head 0
acpivga1:   0x0304 (acpiout4): Unknown Output Device, head 0
acpivga1:   0x0305 (acpiout7): Unknown Output Device, head 0
PDRC (PNP0C02) at acpi0 not configured
A_CC (SMO8810) at acpi0 not configured
acpiwmi0 at acpi0 (AMW0, PNP0C14-0): ACPI WMI Interface
wmidell0 at acpiwmi0: Dell WMI mappings
acpilid0 at acpi0 (LID0, PNP0C0D): ACPI Lid Switch
acpibut0 at acpi0 (PBTN, PNP0C0C): ACPI Power Button
acpibut1 at acpi0 (SBTN, PNP0C0E): ACPI Sleep Button
acpiacad0 at acpi0 (AC, ACPI0003): ACPI AC Adapter
acpibat0 at acpi0 (BAT0, PNP0C0A-1): ACPI Battery
acpibat0: Samsung SDI LION rechargeable battery
acpibat0: granularity: low-warn 0.088 Ah, warn-full 0.088 Ah
acpibat1 at acpi0 (BAT1, PNP0C0A-2): ACPI Battery
RBTN (DELLABCE) at acpi0 not configured
TPM (PNP0C31) at acpi0 not configured
acpitz0 at acpi0 (THM)
acpitz0: levels: critical 107.0 C, passive cooling
ACPI: Enabled 2 GPEs in block 00 to 3F
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] 
(20150410/hwxface-646)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] 
(20150410/hwxface-646)
pckbd0 at pckbc1 (kbd slot)
pckbc1: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pms0 at pckbc1 (aux slot)
pckbc1: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0: vendor 8086 product 0c04 (rev. 0x06)
ppb0 at pci0 dev 1 function 0: vendor 8086 product 0c01 (rev. 0x06)
ppb0: PCI Express capability version 2 Root Port of PCI-E Root Complex x16 @ 
8.0GT/s
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled, rd/line, wr/inv ok
radeon0 at pci1 dev 0 function 0: vendor 1002 product 6606 (rev. 0x00)
i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 0416 (rev. 0x06)
drm: Memory usable by graphics device = 2048M
drm: Supports vblank timestamp caching Rev 2 (21.10.2013).
drm: Driver supports precise vblank timestamp query.
i915drmkms0: interrupting at ioapic0 pin 16 (i915)
intelfb0 at i915drmkms0
i915drmkms0: info: registered panic notifier
intelfb0: framebuffer at 0x80008e5e5000, size 1920x1080, depth 32, stride 
7680
wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), using 
wskbd0
wsmux1: connecting to wsdisplay0
hdaudio0 at pci0 dev 3 function 0: HD Audio Controller
hdaudio0: interrupting at ioapic0 pin 16
hdaudio0: timeout leaving reset state
hdaudio0: device driver failed to attach
vendor 8086 product 8c3a (miscellaneous communications, revision 0x04) at pci0 
dev 22 function 0 not configured
puc0 at pci0 dev 22 function 3: Intel 8 Series KT (com)
com2 at puc0 port 0 (16550-compatible): ioaddr 0xf0e0, interrupting at ioapic0 
pin 19
com2: ns16550a, working fifo
wm0 at pci0 dev 25 function 0: I217 LM Ethernet Connection (rev. 0x04)
wm0: interrupting at ioapic0 pin 20
wm0: PCI-Express bus
wm0: 2048 words FLASH
wm0: Ethernet address f0:1f:af:4e:d5:85
ihphy0 at wm0 phy 2: i217 10/100/1000 media interface, rev. 4
ihphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
ehci0 at pci0 dev 26 function 0: vendor 8086 product 8c2d (rev. 0x04)
ehci0: interrupting at ioapic0 pin 16
ehci0: BIOS has given up ownership
ehci0: EHCI version 1.0
usb0 at ehci0: USB revision 2.0
hdaudio1 at pci0 dev 27 function 0: HD Audio Controller
hdaudio1: interrupting at ioapic0 pin 22
hdafg0 at hdaudio1: vendor 10ec product 0292
hdafg0: DAC00 2ch: Speaker [Built-In], HP Out [Jack]
hdafg0: DAC01 2ch: Speaker [Jack]
hdafg0: 2ch/0ch 32000Hz 44100Hz 48000Hz 88200Hz 96000Hz 192000Hz PCM16 PCM20 
PCM24 AC3
audio0 at hdafg0: full duplex, playback, capture, mmap, independent
ppb1 at pci0 dev 28 function 0: vendor 8086 product 8c10 (rev. 0xd4)
ppb1: PCI Express capability version 2 Root Port of PCI-E Root Complex x1 @ 
5.0GT/s
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
ppb2 at pci0 dev 28 function 2: vendor 8086 

pkgin on CURRENT

[carsten . kunze]

Hello,

is it possible to use pkgin on CURRENT?

I did not find pub/pkgsrc/packages/NetBSD/amd64/7.99.9.

Carsten

Aw: Re: Install over FTP: DNS lookup problem

[carsten . kunze]

 Maybe it is
 http://gnats.netbsd.org/46483
 
 If you suspend from sysinst, what is in
 /etc/resolv.conf and in /targetroot/etc/resolv.conf ?

They both don't exist.

So I did use an IP address, then it works.

The problem then is to change the path to e.g.

pub/NetBSD-daily/HEAD/201504061010Z

Is this really necessary for installing snaphots? Would it not be possible to 
patch the installer that it knows that path?

Carsten