amd64 - bootloader and BIOS see 16gb ram, kernel does not
After being away from OpenBSD for about 2 years, I recently decided to take another look at it for a server I am deploying. The machine is a 8-way amd64 (Intel quad Xeon x 2) with 16GB ram. The BIOS and bootloader correctly see all 16gb, but the kernel only sees 4.00GB (a very non-random amount, indicating to me an artificial limit is being imposed somewhere). Just for comparison purposes, amd64 Windows and amd64 Linux also both see 16gb, but these are not being considered for deployment. I've tried both 4.2 and -current from a week or so back, and have the same problem on both. I also went through the -GENERIC config and GENERIC-MP config and tried to see if any options in there were applicable, but did not see anything that seemed appropriate to fix this issue. A few notes: 1. I am using the amd64 platform release, not i386 (in case someone thought I was trying to do some PAE-related stuff). I verified that it really is the amd64 kernel and not a rogue i386 one that slipped in there accidentally (which would explain the 4GB limit without PAE). 2. Both GENERIC and -MP only see 4gb, but -MP _does_ correctly see all 8 cores. 3. I checked the archive and noticed that some people have had no issues with similar configurations, so I'm probably doing something wrong or I might be missing a config option. (Most of these success stories are using Sun hardware - the machine in question is not, but I'm not sure why the system would be picky in that respect). 4. The memory ranges reported by the bootloader are correct - typical mappings up to 4gb, followed by a large 12.8GB range starting at physical 5GB. All the ranges are enabled. 5. It's a Dell server, in case that matters to anyone. Any thoughts or specific reason why I _should not_ expect this configuration to work (with all 16gb usable) ? -ml [EMAIL PROTECTED]
Re: amd64 - bootloader and BIOS see 16gb ram, kernel does not
Travers Buda wrote The developers need hardware to tackle this. It may be possible for me to loan out this hardware. Where is it needed, and for how long? An private reply is probably better here as to not spam the list. -ml
Re: amd64 - bootloader and BIOS see 16gb ram, kernel does not
Mike Larkin wrote: I see. Just for my personal reference, was this limitation documented somewhere (just want to make sure I didn't miss anything)...? If not, should it be? Finally, did this limitation always exist? I do recall several other posters mentioning that they had similar configurations that _did_ work, but this was about a year back. Perhaps one or two of them didn't realize that only 4gb were usable, but it seems unlikely that _none_ of them realized it. -ml Earlier in the thread there are some links to undeadly that do answer the questions above. Thanks for the info everyone. -ml
Re: amd64 - bootloader and BIOS see 16gb ram, kernel does not
Nick Holland wrote: The amd64 4G issue is a limitation of the platform...at the moment. It is being worked on, slowly, but there be dragons, and they all have to be slain. Nick. I see. Just for my personal reference, was this limitation documented somewhere (just want to make sure I didn't miss anything)...? If not, should it be? Finally, did this limitation always exist? I do recall several other posters mentioning that they had similar configurations that _did_ work, but this was about a year back. Perhaps one or two of them didn't realize that only 4gb were usable, but it seems unlikely that _none_ of them realized it. -ml
Re: HP Vectra VL - 450Mhz Pentium III. obsd 4.2 boots fine. snapshot 2/23 and 2/24 installs, but dies on booting
bofh wrote: bwi0 at pci0 dev 16 function 0 Broadcom BCM4306 rev 0x02: irq 10Data modified on freelist: word 0 of object 0xd0e68c00 size 0x28 previous type free (0x0 != 0xefffeecc), address 00:1a:70:b2:6f:07 Just retried with the Feb 29 snapshot, first boot still dies. But if I disable bwi, then it works. I hate this wireless crap. Gah. I had a similar problem with an older but similar Broadcom card because it was sharing an interrupt with something else (this was about 6mo back, using 4.0). If you'd like, I can try to dig up my notes on what I did to fix it. -ml
Re: HP Vectra VL - 450Mhz Pentium III. obsd 4.2 boots fine. snapshot 2/23 and 2/24 installs, but dies on booting
I had a similar problem with an older but similar Broadcom card because it was sharing an interrupt with something else (this was about 6mo back, using 4.0). If you'd like, I can try to dig up my notes on what I did to fix it. If it's no trouble, that would be great. I would much prefer not to have to buy another card... Thanx in advance! It was a machine that had 2 bcm4307s, but I'm questioning my own notes here as it seems unlikely that a wireless only card (thats what they were) would be using a 4307 as that one apparently also includes LAN features. The cards were just two 'flea market specials'. I had to resort to physically moving the cards around in the machine to avoid using the same int line ( I think this was an early P3 box iirc, like yours ). I'm not 100% certain that the chip number is right, but they were definitely broadcom 43xx. Looking back, it's possible that the cards were interfering with one another and perhaps separating them in the machine also helped. However, I explicitly noted that the irq changed when the cards were moved. Hope that helps. -ml
Re: Singularity OS
Die Gestalt wrote: I wrote several drivers in Windows NT using C++/STL/Boost and they had excellent performances and reliability. Are you sure you used the STL? http://www.microsoft.com/whdc/driver/kernel/KMcode.mspx Read the section about Libraries: Although much of the Standard Template Library is implemented as source code in headers, it occasionally uses library functions or other features that are not available or usable in the kernel environment. I'm guessing you must have had to do some serious mangling of the STL in order to shoehorn it into your driver. Sounds like far more trouble than it's worth. -ml
Re: OpenBSD 4.4
On Tue, Jan 24, 2012 at 03:48:49PM -0200, R0me0 *** wrote: Hello misc :) I'm running a full patched OpenBSD 4.4 with very complex setup, and I'm planning an upgrade to 5.0. At this moment, if I execute nmap 10.20.0/16, I have a dbg . I've limited the number of max connections and connections per seconds, that solved the problem. When dbg occurs, I cannot do a trace because it completely hangs. Following is a dmesg, any directions will be appreciated OpenBSD 4.4 (TENMA.MP) #3: Tue Jan 24 00:46:50 BRST 2012 r...@ns1.mycompany.com:/home/src/sys/arch/amd64/compile/TENMA.MP You're running an ancient version with a non-GENERIC kernel. Go read the FAQ, then come back. -ml real mem = 2132389888 (2033MB) avail mem = 2070573056 (1974MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xee000 (68 entries) bios0: vendor HP version P58 date 08/03/2008 bios0: HP ProLiant DL360 G5 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST APIC BERT HEST SSDT acpi0: wakeup devices PCI0(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz, 2833.79 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,LONG cpu0: 6MB 64b/line 16-way L2 cache cpu0: apic clock running at 333MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz, 2833.44 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,LONG cpu1: 6MB 64b/line 16-way L2 cache cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz, 2833.44 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,LONG cpu2: 6MB 64b/line 16-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Xeon(R) CPU E5440 @ 2.83GHz, 2833.44 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,LONG cpu3: 6MB 64b/line 16-way L2 cache ioapic0 at mainbus0 apid 8 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0 apid 9 pa 0xfec8, version 20, 24 pins acpiprt0 at acpi0: bus 1 (IP2P) acpiprt1 at acpi0: bus 11 (IPE1) acpiprt2 at acpi0: bus 10 (IPE4) acpiprt3 at acpi0: bus 17 (P2P2) acpiprt4 at acpi0: bus 9 (PT02) acpiprt5 at acpi0: bus 6 (PT03) acpiprt6 at acpi0: bus 20 (PT04) acpiprt7 at acpi0: bus 3 (NB01) acpiprt8 at acpi0: bus 5 (NB02) acpiprt9 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C3 acpicpu1 at acpi0: C3 acpicpu2 at acpi0: C3 acpicpu3 at acpi0: C3 acpitz0 at acpi0: critical temperature 31 degC ipmi at mainbus0 not configured cpu0: unknown i686 model 7, can't get bus clockcpu0: EST: unknown system bus clock pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 Intel 5000P Host rev 0xb1 ppb0 at pci0 dev 2 function 0 Intel 5000 PCIE rev 0xb1 pci1 at ppb0 bus 9 ppb1 at pci1 dev 0 function 0 Intel 6321ESB PCIE rev 0x01 pci2 at ppb1 bus 10 ppb2 at pci2 dev 0 function 0 Intel 6321ESB PCIE rev 0x01 pci3 at ppb2 bus 11 ppb3 at pci3 dev 0 function 0 vendor IDT, unknown product 0x8018 rev 0x0e pci4 at ppb3 bus 12 ppb4 at pci4 dev 2 function 0 vendor IDT, unknown product 0x8018 rev 0x0e pci5 at ppb4 bus 13 em0 at pci5 dev 0 function 0 Intel PRO/1000 QP (82571EB) rev 0x06: apic 8 int 19 (irq 10), address 00:1f:29:5f:fe:b5 em1 at pci5 dev 0 function 1 Intel PRO/1000 QP (82571EB) rev 0x06: apic 8 int 18 (irq 10), address 00:1f:29:5f:fe:b4 ppb5 at pci4 dev 4 function 0 vendor IDT, unknown product 0x8018 rev 0x0e pci6 at ppb5 bus 14 em2 at pci6 dev 0 function 0 Intel PRO/1000 QP (82571EB) rev 0x06: apic 8 int 17 (irq 7), address 00:1f:29:5f:fe:b7 em3 at pci6 dev 0 function 1 Intel PRO/1000 QP (82571EB) rev 0x06: apic 8 int 16 (irq 5), address 00:1f:29:5f:fe:b6 ppb6 at pci2 dev 1 function 0 Intel 6321ESB PCIE rev 0x01 pci7 at ppb6 bus 15 ppb7 at pci2 dev 2 function 0 Intel 6321ESB PCIE rev 0x01 pci8 at ppb7 bus 16 ppb8 at pci1 dev 0 function 3 Intel 6321ESB PCIE-PCIX rev 0x01 pci9 at ppb8 bus 17 ppb9 at pci0 dev 3 function 0 Intel 5000 PCIE rev 0xb1 pci10 at ppb9 bus 6 ciss0 at pci10 dev 0 function 0 Hewlett-Packard Smart Array rev 0x04: apic 8 int 16 (irq 5) ciss0: 1 LD, HW rev 4, FW 4.12/4.12 scsibus0 at ciss0: 1 targets, initiator 1 sd0 at scsibus0 targ 0 lun 0: HP, LOGICAL VOLUME, 4.12 SCSI3 0/direct fixed sd0: 139979MB, 17844 cyl, 255 head, 63 sec, 512 bytes/sec, 286677120 sec total ppb10 at pci0 dev 4 function 0 Intel 5000 PCIE x8 rev 0xb1
Re: TP X32 resume fails under 5.0-Release
On Tue, Feb 07, 2012 at 06:49:43PM +0100, Andr? wrote: Hi, under 4.9 everything works fine. Snapshot from yesterday also doesn't work. Same results for a Lenovo TP T60. When the screen comes back 2 keystrokes are possible, that's it. And the TP special keys are working. Did i miss something? Andri 2012/2/5 Andri k...@braselmann.org Hi there, i've installed 5.0-Release on TP X32 Pentium M 1,7 Ghz. Works fine, suspend works via apm (after starting apmd), but resume fails. Under X and on the console, the screen comes back, cursor is blinking an that's it. Pressing ON/OFF forces a quick reaction and simply powers down. The latest release i worked with was 4.6. Has this possibly something to to with the encrypted softraid0 in combination with the CF card ??? I have a very similar machine, and both suspend and resume work fine with both apm and acpi. Try narrowing it down further, and/or locating the specific diff that broke you. -ml
Re: status of ACPI suspend/resume on Thinkpad T60 w/ T7200 processor?
On Thu, Aug 04, 2011 at 09:37:00PM +, Jona Joachim wrote:
On 2011-08-04, Jonathan Thornburg jth...@astro.indiana.edu wrote:
What's the status of suspend/resume on thinkpad T60 series models,
particularly the T60 with T7200 cpu? So far as I know these are ACPI
and I know there have been a lot of improvements lately... but on
2010-10-23 Luca Corti luca () fantacast ! it
(message http://marc.info/?l=openbsd-miscm=128780398703487w=1)
reported
Dmesg from my T60 (T7200) below.
No big issues, but the fan is in fact a bit loud on OpenBSD, even when
running apmd -C. It could even suspend and resume correctly recently,
then stopped working but I don't mind since I don't use s/r.
[[...]]
OpenBSD 4.8-current (GENERIC.MP) #591: Tue Oct 19 11:45:02 MDT 2010
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Does suspend/resume work on T60 as of 4.9-{release,stable}? -current?
It does not work in 4.9. I haven't checked -CURRENT but I don't expect
it to work on -CURRENT either. It used to work at some point but I think
it was a change to the radeon driver that broke it (I assume you have a
radeon card). As of now it suspends but does not resume.
Does the moon icon stay lit, start blinking, go off? Does the screen backlight
light up (even if it's black). Did you try resuming from text mode (eg no X)?
-ml
Best regards,
Jona
--
Pond-erosa Puff wouldn't take no guff
Water oughta be clean and free
So he fought the fight and he set things right
With his OpenBSD
Re: any know bugs with sleep/resume on systems with 8GB ram?
On Fri, Sep 09, 2011 at 10:38:16PM +0200, roberth wrote: Hi, got around to upgrade my Thinkpad X200 (amd64) to 8GB RAM from 2GB. Since then after resume from sleep X is very laggy. Not just talking about apps that were open before the sleep/resume cycle, but also newly started. After rebooting the system every thing is dandy. Anyone? Ideas where to start investigating? - Robert This is a known issue with MTRRs on that model and a few others. The MTRRs are not being reprogrammed properly on resume, and the result is a large range of memory resuming as non-cacheable. It is on the radar to be fixed (a few of us have looked at this but no fix has come yet). Here's what I did: 1. memconfig list - note the non-bios memory ranges at the end of the list 2. make yourself a script that you can run as root after resume. Mine looks like this: memconfig set -b 0x0 -l 0x8000 write-back memconfig set -b 0x8000 -l 0x4000 write-back memconfig set -b 0x1 -l 0x1 write-back memconfig set -b 0x2 -l 0x4000 write-back You'll need to get the base and length values from step 1. Basically, you're just resetting the cacheability bits to whatever 'memconfig list' says they should be. This will probably be fixed at some point, but for now, it's not. -ml
Re: FreeBSD isn't Free
On Tue, Oct 05, 2010 at 11:22:03PM -0600, Theo de Raadt wrote: Just for fun. * 4.3. Licensee shall not export, either directly or indirectly, any of this * software or system incorporating such software without first obtaining any * required license or other approval from the U. S. Department of Commerce or * any other agency or department of the United States Government. In the * event Licensee exports any such software from the United States or * re-exports any such software from a foreign destination, Licensee shall * ensure that the distribution and export/re-export of the software is in * compliance with all laws, regulations, orders, or other restrictions of the * U.S. Export Administration Regulations. Licensee agrees that neither it nor * any of its subsidiaries will export/re-export any technical data, process, * software, or service, directly or indirectly, to any country for which the * United States government or any agency thereof requires an export license, * other governmental approval, or letter of assurance, without first obtaining * such license, approval or letter. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/contrib/dev/acpica/hardware/hwsleep.c?rev=1.2 This is why we have our own ACPI implementation... To avoid nonsense like this. -ml
Re: acpi woes Gateway LT31
On Mon, Dec 27, 2010 at 12:18:56PM -0800, patrick keshishian wrote: Hi, I am having a few issues with this laptop including not being able to make it sleep/suspend and/or wake up. Who are the right (interested) people I should/can send acpidump to? Anything else I should include? zzz will seemingly attempt to suspend the box. But it doesn't fully finish (I assume) leaving the display screen on, but at this point the box is hung. Can't ssh to it or ping it. I think caps-lock will toggle on/off the caps-lock light, but nothing else responds. Only choice is to hold down the power button for 4 seconds for a hard restart. Edit sys/dev/acpi.c, search for pci_dopm. Change the assignment from 1 to 0 and rebuild your kernel. -ml Also, the built-in weefee card will hang the box on `ifconfig athn0 scan`. Thanks, --patrick OpenBSD 4.8-current (GENERIC) #379: Tue Dec 21 19:17:45 MST 2010 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1876754432 (1789MB) avail mem = 1812852736 (1728MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf10d0 (17 entries) bios0: vendor Phoenix Technologies LTD version v1.3201 date 06/18/2009 bios0: Gateway LT31 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET BOOT SLIC acpi0: wakeup devices PB5_(S5) OHC1(S3) OHC2(S3) EHCI(S3) HDAU(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) Processor L110, 1197.21 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 199MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 21, 24 pins acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PB3_) acpiprt2 at acpi0: bus -1 (PB4_) acpiprt3 at acpi0: bus 3 (PB5_) acpiprt4 at acpi0: bus 4 (PB6_) acpiprt5 at acpi0: bus -1 (PB7_) acpiprt6 at acpi0: bus 9 (P2P_) acpiprt7 at acpi0: bus 1 (AGP_) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2 acpitz0 at acpi0: critical temperature 100 degC acpiac0 at acpi0: AC unit offline acpibat0 at acpi0: BAT1 model UM09B44 serial 210 type LION oem SONY acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: PWRB acpivideo0 at acpi0: VGA_ acpivout0 at acpivideo0: LCD_ acpivout1 at acpivideo0: CRT1 acpivout2 at acpivideo0: TV__ acpivout3 at acpivideo0: DFP1 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 ATI RS690 Host rev 0x00 ppb0 at pci0 dev 1 function 0 ATI RS690 PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon X1250 IGP rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 5 function 0 ATI RS690 PCIE rev 0x00 pci2 at ppb1 bus 3 re0 at pci2 dev 0 function 0 Realtek 8101E rev 0x02: RTL8102EL (0x2480), apic 1 int 17 (irq 5), address 00:23:8b:ef:3a:a7 rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1 ppb2 at pci0 dev 6 function 0 ATI RS690 PCIE rev 0x00 pci3 at ppb2 bus 4 athn0 at pci3 dev 0 function 0 Atheros AR9285 rev 0x01: apic 1 int 18 (irq 11), address 00:26:5e:0f:bc:3a athn0: AR9285 rev 2 (1T1R), ROM rev 13 ahci0 at pci0 dev 18 function 0 ATI SB600 SATA rev 0x00: apic 1 int 22 (irq 11), AHCI 1.1 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: ATA, TOSHIBA MK2555GS, FG00 SCSI3 0/direct fixed sd0: 238475MB, 512 bytes/sec, 488397168 sec total ohci0 at pci0 dev 19 function 0 ATI SB600 USB rev 0x00: apic 1 int 16 (irq 10), version 1.0, legacy support ohci1 at pci0 dev 19 function 1 ATI SB600 USB rev 0x00: apic 1 int 17 (irq 5), version 1.0, legacy support ohci2 at pci0 dev 19 function 3 ATI SB600 USB rev 0x00: apic 1 int 17 (irq 5), version 1.0, legacy support ohci3 at pci0 dev 19 function 4 ATI SB600 USB rev 0x00: apic 1 int 18 (irq 11), version 1.0, legacy support ehci0 at pci0 dev 19 function 5 ATI SB600 USB2 rev 0x00: apic 1 int 19 (irq 11) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 ATI EHCI root hub rev 2.00/1.00 addr 1 piixpm0 at pci0 dev 20 function 0 ATI SBx00 SMBus rev 0x14: SMI iic0 at piixpm0 spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM pciide0 at pci0 dev 20 function 1 ATI SB600 IDE rev 0x00: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility azalia0 at pci0 dev 20 function 2 ATI SBx00 HD Audio rev 0x00: apic 1 int 16 (irq 10) azalia0: codecs: Realtek ALC272 audio0 at azalia0 pcib0 at pci0 dev 20 function 3 ATI SB600 ISA rev 0x00 ppb3 at pci0 dev 20
Re: acpi woes Gateway LT31
On Tue, Dec 28, 2010 at 06:42:12PM -0800, Mike Larkin wrote: On Mon, Dec 27, 2010 at 12:18:56PM -0800, patrick keshishian wrote: Hi, I am having a few issues with this laptop including not being able to make it sleep/suspend and/or wake up. Who are the right (interested) people I should/can send acpidump to? Anything else I should include? zzz will seemingly attempt to suspend the box. But it doesn't fully finish (I assume) leaving the display screen on, but at this point the box is hung. Can't ssh to it or ping it. I think caps-lock will toggle on/off the caps-lock light, but nothing else responds. Only choice is to hold down the power button for 4 seconds for a hard restart. Edit sys/dev/acpi.c, search for pci_dopm. Change the assignment from 1 to 0 and rebuild your kernel. er. That was supposed to read /sys/dev/acpi/acpi.c -ml Also, the built-in weefee card will hang the box on `ifconfig athn0 scan`. Thanks, --patrick OpenBSD 4.8-current (GENERIC) #379: Tue Dec 21 19:17:45 MST 2010 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1876754432 (1789MB) avail mem = 1812852736 (1728MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf10d0 (17 entries) bios0: vendor Phoenix Technologies LTD version v1.3201 date 06/18/2009 bios0: Gateway LT31 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET BOOT SLIC acpi0: wakeup devices PB5_(S5) OHC1(S3) OHC2(S3) EHCI(S3) HDAU(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) Processor L110, 1197.21 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 199MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 21, 24 pins acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PB3_) acpiprt2 at acpi0: bus -1 (PB4_) acpiprt3 at acpi0: bus 3 (PB5_) acpiprt4 at acpi0: bus 4 (PB6_) acpiprt5 at acpi0: bus -1 (PB7_) acpiprt6 at acpi0: bus 9 (P2P_) acpiprt7 at acpi0: bus 1 (AGP_) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2 acpitz0 at acpi0: critical temperature 100 degC acpiac0 at acpi0: AC unit offline acpibat0 at acpi0: BAT1 model UM09B44 serial 210 type LION oem SONY acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: PWRB acpivideo0 at acpi0: VGA_ acpivout0 at acpivideo0: LCD_ acpivout1 at acpivideo0: CRT1 acpivout2 at acpivideo0: TV__ acpivout3 at acpivideo0: DFP1 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 ATI RS690 Host rev 0x00 ppb0 at pci0 dev 1 function 0 ATI RS690 PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon X1250 IGP rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 5 function 0 ATI RS690 PCIE rev 0x00 pci2 at ppb1 bus 3 re0 at pci2 dev 0 function 0 Realtek 8101E rev 0x02: RTL8102EL (0x2480), apic 1 int 17 (irq 5), address 00:23:8b:ef:3a:a7 rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1 ppb2 at pci0 dev 6 function 0 ATI RS690 PCIE rev 0x00 pci3 at ppb2 bus 4 athn0 at pci3 dev 0 function 0 Atheros AR9285 rev 0x01: apic 1 int 18 (irq 11), address 00:26:5e:0f:bc:3a athn0: AR9285 rev 2 (1T1R), ROM rev 13 ahci0 at pci0 dev 18 function 0 ATI SB600 SATA rev 0x00: apic 1 int 22 (irq 11), AHCI 1.1 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: ATA, TOSHIBA MK2555GS, FG00 SCSI3 0/direct fixed sd0: 238475MB, 512 bytes/sec, 488397168 sec total ohci0 at pci0 dev 19 function 0 ATI SB600 USB rev 0x00: apic 1 int 16 (irq 10), version 1.0, legacy support ohci1 at pci0 dev 19 function 1 ATI SB600 USB rev 0x00: apic 1 int 17 (irq 5), version 1.0, legacy support ohci2 at pci0 dev 19 function 3 ATI SB600 USB rev 0x00: apic 1 int 17 (irq 5), version 1.0, legacy support ohci3 at pci0 dev 19 function 4 ATI SB600 USB rev 0x00: apic 1 int 18 (irq 11), version 1.0, legacy support ehci0 at pci0 dev 19 function 5 ATI SB600 USB2 rev 0x00: apic 1 int 19 (irq 11) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 ATI EHCI root hub rev 2.00/1.00 addr 1 piixpm0 at pci0 dev 20 function 0 ATI SBx00 SMBus rev 0x14: SMI iic0 at piixpm0 spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM pciide0 at pci0 dev 20 function 1 ATI SB600 IDE rev 0x00: DMA, channel 0 configured to compatibility, channel 1 configured
Re: acpi woes Gateway LT31
On Wed, Dec 29, 2010 at 09:33:40AM -0800, patrick keshishian wrote: On Tue, Dec 28, 2010 at 6:47 PM, Mike Larkin mlar...@azathoth.net wrote: On Tue, Dec 28, 2010 at 06:42:12PM -0800, Mike Larkin wrote: On Mon, Dec 27, 2010 at 12:18:56PM -0800, patrick keshishian wrote: Hi, I am having a few issues with this laptop including not being able to make it sleep/suspend and/or wake up. Who are the right (interested) people I should/can send acpidump to? Anything else I should include? zzz will seemingly attempt to suspend the box. But it doesn't fully finish (I assume) leaving the display screen on, but at this point the box is hung. Can't ssh to it or ping it. I think caps-lock will toggle on/off the caps-lock light, but nothing else responds. Only choice is to hold down the power button for 4 seconds for a hard restart. Edit sys/dev/acpi.c, search for pci_dopm. Change the assignment from 1 to 0 and rebuild your kernel. er. That was supposed to read /sys/dev/acpi/acpi.c That seems to have done the trick! So what does this mean? I now see your check-in comment (dev/pci/ppb.c -r1.46), but question that comes to mind is whether this variable should be toggle-able at run time? No, the right thing to do is not power off pci(4) and ppb(4) if they don't support the feature. IIRC this machine has a ppb(4) that doesn't support power management. I know what to do but have not yet written a diff. -ml Thanks, --patrick -ml Also, the built-in weefee card will hang the box on `ifconfig athn0 scan`. Thanks, --patrick OpenBSD 4.8-current (GENERIC) #379: Tue Dec 21 19:17:45 MST 2010 ? ? dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1876754432 (1789MB) avail mem = 1812852736 (1728MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf10d0 (17 entries) bios0: vendor Phoenix Technologies LTD version v1.3201 date 06/18/2009 bios0: Gateway LT31 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET BOOT SLIC acpi0: wakeup devices PB5_(S5) OHC1(S3) OHC2(S3) EHCI(S3) HDAU(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) Processor L110, 1197.21 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 199MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 21, 24 pins acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PB3_) acpiprt2 at acpi0: bus -1 (PB4_) acpiprt3 at acpi0: bus 3 (PB5_) acpiprt4 at acpi0: bus 4 (PB6_) acpiprt5 at acpi0: bus -1 (PB7_) acpiprt6 at acpi0: bus 9 (P2P_) acpiprt7 at acpi0: bus 1 (AGP_) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2 acpitz0 at acpi0: critical temperature 100 degC acpiac0 at acpi0: AC unit offline acpibat0 at acpi0: BAT1 model UM09B44 serial 210 type LION oem SONY acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: PWRB acpivideo0 at acpi0: VGA_ acpivout0 at acpivideo0: LCD_ acpivout1 at acpivideo0: CRT1 acpivout2 at acpivideo0: TV__ acpivout3 at acpivideo0: DFP1 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 ATI RS690 Host rev 0x00 ppb0 at pci0 dev 1 function 0 ATI RS690 PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon X1250 IGP rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 5 function 0 ATI RS690 PCIE rev 0x00 pci2 at ppb1 bus 3 re0 at pci2 dev 0 function 0 Realtek 8101E rev 0x02: RTL8102EL (0x2480), apic 1 int 17 (irq 5), address 00:23:8b:ef:3a:a7 rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1 ppb2 at pci0 dev 6 function 0 ATI RS690 PCIE rev 0x00 pci3 at ppb2 bus 4 athn0 at pci3 dev 0 function 0 Atheros AR9285 rev 0x01: apic 1 int 18 (irq 11), address 00:26:5e:0f:bc:3a athn0: AR9285 rev 2 (1T1R), ROM rev 13 ahci0 at pci0 dev 18 function 0 ATI SB600 SATA rev 0x00: apic 1 int 22 (irq 11), AHCI 1.1 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: ATA, TOSHIBA MK2555GS, FG00 SCSI3 0/direct fixed sd0: 238475MB, 512 bytes/sec, 488397168 sec total ohci0 at pci0 dev 19 function 0 ATI SB600 USB rev 0x00: apic 1 int 16 (irq 10), version 1.0, legacy support ohci1 at pci0 dev 19 function 1 ATI SB600 USB rev 0x00: apic 1 int 17 (irq 5), version
Re: asus eee 1201n - acpitz0 critical temperature 255C (5282K), shutting down
On Tue, Jan 04, 2011 at 02:31:58PM -0800, Skylar Hawk wrote: On Tue, 04 Jan 2011 23:45:32 +0300 admin ad...@naranet.ru wrote: Hello, I've tryed to install openbsd 4.8 amd64 on asus eee 1201n, and i've got the message: acpitz0: Critical temperature 255C (5282K), shutting down while loading. Since 10 secons netbook is shutting down. I've got the same issue on a ASUS Eee PC 1015PED. In my case, installation went fine installing from a live USB drive using bsd.rd but when I tried to run the laptop itself I got shutdown due to critical temperature. My solution: disable the acpitz driver. You can either do it every time you boot by running bsd -c and then typing disable acpitz, or you can use config and have it disable it there. With that, everything else seems to work reasonable. No wifi, but I'll wait til the drivers get developed. On that note though, where should I send a dmesg so that people who want to work on it can have the information. Also, what other info would be useful to developers? -Sky Send a dmesg and acpidump (tar+gz it) to me (mlarkin@). I think it's likely the same problem we've seen on other acpitz-enabled machines. It might be related to acpiec or some other race. Some have said that unplugging and plugging in the power during boot (during autoconf) avoids it. Others haven't been so lucky. With the dmesg and acpidump I can at least see if it's the same machines that have had the same problem in the past. PS - disabling acpitz will result in overheating in certain cases. -ml
Re: acpitz critical temperature is too high
On Mon, Jun 18, 2012 at 06:35:58AM -0700, Robert Connolly wrote: Hello. During boot I see: acpitz0 at acpi0: critical temperature is 200 degC The acpitz(4) man page mentions that the system will power down if this critical temperature is reached. I assume this temperature is retrieved from BIOS, but I do not have an option in BIOS setup for it. Can I hard code this temperature in sys/dev/acpi/acpitz.c to a saner number? If so, it looks like I need to define sc-sc_crt, or possibly _CRT. Or is there another way to do this? Thanks Why do you want to do this? -ml
Re: acpitz critical temperature is too high
On Mon, Jun 18, 2012 at 05:54:31PM -0700, Robert Connolly wrote: I want to initiate a shutdown if the temperature gets too high. I have been This already happens if the temperature gets too high. See recent threads on misc@ about this. using sensorsd(8), but sensorsd(8) only reacts once to the high (or low) event, leaving it up to the program/script to run timers to keep checking if the temperature gets worse. For my satisfaction, the timers would have to keep running until the system cooled down below the high temperature, so that sensorsd(8) will pick up the monitoring from there. When the temperature gets to a warning level, I would like sensorsd(8) to notify logged in users (me), mail root, step down the CPU with apm -L, and then let the kernel do a shutdown, with acpitz(4), if the temperature continues to rise to critical. This would be easier and more simple for me than using sensorsd(8) alone (no timers). You want to continue to run your machine after its reached critical temperature? Critical means just that ... shut down I checked this out a little bit today. Some laptop manufacturers release Windows programs to control these temperature settings. I don't know if the setting is permanent/saved in BIOS, but if it is then I could run it from a Windows Livecd to reset the critical temperature. Another idea was installing Coreboot (free-bios), but I doubt my mainboard is supported, and it could brick my system. Or, configure the OpenBSD kernel to ignore the BIOS setting, and use my hard coded temperature instead. Or, use sensorsd(8) and a script. Good luck with this. On Mon, Jun 18, 2012 at 9:35 AM, Mike Larkin mlar...@azathoth.net wrote: On Mon, Jun 18, 2012 at 06:35:58AM -0700, Robert Connolly wrote: Hello. During boot I see: acpitz0 at acpi0: critical temperature is 200 degC The acpitz(4) man page mentions that the system will power down if this critical temperature is reached. I assume this temperature is retrieved from BIOS, but I do not have an option in BIOS setup for it. Can I hard code this temperature in sys/dev/acpi/acpitz.c to a saner number? If so, it looks like I need to define sc-sc_crt, or possibly _CRT. Or is there another way to do this? Thanks Why do you want to do this? -ml
Re: Hibernate doesn't work on my T43
On Sun, Jul 22, 2012 at 02:03:09PM +0200, Andr?? S. wrote: Alexey E. Suslikov wrote: You should try with newer BIOS. Done, as well as the ECP. Booting now with apm disabled causes OpenBSD to hang on starting network. The cursor is still blinking, but after 15 minutes it's still stuck there. Another idea - cardbus isn't hibernating/resuming properly. People on the list wouldn't like such an advice, but try to boot with ccb disabled, ZZZ and resume. You meant cbb, right? This causes the system not to hang on boot at least, but it still doesn't wake after ZZZ. Attached is a dmesg with updated BIOS+ECP and disabled apm+cbb. Regards Andre cut dmesg My t43p hibernates and resumes fine with the following changes: 1. Disable apm 2. change pci_dopm=1 to 0 in dev/acpi/acpi.c I did notice that the unpack (on resume) of the hibernated image is quite slow on this machine, about 2 minutes. The W500 Thinkpad has a similar problem ... still investigating why this happens on some machines (and not others). But it does work. -ml
Re: Hibernate doesn't work on my T43
On Tue, Jul 24, 2012 at 05:51:51PM +0200, Andr?? S. wrote: Mike Larkin wrote: My t43p hibernates and resumes fine with the following changes: 1. Disable apm 2. change pci_dopm=1 to 0 in dev/acpi/acpi.c OK, did that. I now see that it actually tries to hibernate but I get this kernel message repeatedly: pciide0:0:0: timeout waiting for DRQ, st=0x51DRDY,DSC,ERR, err=0x00 15 minutes later and the machine's still trying to hibernate, telling me about this DRQ-thing I don't know nothing about. Is it safe to just hard reset the machine? Thanks. Regards Andr?? Probably different disk controller than mine. You'll need to wait for the proper power management fix, which is being worked on. -ml
Re: XenServer and re0 watchdog timeout
On Fri, Nov 16, 2012 at 04:43:42PM +, Rodolfo Gouveia wrote: Hi all, Has anybody tested XenServer 6.0 with OpenBSD 5.2 amd64 as a guest? Network doesn't work and I all get are re0 watchdog timeout over and over... p.s. no dmesg because I don't have network access qemu's doing the device emulation and it does not implement the device's watchdog timer. You need to switch to a different emulated nic, or patch the re(4) driver so that it doesn't expect a watchdog. Two ways: 1. Change the vif type in XenServer to be e1000 or ne2k 2. There is a patch for NetBSD that disables the watchdog timer. A quick google search will find it for you. You might need to massage it a bit to get it to apply to -current. -ml
Re: Kernel panic with Asus U36S on 5.2 and current amd64
On Sat, Dec 15, 2012 at 05:46:39PM +0100, Tomas Bodzar wrote: Hi all, my friend tested OpenBSD amd64 (5.2 and current) with Asus U36S, but install goes always fine. However first reboot always result in a kernel panic related to aml and acpi. BIOS is 203, there's newer one 206 with updates to VGA bios and 205 was with updates to BIOS (Asus doesn't describe those well). I have three pictures taken by him of trace and ps if anyone interested (in ps is only swapper anyway). It boots once 'disable acpi' done in UKC. In terminal it looks fine (asking for dmesg), just doing startx hangs PC. He will try to update BIOS today. dmesg and panic text with trace, please. An acpidump would also be useful. -ml
Re: Kernel panic with Asus U36S on 5.2 and current amd64
On Mon, Dec 17, 2012 at 06:16:29PM +0100, Tomas Bodzar wrote: On Sat, Dec 15, 2012 at 11:01 PM, Mike Larkin mlar...@azathoth.net wrote: On Sat, Dec 15, 2012 at 05:46:39PM +0100, Tomas Bodzar wrote: Hi all, my friend tested OpenBSD amd64 (5.2 and current) with Asus U36S, but install goes always fine. However first reboot always result in a kernel panic related to aml and acpi. BIOS is 203, there's newer one 206 with updates to VGA bios and 205 was with updates to BIOS (Asus doesn't describe those well). I have three pictures taken by him of trace and ps if anyone interested (in ps is only swapper anyway). It boots once 'disable acpi' done in UKC. In terminal it looks fine (asking for dmesg), just doing startx hangs PC. He will try to update BIOS today. dmesg and panic text with trace, please. An acpidump would also be useful. I will be able to collect those during this week. However this is nVidia Optimus platform for VGA and even in latest BIOS there's not switch to use only integrated Intel VGA so let's see what will happen. On AC adapter it runs nVidia, without AC adapter it runs Intel. -ml This probably has nothing to do with nVidia. -ml
Re: Laptop freeze on boot because of ACPI
On Mon, Feb 04, 2013 at 11:53:02PM +0100, Charles Rapenne wrote:
Hello,
I installed successfully OpenBSD on my laptop, but at boot it hangs on
acpi. Disabling ACPI let me boot.
Please find the dmesg once booted, I typed trace and ps as asked
during the panic. The dmesg hanging has been done with bsd.sp (the
same thing happens with bsd.mp). It happens also with 5.1 and 5.2, I
upgraded to -current (5.3) and nothing changed.
Please provide an acpidump.
-ml
OpenBSD 5.3-beta (GENERIC) #25: Mon Feb 4 01:18:15 MST 2013
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz (GenuineIntel
686-class) 2.30 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,LAHF,PERF,ITSC
real mem = 2860101632 (2727MB)
avail mem = 2802405376 (2672MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/03/10, SMBIOS rev. 2.6 @
0xeb9e0 (78 entries)
bios0: vendor American Megatrends Inc. version N55SF.207 date 08/29/2011
bios0: ASUSTeK Computer Inc. N55SF
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC DBGP ECDT SLIC HPET MCFG SSDT SSDT ASF!
acpi0: wakeup devices P0P1(S4) HDEF(S4) GLAN(S4) PEG0(S4) PEG1(S4)
PEG2(S4) PEG3(S4) B0D4(S4) EHC1(S3) USB1(S3) USB2(S3) USB3(S3)
USB4(S3) EHC2(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S4) RP02(S4)
WLAN(S3) RP03(S4) RP04(S4) XHCI(S3) RP05(S4) RP06(S4) GLAN(S4)
RP07(S4) RP08(S4) SLPB(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 99MHz
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiec0 at acpi0
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P1)
acpiprt2 at acpi0: bus 1 (PEG0)
acpiprt3 at acpi0: bus -1 (PEG1)
acpiprt4 at acpi0: bus -1 (PEG2)
acpiprt5 at acpi0: bus -1 (PEG3)
acpiprt6 at acpi0: bus 2 (RP01)
acpiprt7 at acpi0: bus 3 (RP02)
acpiprt8 at acpi0: bus -1 (RP03)
acpiprt9 at acpi0: bus 4 (RP04)
acpiprt10 at acpi0: bus -1 (RP05)
acpiprt11 at acpi0: bus 5 (RP06)
acpiprt12 at acpi0: bus -1 (RP07)
acpiprt13 at acpi0: bus -1 (RP08)
acpicpu0 at acpi0: C1, PSS
acpitz0 at acpi0acpitz0: THRM: failed to read _CRT
: no critical temperature defined
acpiac0 at acpi0: AC unit in unknown state
acpibat0 at acpi0: BAT0 not present
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: SLPB
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: LCDD
[\\_SB_.PCI0.SBRG.EC0_.PWAC] 0xd39fd1c4 cnt:02 stk:00 buffer: 40 {33,
40, 4d, 5a, 67, 73, 80, 8d, a7, cd, ff, ff, ff, ff, ff, ff, 21, 2e,
3b, 48, 55, 61, 6e, 7b, 9a, c5, ff, ff, ff, ff, ff, ff, ff, ff, ff,
ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff,
ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff, ff}
Index out of bounds 3818/64
13665 Called: \\_SB_.PCI0.PEG0.GFX0.LCDD._BCL
local0: 0xd3a1f744 cnt:01 stk:60 integer: 0
local3: 0xd3a1d1c4 cnt:02 stk:63 integer: eea
local4: 0xd3a1d204 cnt:01 stk:64 integer: ee0
13632 Called: \\_SB_.PCI0.PEG0.GFX0.LCDD._BCL
local0: 0xd3a1f744 cnt:01 stk:60 integer: 0
local3: 0xd3a1d1c4 cnt:02 stk:63 integer: eea
local4: 0xd3a1d204 cnt:01 stk:64 integer: ee0
panic: aml_die aml_parse:3606
Stopped at Debugger+0x4: popl %ebp
Debugger(d08fc71c,d0bc8694,d09d805a,d0bc8694,d3a1fd04) at Debugger+0x4
panic(d09d805a,d09d7e12,e16,0,d0bc86c4) at panic+0x5d
_aml_die(d09d7e12,e16,d09d8340,eea,40) at _aml_die+0x135
aml_parse(d3a1fbc4,74,d09d838a,0,0) at aml_parse+0x1b72
aml_parse(d3a1fbc4,74,d09d881b,0,d3a1fc44) at aml_parse+0x1bb
aml_parse(d3a1f504,54,d09d846c,14,d0bc88d7) at aml_parse+0x1bb
aml_eval(0,d3a0d884,74,0,0) at aml_eval+0x21c
aml_evalnode(d398bc00,d3a0d8c4,0,0,d0bc8948) at aml_evalnode+0x68
acpivout_get_bcl(d38a1480,d38a1480,d0bc89d8,d03f486b,0) at
acpivout_get_bcl+0x3d
config_attach(d3a1fa00,d09e07e0,d0bc89d8,d0859aa0,d39c4644) at
config_attach+0x1bb
RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
ddb Debugger(d08fc71c,d0bc8694,d09d805a,d0bc8694,d3a1fd04) at Debugger+0x4
panic(d09d805a,d09d7e12,e16,0,d0bc86c4) at panic+0x5d
_aml_die(d09d7e12,e16,d09d8340,eea,40) at _aml_die+0x135
aml_parse(d3a1fbc4,74,d09d838a,0,0) at aml_parse+0x1b72
aml_parse(d3a1fbc4,74,d09d881b,0,d3a1fc44) at aml_parse+0x1bb
aml_parse(d3a1f504,54,d09d846c,14,d0bc88d7) at aml_parse+0x1bb
aml_eval(0,d3a0d884,74,0,0) at aml_eval+0x21c
aml_evalnode(d398bc00,d3a0d8c4,0,0,d0bc8948) at aml_evalnode+0x68
Re: Laptop freeze on boot because of ACPI
On Tue, Feb 05, 2013 at 10:01:10PM +0100, Charles Rapenne wrote: I used the command acpidump -o a. I didn't understand the use of the prefix so I put a. Thank you for your help (I cut the gibberish out) Please give me an acpidump that is actually usable. What you inlined won't do any good. Use sendbug. -ml
Re: 5.2, i386, small kernel crash
On Fri, Feb 08, 2013 at 06:56:08PM +0100, Christian Groessler wrote: Hi, I've tried to make a kernel config which only includes what I need. It's attached. The resulting kernel crashes in vga_pci_attach() when it writes to do_real_mode_post. do_real_mode_post is in the text section, so should be readonly, therefore the crash makes sense. But when I build GENERIC the crash doesn't happen, do_real_mode_post still in text section. How does this work? And, what is wrong with my config? In the meanwhile I'm avoiding the crash by patching vga_pci.c. The machine won't got to sleep (it's a server), so it's ok for now. Kernels other than GENERIC/GENERIC.MP and RAMDISK aren't supported by devs. That being said, we should probably clean up the do_real_mode_post business at some point. I think it's outlived its usefulness. -ml
Re: Thinkpad X230t convertible and openbsd
On Thu, May 23, 2013 at 02:26:39PM +0200, Thanos Tsouanas wrote: Christian Weisgerber wrote: FWIW, the Intel Centrino Ultimate-N 6300 iwn(4) in my non-t X230 works just fine. That's the 3x3 card on their order site. Could you please check the exact model and FCC ID of that card? The (non-t) X230 that I bought came with the Intel Centrino Wireless-N 2200 card (model: 2200BNHMW, FCC ID: PD92200BNHU) I've got a start of a driver for this in my tree. It can detect the card, upload the firmware, start the device up but presently has problems calibrating the RF crystal. I haven't had time to debug it further but maybe at the upcoming hackathon (doubtful though). -ml which does not work on OpenBSD, so I bought the Intel Centrino Ultimate-N 6300 card (model: 633ANHMW, FCC ID: PD9633ANH) which I was hoping it to be in the whitelist of the X230. However, it is not.. So, either the whitelist is different depending on the configuration settings (so that they only whitelist the card you bought it with), or it is a problem with the specific model of my 6300 card. Any info/ideas, appreciated.. thanks! On Thu, May 9, 2013 at 4:11 PM, Edd Barrett vex...@gmail.com wrote: On Wed, May 08, 2013 at 01:28:05PM +0200, David Coppa wrote: It depends if it is a serial wacom tablet or a usb one. See: http://openbsd.7691.n7.nabble.com/X60-Tablet-Wacom-Atheros-5213-amp-others-td67571.html#a67575 Hmm, I am not sure to be honest. -- Best Regards Edd Barrett http://www.theunixzoo.co.uk -- Thanos Tsouanas http://perso.ens-lyon.fr/thanos.tsouanas/
Re: Thinkpad R61 does not fully resume
On Wed, Oct 23, 2013 at 07:36:30AM +0200, Jan Stary wrote: On Oct 22 14:25:33, mlar...@azathoth.net wrote: Not sure if someone else already replied, but this: vga1 at pci1 dev 0 function 0 vendor NVIDIA, unknown product 0x0429 rev 0xa1 is your problem. We don't resume NVIDIA cards. We don't know how, and NVIDIA won't tell us how. Thank you for the insight. does that also influence the NIC not comming back up? Jan Which nic? iwn or em? Both should be supported in resume today. -ml On Thu, Oct 10, 2013 at 04:13:35PM +0200, Jan Stary wrote: With the latest i386 snapshot, my Lenovo R61 suspends, but does not fully resume. The behaviour was the same with the previous snapshot. After apm -S (or closing the lid) and then Fn+F4 (or opening the lid) I can see the disk and power leds blinking as if comming back up, but the screen stays black, and the machine is not remotely accessible. I haven't tried yet whether wifi or USB come back up. However, typing 'halt -p' blindly at the black console shuts the machine down correctly. See the dmesg below; acpidump here: http://stare.cz/dmesg/lenovoR61.tar What can I do to help OpenBSD better support this? Thank you Jan OpenBSD 5.4-current (GENERIC.MP) #70: Tue Oct 1 12:57:28 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz (GenuineIntel 686-class) 799 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF real mem = 1071894528 (1022MB) avail mem = 1042628608 (994MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/27/07, BIOS32 rev. 0 @ 0xfdc70, SMBIOS rev. 2.4 @ 0xe0010 (71 entries) bios0: vendor LENOVO version 7KET72WW (1.22 ) date 08/27/2007 bios0: LENOVO 8918B8G acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz (GenuineIntel 686-class) 2 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model COMPATIBLE serial 13920 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) bios0: ROM list: 0xc/0xf000 0xcf000/0x1000 0xd/0x1000 0xe/0x1! cpu0: Enhanced SpeedStep 1995 MHz: speeds: 2001, 2000, 1600, 1200, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel GM965 Host rev 0x0c ppb0 at pci0 dev 1 function 0 Intel GM965 PCIE rev 0x0c: apic 1 int 16 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 vendor NVIDIA, unknown product 0x0429 rev 0xa1 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) em0 at pci0 dev 25 function 0 Intel ICH8 IGP M rev 0x03: msi, address 00:1a:6b:d4:5f:22 uhci0 at pci0 dev 26 function 0 Intel 82801H USB rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 Intel 82801H USB rev 0x03: apic 1 int 21 ehci0 at pci0 dev 26 function 7 Intel 82801H USB rev 0x03: apic 1 int 22 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801H HD Audio rev 0x03: msi azalia0: codecs:
Re: Forced shutdown due high temperatures
On Tue, Nov 05, 2013 at 12:23:56AM +, E. Goncalves wrote: Hello there, I've just installed OpenBSD 5.4 on my machine and a few minutes of uptime without doing nothing the system shuts down saying the temperature is high, and I put my hands on top of keyboard in the location where the processor is but it is not warn at all. This issue never happened to me using this laptop or OpenBSD before (using 5.3). I use OpenBSD mainly to code in C, C++ and CLisp but, basically pass most of time with a instance of Emacs running and issuing make, and if I put my hand in the same spot above the processor location it feels warn (but not warmer then when I was using openSUSE), and warmer than in OpenBSD 5.4 but it does not shutdown. Does anyone is experiencing the same issues? Can someone help me? No dmesg, no help.
Re: Failed to hibernate in 5.4 current i386
On Tue, Nov 05, 2013 at 06:40:03PM +0100, Jes wrote: Sorry, I don't understand you. You says the problem is solved since yesterday (the snapshot my computer is running is from 03/11/2013), but at the same time you says the swap size is not bib enough, but it's more than the memory+64Mb (http://undeadly.org/cgi?action=articlesid=20120712101743). And, in fact, my laptop hibernated one week ago (more or less). The old way (up until yesterday) entailed the following: 1. Check if the default swap device (the one printed in autoconf) was the size of physical memory or greater. If not, abort hibernate. 2. Next, check if the range consuming the last physical memory size amount of swap was unallocated (eg, on an 8GB machine, check to make sure that the last 8GB was unallocated). If not, abort hibernate. You probably had something swapped out into that end range, so we aborted. But as Theo mentions, this discussion is moot due to the improvements that went in yesterday. I have two swap partitions, sd1b and sd1j. The total amount of swap is about 12G. I think with the small one (more than 3Gb) the system hibernated, and with the 8Gb it did too. We currently only use the default swap device. Any extra swap you've got defined is ignored. Could you explain a bit more this? About the USB problem... thanks for solve it :) Thanks Jes On Tue, Nov 5, 2013 at 6:23 PM, Theo de Raadt dera...@cvs.openbsd.orgwrote: This ocurrs in last two o three snapshots (I cannot be more precise) but it used to work fine in current. Hibernation fails with the following message: insufficient swap space for hibernate acpi0: hibernate_suspend failed This problem has been there since the start. Anyways, I fixed it yesterday. It now will let you hibernate. There are some range checks still missing in the code, and those are being improved... b: 17946495177387840swap No, it is not big enough. The old calculation required a lot more overhead. It was ridiculous. Hibernation it's very useful due to a problem in my laptop (Thinkpad T410 with IvyBridge): no powered usb ports on resume after suspend. Hibernation is a good replacement for suspend when it runs out of battery. This USB problem is about to be solved, a diff is coming from mpi@ T
Re: QEMU CPU cores not showing up
On Wed, Nov 13, 2013 at 09:44:11PM +0100, Otto Moerbeek wrote: On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote: Hi Otto, http://pastebin.com/zfkEUxX8 This is generic.mp with flags of apm and acpi disable Why would you start trying to disable random devices in the kernel and expect things to get any better? For the past several years, acpi is needed on most machines to do anything useful with those machines. That includes VMs. http://pastebin.com/PEjCr2vY Generic.MP boot. I am not sure what is wrong and why this works with all the other OS's... From your output, there are no APs being presented to the VM. Talk to your cloud provider. -ml No clue then. Maybe some kernel hacker can guess. -Otto -- Bruno Delbono | Cognitive Researcher - Human Behavioural Project | Real Sociedad Espa??ola De Antropolog??a | ???: +1 855 253 5436 ???: +1 424 354 4700 From: Otto Moerbeek o...@drijf.net Sent: Wednesday, November 13, 2013 3:11 PM To: Bruno Delbono Cc: misc@openbsd.org Subject: Re: QEMU CPU cores not showing up On Wed, Nov 13, 2013 at 07:36:58PM +, Bruno Delbono wrote: Hello, I have a QEMU instance that works perfectly fine at detecting cpu cores on NetBSD/FreeBSD/Linux. All except OpenBSD 5.4 - I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp snapshot kernel. Use the GENERIC.MP kernel. - I have tried disabling apm and acpi* during boot config I am completely lost as to why this may be happening. You can see the NetBSD boot 6.1.2 on the same machine here: http://pastebin.com/FJeiRp9t You can see OpenBSD snapshot boot (please ignore disable acpi vs acpiprt* - I tried both) here: http://pastebin.com/v9XWv4XY I am using BlueVM (www.BlueVM.comhttp://www.BlueVM.com) as my KVM provider. Can anyone guide me on what I should do or try next? Is it a QEMU issue with the Cloud Services Provider? Thanks, -Bruno
Re: System freeze after zzz
On Sun, Nov 24, 2013 at 10:42:45AM -0500, Don Allen wrote: I'm running current (as of the 11/14 snapshot) on a micro-itx box I built around an Intel Atom d510mo motherboard. When I try to wake the system after zzz, my X session comes alive and I can change workspaces with the window manager (xmonad; no desktop system), but firefox is hung (won't repaint its window), can't run top, can't run shutdown from another console. I can ping the system from another, but can't ssh to it. Guesswork on my part: the kernel is giant-locked, so no system calls? The only way I've found to get out of this is to power-cycle. It's happened a few times now, so I think I can reproduce it and am certainly willing to try to help debug. Can you try to see if time is advancing after resume? Eg, a sequence of 'date' commands from an open xterm? -ml Dmesg: OpenBSD 5.4-current (GENERIC.MP) #147: Tue Nov 12 16:37:15 MST 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80clock_battery real mem = 4260089856 (4062MB) avail mem = 4138549248 (3946MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe43c0 (27 entries) bios0: vendor Intel Corp. version MOPNV10J.86A.0311.2010.0802.2346 date 08/02/2010 bios0: Intel Corporation D510MO acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET SSDT acpi0: wakeup devices SLPB(S4) PS2M(S4) PS2K(S4) UAR1(S4) UAR2(S4) P32_(S4) ILAN(S4) PEX0(S4) PEX1(S4) PEX2(S4) PEX3(S4) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) EHCI(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.96 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF cpu0: 512KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.1.0.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.69 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF cpu1: 512KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.69 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF cpu2: 512KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.69 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF cpu3: 512KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 5 (P32_) acpiprt1 at acpi0: bus 0 (PCI0) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus 2 (PEX1) acpiprt4 at acpi0: bus 3 (PEX2) acpiprt5 at acpi0: bus 4 (PEX3) acpicpu0 at acpi0: C1 acpicpu1 at acpi0: C1 acpicpu2 at acpi0: C1 acpicpu3 at acpi0: C1 acpibtn0 at acpi0: SLPB pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Pineview DMI rev 0x02 vga1 at pci0 dev 2 function 0 Intel Pineview Video rev 0x02 intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 intel_overlay_map_regs partial stub inteldrm0: 1280x800 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x01: msi azalia0: codecs: Realtek ALC662 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: msi pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 Realtek 8168 rev 0x03: RTL8168D/8111D (0x2800), apic 8 int 16, address 00:27:0e:0e:ff:a9 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x01: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x01: msi pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x01: msi pci4 at ppb3 bus 4 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 8 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic
Re: System freeze after zzz
On Tue, Nov 26, 2013 at 07:44:32AM -0500, Donald Allen wrote:
On Tue, Nov 26, 2013 at 2:15 AM, Mike Larkin mlar...@azathoth.net wrote:
On Sun, Nov 24, 2013 at 10:42:45AM -0500, Don Allen wrote:
..snip..
After waking up:
Switching consoles with ctrl-alt F2, I was able to run the date
command repeatedly, and the time is advancing. 'ls' also worked
normally, but 'ls -l' hung. 'ps aux' hangs. 'shutdown' and 'reboot'
both hang.
Switching consoles with ctrl-alt F1, I noticed the following chatter:
ahci0: device on port 0 didn't come ready TFD: 0x80BSY
ahci0: Stopping the port, soft reset slot 31 was still active
ahci0: unable to communicate with device on port 1
That's your problem, your disk didn't come back after resume. I'm not sure
why, this is the first time I've seen that. Maybe some ahci expert
can comment further. I've frequently seen the first ahci0: line above
but my disks always come back online after that.
I don't know if the above is significant, but it isn't there on that
first console if I don't suspend and it struck me as suspicious.
I also noticed that the disk-busy light on the front panel is on solid
after attempting to resume. In normal operation, when there is disk
activity and the light is on, I can hear the disk, presumably the
heads seeking. In this situation, I don't hear that. I realize that
doesn't mean there isn't disk activity, just not long enough head
excursions to be audible.
The disk came back partly-resumed. Who knows what state it's in.
I have all filesystems mounted with softdep enabled, and after
power-cycling to reboot, there's usually a lot of chatter from fsck
about repairing things on various filesystems. One that usually turns
up needing repair is sd0d, which is /tmp. If the fsck output is logged
somewhere and it would be helpful, I can send it. I tried to find it
with
cd /var
find . -exec fgrep SALVAGED {} \; -print
which turned up nothing. Or I can try to photograph the screen as it's
happening.
Your FSes were uncleanly shut down since the disk didn't resume and that's
why fsck finds a bunch of uncleanliness.
I also tried suspending with 'zzz' right after booting and logging in,
no 'startx'. After attempting to resume, I got a stream of messages on
the first console, all the same:
ehci_idone: ex=0x801f3c00 is done!
That's irrelevant and may even be fixed by some recent commits. It's
because we basically need to tear down the USB device tree and reconnect
it on resume. There was probably an xfer in flight when you suspended and
the device to which it was associated dissappeared (temporarily) on
resume.
The disk-busy light was not on. I could not switch consoles to try
commands and could not type at the console that was spewing these
messages. As with the above, I had to power-cycle to recover.
/Don
Your problem is that your disk didn't resume. There are some efforts going
on presently to improve some of the wakeup/resume codepaths, but those
diffs aren't in the tree yet. They may or may not help.
Re: Suspend/Resume and USB filesystems
On Fri, Jan 03, 2014 at 12:13:05AM -0500, Ted Unangst wrote: On Fri, Jan 03, 2014 at 09:17, Helg Bredow wrote: I've been running OpenBSD 5.4 off a USB stick and couldn't get suspend/resume to work on either of my laptops. I thought maybe it was a driver issue but I've now installed the latest snapshot to the internal HDD and suspend/resume seems to be working fine. However, suspend causes a detach of the whole ugen to umass stack to detach so any mounted USB filesytems end up in an unclean state. This is probably what was causing it to fail when booting off USB. Is there anything that I need to configure in order to prevent this from happening? I don't think there's anything you can do. That's how the kernel does things (detach usb, reattach). We could: 1. postpone the device detach until after resume, and then only detach devices which are actually missing. I'm not sure how much madness this would involve. 2. postpone forced filesystem unmount until after resume to see if the disk comes back. I'm fairly certain this will involve a lot of madness. This is not likely going to be fixed in any near timeframe. It's just too much headache. -ml
Re: 5.5 current resume hangs
On Sun, Apr 13, 2014 at 10:06:18AM +0200, Jes wrote: From at least a couple of month my laptop doesn't resume after suspend. Mine is a thinkpad T410 with intel integrated gpu. The behaviour seems to be the same as reported in: http://openbsd.7691.n7.nabble.com/T410i-resume-broken-with-amd64-bsd-mp-and-revision-1-249-of-acpi-c-td240150.html But, I think in december 2013 my laptop was able to resume with current. With the SP kernel the system suspends and resumes perfectly. I didn't see any other report besides the previous one about this issue. Thanks in advance, Jes ... and yet you don't offer us any dmesg or other information about your machine so we can help you.
Re: Boot panic on MP amd64 with 5.5, snapshot kernels
On Sun, May 18, 2014 at 03:04:30PM -0400, John D. Verne wrote: I just got a new amd64 box to run OpenBSD on, but it is panicking on boot when I try to run the 5.5 kernel on it. The panic is unknown MPS interrupt trigger 2 somewhere in the acpi code. bsd.rd, bsd and bsd.mp all panic in the same places, as does bsd.rd from the latest amd64 snapshot. I haven't tried i386 yet. I messed around with boot -c and verbose mode, and captured the entire dmseg from ddb from 5.5 /bsd. I've placed the lame camera phone pics here: http://www.clevermonkey.org/OpenBSD/amd64_55_info/ I couldn't figure out how to save the actual text. Sorry. Also, if it matters, this is all done via PXE boot, as this box has no CDROM or floppy, and I didn't have the facility to make an amd64 USB stick (this is my only amd64 box.) Also, if it matters, I opted to not get the Atom version of this board because I wanted some of the more interesting chipset support. It is a Celeron J1000. I also wanted the better supported Intel graphics stuff (even though I suspect this box will run in text-only mode most of its life.) I'm staring at the ACPI code trying to figure out the various defines used, and 2 seems to be there. I welcome conversations about what this code is doing and what it wants out of total curiousity. -- John D. Verne j...@clevermonkey.org Is this 5.5-current? We made some changes in the MADT code recently. -ml
Re: uaudio useless?
On Sun, May 18, 2014 at 10:17:41PM +0100, Kevin Chadwick wrote: previously on this list Christian Weisgerber contributed: Maybe there are audio dongles that run at hi-speed, otherwise uaudio(4) looks pretty useless. FWIW, I have 3 different uaudio dongles and they all work fine. One is a Creative (I can get the model # if you want) and the other two are no-name brands. I have a fourth uaudio that attaches in an expresscard slot and that one doesn't work, but it's not for the same reason as yours (it can't understand the codecs, I think). -ml I may have one as it supports DSD however it comes up as ugen currently so I am not sure if it would use uaudio until I have the time to look into how much I can get to work with OpenBSD. -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) In Other Words - Don't design like polkit or systemd ___ I have no idea why RTFM is used so aggressively on LINUX mailing lists because whilst 'apropos' is traditionally the most powerful command on Unix-like systems it's 'modern' replacement 'apropos' on Linux is a tool to help psychopaths learn to control their anger. (Kevin Chadwick) ___
Re: Boot panic on MP amd64 with 5.5, snapshot kernels
On Mon, May 19, 2014 at 01:42:49PM -0400, John D. Verne wrote: On Sun, May 18, 2014 at 03:04:30PM -0400, John D. Verne wrote: I just got a new amd64 box to run OpenBSD on, but it is panicking on boot when I try to run the 5.5 kernel on it. The panic is unknown MPS interrupt trigger 2 somewhere in the acpi code. bsd.rd, bsd and bsd.mp all panic in the same places, as does bsd.rd from the latest amd64 snapshot. NetBSD 6.1.4 manages to enumerate all the ACPI stuff when I use their boot image. So there's that. As an aside, I was surprised at how different the src/sys tree is from OpenBSD. But I'm going to try and see how they handle the Intel ACPICA 20110623 device, which seems to be the thing that is not working right. Get a dump of the AML using FreeBSD then. Can't really help otherwise. And PS there is no such thing as an Intel ACPICA 20110623 device. That's the parser code NetBSD is using. We have our own. -- John D. Verne j...@clevermonkey.org
Re: System refuses to boot without first disabling acpimadt
On Thu, May 29, 2014 at 02:26:04PM -0500, Cal Folds wrote: I'm learning OpenBSD on an older laptop from a company called Hannspree. The installation went great and everything seemed fine, but when the system boots it quickly starts to slow down and eventually hangs with a flashing screen before the log in prompt. The problem goes away when I disable acpimadt. I'm running well enough for my purposes at the moment, but I was encouraged by some helpful redditors to post this problem here. Apparently, learning to productively participate with the mailing list is an essential openbsd lesson and hopefully someone knows what I've done wrong or this can help a dev fix a bug. I've uploaded a video of the problem here : https://www.youtube.com/watch?v=ALN00Y8w0l8 We've made some changes in acpimadt in the last month or so. Try updating to -current and see if the problem still exists. -ml dmesg below: OpenBSD 5.5 (GENERIC.MP) #315: Wed Mar 5 09:37:46 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2093547520 (1996MB) avail mem = 2029264896 (1935MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xfba90 (57 entries) bios0: vendor American Megatrends Inc. version 080016 date 06/01/2010 bios0: HANNspree SN12E200 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG SLIC OEMB HPET SSDT acpi0: wakeup devices P0P2(S4) P0P1(S4) USB2(S4) USB4(S4) USB6(S4) GBE_(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) USB0(S4) USB1(S4) USB3(S4) USB5(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P2) acpiprt2 at acpi0: bus 2 (P0P4) acpiprt3 at acpi0: bus 3 (P0P5) acpiprt4 at acpi0: bus -1 (P0P6) acpiprt5 at acpi0: bus 4 (P0P7) acpiprt6 at acpi0: bus -1 (P0P8) acpiprt7 at acpi0: bus -1 (P0P9) acpiec0 at acpi0 acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: PWRB acpiac0 at acpi0: AC unit offline acpibat0 at acpi0: BAT1 not present acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD02 mpbios0 at bios0: Intel MP Specification 1.4 cpu0 at mainbus0: apid 0 (boot processor) cpu0: Genuine Intel(R) CPU U4100 @ 1.30GHz, 1296.99 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,NXE,LONG,LAHF,PERF cpu0: 2MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Genuine Intel(R) CPU U4100 @ 1.30GHz, 1296.76 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,NXE,LONG,LAHF,PERF cpu1: 2MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 mpbios0: bus 0 is type PCI mpbios0: bus 1 is type PCI mpbios0: bus 2 is type PCI mpbios0: bus 3 is type PCI mpbios0: bus 4 is type PCI mpbios0: bus 5 is type ISA ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins cpu0: unknown Enhanced SpeedStep CPU, msr 0x060f461506004615 cpu0: using only highest and lowest power states cpu0: Enhanced SpeedStep 1296 MHz: speeds: 14000, 1200 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07 vga1 at pci0 dev 2 function 0 Intel GM45 Video rev 0x07 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1366x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel GM45 Video rev 0x07 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 2 int 16 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 2 int 21 uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 2 int 19 ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 2 int 18 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801I HD Audio rev 0x03: msi azalia0: codecs: Realtek ALC269, Intel/0x2802, using Realtek ALC269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x03: msi pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 Intel 82801I PCIE rev 0x03: msi pci2 at ppb1 bus 3 athn0 at pci2 dev 0 function 0 Atheros AR9285 rev 0x01: apic 2 int 17 athn0: AR9285 rev 2 (1T1R), ROM rev 14, address 78:e4:00:5d:44:95 ppb2 at pci0 dev 28 function 3 Intel 82801I PCIE rev 0x03: msi pci3 at ppb2 bus 4 alc0 at pci3 dev 0 function 0 Attansic Technology
Re: hibernate fails to restore on i386
On Thu, May 29, 2014 at 11:51:07PM -0400, Josh Grosse wrote: I use ZZZ rarely, so I have no clue when the regression -- if it is a regression -- began. Clue sticks welcome, as well a guidance for producing more useful diagnostics. Symptom: ZZZ apparently saves and shuts down. On reboot, it appears to unpack the image, then abandon the image and reboot. I've got a couple of diffs pending for corruption during unpack during resume. I hope to get those in in the next few days. The DEBUG kernel used here adds -g and HIB_DEBUG to GENERIC.MP: --- --- GENERIC.MPFri Dec 26 12:10:45 2008 +++ DEBUG Thu May 29 23:12:18 2014 @@ -6,5 +6,7 @@ include arch/i386/conf/GENERIC option MULTIPROCESSOR # Multiple processor support +makeoptions DEBUG=-g +option HIB_DEBUG cpu* at mainbus? --- I added -Wno-error to brute force past formatting errors for a DPRINT in kern/subr_hibernate.c at line 1011 where %p fails to manage paddr_t. I fixed the format specifier. Thanks. This kernel is sufficiently up-to-date to include today's r 1.91 of kern/subr_hibernate. --- OpenBSD 5.5-current (DEBUG) #5: Thu May 29 23:30:50 EDT 2014 j...@netbook.jggimi.homeip.net:/usr/src/sys/arch/i386/compile/DEBUG cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF real mem = 1064464384 (1015MB) avail mem = 1034600448 (986MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 04/18/11, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0xf0720 (30 entries) bios0: vendor American Megatrends Inc. version 1601 date 04/18/2011 bios0: ASUSTeK Computer INC. 1005HA acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT acpi0: wakeup devices P0P2(S4) P0P1(S4) HDAC(S4) P0P4(S4) P0P8(S4) P0P5(S4) P0P7(S4) P0P9(S4) P0P6(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 133MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 1, remapped to apid 2 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (P0P5) acpiprt2 at acpi0: bus 1 (P0P7) acpiprt3 at acpi0: bus -1 (P0P6) acpiec0 at acpi0 acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpitz0 at acpi0: critical temperature is 88 degC acpibat0 at acpi0: BAT0 model 1005HA serial type LION oem ASUS acpiac0 at acpi0: AC unit online acpiasus0 at acpi0 acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: PWRB bios0: ROM list: 0xc/0xec00! cpu0: Enhanced SpeedStep 1600 MHz: speeds: 1600, 1333, 1067, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82945GME Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GME Video rev 0x03 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x600 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: msi azalia0: codecs: Realtek ALC269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 2 int 16 pci1 at ppb0 bus 4 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 2 int 17 pci2 at ppb1 bus 2 athn0 at pci2 dev 0 function 0 Atheros AR9285 rev 0x01: apic 2 int 17 athn0: AR9285 rev 2 (1T1R), ROM rev 13, address 00:25:d3:8a:f6:b4 ppb2 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x02: apic 2 int 19 pci3 at ppb2 bus 1 alc0 at pci3 dev 0 function 0 Attansic Technology L2C rev 0xc0: msi, address 90:e6:ba:37:cf:5e atphy0 at alc0 phy 0: F1 10/100/1000 PHY, rev. 11 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 2 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 2 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: apic 2 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02:
Re: CPU power consumption on thinkpad x201 on openbsd current
On Thu, Jun 05, 2014 at 10:53:38AM +0200, Johan Svensson wrote: On 06/05/14 00:53, STeve Andre' wrote: On 06/04/14 17:08, Johan Svensson wrote: I'm trying to migrate from Linux to Openbsd on my laptop (thinkpad x201). The first problem that i came across was that the Cpu fanspeed was running constantly at 3500RPM. After the acpithinkpad.c patch from jcs (and i modified to make it work on the openbsd-current(link: http://exclude.se/patch/jcs_mod_by_js.diff) Another thing that i noticed is that the battery lifetime is really bad. In Linux i get around ~5,5 hours. In OpenBSD i get around 2 hours. when i ran : sysctl hw.sensors | grep -i consumption. the output of the cpu was 6W. in Linux it's around 1,5W. with: apmd -C and apmd -L it's the same. dmesg: http://exclude.se/openbsd/dmesg.txt Is there anyway to fix this? Regards Johan Svensson Take a look at hw.setperf in sysctl. I think you are running at the maximum cpu speed? On my 2.8GHz W500 I can run at 800, 1600, 2133 and 2801. 800MHz makes a huge difference. You have to try different values for setperf to see what happens. sysctl will also tell you the speed in hw.cpuspeed. --STeve Andre' This my output from sysctl and apm when running on the lowest clockspeed: # sysctl hw | grep -iE cpuspeed|setperf|fan|consumption hw.sensors.acpithinkpad0.fan0=1959 RPM hw.sensors.itherm0.power0=6.00 W (CPU power consumption) hw.cpuspeed=1199 hw.setperf=0 # apm Battery state: high, 70% remaining, 111 minutes life estimate A/C adapter state: not connected Performance adjustment mode: manual (1199 MHz) This is the output when i use apm -H: # sysctl hw | grep -iE cpuspeed|setperf|fan|consumption hw.sensors.acpithinkpad0.fan0=1972 RPM hw.sensors.itherm0.power0=6.00 W (CPU power consumption) hw.cpuspeed=2666 hw.setperf=100 # apm Battery state: high, 68% remaining, 107 minutes life estimate A/C adapter state: not connected Performance adjustment mode: manual (2666 MHz) The energy consumption is the same which is odd. --Johan This may be a bug in itherm(4), I'll take a look.
Re: Very slow I/O under OpenBSD i386 on qemu-kvm from RHEL7rc
On Tue, Jun 17, 2014 at 05:10:51AM -0400, Brad Smith wrote: On 17/06/14 4:56 AM, Mikolaj Kucharski wrote: On Mon, Jun 16, 2014 at 11:07:39PM +0100, Kevin Chadwick wrote: previously on this list Mikolaj Kucharski contributed: by disabling mpbios on OpenBSD and falling back to the old pic controller, in this case you I cannot find how to enable 'the old pic controller' in libvirt with qemu-kvm. Do you know by any chance how to enable it? I believe he means disabling mpbios at OpenBSD's boot or in boot.conf means KVM will automatically fall back. Virtual hosting companies like arpnetworks generally ask you to do this for OpenBSD. boot -c disable mpbios Ah, I got confused. Yes, I'm aware of this, as I've seen this on the list archives mentioned few times. I actually tested this, and I don't see any difference. See at my below tests: Because ACPI is in use which takes higher precedence over MP BIOS. You have to disable acpimadt. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Randomly disabling parts of the kernel is likely to cause other problems. -ml
Re: Very slow I/O under OpenBSD i386 on qemu-kvm from RHEL7rc
On Tue, Jun 17, 2014 at 07:47:32PM +0100, Mikolaj Kucharski wrote: Mike, On Tue, Jun 17, 2014 at 10:30:23AM -0700, Mike Larkin wrote: On Tue, Jun 17, 2014 at 05:10:51AM -0400, Brad Smith wrote: Because ACPI is in use which takes higher precedence over MP BIOS. You have to disable acpimadt. Randomly disabling parts of the kernel is likely to cause other problems. I agree, but disabling mpbios and acpimadt makes a huge difference for me on qemu-kvm-1.5.3-60.el7.x86_64: Please don't bother filing any bug reports for a system where you've done this. -ml OpenBSD i386/virtio (bsd.sp disable mpbios and acpimadt) # time dd if=/dev/zero of=/tmp/TEST bs=4096 count=1024x1024 1048576+0 records in 1048576+0 records out 4294967296 bytes transferred in 18.524 secs (231854084 bytes/sec) 0m18.52s real 0m0.24s user 0m14.48s system It takes now 18 seconds to run above dd(1), when previously it took 60 mintues. Thanks Christiano and Brad for the tips. Do you guys think it's worth opening bug report with RedHat to get them look into this, or is the problem more on OpenBSD side? Ideally I would like to run unmodified OpenBSD kernel on my VMs. $ diff -I'^iic0' dmesg.txt disable-mpbios-and-acpimadt.txt --- dmesg.txt Sat Jun 14 15:49:02 2014 +++ disable-mpbios-and-acpimadt.txt Tue Jun 17 13:30:46 2014 @@ -4,6 +4,13 @@ cpu0: FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,NXE,LONG,SSE3,CX16,LAHF,ABM,SSE4A,PERF real mem = 536367104 (511MB) avail mem = 515158016 (491MB) +User Kernel Config +UKC disable mpbios +368 mpbios0 disabled +UKC disable acpimadt +501 acpimadt0 disabled +UKC quit +Continuing... mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root @@ -15,22 +22,20 @@ acpi0: tables DSDT FACP SSDT APIC RSDT acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits -acpimadt0 at acpi0 addr 0xfee0: PC-AT compat -cpu0 at mainbus0: apid 0 (boot processor) -mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges -cpu0: apic clock running at 999MHz -ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0 +mpbios at bios0 function 0x0 not configured bios0: ROM list: 0xc/0x1000! 0xc1000/0xa00 0xc2000/0x2400 0xed800/0x2800! +cpu0 at mainbus0: (uniprocessor) +mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82441FX rev 0x02 pcib0 at pci0 dev 1 function 0 Intel 82371SB ISA rev 0x00 pciide0 at pci0 dev 1 function 1 Intel 82371SB IDE rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility pciide0: channel 0 disabled (no drives) pciide0: channel 1 disabled (no drives) -uhci0 at pci0 dev 1 function 2 Intel 82371SB USB rev 0x01: apic 0 int 11 -piixpm0 at pci0 dev 1 function 3 Intel 82371AB Power rev 0x03: apic 0 int 9 +uhci0 at pci0 dev 1 function 2 Intel 82371SB USB rev 0x01: irq 11 +piixpm0 at pci0 dev 1 function 3 Intel 82371AB Power rev 0x03: irq 9 iic0 at piixpm0 iic0: addr 0x1c 0f=00 words 00=d4d0 01=d4d0 02=d4d0 03=d4d0 04=d4d0 05=d4d0 06=d4d0 07=d4d0 iic0: addr 0x1d 0f=00 words 00=d4d0 01=d4d0 02=d4d0 03=d4d0 04=d4d0 05=d4d0 06=d4d0 07=d4d0 @@ -39,13 +44,13 @@ iic0: addr 0x4e 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00 3e=d1 48=d1 4a=d1 4e=d1 fc=d1 fe=d1 words 00=9d87 01=9d87 02=9d87 03=9d87 04=9d87 05=9d87 06=9d87 07=9d87 virtio0 at pci0 dev 3 function 0 Qumranet Virtio Network rev 0x00: Virtio Network Device vio0 at virtio0: address 52:54:00:12:34:70 -virtio0: apic 0 int 11 +virtio0: irq 11 virtio1 at pci0 dev 4 function 0 Qumranet Virtio Storage rev 0x00: Virtio Block Device vioblk0 at virtio1 scsibus1 at vioblk0: 2 targets sd0 at scsibus1 targ 0 lun 0: VirtIO, Block Device, SCSI3 0/direct fixed sd0: 102400MB, 512 bytes/sector, 209715200 sectors -virtio1: apic 0 int 11 +virtio1: irq 11 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo -- best regards q#
Re: kernel panic from sys/dev/acpi/dsdt.c rev1.210 change
On Fri, Jun 27, 2014 at 01:15:59PM -0600, Theo de Raadt wrote: On 2014-06-26, Scott Vanderbilt li...@datagenic.com wrote: Having done a little man page reading on boot-time configuration, I learned about the existence of ukc. I'm wondering whether something like ukc disable acpi0 might circumvent the kernel panic and allow the boot to successfully complete. I'm hoping that since this is a server, ACPI is non-essential. Just grasping at straws in an effort to get this machine up and running again. I think you should consider ACPI essential on pretty much any x86 machine from the last 4-5 years or so - servers, laptops, standard PCs. Yes, ACPI is essential. It is the modern way to interface to the hardware; it is the modern BIOS API. The other BIOS interfaces (MPBIOS and PCIBIOS) are totally unreliable and rotting on most machines these days. The vendors include support, but they do not verify their correctness. In an emergency such as this you might get away with it briefly, but some devices are likely not to work, and it's not recommended leaving it like that for any length of time, ACPI is involved in a lot of system controls (thermal controls, power etc) and most modern machines are just not designed/tested to work without it. Stuart is correct. Those of you turning off ACPI are relying on an interface model we have repeatedly described as broken. I have some hardware that doesn't work. Should I just disable mainbus? That way it doesn't attach. Maybe that would fix the problem. -ml
Re: kernel panic from sys/dev/acpi/dsdt.c rev1.210 change
On Fri, Jun 27, 2014 at 12:37:33PM -0700, Scott Vanderbilt wrote: On 6/27/2014 12:10 PM, Stuart Henderson wrote: On 2014-06-26, Scott Vanderbilt li...@datagenic.com wrote: Having done a little man page reading on boot-time configuration, I learned about the existence of ukc. I'm wondering whether something like ukc disable acpi0 might circumvent the kernel panic and allow the boot to successfully complete. I'm hoping that since this is a server, ACPI is non-essential. Just grasping at straws in an effort to get this machine up and running again. I think you should consider ACPI essential on pretty much any x86 machine from the last 4-5 years or so - servers, laptops, standard PCs. In an emergency such as this you might get away with it briefly, but some devices are likely not to work, and it's not recommended leaving it like that for any length of time, ACPI is involved in a lot of system controls (thermal controls, power etc) and most modern machines are just not designed/tested to work without it. Thanks for clarifying. Disabling acpi was only meant to be a stopgap measure so I could get around the assertion in the kernel that caused a panic on boot. Once I was able to boot the machine, I upgraded to a later snapshot in which the assertion was removed. I never intended to permanently disable acpi. As the machine was at a remote co-lo, I felt had no other choice. Is there some better way that I should have handled this situation? Keep another kernel in / that is known working. -ml
Re: zzz, /dev/wsmouse1: read error Input/output error
On Sun, Jul 13, 2014 at 06:22:34PM -0400, Mike Burns wrote: Thinkpad X1 Carbon with a touchscreen, running 5.5-stable. When I resume from suspend my Xorg.0.log is flooded with: (EE) ws: /dev/wsmouse1: read error Input/output error In my dmesg: wsmouse1: can't attach mux (error=5) Are you using wsmoused? -ml Attached are four files: the dmesg before zzz, Xorg.0.log before zzz, dmesg added after zzz, Xorg.0.log added after zzz. Is this fixed on -current? Is there a workaround? Something I need to configure? More information needed? -Mike OpenBSD 5.5-stable (GENERIC.MP) #0: Sat Jul 12 23:07:41 CEST 2014 m...@bellifortis.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8255762432 (7873MB) avail mem = 8027381760 (7655MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9d000 (71 entries) bios0: vendor LENOVO version G6ET93WW (2.53 ) date 02/04/2013 bios0: LENOVO 3444CUU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! UEFI UEFI MSDM SSDT SSDT UEFI SSDT DBG2 acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz, 1896.04 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz, 1895.70 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz, 1895.70 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz, 1895.70 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpicpu2 at acpi0: C2, C1, PSS acpicpu3 at acpi0: C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1, EHC2 acpitz0 at acpi0: critical temperature is 200 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 45N1071 serial 1475 type LiP oem SMP acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 cpu0: Enhanced SpeedStep 1896 MHz: speeds: 2001, 2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core 3G Host rev 0x09 vga1 at pci0 dev 2 function 0 Intel HD Graphics 4000 rev 0x09 intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1600x900 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 7 Series xHCI rev 0x04 at pci0 dev 20 function 0 not configured Intel 7 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured puc0 at pci0 dev 22 function 3 Intel 7 Series KT rev 0x04: ports: 1 com com4 at puc0 port 0 apic 2 int 19: ns16550a, 16 byte fifo com4: probed fifo depth: 0 bytes ehci0 at
Re: ACPI0 Interrupts and System Time
On Wed, Jul 16, 2014 at 08:55:15AM -0500, Josh Hoppes wrote: Hello, I've got a few machines I'm setting up which I noticed ACPI0 is generating a lot of constant interrupts which appears to be consuming system time on CPU0 up to 80%. I think other interrupts are still getting time to process, but I'm not sure if it could still cause a performance impact as I'm looking to use these systems to handle filtering and queuing on the edge of our network. Any ideas or suggestions would be appreciated. The systems are Dell R620, dmesg below. We saw (and kettenis@ fixed) a similar issue on this machine in late June. Can you please try a snap from a later date? I'd say at least July 1 or later. -ml OpenBSD 5.5-stable (GENERIC.MP) #3: Sun May 11 18:30:30 CDT 2014 r...@build.kncm.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34295709696 (32706MB) avail mem = 33374154752 (31828MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xcf42c000 (99 entries) bios0: vendor Dell Inc. version 2.2.2 date 01/16/2014 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpi0: wakeup devices PCI0(S5) PCI1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 3, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 16 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 8, package 0 cpu4 at mainbus0: apid 18 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 9, package 0 cpu5 at mainbus0: apid 20 (application processor) cpu5: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 0, core 10, package 0 cpu6 at mainbus0: apid 5 (application processor) cpu6: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu6: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu6: 256KB 64b/line 8-way L2 cache cpu6: smt 1, core 2, package 0 cpu7 at mainbus0: apid
Re: ACPI0 Interrupts and System Time
On Wed, Jul 16, 2014 at 11:36:21AM -0500, Josh Hoppes wrote: Would there happen to be any pre-built snapshots that are known good? This is a short term event and I don't a lot of time to work since doors open tomorrow morning. Was the fix kernel only and would that work with my existing userland or has there been a significant enough change that I would need to do a full upgrade? Thanks for the help so far! The change was just in the kernel, but unless you wanted to go and pull out that one patch and apply it to an older tree, you might be better off installing a complete snap. I've been told there are older snaps kept here: http://ftp.hostserver.de/archive I'd grab one from between 26 Jun and 6 July. Much later than 6 July and you run the risk of running into the hackathon commits, which sometimes destabilize the tree for a short time. The pair of commits I think you may need were made on 23 Jul and 25 Jul (the 23 Jul diff being the more relevant one for your issue). -ml On Wed, Jul 16, 2014 at 11:04 AM, Mike Larkin mlar...@azathoth.net wrote: On Wed, Jul 16, 2014 at 08:55:15AM -0500, Josh Hoppes wrote: Hello, I've got a few machines I'm setting up which I noticed ACPI0 is generating a lot of constant interrupts which appears to be consuming system time on CPU0 up to 80%. I think other interrupts are still getting time to process, but I'm not sure if it could still cause a performance impact as I'm looking to use these systems to handle filtering and queuing on the edge of our network. Any ideas or suggestions would be appreciated. The systems are Dell R620, dmesg below. We saw (and kettenis@ fixed) a similar issue on this machine in late June. Can you please try a snap from a later date? I'd say at least July 1 or later. -ml OpenBSD 5.5-stable (GENERIC.MP) #3: Sun May 11 18:30:30 CDT 2014 r...@build.kncm.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34295709696 (32706MB) avail mem = 33374154752 (31828MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xcf42c000 (99 entries) bios0: vendor Dell Inc. version 2.2.2 date 01/16/2014 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpi0: wakeup devices PCI0(S5) PCI1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 3, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 16 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 8, package 0 cpu4 at mainbus0: apid 18 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES
Re: ACPI0 Interrupts and System Time
On Wed, Jul 16, 2014 at 09:51:12AM -0700, Mike Larkin wrote: On Wed, Jul 16, 2014 at 11:36:21AM -0500, Josh Hoppes wrote: Would there happen to be any pre-built snapshots that are known good? This is a short term event and I don't a lot of time to work since doors open tomorrow morning. Was the fix kernel only and would that work with my existing userland or has there been a significant enough change that I would need to do a full upgrade? Thanks for the help so far! The change was just in the kernel, but unless you wanted to go and pull out that one patch and apply it to an older tree, you might be better off installing a complete snap. I've been told there are older snaps kept here: http://ftp.hostserver.de/archive I'd grab one from between 26 Jun and 6 July. Much later than 6 July and you run the risk of running into the hackathon commits, which sometimes destabilize the tree for a short time. The pair of commits I think you may need were made on 23 Jul and 25 Jul (the 23 Jul diff being the more relevant one for your issue). Should have been 23 Jun and 25 Jun there ... -ml On Wed, Jul 16, 2014 at 11:04 AM, Mike Larkin mlar...@azathoth.net wrote: On Wed, Jul 16, 2014 at 08:55:15AM -0500, Josh Hoppes wrote: Hello, I've got a few machines I'm setting up which I noticed ACPI0 is generating a lot of constant interrupts which appears to be consuming system time on CPU0 up to 80%. I think other interrupts are still getting time to process, but I'm not sure if it could still cause a performance impact as I'm looking to use these systems to handle filtering and queuing on the edge of our network. Any ideas or suggestions would be appreciated. The systems are Dell R620, dmesg below. We saw (and kettenis@ fixed) a similar issue on this machine in late June. Can you please try a snap from a later date? I'd say at least July 1 or later. -ml OpenBSD 5.5-stable (GENERIC.MP) #3: Sun May 11 18:30:30 CDT 2014 r...@build.kncm.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34295709696 (32706MB) avail mem = 33374154752 (31828MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xcf42c000 (99 entries) bios0: vendor Dell Inc. version 2.2.2 date 01/16/2014 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpi0: wakeup devices PCI0(S5) PCI1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 4 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.45 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 2, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 6 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 3, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 16 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 8, package 0 cpu4 at mainbus0: apid 18 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2643 v2 @ 3.50GHz, 3500.01 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC
Re: Immediately resumes after hibernate
On Tue, Jul 29, 2014 at 10:14:40AM -0400, Elijah Buck wrote: I have a whitebox desktop with a Biostar TH55B HD motherboard. Hibernate (via ZZZ) works great, as does resume. However, when hibernating, the system briefly powers off and then immediately starts back up. The issue occurs both on 5.5 amd64 and 5.6-beta (Jul 27) amd64. I tried setting the BIOS to use ACPI v1.0, v2.0, v3.0 with no effect. I tried removing usb devices, in case they were waking the system. Hibernate in Windows 8.1 works. What might the problem be? I've got a machine with the same symptoms with very similar hardware. It doesn't fire any GPEs on resume, and the fixed function buttons aren't set either. So the reason for resume is still a mystery. 1. Please send an acpidump. 2. In dev/acpi/acpi.c, try commenting out the following line: acpi_enable_wakegpes(sc, state); ... in my tree that's on line 2157. Note there are two occurrences of that line of code, you want to comment out the one in acpi_sleep_state and not acpi_powerdown. Then rebuild/reinstall the kernel and see if ZZZ works - that change will disable the wake devices -ml Thanks, Elijah dmesg below (for the snapshot I am now running): OpenBSD 5.6-beta (GENERIC.MP) #305: Sun Jul 27 19:02:25 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8530690048 (8135MB) avail mem = 8294817792 (7910MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xfc620 (66 entries) bios0: vendor American Megatrends Inc. version 080015 date 10/15/2010 bios0: BIOSTAR Group TH55B HD acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB SSDT acpi0: wakeup devices P0P1(S4) P0P3(S4) P0P4(S4) P0P5(S4) P0P6(S4) BR1E(S4) UAR1(S4) PS2K(S4) PS2M(S4) EUSB(S4) USB0(S4) USB1(S4) USB2(S4) USB3(S4) USBE(S4) USB4(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz, 2745.42 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 137MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.0, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz, 2745.04 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz, 2745.04 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz, 2745.04 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,NXE,LONG,LAHF,PERF,ITSC cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 7 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 1, remapped to apid 7 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P4) acpiprt2 at acpi0: bus 5 (BR1E) acpiprt3 at acpi0: bus 2 (BR20) acpiprt4 at acpi0: bus -1 (BR22) acpiprt5 at acpi0: bus -1 (BR23) acpiprt6 at acpi0: bus 3 (BR24) acpiprt7 at acpi0: bus 4 (BR25) acpiprt8 at acpi0: bus -1 (BR26) acpiprt9 at acpi0: bus -1 (BR27) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpicpu2 at acpi0: C3, C2, C1, PSS acpicpu3 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0: critical temperature is 85 degC acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB cpu0: Enhanced SpeedStep 2745 MHz: speeds: 2668, 2667, 2533, 2400, 2267, 2133, 2000, 1867, 1733, 1600, 1467, 1333, 1200 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core DMI rev 0x11 ppb0 at pci0 dev 3 function 0 Intel Core PCIE rev 0x11 pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 ATI Radeon HD 5750 rev 0x00 drm0 at radeondrm0 radeondrm0: msi azalia0 at pci1 dev 0 function 1 ATI Radeon HD 5700
Re: Immediately resumes after hibernate
On Wed, Jul 30, 2014 at 11:07:27AM -0400, Elijah Buck wrote: On Wed, Jul 30, 2014 at 01:26:06AM -0700, Mike Larkin wrote: I've got a machine with the same symptoms with very similar hardware. It doesn't fire any GPEs on resume, and the fixed function buttons aren't set either. So the reason for resume is still a mystery. 1. Please send an acpidump. 2. In dev/acpi/acpi.c, try commenting out the following line: acpi_enable_wakegpes(sc, state); ... in my tree that's on line 2157. Note there are two occurrences of that line of code, you want to comment out the one in acpi_sleep_state and not acpi_powerdown. Then rebuild/reinstall the kernel and see if ZZZ works - that change will disable the wake devices -ml The change to dev/acpi/acpi.c works perfectly. That's good news, but unfortunately it's just a diagnostic tool to indicate what I already suspected - a GPE is firing, but it's still unknown which one. The spec is a little unclear here (gee, what a surprise). It only says that the implementation must provide a way for OSPM to determine the GPE that fired to wake the machine up. But it doesn't say what that way is. A few weeks ago I cooked up a diff to read the GPE status right on wake (from S3) and on the machines I have that immediately wake from S3, it didn't show any GPE as signaled. We can't use the same approach on wake from S4 because of all the other stuff that happens before we can read the GPE registers. The change I recommended can't be committed as is. But it does help point things in the right direction. I'll take a look at the AML and see if I can see a suspect GPE. -ml I am attaching a tar of the apcidump output (which will of course be stripped by the list). Let me know if there's another way you'd like me to send it. Thanks, Elijah [demime 1.01d removed an attachment of type application/x-tar]
Re: Immediately resumes after hibernate
On Thu, Jul 31, 2014 at 10:10:59AM -0400, Elijah Buck wrote:
On Wed, Jul 30, 2014 at 12:29:00PM -0700, Mike Larkin wrote:
That's good news, but unfortunately it's just a diagnostic tool to indicate
what I already suspected - a GPE is firing, but it's still unknown which
one.
So, I modified the conditional in acpi_enable_wakegpes in acpi.c to exclude
sets of wakeup devices. Eventually I landed on:
void
acpi_enable_wakegpes(struct acpi_softc *sc, int state)
{
struct acpi_wakeq *wentry;
SIMPLEQ_FOREACH(wentry, sc-sc_wakedevs, q_next) {
dnprintf(10, %.4s(S%d) gpe %.2x\n, wentry-q_node-name,
wentry-q_state,
wentry-q_gpe);
if ((state = wentry-q_state)
(strncmp(SLPB, wentry-q_node-name, 4) != 0))
acpi_enable_onegpe(sc, wentry-q_gpe);
}
}
What is SLPB? I'll try to find out for myself, but just wanted to share
my progress.
Elijah
Sleep Button most likely. But you'd need to look at the AML to be sure.
Do you have a sleep button on the case or keyboard?
-ml
Re: Access Point Section of the faq
On Fri, Aug 01, 2014 at 07:47:51PM +0100, Kevin Chadwick wrote: I wonder if a short list of access mode capable devices or chipsets that are known to work well for atleast 24 hours or maybe 60 days would be a good addition to the access point section of the faq (6.13) especially with OpenBSD being such a good system to use as an access point. In the mailing lists sthen suggests pci atheros are more stable so perhaps a couple of those device names could go in and then whatever particular chipsets or even driver type that is thought most reliable in hostap mode could go in too? For example I was considering trying a rum driver and was completely unsure about it despite some mailing list searches and then read the man page caveat section and so won't. I guess atheros was right but I should look into a card type or another chipset. I'm sure many use wireless a lot more than me so if you've had a reliable experience with OpenBSD as an wpa2 access point then perhaps you could list it here or look up your devices chipset at https://wikidevi.com/wiki/Main_Page and list that. Cheers, Kc -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) In Other Words - Don't design like polkit or systemd ___ I have been using this: athn0 at pci7 dev 0 function 0 Atheros AR5418 rev 0x01: apic 0 int 17 athn0: MAC AR5418 rev 2, RF AR5133 (2T3R), ROM rev 8 ... in hostap mode for over a year and a half without any issues. And yes, it's doing WPA2. I know other people have said that hostap mode is not stable but on this machine it's been rock solid. It's a mini pcie card inside a soekris 6501. -ml
Re: acpi error running openbsd snapshot 20140820 (amd64)
On Wed, Aug 20, 2014 at 12:34:24PM +0400, Wesley MOUEDINE ASSABY wrote: Hi, Running the install56.fs from an usb key give me the following error : http://pbrd.co/1rWT1Us So i disabled acpi using UKC to be able to install : http://pbrd.co/1rWUqL0 OpenBSD is installed now, but running it with acpi support give me a kernel panic : http://pbrd.co/1rWTCFX trace : http://pbrd.co/1rWTKVS http://pbrd.co/1rWTUws and ps : http://pbrd.co/1rWU1bl So you expect us to help you when: 1. You've been randomly disabling code in the kernel. 2. You're claiming the bug is somehow related to acpi and yet you've provided us with no acpidump. What would your mechanic say if you took your car to the garage and said My engine is making a strange sound, but I'm not going to tell you what sound it's making. By the way, I've unplugged some random wires somewhere in the engine compartment. -ml Below, dmesg without acpi support : OpenBSD 5.6-current (GENERIC.MP) #336: Tue Aug 19 20:39:19 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1996161024 (1903MB) avail mem = 1934336000 (1844MB) User Kernel Config UKC disable acpi 358 acpi0 disabled UKC quit Continuing... mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xfced0 (28 entries) bios0: vendor American Megatrends Inc. version P1.60 date 06/12/2007 acpi at bios0 not configured mpbios0 at bios0: Intel MP Specification 1.4 cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 4800+, 2411.13 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) 64 X2 Dual Core Processor 4800+, 2410.78 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mpbios0: bus 0 is type PCI mpbios0: bus 1 is type PCI mpbios0: bus 2 is type PCI mpbios0: bus 3 is type PCI mpbios0: bus 4 is type PCI mpbios0: bus 5 is type ISA ioapic0 at mainbus0: apid 2 pa 0xfec0, version 11, 24 pins cpu0: PowerNow! K8 2411 MHz: speeds: 2500 2400 2200 2000 1800 1000 MHz pci0 at mainbus0 bus 0 NVIDIA MCP61 Memory rev 0xa1 at pci0 dev 0 function 0 not configured pcib0 at pci0 dev 1 function 0 NVIDIA MCP61 ISA rev 0xa2 nviic0 at pci0 dev 1 function 1 NVIDIA MCP61 SMBus rev 0xa2 iic0 at nviic0 iic0: addr 0x4c 00=28 01=2f 02=80 03=01 04=06 05=46 06=00 07=46 08=00 10=60 11=00 12=00 13=00 14=00 19=6e 20=55 21=0a bf=06 e0=bb e1=c0 e2=82 e3=bb e4=c0 e5=2f e6=29 e7=68 e8=82 eb=4f ec=02 f1=20 f2=00 f3=10 f4=80 f5=00 f7=00 f8=00 f9=02 fa=00 fb=4c fc=4f fd=37 fe=5c ff=01 words 00=29ff 01=2fff 02=80ff 03=01ff 04=06ff 05=46ff 06=00ff 07=46ff spdmem0 at iic0 addr 0x51: 2GB DDR2 SDRAM non-parity PC2-6400CL5 iic1 at nviic0 NVIDIA MCP61 Memory rev 0xa2 at pci0 dev 1 function 2 not configured ohci0 at pci0 dev 2 function 0 NVIDIA MCP61 USB rev 0xa2: apic 2 int 5, version 1.0, legacy support ehci0 at pci0 dev 2 function 1 NVIDIA MCP61 USB rev 0xa2: apic 2 int 10 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 ppb0 at pci0 dev 4 function 0 NVIDIA MCP61 rev 0xa1 pci1 at ppb0 bus 1 rl0 at pci1 dev 8 function 0 Realtek 8139 rev 0x10: apic 2 int 11, address 00:50:fc:47:20:a0 rlphy0 at rl0 phy 0: RTL internal PHY rl1 at pci1 dev 10 function 0 Realtek 8139 rev 0x10: apic 2 int 5, address 00:50:bf:93:3f:78 rlphy1 at rl1 phy 0: RTL internal PHY azalia0 at pci0 dev 5 function 0 NVIDIA MCP61 HD Audio rev 0xa2: apic 2 int 11 azalia0: codecs: Realtek ALC888 audio0 at azalia0 pciide0 at pci0 dev 6 function 0 NVIDIA MCP61 IDE rev 0xa2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) pciide0: channel 1 ignored (disabled) nfe0 at pci0 dev 7 function 0 NVIDIA MCP61 LAN rev 0xa2: apic 2 int 10, address 00:19:66:3a:de:a4 rlphy2 at nfe0 phy 1: RTL8201L 10/100 PHY, rev. 1 pciide1 at pci0 dev 8 function 0 NVIDIA MCP61 SATA rev 0xa2: DMA pciide1: using apic 2 int 10 for native-PCI interrupt wd0
Re: acpi error running openbsd snapshot 20140820 (amd64)
On Wed, Aug 20, 2014 at 07:47:57PM +0400, Wesley MOUEDINE ASSABY wrote: On 20.08.2014 19:27, Mike Larkin wrote: On Wed, Aug 20, 2014 at 12:34:24PM +0400, Wesley MOUEDINE ASSABY wrote: Hi, Running the install56.fs from an usb key give me the following error : http://pbrd.co/1rWT1Us So i disabled acpi using UKC to be able to install : http://pbrd.co/1rWUqL0 OpenBSD is installed now, but running it with acpi support give me a kernel panic : http://pbrd.co/1rWTCFX trace : http://pbrd.co/1rWTKVS http://pbrd.co/1rWTUws and ps : http://pbrd.co/1rWU1bl So you expect us to help you when: 1. You've been randomly disabling code in the kernel. I can't install it with acpi support as i mentioned. The error with acpi at install process : Running the install56.fs from an usb key give me the following error : http://pbrd.co/1rWT1Us 2. You're claiming the bug is somehow related to acpi and yet you've provided us with no acpidump. If you look the error message : http://pbrd.co/1rWT1Us How can i get the acpidump if there 's no ddb prompt ? :) man acpidump What would your mechanic say if you took your car to the garage and said My engine is making a strange sound, but I'm not going to tell you what sound it's making. By the way, I've unplugged some random wires somewhere in the engine compartment. Criticism is easy :) Asking for help and providing a substandard bug report is easier.
Re: mpd unable to start on recent snapshots
On Wed, Sep 03, 2014 at 10:55:47AM -0500, Nicholas Fleisher wrote: With the two latest snapshots I've installed (Aug 29 and Sep 2, amd64) and the most recent package of mpd (built Aug 30 on my mirror), mpd no longer starts up, either at boot (via pkg_scripts in /etc/rc.conf.local) or manually (/etc/rc.d/mpd start yields mpd(failed)). Attempting to connect with clients results in the following error: Couldn't connect to MPD (host = localhost, port = 6600): Connection refused I've had problems like this when localhost gets redefined (usually by accident via someone updating DNS incorrectly) to something other than 127.0.0.1. Does mpc -h 127.0.0.1 work? -ml I know there have been some recent changes to the /etc infrastructure, but am unsure what has prompted the failure with mpd. I can add that mpd was working fine as recently as the Aug 26 snapshot (amd64), though this was also an older package (built late July, I believe). Anyone else experiencing this problem? Given the simultaneous updating of system and packages, I'm unsure where the source of the problem lies. Any thoughts/suggestions much appreciated. Thanks, Nick (dmesg below) using PIO mode 4, Ultra-DMA mode 6 cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5 ichiic0 at pci0 dev 31 function 3 Intel 6 Series SMBus rev 0x04: apic 2 int 18 iic0 at ichiic0 spdmem0 at iic0 addr 0x51: 2GB DDR3 SDRAM PC3-10600 spdmem1 at iic0 addr 0x53: 2GB DDR3 SDRAM PC3-10600 pciide1 at pci0 dev 31 function 5 Intel 6 Series SATA rev 0x04: DMA, channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide1: using apic 2 int 18 for native-PCI interrupt isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 uhub2 at uhub0 port 1 Intel Rate Matching Hub rev 2.00/0.00 addr 2 umass0 at uhub2 port 2 configuration 1 interface 0 Generic Mass Storage Device rev 2.00/1.00 addr 3 umass0: using SCSI over Bulk-Only scsibus2 at umass0: 2 targets, initiator 0 sd0 at scsibus2 targ 1 lun 0: Generic-, SD/MMC, 1.00 SCSI0 0/direct removable sd1 at scsibus2 targ 1 lun 1: Generic-, Compact Flash, 1.01 SCSI0 0/direct removable sd2 at scsibus2 targ 1 lun 2: Generic-, SM/xD Picture, 1.02 SCSI0 0/direct removable sd3 at scsibus2 targ 1 lun 3: Generic-, MS/MS-Pro, 1.03 SCSI0 0/direct removable uhub3 at uhub1 port 1 Intel Rate Matching Hub rev 2.00/0.00 addr 2 umass1 at uhub3 port 3 configuration 1 interface 0 Seagate Expansion rev 2.10/2.19 addr 3 umass1: using SCSI over Bulk-Only scsibus3 at umass1: 2 targets, initiator 0 sd4 at scsibus3 targ 1 lun 0: Seagate, Expansion, 0219 SCSI4 0/direct fixed sd4: 953869MB, 512 bytes/sector, 1953525167 sectors uhub4 at uhub3 port 4 Standard Microsystems product 0x2514 rev 2.00/b.b3 addr 4 uhidev0 at uhub3 port 5 configuration 1 interface 0 KINESIS FREESTYLE KB800 KB800 Kinesis Freestyle rev 1.10/1.22 addr 5 uhidev0: iclass 3/1 ukbd0 at uhidev0: 8 variable keys, 6 key codes wskbd1 at ukbd0 mux 1 wskbd1: connecting to wsdisplay0 uhidev1 at uhub3 port 5 configuration 1 interface 1 KINESIS FREESTYLE KB800 KB800 Kinesis Freestyle rev 1.10/1.22 addr 5 uhidev1: iclass 3/0, 3 report ids uhid0 at uhidev1 reportid 2: input=1, output=0, feature=0 uhid1 at uhidev1 reportid 3: input=2, output=0, feature=0 uhidev2 at uhub3 port 6 configuration 1 interface 0 Sunplus USB Optical Mouse rev 2.00/0.14 addr 6 uhidev2: iclass 3/1, 2 report ids ums0 at uhidev2 reportid 1: 3 buttons, Z dir wsmouse0 at ums0 mux 0 uhid2 at uhidev2 reportid 2: input=1, output=0, feature=0 vscsi0 at root scsibus4 at vscsi0: 256 targets softraid0 at root scsibus5 at softraid0: 256 targets root on wd0a (e7ded47759faeaf3.a) swap on wd0b dump on wd0b uhub4 detached uhub4 at uhub3 port 4 Standard Microsystems product 0x2514 rev 2.00/b.b3 addr 4 syncing disks... done rebooting... OpenBSD 5.6-current (RAMDISK_CD) #325: Fri Aug 29 17:06:06 MDT 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD RTC BIOS diagnostic error 3fconfig_unit,memory_size,fixed_disk,invalid_time real mem = 4153880576 (3961MB) avail mem = 4037914624 (3850MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf3f40 (80 entries) bios0: vendor Dell Inc. version A05 date 05/28/2011 bios0: Dell Inc. OptiPlex 990 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC TCPA MCFG HPET BOOT SSDT SSDT DMAR SLIC acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz, 3293.06 MHz cpu0:
Re: openbsd 5.5 sometimes trap after wake from suspend (apm -z)
Next time this happens, try to get a picture of 'show registers' in addition to 'trace'. Thanks. -ml On Tue, Sep 16, 2014 at 10:31:13AM +0400, wrote: Hello. Here is trace at ddb: http://i.imgur.com/MoPz405.jpg Help, please! Thanks! Here is dmesg: OpenBSD 5.5 (GENERIC.MP) #262: Wed Mar 5 10:06:29 MST 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.61 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF real mem = 1062436864 (1013MB) avail mem = 1032744960 (984MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 04/14/08, SMBIOS rev. 2.4 @ 0x3f607010 (45 entries) bios0: vendor American Megatrends Inc. version 4.6.3 date 07/16/2008 bios0: MICRO-STAR INTERNATIONAL CO., LTD U-100 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG SLIC SSDT SSDT SSDT acpi0: wakeup devices P0P2(S4) PEGP(S4) USB0(S1) USB1(S1) USB2(S1) USB3(S1) EHCI(S1) MC97(S4) P0P1(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 133MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P2) acpiprt2 at acpi0: bus 1 (P0P4) acpiprt3 at acpi0: bus 2 (P0P5) acpiprt4 at acpi0: bus -1 (P0P6) acpiprt5 at acpi0: bus -1 (P0P7) acpiprt6 at acpi0: bus -1 (P0P8) acpiprt7 at acpi0: bus -1 (P0P9) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0: critical temperature is 100 degC acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT1 model MS-N011 serial type LION oem MSI Corp. acpibtn0 at acpi0: LID0 acpibtn1 at acpi0: PWRB acpibtn2 at acpi0: SLPB acpivideo0 at acpi0: IGD_ acpivout0 at acpivideo0: LCD_ bios0: ROM list: 0xc/0xea00! 0xcf000/0x1000 cpu0: Enhanced SpeedStep 1600 MHz: speeds: 1600, 1333, 1067, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82945GME Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GME Video rev 0x03 intagp0 at vga1 agp0 at intagp0: aperture at 0xc000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 composite sync not supported composite sync not supported inteldrm0: 1024x600 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: msi azalia0: codecs: Realtek ALC888 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 2 int 16 pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 Realtek 8101E rev 0x02: RTL8102E (0x3480), msi, address 00:21:85:52:d5:ea rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 2 int 17 pci2 at ppb1 bus 2 iwn0 at pci2 dev 0 function 0 Intel Wireless WiFi Link 4965 rev 0x61: msi, MIMO 2T3R, MoW2, address 00:13:e8:7a:c3:7d uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 2 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 2 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: apic 2 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 2 int 16 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: apic 2 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb2 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe2 pci3 at ppb2 bus 3 ichpcib0 at pci0 dev 31 function 0 Intel 82801GBM LPC rev 0x02: PM disabled pciide0 at pci0 dev 31 function 2 Intel 82801GBM SATA rev 0x02: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: TOSHIBA MQ01ABD100 wd0: 16-sector PIO, LBA48, 953869MB, 1953525168 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at
Re: Goldman Sachs rescued(?) by Google
On Mon, Sep 22, 2014 at 07:51:36PM +0100, Maurice McCarthy wrote: Goldman says Google has blocked email with leaked client data http://www.reuters.com/article/2014/07/03/us-google-goldman-leak-idUSKBN0F729I20140703 How does this have anything to do at all with OpenBSD?
Re: X dies after suspend to ram
On Thu, Sep 25, 2014 at 12:12:55PM -0400, Ted W. wrote: I have really enjoyed the last few weeks of running OpenBSD on my Thinkpad. Almost everything I need works and or worked right out of the box. The only real issue I've noticed is that when the system returns from suspend and press ctrl-alt-del to restart X either X or SLiM (not sure which) will not come back up. To work around this issue, I switch to TTY2, log in as root and run `/etc/rc.d/slim restart`. I've tried suspending with and without using slock first and the behavior stays the same. Any input on the matter would be appreciated, -- Ted W. t...@xy0.org No dmesg, no help.
Re: X dies after suspend to ram
On Tue, Sep 30, 2014 at 08:14:22AM -0400, Ted W. wrote: On 09/28/14 09:11, Mike Larkin wrote: On Thu, Sep 25, 2014 at 12:12:55PM -0400, Ted W. wrote: I have really enjoyed the last few weeks of running OpenBSD on my Thinkpad. Almost everything I need works and or worked right out of the box. The only real issue I've noticed is that when the system returns from suspend and press ctrl-alt-del to restart X either X or SLiM (not sure which) will not come back up. To work around this issue, I switch to TTY2, log in as root and run `/etc/rc.d/slim restart`. I've tried suspending with and without using slock first and the behavior stays the same. Any input on the matter would be appreciated, -- Ted W. t...@xy0.org No dmesg, no help. Thank you for letting me know. I was not sure what would be helpful information to provide here. I have included the dmesg output below. I have also included Xorg.0.log in case that's helpful. I'm happy to provide any other information that would be useful. That dmesg is no good. Please provide one from a clean boot. The idea is to look at what hardware is on the machine. -ml == # dmesg : bus 6 device 0 cacheline 0x0, lattimer 0xb0 pcmcia0 at cardslot0 pcib0 at pci0 dev 31 function 0 Intel 82801HEM LPC rev 0x03 pciide0 at pci0 dev 31 function 1 Intel 82801HBM IDE rev 0x03: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) pciide0: channel 1 ignored (disabled) ahci0 at pci0 dev 31 function 2 Intel 82801HBM AHCI rev 0x03: msi, AHCI 1.1 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: ATA, ST500LM000-1EJ16, DEM4 SCSI3 0/direct fixed naa.5000c5006a47abd7 sd0: 476940MB, 512 bytes/sector, 976773168 sectors ichiic0 at pci0 dev 31 function 3 Intel 82801H SMBus rev 0x03: apic 1 int 23 iic0 at ichiic0 usb2 at uhci0: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhci1: USB revision 1.0 uhub3 at usb3 Intel UHCI root hub rev 1.00/1.00 addr 1 usb4 at uhci2: USB revision 1.0 uhub4 at usb4 Intel UHCI root hub rev 1.00/1.00 addr 1 usb5 at uhci3: USB revision 1.0 uhub5 at usb5 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 aps0 at isa0 port 0x1600/31 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 ugen0 at uhub2 port 2 STMicroelectronics Biometric Coprocessor rev 1.00/0.01 addr 2 vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets root on sd0a (5d6cdf996da41425.a) swap on sd0b dump on sd0b ugen0 detached ugen0 at uhub2 port 2 STMicroelectronics Biometric Coprocessor rev 1.00/0.01 addr 2 iwn0: fatal firmware error firmware error log: error type = NMI_INTERRUPT_WDG (0x0004) program counter = 0x046C source line = 0x00D0 error data = 0x00020263 branch link = 0x4B0C04C2 interrupt link = 0x06DE4B22 time= 2978746026 driver status: tx ring 0: qid=0 cur=187 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=0 queued=0 tx ring 4: qid=4 cur=26 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=40 802.11 state 4 iwn0: fatal firmware error firmware error log: error type = NMI_INTERRUPT_WDG (0x0004) program counter = 0x046C source line = 0x00D0 error data = 0x00020263 branch link = 0x4B0C04C2 interrupt link = 0x06DE4B22 time= 2503288226 driver status: tx ring 0: qid=0 cur=127 queued=1 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=0 queued=0 tx ring 4: qid=4 cur=225 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0
Re: ThinkPad x131e - backlight brightness hotkeys not working
On Tue, Oct 07, 2014 at 03:22:18PM -0400, Joe Gidi wrote: Hello, I have a ThinkPad x131e (Intel version) that generally works beautifully under OpenBSD. The only quirk I've noticed so far is that the brightness hotkeys (Fn-F8 and Fn-F9) don't work to control the backlight brightness. I am able to adjust the backlight via the xbacklight utility, though. The brightness hotkeys don't trigger keypress events in xev like the audio hotkeys do, so I assume they instead generate ACPI events. It appears that I may need to add some defines to src/sys/dev/acpi/acpithinkpad.c to recognize the proper ACPI events, but I'm not clear on how I determine the right defines to add. Can someone point me in the right direction? Try adding a printf to the big set of case statements in acpithinkpad.c that ends with handled=1; - You'll then see which of the ones in there is being generated (if any). You'd already be seeing the default case printf, that's why I think it's one of those that are all marked as handled without us doing anything. If it's not that, we'll have to dig deeper. -ml Dmesg from a -current snapshot follows, and I'll be happy to make acpidump output available if it's useful. Thanks, -- Joe Gidi j...@entropicblur.com You cannot buy skill. -- Ross Seyfried - OpenBSD 5.6-current (GENERIC.MP) #400: Mon Oct 6 12:51:24 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3987337216 (3802MB) avail mem = 3872477184 (3693MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae3a000 (48 entries) bios0: vendor LENOVO version G8ET98WW (2.58 ) date 07/14/2014 bios0: LENOVO 33671T9 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC TCPA ASF! HPET APIC MCFG FPDT SSDT SSDT UEFI UEFI MSDM UEFI DBG2 acpi0: wakeup devices P0P1(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S4) RP04(S4) PXSX(S4) RP06(S4) PXSX(S4) BLAN(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEG2(S4) PEG3(S4) LID_(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Celeron(R) CPU 1007U @ 1.50GHz, 1496.85 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Celeron(R) CPU 1007U @ 1.50GHz, 1496.60 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 2 (RP01) acpiprt3 at acpi0: bus 3 (RP02) acpiprt4 at acpi0: bus 4 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus 9 (RP06) acpiprt8 at acpi0: bus -1 (RP07) acpiprt9 at acpi0: bus -1 (RP08) acpiprt10 at acpi0: bus -1 (PEG0) acpiprt11 at acpi0: bus -1 (PEG1) acpiprt12 at acpi0: bus -1 (PEG2) acpiprt13 at acpi0: bus -1 (PEG3) acpiec0 at acpi0 acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpitz0 at acpi0: critical temperature is 99 degC acpithinkpad0 at acpi0 acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT1 model 45N1063 serial 5699 type LION oem LGC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PWRB acpibtn2 at acpi0: SLPB cpu0: Enhanced SpeedStep 1496 MHz: speeds: 1500, 1400, 1300, 1200, 1100, 1000, 900, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core 3G Host rev 0x09 vga1 at pci0 dev 2 function 0 Intel HD Graphics 2500 rev 0x09 intagp at vga1 not configured inteldrm0 at vga1 drm0 at inteldrm0 drm: Memory usable by graphics device = 2048M inteldrm0: 1366x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 7 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured ehci0 at pci0 dev 26 function 0 Intel 7 Series USB rev 0x04: apic 2 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 7 Series HD Audio rev 0x04: msi azalia0:
Re: Trying to get suspend to RAM working on an X31
On Fri, Oct 10, 2014 at 10:01:18AM -0700, John Magolske wrote: Hi, I have an X31 ThinkPad on which I've installed OpenBSD. Everything seems to be working fine, with the exception of suspend to RAM. cat /etc/rc.conf.local apmd_flags=-C Upon issuing the `zzz` command, the screen turns off, the machine spins down and the little crescent-moon sleep indicator lights up. But when woken, the screen comes up frozen with lots of vertical stripes. Blind-typing comands into the console has no effect (e.g. `zzz` from a root console then `halt -p` after the awakening attempt). I've tried `zzz` from X as well as from the console, tried `disable acpithinkpad` `disable acpi` (independently from each other) after boot -c, fiddled various settings in the BIOS...but in all cases there is the same frozen screen with vertical stripes. Because I've also had no luck getting suspend to work under Debian (Stable Testing), I'm thinking the issue might be an old graphics card that's no longer supported. I realize this machine is over 10 years old and at some point dev effort must focus on more recent hardware... but I just wanted to check see if there's something else to try that might get suspend working here. Though a pretty meager machine performance-wise by today's standards, from a physicality standpoint the X31 is IMO one of the nicest compact laptops out there. Very nice keyboard (better key action than the X201s I type this) and I like the tall-screen format (the low-res is fine for me with the right bitmap font). And it has enough power for my basic needs (running a shell, tmux, mutt, vim, elinks, ncmpcpp etc). Anyhow, just trying to squeeze some more life out of this ThinkPad. If I can't get suspend to work, maybe I'll look into swapping out the mobo with something lightweight like a Pandaboard... BTW -- this is my first experience with OpenBSD, and I have to say the installation was incredibly straightforward and easy to understand. Really liking what I see so far! Thanks for any suggestions, John boot -c , disable radeondrm (and also disable auto xdm start). See if you can zzz/resume from the console without radeondrm running. That will at least give us a place to start. Another thing you can try is seeing if the machine is in ddb on resume for some reason. Try a few (3 or 4) bo re commands (enter after each). See if the machine reboots, and if so you might have clues in dmesg after reboot. -ml
Re: Zenocara Intel Crestline Graphics
On Sun, Oct 12, 2014 at 09:20:09AM -0700, Raymond Lillard wrote: On 10/12/2014 12:35 AM, Doug Hogan wrote: On Sat, Oct 11, 2014 at 02:13:05PM -0700, Raymond Lillard wrote: I have the opportunity to purchase a Dell laptop with Intel Crestline Graphics hardware. Crestline appears to be marketing speak for: intel GM965/GMA X3100 Can someone advice me as to the likelihood of using the h/w or will I be limitied to the framebuffer? I think Crestline means the GMA X3100 core but not necessarily the GM965. According to Intel's ARK, it could be GM965, GME965, GL960 or GLE960. In practice, I don't think it will matter. http://ark.intel.com/products/codename/2672/Crestline One of my old laptops has a GM965 and it works fine in X. It's a Dell Inspiron 1525 that was advertised as having Crestline graphics. The only problem that I've run into on the laptop is that suspend/resume is flaky. Thanks to Doug Chris for the information. It is good news. The machine in question is a Latitude D830. It has a T9500 processor (64-bit @2.6GHz), a 1920x1200 display and a serial port. I should have possession of the machine in about a week and will report my progress/results. I hope to get accelerated graphics working so I can use it as my personal workstation. I have been using OBSD for infrastructure since 3.0, and Linux for my daily driver desktop. I have tried moving my workstation to OBSD but always moved back because I needed functionality only available on Linux. I so very much want to be done with Linux even though I have been using it since 0.9* kernels. If suspend/resume doesn't work, I can live with that. I will be chasing -current so maybe it can be sorted out if need be. I'm looking forward to this. Later, Ray zzz/ZZZ should work fine on the machine. I have a D820 here that I test on pretty regularly and I think those machines are pretty close. Let me know if otherwise. -ml
Re: shutdown/reboot on acpi/qemu signals
On Mon, Oct 13, 2014 at 07:42:34PM +0100, Nux! wrote: Hello, I'm having an issue with my OpenBSD cloud instance in that it completely ignores the signals sent to it by qemu-kvm, so instead of getting shut down or rebooted gracefully it has to be reset. Anyone hit this issue before and can advise on the matter? Thanks, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro What version of OpenBSD? We fixed this in April.
Re: shutdown/reboot on acpi/qemu signals
On Mon, Oct 13, 2014 at 03:51:45PM -0300, Giancarlo Razzolini wrote: On 13-10-2014 15:42, Nux! wrote: I'm having an issue with my OpenBSD cloud instance in that it completely ignores the signals sent to it by qemu-kvm, so instead of getting shut down or rebooted gracefully it has to be reset. Anyone hit this issue before and can advise on the matter? Yes, this is a know issue. You need to disable mpbios on your kernel: config -ef /bsd ulc disable mpbios ukc quit This will permanently disable mpbios on your kernel. If you follow current and recompile you kernel often, then you'll need to run this command every time you install a new kernel. Reboot your system and check if mpbios is disabled: dmesg | grep mpbios You should get this: mpbios at bios0 not configured Now you can try issue virsh shutdown domain of shutting it down from virt-manager. It will also correctly shutdown the OpenBSD guest in the event of a host shutdown. Cheers, Giancarlo Razzolini [demime 1.01d removed an attachment of type application/pkcs7-signature which had a name of smime.p7s] You are smoking some serious crack there.
Re: shutdown/reboot on acpi/qemu signals
On Mon, Oct 13, 2014 at 07:02:36PM -0300, Giancarlo Razzolini wrote: On 13-10-2014 16:50, Mike Larkin wrote: You are smoking some serious crack there. This is the only thing that works for me on all my OpenBSD virtualized installations. And I'm running 5.5 stable on all of them. I can't really speak for 5.6, since I don't run current on my production systems. So no, I'm not smoking crack. Cheers [demime 1.01d removed an attachment of type application/pkcs7-signature which had a name of smime.p7s] Disabling random parts of the kernel without understanding what you are doing is certainly smoking crack. I doubt you heard disable mpbios as a valid solution from any OpenBSD developer. The fix for this issue went in after 5.5. So if you don't want to update to -current, I'd ask that you don't advise other people to follow you down untested/unsupported paths.
Re: poor network performance after wake from suspend
On Fri, Sep 26, 2014 at 11:46:04AM +0400, Кирилл wrote: Hello. After apm -z and wake by wol (re0) sometimes machine becomes very slow on network operations (even ssh!) Help, please. Here is dmesg and ifconfig: ... snip ... re0: watchdog timeout Do you see only one of these watchdog timeouts or a bunch? And does this problem happen with non-WOL wakeups? -ml ifconfig re0 re0: flags=108843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,WOL mtu 1500 lladdr 00:21:85:52:d5:ea priority: 0 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::221:85ff:fe52:d5ea%re0 prefixlen 64 scopeid 0x1 inet 192.168.1.4 netmask 0xff00 broadcast 192.168.1.255
Re: is this normal or problematic?
On Thu, Oct 23, 2014 at 06:55:11PM +0200, Peter J. Philipp wrote: I have a tcpdump set in the background on OpenBSD 5.5-current from: mercury$ sysctl kern.version kern.version=OpenBSD 5.5-current (MERCURY.MP) #2: Sat Jun 21 08:24:41 What (and why) did you change in GENERIC.MP?
Re: Libretto 70CT
On Thu, Oct 23, 2014 at 09:59:04PM +0100, Fred wrote: Hi Sebastian, I've just installed -current on my Libretto 70CT - as you can see from the output below it stoped with: kernel: integer divide fault trap, code=0 Rebooted it and disable it, schsio and softraid and it has now made it to the end of boot - but it has not yet made it to a login prompt. Last time I tried this I left it running for about a week - and still did not make it to a login prompt. hth Fred PS I've CC misc@ for the archives rather than clog up ports@ Script started on Thu Oct 23 21:10:34 2014 port:fred ~ cu -l /dev/cuaU0 Connected to /dev/cuaU0 (speed 9600) OpenBSD/i386 BOOT 3.26 boot \|/-\|/booting hd0a:/bsd: -\|/-9699132\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\+1067500 [72+403280|/-\|/-\|/-\|/-\|/-\|/-\+397651|/-\|/-\|/-\|/-\|/-\|/-\|]=0xb083b0 entry point at 0x200120 [ using 801416 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.6-current (GENERIC) #415: Wed Oct 22 11:33:32 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 121 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX real mem = 16412672 (15MB) avail mem = 3915776 (3MB) For what it's worth, 16MB doesn't appear to be enough anymore. qemu with 16MB hangs at the same place as you're reporting, but configuring it for 20MB RAM seems to boot ok. It's pretty slow but it does work. -ml mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/11/97 apm0 at bios0: Power Management spec V1.2 pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xe4000/0xc000 cpu0 at mainbus0: (uniprocessor) cpu0: F00F bug workaround installed isa0 at mainbus0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 vga0 at isa0 port 0x3b0/48 iomem 0xa/131072 wsdisplay0 at vga0 mux 1: console (80x25, vt100 emulation), using wskbd0 wsdisplay0: screen 1-5 added (80x25, vt100 emulation) wdc0 at isa0 port 0x1f0/8 irq 14 wd0 at wdc0 channel 0 drive 0: IBM-DDLA-21620 wd0: 16-sector PIO, LBA, 1551MB, 3177216 sectors wd0(wdc0:0:0): using BIOS timings sb0 at isa0 port 0x220/24 irq 5 drq 1: dsp v3.01 midi0 at sb0: SB MIDI UART audio0 at sb0 opl at sb0 not configured wss0 at isa0 port 0x530/8 irq 10 drq 0: CS4231 or AD1845 (vers 4) audio1 at wss0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pcic0 at isa0 port 0x3e0/2 iomem 0xd/65536 pcic0 controller 0: Intel 82365SL rev 1 has sockets A and B pcmcia0 at pcic0 controller 0 socket 0 xe0 at pcmcia0 function 0 Xircom, CreditCard 10Base-T, PS-CE2-10 port 0x340/16, irq 9: address 00:80:c7:42:37:d9 pcmcia1 at pcic0 controller 0 socket 1 pcic0: irq 11, polling enabled vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets kernel: integer divide fault trap, code=0 Stopped at cpu_switchto+0x64: popl%ebx ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND 13605 0 0 0 2 0x14200crypto 21232 0 0 0 2 0x14200pfpurge 18646 0 0 0 2 0x14200pcic0,0,1 14390 0 0 0 2 0x14200pcic0,0,0 28330 0 0 0 2 0x14200apm0 1636 0 0 0 2 0x14200systqmp 12593 0 0 0 2 0x14200systq 9503 0 0 0 2 0x14200syswq 25602 0 0 0 1 0x14200idle0 2351 0 0 0 2 0x14200kmthread *1 0 0 0 7 0swapper 0 -1 0 0 3 0x10200 wdccmdswapper ddb trace
Re: Libretto 70CT
On Thu, Oct 23, 2014 at 10:08:31PM -0400, Nick Holland wrote: On 10/23/14 19:17, Fred wrote: On 10/23/14 23:30, Mike Larkin wrote: On Thu, Oct 23, 2014 at 09:59:04PM +0100, Fred wrote: Hi Sebastian, I've just installed -current on my Libretto 70CT - as you can see from the output below it stoped with: kernel: integer divide fault trap, code=0 Rebooted it and disable it, schsio and softraid and it has now made it to the end of boot - but it has not yet made it to a login prompt. Last time I tried this I left it running for about a week - and still did not make it to a login prompt. hth Fred PS I've CC misc@ for the archives rather than clog up ports@ Script started on Thu Oct 23 21:10:34 2014 port:fred ~ cu -l /dev/cuaU0 Connected to /dev/cuaU0 (speed 9600) OpenBSD/i386 BOOT 3.26 boot \|/-\|/booting hd0a:/bsd: -\|/-9699132\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\+1067500 [72+403280|/-\|/-\|/-\|/-\|/-\|/-\+397651|/-\|/-\|/-\|/-\|/-\|/-\|]=0xb083b0 entry point at 0x200120 [ using 801416 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.6-current (GENERIC) #415: Wed Oct 22 11:33:32 MDT 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 121 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX real mem = 16412672 (15MB) avail mem = 3915776 (3MB) For what it's worth, 16MB doesn't appear to be enough anymore. qemu with 16MB hangs at the same place as you're reporting, but configuring it for 20MB RAM seems to boot ok. It's pretty slow but it does work. -ml Memory is definately an issue on my Libretto 70CT - but I think there might be more to it especially when you go back to 4.4 when if first displayed this issue... I might consign it to OpenBSD 4.3 :~) Really, that's about when 16M became Just Too Little, it has been a long time. And...you know, I'm not going to apologize for that. :) 2.7 worked pretty well on 16M RAM, iirc. By 3.4, I'm pretty sure you were swapping before you completed a login. As a labor of love, you could strip a lot of stuff out of the kernel and see if you could make something that worked, but it really isn't worth it. Nick. It isn't. We will all laugh at you if you change GENERIC/GENERIC.MP and then post a bug.
Re: Turning off Nvidia GPU card in Optimus configuration
On Sun, Nov 09, 2014 at 11:01:32AM +0100, Lampshade wrote: Hi I was trying half year ago to use OpenBSD 5.5, but system heated my laptop. I have Intel and Nvidia GPU in laptop. I can not disable Nvidia GPU via BIOS. Laptop always exposes and enables two GPUs by default. OpenBSD does not disabled Nvidia GPU, so it heated laptop. I have tried OpenBSD 5.6 and it still heats my laptop. On Linux Nvidia's GPU is disabled automatically. I wanted to find how to disable my card manually, I used acpi_call Linux module (on Linux of course). In my laptop script turn_off_gpu.sh is disabling GPU when I strip methods variable to: methods= \_SB.PCI0.PEG0.PEGP._OFF and enables when: methods= \_SB.PCI0.PEG0.PEGP._ON Is there any way in OpenBSD to send first (disabling) command to hardware? It is the only reason I don't use OpenBSD. Maybe somebody can write few lines of code and I will compile kernel for myself? References: http://linux-hybrid-graphics.blogspot.com/2010/07/u ??? ch-onoff.html https://github.com/mkottman/acpi_call The right way to handle this IMO isn't to provide a generic way to evaluate arbitrary AML methods. That way lies madness. A better solution is to create an actual driver for nvidia0 or whatever and have that driver do nothing except disable the hardware by evaluating the method referenced above and likely also putting the device in D3 from the PCI side. Your diff to implement said functionality is certainly welcome.
Re: Trying to get suspend to RAM working on an X31
On Thu, Nov 13, 2014 at 12:16:46AM +0200, Antonio Barrones wrote: Mike Larkin mlarkin at azathoth.net writes: On Fri, Oct 10, 2014 at 10:01:18AM -0700, John Magolske wrote: Hi, I have an X31 ThinkPad on which I've installed OpenBSD. Everything boot -c , disable radeondrm (and also disable auto xdm start). See if you can zzz/resume from the console without radeondrm running. That will at least give us a place to start. Another thing you can try is seeing if the machine is in ddb on resume for some reason. Try a few (3 or 4) bo re commands (enter after each). See if the machine reboots, and if so you might have clues in dmesg after reboot. -ml Hi, with the current version and disabling radeondrm at boot, the resume works. Without disabling anything the resume doesn't work. The keyboard looks not responding, but the keys to change the lights in the display are working Not sure I understand. You say ...the resume works but then say a bunch of stuff doesn't work. Which is it? -ml (Fn+Home or Fn+End), but no any response when I press Caps Lock, or I try to reboot. Disabling the radeondrm in the dmesg the keyboard is using wsdisplay0: wskbd0 at pckbd0: console keyboard, using wsdisplay0 with the radeondrm there is not wsdisplay0: wskbd0 at pckbd0: console keyboard I don't know if this is normal or not. The dmesg with radeondrm disabled: OpenBSD 5.6-current (GENERIC) #503: Wed Nov 12 00:43:00 MST 2014 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1400MHz (GenuineIntel 686-class) 1.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE,EST,TM2,PERF real mem = 1341026304 (1278MB) avail mem = 1306824704 (1246MB) User Kernel Config UKC disable radeondrm 247 radeondrm* disabled UKC exit Continuing... mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 09/22/05, BIOS32 rev. 0 @ 0xfd750, SMBIOS rev. 2.33 @ 0xe0010 (57 entries) bios0: vendor IBM version 1QET97WW (3.02 ) date 09/22/2005 bios0: IBM 2672C2G acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA BOOT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) PCI0(S3) PCI1(S4) DOCK(S4) USB0(S3) USB1(S3) AC9M(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (PCI1) acpiprt3 at acpi0: bus -1 (DOCK) acpicpu0 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB1, USB7 acpitz0 at acpi0: critical temperature is 91 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model IBM-COMPATIBLE serial21 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) bios0: ROM list: 0xc/0x1 0xd/0x1000 0xd1000/0x1000 0xdc000/0x4000! 0xe/0x1 cpu0 at mainbus0: (uniprocessor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: Enhanced SpeedStep 1399 MHz: speeds: 1400, 1200, 1000, 800, 600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82855PM Host rev 0x03 intelagp0 at pchb0 agp0 at intelagp0: aperture at 0xd000, size 0x1000 ppb0 at pci0 dev 1 function 0 Intel 82855PM AGP rev 0x03 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Radeon Mobility M6 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 11 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 11 uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 11 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 11 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb1 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x81 pci2 at ppb1 bus 2 2:0:0: mem address conflict 0xb000/0x1000 2:0:1: mem address conflict 0xb100/0x1000 cbb0 at pci2 dev 0 function 0 Ricoh 5C476 CardBus rev 0xaa: irq 11 cbb1 at pci2 dev 0 function 1 Ricoh 5C476 CardBus rev 0xaa: irq 11 Ricoh 5C552 Firewire rev 0x02 at pci2 dev 0 function 2 not configured fxp0 at pci2 dev 8 function 0 Intel PRO/100 VE rev 0x81, i82562: irq 11, address 00:0d:60:78:16:30 inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 3 device 0 cacheline 0x0, lattimer 0xb0 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 6 device 0 cacheline 0x0, lattimer 0xb0 pcmcia1 at cardslot1 ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x01 pciide0 at pci0 dev 31 function 1 Intel
Re: Thinkpad T410 fan control
On Fri, Nov 14, 2014 at 02:02:23AM +0400, Seiran Umetov wrote: Hello. I've installed OpenBSD 5.6 on my Thinkpad laptop, everything looks fine, but i have problem with fan. His minimal speed is 3500, even if i use apm -L (or apm -C). http://pastebin.com/wUY8MqjX - here is my dmesg output. It's 59 degC at the PCH, I think the fan would likely run that fast if the PCH were that hot. -ml sensors: sysctl hw.sensors hw.sensors.cpu0.temp0=33.00 degC hw.sensors.cpu1.temp0=33.00 degC hw.sensors.cpu2.temp0=33.00 degC hw.sensors.cpu3.temp0=33.00 degC hw.sensors.acpitz0.temp0=53.00 degC (zone temperature) hw.sensors.acpibtn0.indicator0=On (lid open) hw.sensors.acpibat0.volt0=10.80 VDC (voltage) hw.sensors.acpibat0.volt1=12.40 VDC (current voltage) hw.sensors.acpibat0.current0=0.00 A (rate) hw.sensors.acpibat0.amphour0=4.12 Ah (last full capacity) hw.sensors.acpibat0.amphour1=0.21 Ah (warning capacity) hw.sensors.acpibat0.amphour2=0.02 Ah (low capacity) hw.sensors.acpibat0.amphour3=4.12 Ah (remaining capacity), OK hw.sensors.acpibat0.amphour4=4.75 Ah (design capacity) hw.sensors.acpibat0.raw0=0 (battery idle), OK hw.sensors.acpiac0.indicator0=On (power supply) hw.sensors.acpithinkpad0.temp0=53.00 degC hw.sensors.acpithinkpad0.temp1=53.00 degC hw.sensors.acpithinkpad0.temp2=53.00 degC hw.sensors.acpithinkpad0.temp3=53.00 degC hw.sensors.acpithinkpad0.temp4=53.00 degC hw.sensors.acpithinkpad0.temp5=53.00 degC hw.sensors.acpithinkpad0.temp6=53.00 degC hw.sensors.acpithinkpad0.temp7=53.00 degC hw.sensors.acpithinkpad0.fan0=3565 RPM hw.sensors.itherm0.temp0=0.00 degC (Thermometer) hw.sensors.itherm0.temp1=50.01 degC (Core 1) hw.sensors.itherm0.temp4=52.00 degC (CPU/GPU Max temp) hw.sensors.itherm0.temp9=52.00 degC (GPU/Memory controller abs.) hw.sensors.itherm0.temp10=59.00 degC (PCH abs.) hw.sensors.itherm0.power0=7.00 W (CPU power consumption) hw.sensors.aps0.temp0=40.00 degC hw.sensors.aps0.temp1=40.00 degC hw.sensors.aps0.indicator0=Off (Keyboard Active) hw.sensors.aps0.indicator1=Off (Mouse Active) hw.sensors.aps0.indicator2=On (Lid Open) hw.sensors.aps0.raw0=519 (X_ACCEL) hw.sensors.aps0.raw1=505 (Y_ACCEL) hw.sensors.aps0.raw2=519 (X_VAR) hw.sensors.aps0.raw3=505 (Y_VAR) $ apm -v Battery state: high, 99% remaining, unknown life estimate A/C adapter state: connected Performance adjustment mode: manual (1199 MHz) How can i decrease my fan speed? because laptop works in the night and its too loud.
Re: Temperature
On Fri, Nov 14, 2014 at 11:59:26AM -0800, patrick keshishian wrote: Hi, On 11/14/14, Etienne etienne.m...@magickarpet.org wrote: Hello list, I seem to have a little hardware related problem. I have been using a Lenovo x120e for some time, and OpenBSD ran nicely on it until April. As soon as I upgraded to 5.5, and from quite early after kernel loading, the console started showing and repeating at regular intervals: acpitz0: critical temperature reached 93C, shutting down acpithinkpad0: Unknown event 0x6022 I don't believe I have ever seen the issue you describe with my x120e. hw.vendor=LENOVO hw.version=ThinkPad X120e hw.sensors.acpitz0.temp0=75.00 degC (zone temperature) hw.sensors.acpithinkpad0.temp0=75.00 degC hw.sensors.acpithinkpad0.temp1=0.00 degC hw.sensors.acpithinkpad0.temp2=75.00 degC hw.sensors.acpithinkpad0.temp3=0.00 degC hw.sensors.acpithinkpad0.temp4=0.00 degC hw.sensors.acpithinkpad0.temp5=0.00 degC hw.sensors.acpithinkpad0.temp6=27.00 degC hw.sensors.acpithinkpad0.temp7=0.00 degC hw.sensors.km0.temp0=75.88 degC hw.sensors.acpithinkpad0.fan0=441 RPM (93C is just a typical value, I've seen any between 92 and 98). I usually have just the time to log in before the system logs me out and shuts down. This laptop normally runs at around 80?C, and I think the temperature reading in OpenBSD is correct, because I get similar warnings and temperature values when I reboot immediately into another OS. That may be a hint that something may be wrong with your cooling. Dust blockage, etc. Booting on 5.6 bsd.rd and upgrading the system went fine, but as soon as I restarted the system, the same situation happened. Feeling adventurous, I tried to disable acpitz* during the boot process, which made the messages go away. The system ran just below 100?C (as reported by sysctl) for some time without any problem, until I didn't want to take the risk for any longer and shut it down manually. I also have an x100e from the same brand, quite similar even if older and slower, which does _NOT_ show the same symptoms. I'm attaching the dmesg and sysctl hw.sensors output of both machines running 5.6. Has anyone been running 5.5 and 5.6 on a x120e? Any clues on what I should do to diagnose the problem any better? As I say, I never have had this issue with x120e, which I've been using for over 3 years with OpenBSD, mainly following snapshots. Running older snapshot atm: $ sysctl kern.version kern.version=OpenBSD 5.6-current (GENERIC.MP) #368: Tue Sep 9 00:28:20 MDT 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP I have a Gateway LT31 (?) that used to have similar issue as you describe. After first cold boot, it would immediately shutdown because of temperature warning. Next boot, it would be fine. However, since the last snapshot I put on it, from Sep. It hasn't exhibited this behavior. Then again, the Gateway isn't used much; so it could be that I've been lucky. I fixed the bogus shutdowns at the last hackathon (the ones where acpitz(4) would return temperatures in the 4000-5000K range). -ml --patrick Cheers! -- ?tienne OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1861025792 (1774MB) avail mem = 1802760192 (1719MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf09b0 (43 entries) bios0: vendor LENOVO version 6XET45WW (1.28 ) date 09/17/2010 bios0: LENOVO 35089CU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA SSDT APIC MCFG HPET SLIC acpi0: wakeup devices PB5_(S5) OHC0(S3) OHC1(S3) OHC2(S3) OHC3(S3) OHC4(S3) P2P_(S5) LID_(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1597.30 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 256KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) Neo X2 Dual Core Processor L335, 1596.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,3DNOWP cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line
Re: Trying to get suspend to RAM working on an X31
On Thu, Nov 13, 2014 at 10:41:35AM +0200, Antonio Barrones wrote: On 13 November 2014 01:33, Mike Larkin mlar...@azathoth.net wrote: On Thu, Nov 13, 2014 at 12:16:46AM +0200, Antonio Barrones wrote: Mike Larkin mlarkin at azathoth.net writes: On Fri, Oct 10, 2014 at 10:01:18AM -0700, John Magolske wrote: Hi, I have an X31 ThinkPad on which I've installed OpenBSD. Everything boot -c , disable radeondrm (and also disable auto xdm start). See if you can zzz/resume from the console without radeondrm running. That will at least give us a place to start. Another thing you can try is seeing if the machine is in ddb on resume for some reason. Try a few (3 or 4) bo re commands (enter after each). See if the machine reboots, and if so you might have clues in dmesg after reboot. -ml Hi, with the current version and disabling radeondrm at boot, the resume works. Without disabling anything the resume doesn't work. The keyboard looks not responding, but the keys to change the lights in the display are working Not sure I understand. You say ...the resume works but then say a bunch of stuff doesn't work. Which is it? -ml When you disable radeondrm at boot (boot -c), then in the -current version of OpenBSD, the resume works (but X window doesn't work I have tried also with vesa driver in xorg.conf). Doing the same with the 5.6 -release version, resume works, but the console is corrupted and the characters are not legible but the keyboard works and you can boot without hard reset. If you don't disable anything at boot (with the -current version ) then resume doesn't work. In the previous mail I posted the dmesg with radeondrm disabled and also the dmesg without disabling anything at boot. Antonio Looks like a problem in radeondrm resume for this chip, then, since disabling that works. I wouldn't expect X to work here since you're basically running half of a radeon config (radeon but no DRM/KMS) at that point. -ml
Re: Can't boot Nov 21 amd64/bsd.rd - finishes at 'entry point'...
On Mon, Nov 24, 2014 at 05:14:10PM -0500, Jiri B wrote: On Sat, Nov 22, 2014 at 12:40:22PM -0700, Theo de Raadt wrote: I can't boot bsd.rd (amd64) from Nov 21 2014. I've tried to upgrade my FDE-based amd64 installation. I entered passphrase for crypto softraid in boot loader, typed 'bsd.rd' and after one line it finished: entry point at 0x1000160 [7205c768, 3404, 24448b12, 6670a304] (I hope I wrote it down correctly.) As you and other readers of this list know very well, the above is an incomplete bug report. It is nice to know that you have spotted a problem, but there simply is not enough information for anyone to move forward. I just tested the same stuff on 3 of my machines. Considering the effort we put into making this code, please put a bit more effort into it yourself? Thanks. Hi, yeah I should have to include my working dmesg, so here it is from my Lenovo T500. I don't know what else I could provide, I can't boot anymore bsd.mp, bsd.rd and even cdboot.iso I burnt (all amd64). They all finish on just 2nd line as state above, no idea. If those numbers are important I would do a photo (laptop, no console) and write it down. How else could I help? Try a newer snapshot and let us know if it is still broken. -ml OpenBSD 5.6-current (GENERIC.MP) #544: Fri Nov 7 10:36:24 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4166717440 (3973MB) avail mem = 4051992576 (3864MB) warning: no entropy supplied by boot loader mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (80 entries) bios0: vendor LENOVO version 6FET82WW (3.12 ) date 11/26/2009 bios0: LENOVO 2089A35 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz, 2394.37 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,LONG,LAHF,PERF cpu0: 3MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges cpu0: apic clock running at 266MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz, 2394.01 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,LONG,LAHF,PERF cpu1: 3MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus -1 (EXP2) acpiprt5 at acpi0: bus -1 (EXP3) acpiprt6 at acpi0: bus 13 (EXP4) acpiprt7 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB3, USB5, EHC0, EHC1 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4621 serial 1562 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2401, 2400, 1600, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07 vga1 at pci0 dev 2 function 0 Intel GM45 Video rev 0x07 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1680x1050 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel GM45 Video rev 0x07 at pci0 dev 2 function 1 not configured Intel GM45 HECI rev 0x07 at pci0 dev 3 function 0 not configured em0 at pci0 dev 25 function 0 Intel ICH9 IGP M AMT rev 0x03: msi, address 00:27:13:b7:d2:45 uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 1 int 21 uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 1 int 22 ehci0 at pci0
Re: Lenovo T500 doesn't boot [Was: Re: Can't boot Nov 21 amd64/bsd.rd - finishes at 'entry point'...]
On Wed, Nov 26, 2014 at 02:48:33PM -0500, Jiri B wrote: Does anybody have an archive for each amd64 snapshot? I'd like to check what is the latest amd64 kernel which can boot on T500. Nov 7 snapshot works OK but recent ones do not. I updated bios, ran memtest86+, still same problem. But... I see I don't have any getty, strange, I haven't observe it before as I use X. Can you verify you've enabled NX (sometimes called execute disable) in your BIOS? We made some changes in this area recently and while I did test on a non-NX setup, maybe we missed something. I see your CPUID outputs in the dmesg that works don't have NXE, which leads me to believe you disabled it in the BIOS for some reason (as your CPU does support it). -ml USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 1 0.0 0.0 604 540 ?? Ss 8:26PM0:01.07 /sbin/init root 16946 0.0 0.0 796 988 ?? Is 8:26PM0:00.00 syslogd: [priv] (syslogd) _syslogd 27946 0.0 0.0 796 1104 ?? S 8:26PM0:00.08 /usr/sbin/syslogd root 30726 0.0 0.0 824 584 ?? Is 8:26PM0:00.01 pflogd: [priv] (pflogd) _pflogd 1386 0.0 0.0 888 368 ?? S 8:26PM0:00.06 pflogd: [running] -s 160 -i pflog0 -f /var/log/pflog (pflogd) root 6328 0.0 0.0 1160 1352 ?? Is 8:26PM0:00.00 /usr/sbin/sshd _smtpd1994 0.0 0.1 1608 2776 ?? I 8:26PM0:00.01 smtpd: pony express (smtpd) _smtpd 32643 0.0 0.0 1452 1968 ?? I 8:26PM0:00.00 smtpd: klondike (smtpd) root 3845 0.0 0.1 1584 2204 ?? Is 8:26PM0:00.01 smtpd: [priv] (smtpd) _smtpq 27223 0.0 0.1 1584 2252 ?? I 8:26PM0:00.01 smtpd: queue (smtpd) _smtpd 15481 0.0 0.1 1724 2308 ?? I 8:26PM0:00.00 smtpd: control (smtpd) _smtpd4473 0.0 0.1 1588 2308 ?? I 8:26PM0:00.00 smtpd: lookup (smtpd) _smtpd4297 0.0 0.0 1380 1980 ?? I 8:26PM0:00.00 smtpd: scheduler (smtpd) _sndio 32512 0.0 0.0 752 964 ?? Is8:26PM0:00.00 /usr/bin/sndiod _dnscrypt-proxy 18418 0.0 0.0 1072 1416 ?? Is 8:26PM0:00.01 /usr/local/sbin/dnscrypt-proxy -d --user=_dnscrypt-proxy --local-address=127.0.0.1:5331 --user=_dnsc _pdnsd 18198 0.0 0.1 4400 5004 ?? I 8:26PM0:00.02 /usr/local/sbin/pdnsd -d _mpd 4212 0.0 0.2 16144 7864 ?? Is 8:26PM0:00.02 /usr/local/sbin/mpd root 26670 0.0 0.0 540 908 ?? Ss 8:26PM0:00.00 /usr/sbin/apmd -A root 25744 0.0 0.0 812 1168 ?? Ss 8:26PM0:00.00 /usr/sbin/cron root 28624 0.0 0.0 796 1968 ?? Is 8:26PM0:00.04 /usr/X11R6/bin/xdm _x11 20501 0.0 0.6 16252 24784 ?? Ss 8:26PM0:03.01 /usr/X11R6/bin/X :0 vt05 -auth /etc/X11/xdm/authdir/authfiles/A:0-hh1yAL (Xorg) root 4464 0.0 0.0 2504 1356 ?? I 8:26PM0:00.03 X: [priv] (Xorg) root 5150 0.0 0.2 1416 6448 ?? Is 8:26PM0:00.17 xdm: :0 (xdm) jirib 5092 0.0 0.0 636 664 ?? Is 8:26PM0:00.02 /bin/sh /etc/X11/xdm/Xsession jirib 1893 0.0 0.0 692 1704 ?? Is 8:26PM0:00.01 ssh-agent -s jirib 3965 0.0 0.1 1008 5560 ?? I 8:26PM0:00.03 cwm jirib29718 0.0 0.0 852 1720 ?? I 8:26PM0:00.00 dbus-launch --sh-syntax --exit-with-session jirib20225 0.0 0.0 928 1164 ?? Is 8:26PM0:00.00 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session jirib 9543 0.0 0.1 592 2276 ?? I 8:26PM0:00.01 xidle jirib24260 0.0 0.1 1608 3336 ?? S 8:26PM0:00.20 xstatbar -f -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso10646-1 -w 1680 -h 14 jirib 3144 0.0 0.3 7868 13696 ?? S 8:26PM0:00.39 xterm -class UXTerm jirib25699 0.0 0.1 2080 3636 ?? Ss 8:26PM0:00.61 tmux: server (/tmp/tmux-1001/default) (tmux) root 21781 0.0 0.0 764 568 ?? S 8:34PM0:00.00 /sbin/init root 10920 0.0 0.0 768 584 ?? S 8:34PM0:00.00 /sbin/init root 18579 0.0 0.0 772 600 ?? S 8:34PM0:00.00 /sbin/init root 26966 0.0 0.0 764 580 ?? S 8:34PM0:00.00 /sbin/init root 28783 0.0 0.0 760 576 ?? S 8:34PM0:00.00 /sbin/init ^^^ jirib10749 0.0 0.0 680 844 p0 Is 8:26PM0:00.01 -ksh (ksh) jirib12212 0.0 0.0 992 1964 p0 I+ 8:26PM0:00.01 tmux: client (/tmp/tmux-1001/default) (tmux) jirib 3196 0.0 0.0 724 824 p1 Is 8:26PM0:00.03 -ksh (ksh) root 16221 0.0 0.0 740 732 p1 S 8:31PM0:00.08 -ksh (ksh) root 6363 0.0 0.0 480 404 p1 R+ 8:35PM0:00.00 ps -aux Using drive 0, partition 3. Loading. probing: pc0 mem[635K 3027M 1M 732K 960M a20=on]
Re: Lenovo T500 doesn't boot [Was: Re: Can't boot Nov 21 amd64/bsd.rd - finishes at 'entry point'...]
On Wed, Nov 26, 2014 at 10:49:32PM +0100, pet...@schwertfisch.de wrote: Mike Larkin mlar...@azathoth.net wrote: On Wed, Nov 26, 2014 at 02:48:33PM -0500, Jiri B wrote: Does anybody have an archive for each amd64 snapshot? I'd like to check what is the latest amd64 kernel which can boot on T500. Nov 7 snapshot works OK but recent ones do not. I updated bios, ran memtest86+, still same problem. But... I see I don't have any getty, strange, I haven't observe it before as I use X. Can you verify you've enabled NX (sometimes called execute disable) in your BIOS? We made some changes in this area recently and while I did test on a non-NX setup, maybe we missed something. I see your CPUID outputs in the dmesg that works don't have NXE, which leads me to believe you disabled it in the BIOS for some reason (as your CPU does support it). I've also had trouble booting bsd.rd for the last few days on a Lenovo X220. This problem went away after changing the BIOS setup: Security - Memory Protection - Execution Prevention [Disabled] - [Enabled] My dmesg is included below. Regards Dirk I think we've identified where the problem is, will test and commit shortly. Thanks to both for testing. -ml OpenBSD 5.6-current (GENERIC.MP) #614: Wed Nov 26 02:31:16 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4156157952 (3963MB) avail mem = 4041678848 (3854MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (65 entries) bios0: vendor LENOVO version 8DET52WW (1.22 ) date 09/15/2011 bios0: LENOVO 4290W1B acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT SSDT UEFI UEFI UEFI acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2492.30 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus 5 (EXP4) acpiprt5 at acpi0: bus 13 (EXP5) acpiprt6 at acpi0: bus -1 (EXP7) acpicpu0 at acpi0: C3, C1, PSS acpicpu1 at acpi0: C3, C1, PSS acpicpu2 at acpi0: C3, C1, PSS acpicpu3 at acpi0: C3, C1, PSS acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 acpitz0 at acpi0: critical temperature is 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4861 serial 5709 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) cpu0: Enhanced SpeedStep 2492 MHz: speeds: 2501, 2500, 2200, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0
Re: Poor disk performance
On Thu, Nov 27, 2014 at 06:04:46PM +0100, David Unric wrote: Bellow are relevant rows of dmesg output: And here is the relevant part of a solution: What do you think? Helpful, huh? Next time please provide a complete dmesg. There is a reason he didn't ask you to parse it yourself. There are other things we look for. Without the full report, we can't see if you have conflicts, etc. -ml snip -- OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xea450 (94 entries) bios0: vendor American Megatrends Inc. version 13HX.M038.20110729.SSH date 07/29/2011 bios0: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core 2G Host rev 0x09 pcib0 at pci0 dev 31 function 0 Intel HM65 LPC rev 0x04 ahci0 at pci0 dev 31 function 2 Intel 6 Series AHCI rev 0x04: msi, AHCI 1.3 scsibus1 at ahci0: 32 targets sd0 at scsibus1 targ 0 lun 0: ATA, Hitachi HTS54757, JE4O SCSI3 0/direct fixed naa.5000cca63fc2c8ee sd0: 715404MB, 512 bytes/sector, 1465149168 sectors cd0 at scsibus1 targ 2 lun 0: TSSTcorp, CDDVDW SN-208BB, SC00 ATAPI 5/cdrom removable ichiic0 at pci0 dev 31 function 3 Intel 6 Series SMBus rev 0x04: apic 2 int 18 iic0 at ichiic0 spdmem0 at iic0 addr 0x50: 2GB DDR3 SDRAM PC3-10600 SO-DIMM spdmem1 at iic0 addr 0x52: 4GB DDR3 SDRAM PC3-10600 SO-DIMM isa0 at pcib0 isadma0 at isa0 vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on sd0a (60b75564032edafa.a) swap on sd0b dump on sd0b snip -- Thanks. On Thu, Nov 27, 2014 at 5:01 PM, Brad Smith b...@comstyle.com wrote: On 11/27/14 10:57, David Unric wrote: Hello, I'd like to figure out what causes very low performance of disk operations on my laptop. I've tested it by unpacking gzipped tar archive ( http://ftp.heanet.ie/pub/OpenBSD/5.6/src.tar.gz) about 125 MiB big. On the same machine, not cached, various results by operating system: NetBSD 6.1.522 secs Linux 3.14.228 secs OpenBSD 5.6 aborted after 10 minutes as still not finished Unpacking was done with `tar xzf src.tar.gz', even tried on uncompressed src.tar but roughly same results. By comparing with more similar NetBSD I've found the SATA disk is attached differently: - in OpenBSD detected as SCSI, `sd' driver used, no sign of Ultra-DMA access - in NetBSD detected as (SATA) IDE, `wd' driver used, UDMA/133 activated I've tried mount the partition with softdeps and noatime options, but that's only a slight improvement. Any idea how to fix this issue (like forcing use of wd?) or I'm out of luck and my 750GB Hitachi SATA IDE is unsupported in OpenBSD and no generic driver can be used ? Reply with the output of dmesg to the list as a start. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: Poor disk performance
at uvideo0
uhub3 at uhub1 port 1 Intel Rate Matching Hub rev 2.00/0.00 addr 2
ugen0 at uhub3 port 3 Broadcom Corp Broadcom BCM2070 Bluetooth Device rev
2.00/6.28 addr 3
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (60b75564032edafa.a) swap on sd0b dump on sd0b
On Thu, Nov 27, 2014 at 6:27 PM, Mike Larkin mlar...@azathoth.net wrote:
On Thu, Nov 27, 2014 at 06:04:46PM +0100, David Unric wrote:
Bellow are relevant rows of dmesg output:
And here is the relevant part of a solution:
What do you think? Helpful, huh?
Next time please provide a complete dmesg. There is a reason he didn't
ask you to parse it yourself. There are other things we look for. Without
the full report, we can't see if you have conflicts, etc.
-ml
snip
--
OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xea450 (94 entries)
bios0: vendor American Megatrends Inc. version 13HX.M038.20110729.SSH
date 07/29/2011
bios0: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel Core 2G Host rev 0x09
pcib0 at pci0 dev 31 function 0 Intel HM65 LPC rev 0x04
ahci0 at pci0 dev 31 function 2 Intel 6 Series AHCI rev 0x04: msi, AHCI
1.3
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: ATA, Hitachi HTS54757, JE4O SCSI3
0/direct
fixed naa.5000cca63fc2c8ee
sd0: 715404MB, 512 bytes/sector, 1465149168 sectors
cd0 at scsibus1 targ 2 lun 0: TSSTcorp, CDDVDW SN-208BB, SC00 ATAPI
5/cdrom removable
ichiic0 at pci0 dev 31 function 3 Intel 6 Series SMBus rev 0x04: apic 2
int 18
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 2GB DDR3 SDRAM PC3-10600 SO-DIMM
spdmem1 at iic0 addr 0x52: 4GB DDR3 SDRAM PC3-10600 SO-DIMM
isa0 at pcib0
isadma0 at isa0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (60b75564032edafa.a) swap on sd0b dump on sd0b
snip
--
Thanks.
On Thu, Nov 27, 2014 at 5:01 PM, Brad Smith b...@comstyle.com wrote:
On 11/27/14 10:57, David Unric wrote:
Hello,
I'd like to figure out what causes very low performance of disk
operations
on my laptop.
I've tested it by unpacking gzipped tar archive (
http://ftp.heanet.ie/pub/OpenBSD/5.6/src.tar.gz) about 125 MiB big.
On the same machine, not cached, various results by operating system:
NetBSD 6.1.522 secs
Linux 3.14.228 secs
OpenBSD 5.6 aborted after 10 minutes as still not finished
Unpacking was done with `tar xzf src.tar.gz', even tried on
uncompressed
src.tar but roughly same results.
By comparing with more similar NetBSD I've found the SATA disk is
attached
differently:
- in OpenBSD detected as SCSI, `sd' driver used, no sign of
Ultra-DMA
access
- in NetBSD detected as (SATA) IDE, `wd' driver used, UDMA/133
activated
I've tried mount the partition with softdeps and noatime options, but
that's only a slight improvement.
Any idea how to fix this issue (like forcing use of wd?) or I'm out of
luck
and my 750GB Hitachi SATA IDE is unsupported in OpenBSD and no generic
driver can be used ?
Reply with the output of dmesg to the list as a start.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Re: missing packages for SPARC
On Wed, Dec 03, 2014 at 05:54:14PM -0500, dev wrote: We keep having this tail of zombie architectures. Long obsolete hardware, run by few people, with pitiful best effort package builds happening each release and with luck once between. They slowly sink under the accumulating bitrot that nobody cares to fix, but at the same time people can't bring themselves to completely abandon those archs. *shrug* snip I will dust off my ss20 this weekend see if it powers up. A SparcStation 20 is a relic for historical reference only. A cool item and if it powers up I would be surprised. However it won't make any more sense than to have a 1976 Ford truck as a daily driver. What you miss is that running on these architectures expose bugs that would otherwise not be found. Endianness issues, timing differences due to slower CPUs, alignment bugs, etc... And those bugs sometimes turn out to be MI bugs that affect all architectures. It would be a waste of effort to look at anything previous to a Sun Fire V890 or any UltraSPARC IV based server. There are very few out there running Solaris any more and only hobby types have SPARC anywhere else. I ran OpenBSD 5.4 briefly on a small UltraSPARC Netra and it ran very well. However I ran into issues trying to compile things. I may look at OpenBSD again but really anything less than a modern Niagara class UltraSparc would be wasted efforts I think. Dennis
Re: apmd.8 lacks of hibernation quirks info
On Sun, Dec 07, 2014 at 06:05:16PM +0100, Alessandro DE LAURENZIS wrote: Greetings, With OpenBSD 5.6 release, I finally have a pretty functional (and usable) hibernation function (not on all my hardware, but at least for a not-so-recent HP laptop it works!). Which machines don't work, and how do they break? I would like to know. Please file a bug report (man sendbug). Thanks. -ml I was digging into my scripts in order to apply some quirks before hibernating the machine, and noticed that the man page lacks some info. In particular, the code already support a specific file to be executed before entering the S4 state (/etc/apm/hibernate), even if uses the same file (/etc/apm/resume) after resuming from both S3 and S4 (if my understanding is wrong, please correct me). So: 1) a proposed patch for the man page (as per the 5.6 code): --- ./usr.sbin/apmd/apmd.8Thu Jul 24 03:04:58 2014 +++ ./usr.sbin/apmd/apmd.8.patchedSun Dec 7 17:47:58 2014 @@ -137,14 +137,15 @@ in the requested state after running the configuration script and flushing the buffer cache. .Pp -Actions can be configured for the following five transitions: +Actions can be configured for the following six transitions: suspend, +hibernate, standby, resume, powerup, and powerdown. -The suspend and standby actions are run prior to +The suspend, hibernate and standby actions are run prior to .Nm performing any other actions (such as disk syncs) and entering the new state. @@ -159,6 +160,7 @@ Default device used to control the APM kernel driver. .Pp .It /etc/apm/suspend +.It /etc/apm/hibernate .It /etc/apm/standby .It /etc/apm/resume .It /etc/apm/powerup @@ -169,6 +171,7 @@ by examining the name by which it was called, which is one of suspend, +hibernate, standby, resume, powerup, 2) a question: why two different files for entering suspend/hibernate states, but only one for resuming? At the moment, I do not apply any quirks on resume, but having the possibility to differentiate b/w S3 and S4 wake-up could be useful in some corner cases. Thanks in advance for your time. -- Alessandro DE LAURENZIS [mailto:just22@gmail.com] LinkedIn: http://it.linkedin.com/in/delaurenzis
Re: DigitalOcean's BSD debut is FreeBSD only
On Thu, Dec 18, 2014 at 12:24:45PM -0600, Adam Thompson wrote: On 14-12-18 12:06 PM, andrew fabbro wrote: In short - the list of VPS providers who can support OpenBSD is actually very big. I have to take issue with that statement... The list of VPS providers where OpenBSD will run, more or less correctly, more or less all of the time, is actually very big. It will even run correctly all of the time on a fairly large list of providers. However, the list of VPS providers who are willing to *support* OpenBSD is extremely small. What do you do if one day you're only getting 100kbps throughput? Call support, who - as soon as they learn you're running OpenBSD - tell you that's not supported, sorry and hang up. When ACPI goes haywire (normal under KVM so far)... same thing. Not naming names, And your bug report for this is ... where? -ml
Re: DigitalOcean's BSD debut is FreeBSD only
On Thu, Dec 18, 2014 at 01:21:47PM -0600, Adam Thompson wrote: On 14-12-18 12:57 PM, Mike Larkin wrote: On Thu, Dec 18, 2014 at 12:24:45PM -0600, Adam Thompson wrote: On 14-12-18 12:06 PM, andrew fabbro wrote: In short - the list of VPS providers who can support OpenBSD is actually very big. I have to take issue with that statement... The list of VPS providers where OpenBSD will run, more or less correctly, more or less all of the time, is actually very big. It will even run correctly all of the time on a fairly large list of providers. However, the list of VPS providers who are willing to *support* OpenBSD is extremely small. What do you do if one day you're only getting 100kbps throughput? Call support, who - as soon as they learn you're running OpenBSD - tell you that's not supported, sorry and hang up. When ACPI goes haywire (normal under KVM so far)... same thing. Not naming names, And your bug report for this is ... where? -ml The last time I filed a bugreport on OpenBSD in a virtualized environment, I got flamed for not running it on real hardware. Haven't bothered since. However, that was a few years ago, and the ACPI shutdown issue is a big enough PITA that I'll file again soon. Difficult to debug, though, since the all I/O except wscons just freezes upon receipt of the ACPI signal. -- -Adam Thompson athom...@athompso.net It would be useful to at least see if this is a real ACPI issue or if this some problem KVM is causing. The former will elicit more sympathy than the latter. -ml
Re: Poor disk performance
On Thu, Nov 27, 2014 at 07:37:48PM +0100, David Unric wrote: Thanks for the quick answer ! Just following up on this. I repeated your unpack experiment on my machine and I got a time of 0m47s, and my fs is going through softraid crypto. I repeated on a different machine and the time was 0m40s, that one was a slower machine but no softraid. Neither machine was using softdep. Regarding the comment about the clock interrupt below; that's expected for a machine with 8 cores. You might consider trying this test again with a UP kernel, just for comparison (although I don't think you'll see much difference). -ml ad 1) disabled AHCI in BIOS as the only available option OpenBSD now boots with hdd attached as wd0 device, UDMA mode 6 and it did a significant improvement - unpacking finishes in about 6 minutes, but still magnitude worse then in NetBSD. ad 2) Not slowed down by terminal/console output. Tar command miss `-v' argument as you may notice from my original post, so no stdout at all. ad 3) bellow is the output from vmstat, when tested with AHCI disabled (see par. 1) interrupt total rate irq0/clock 58557 750 irq0/ipi 2521 32 irq144/acpi0 160 irq96/ppb0 00 irq97/inteldrm0 80 irq97/ehci0500 irq176/azalia0 10 irq98/ppb1 00 irq99/ppb2 00 irq112/re0 00 irq100/ppb3 00 irq101/ehci1 690 irq102/pciide0 8970 115 irq103/ichiic0 00 irq102/pciide1 00 irq145/pckbc0 2633 irq146/pckbc0 1401 Total 70595 905 irq0/clock interrupts count is constantly increasing during test. Is the number too high ? Possible issue here ? ad 4) apm was set to high, CPUs were running at max frequency 2 GHz (shown by sysctl) ad 5) partition mounted with rw, softdep and noatime options. I'm reluctant to turn async option on, as it shouldn't be enabled for normal operation. Take care. On Thu, Nov 27, 2014 at 6:58 PM, Mike Larkin mlar...@azathoth.net wrote: On Thu, Nov 27, 2014 at 06:41:17PM +0100, David Unric wrote: Here is a full dmesg output if you think it would help: Next steps I would try. 1. If you really wanted to verify this is a wd vs sd issue, you can usually change the SATA controller mode in the BIOS to IDE instead of AHCI. As long as you used DUIDs in fstab, the kernel should be able to find that you moved from sd - wd. I don't think you're going to find much here, but worth a try, I guess. 2. Are you unpacking this at the console? in X? I've sometimes seen console output scrolling cause lots of delays. Try unpacking it and redirecting the output to /dev/null and see if that helps. 3. vmstat -zi during unpack and systat vm 1 can help you identify what's going on sometimes as well. 4. make sure apm is set to high performance (apmd, apm -H) 5. make sure you aren't doing something obvious like mounting the filesystem as 'sync', etc. Your machine has hardware that is pretty similar to what many of us have ,so I doubt this is some systemic problem and likely an issue either with your machine specifically or the way you are doing your test. -ml OpenBSD 5.6 (GENERIC.MP) #333: Fri Aug 8 00:20:21 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 6333923328 (6040MB) avail mem = 6156533760 (5871MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xea450 (94 entries) bios0: vendor American Megatrends Inc. version 13HX.M038.20110729.SSH date 07/29/2011 bios0: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC HPET SLIC MCFG SSDT SSDT SSDT SSDT acpi0: wakeup devices USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) RP01(S3) RP04(S4) PEGA(S4) PWRB(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, 1995.80 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,X SAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr
Re: mobile internet support
On Wed, Jan 21, 2015 at 10:02:47AM +0100, Martijn van Duren wrote: Hello misc@, I need to have mobile internet to be standby for work. Is there any 4G dongle fully supported by OpenBSD (in combination with dutch mobile internet providers)? Sincerely, Martijn van Duren Tether to your cellphone and use urndis(4)?
Re: shutdown -hp now doesn't power down
On Tue, Jan 27, 2015 at 11:37:29PM +0100, Dorian B?ttner wrote: Good evening, my notebook doesn't powerdown anymore when the power supply is anymore ... when did it last work? -ml connected, it just reboots (looks like it can't power off). However it works when run on battery only. If memory serves well, there was some hibernation code work in december, but at roughly the same time the manufacturer published a bios update so I can't tell what's the root cause here. Also, when I close the lid the machine keeps suspend/resume cycling? http://wikisend.com/download/975438/W740SU.DSDT.dsl http://wikisend.com/download/111590/W740SU.tgz dmesg attached and hopefully the wikisend thing works... Just wanted to stray this in as I've seen a call to test what's going into release ;-) Thanks, Dorian OpenBSD 5.7-beta (GENERIC.MP) #44: Tue Jan 27 08:33:26 CET 2015 r...@smartie.doris.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8489222144 (8095MB) avail mem = 8259362816 (7876MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb270 (35 entries) bios0: vendor American Megatrends Inc. version 4.6.5 date 09/11/2014 bios0: Notebook W740SU acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT SSDT SSDT SSDT MCFG HPET SSDT SSDT DMAR acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) PXSX(S4) RP08(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz, 1995.70 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz, 1995.38 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz, 1995.38 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz, 1995.38 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz, 1995.38 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 1, core 0, package 0 cpu5 at mainbus0: apid 3 (application processor) cpu5: Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz, 1995.38 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 1, core 1, package 0 cpu6 at
Re: Resume-from-suspend issue with Acer Notebook in OpenBSD 5.6/5.7 beta
On Sat, Mar 14, 2015 at 02:02:09PM -0400, Kevin Kwan wrote: Nope, hibernate/suspend to disk also causes a reset. Is there anything else I should try? Hibernate resume will perform what looks like a full boot. Did you let it go through that or did you power off when you saw it booting again? Or did it load the hibernated image and *then* reboot? -ml On Mar 14, 2015 1:22 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: My daily driver notebook is an Acer Aspire 1410 notebook. Penryn-ULV Celeron, Intel GS45 chipset, Intel Centrino 6205 (iwn) swapping a non-supported Atheros AR2425, 6GB of RAM, normal everyday HDD. Everything seems to work in OpenBSD 5.6 except for the fact that every time I put it on suspend (zzz), it suspends properly (LED indicators in the front goes from blue to blinking orange), but when I take it out of suspend it goes into instant amnesia, takes me back to the Acer boot logo, You mean the machine resets. Okay, what should be my next steps here? I see from precursory Google searches that the Linux guys had this problem back in the old Kernel 3.3 days, and their workaround involves passing grub the i8042.reset parameter, which seems to tell the on-board keyboard controller to clean up its own mess. Any similar directives I can use here? Highly unlikely. Thanks for including all the information in the report. Result is a few people can glance over it and look for hints (as I am about to do). Unfortunately the few rare suspend/resume issues we see are pretty hard to diagnose without access to failing machines. One thing is missing from your report. Does hibernate work?
Re: Resume-from-suspend issue with Acer Notebook in OpenBSD 5.6/5.7 beta
On Sun, Mar 15, 2015 at 01:58:10AM -0400, Kevin Kwan wrote: Well, here's the thing - I am not even sure if it tried to load the hibernated image, or it failed in the middle, or it crashed after the load. When I powered it up after an s2d it went through the Acer logo, the boot prompt, the usual device laundry list shows up, the Intel graphics driver redrew the console, the USB configurations show up, one more line of text shows up for about 2 seconds, and then it was back to the Acer logo once again. I had to do the same thing multiple times just to catch the line at the very end: unhibernating @ block 12872447 length 31971840 bytes I made an annotated video of the entire experience here: https://www.youtube.com/watch?v=-GTWnES_134 ok you're failing in the early resume sequence, since that's shared between both ZZZ and zzz resume paths. I'll try to see if I have a similar machine to try to reproduce. On Sat, Mar 14, 2015 at 6:56 PM, Mike Larkin mlar...@azathoth.net wrote: On Sat, Mar 14, 2015 at 02:02:09PM -0400, Kevin Kwan wrote: Nope, hibernate/suspend to disk also causes a reset. Is there anything else I should try? Hibernate resume will perform what looks like a full boot. Did you let it go through that or did you power off when you saw it booting again? Or did it load the hibernated image and *then* reboot? -ml On Mar 14, 2015 1:22 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: My daily driver notebook is an Acer Aspire 1410 notebook. Penryn-ULV Celeron, Intel GS45 chipset, Intel Centrino 6205 (iwn) swapping a non-supported Atheros AR2425, 6GB of RAM, normal everyday HDD. Everything seems to work in OpenBSD 5.6 except for the fact that every time I put it on suspend (zzz), it suspends properly (LED indicators in the front goes from blue to blinking orange), but when I take it out of suspend it goes into instant amnesia, takes me back to the Acer boot logo, You mean the machine resets. Okay, what should be my next steps here? I see from precursory Google searches that the Linux guys had this problem back in the old Kernel 3.3 days, and their workaround involves passing grub the i8042.reset parameter, which seems to tell the on-board keyboard controller to clean up its own mess. Any similar directives I can use here? Highly unlikely. Thanks for including all the information in the report. Result is a few people can glance over it and look for hints (as I am about to do). Unfortunately the few rare suspend/resume issues we see are pretty hard to diagnose without access to failing machines. One thing is missing from your report. Does hibernate work?
Re: ACPI implementation for Aspeed AST2050
On Sun, Mar 29, 2015 at 11:55:49AM +0400, Denis Lapshin wrote: Since 4.9 till current 8510p/w read acpi temp with error (enormous high temp about 2000-5000 C) because SMBus data is not ready for reading. It seems data reading should be delayed. I thought we(I) fixed this last year. If you still have a problem with high temperature readings, this is the first I've heard of it since then. Probably a half dozen people sent me yes this fixed it emails. http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/acpi/acpitz.c?rev=1.47content-type=text/x-cvsweb-markup As a matter of fact I fixed it *on an 8510p*. If for some reason you are still having problems, I'd suggest sending in a proper bug report instead of just ranting. -ml Theo, you told that you don't want to implement shit in CVS repository. Most of ACPI code should be rewritten in new way. I have enormous high temperature reading in various ACPI zones on HP Compaq laptops from time to time. Still applying delay patch into acpiec.c to have it working. On 28.03.2015 22:48, Theo de Raadt wrote: Every release I need to apply a patch after upgrade for reading ACPII data from 8510p in time, to prevent wrong data on SMBUS. Theo replied that the patch will not be implemented in CVS because all ACPI must be rewritten in new manner. But they will do nothing since my last report... I doubt I said anything close to your interpretation. -- Denis Lapshin mailto: den...@mindall.org
Re: i386 bsd.rd panic
On Sun, Apr 26, 2015 at 01:02:49PM +0200, Eivind Eide wrote: I've been trying to update this -current machine with the bsd.rd from the last 4 snapshots, the last being from Sun Apr 26 02:22:08 MDT 2015. However this kernel immediately after reporting how much ram I have panics with this message: fatal protection fault (4) in supervisor mode trap type 4 code 0 eip d020204e cs 8 eflags 10006 cr2 0 cpl 0 panic: trap type 4, code=0, pc=d020204e Any ideas? dmesg from still installed system: OpenBSD 5.7-current (GENERIC) #760: Thu Apr 2 11:18:47 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 Mobile CPU 1.80GHz (GenuineIntel 686-class) 1.80 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PERF Turn on NX (Execute Disable) support in your BIOS or wait for the next snapshot. -ml real mem = 2146852864 (2047MB) avail mem = 2099503104 (2002MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: date 05/15/03, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xf7690 (61 entries) bios0: vendor Dell Computer Corporation version A09 date 05/15/2003 bios0: Dell Computer Corporation Latitude C640 acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP acpi0: wakeup devices LID_(S3) PBTN(S4) PCI0(S3) UAR1(S3) USB0(S1) USB1(S1) USB2(S1) MODM(S3) PCIE(S3) MPCI(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (PCIE) acpiprt3 at acpi0: bus -1 (MPCI) acpicpu0 at acpi0acpicpu0: struck PSS entry, core frequency equals last acpicpu0: struck PSS entry, core frequency equals last acpicpu0: invalid _PSS length : C2 acpipwrres0 at acpi0: PADA, resource for ADPT acpitz0 at acpi0: critical temperature is 99 degC acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model LIP8120DLP serial 5184 type LION oem Sony Corp. acpibat1 at acpi0: BAT1 not present acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PBTN acpibtn2 at acpi0: SBTN acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ bios0: ROM list: 0xc/0xf000 0xcf000/0x800! 0xcf800/0x800! cpu0 at mainbus0: (uniprocessor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82845 Host rev 0x04 intelagp0 at pchb0 agp0 at intelagp0: aperture at 0xe800, size 0x400 ppb0 at pci0 dev 1 function 0 Intel 82845 AGP rev 0x04 pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 ATI Radeon Mobility M7 rev 0x00 drm0 at radeondrm0 radeondrm0: irq 11 uhci0 at pci0 dev 29 function 0 Intel 82801CA/CAM USB rev 0x02: irq 11 ppb1 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x42 pci2 at ppb1 bus 2 xl0 at pci2 dev 0 function 0 3Com 3c905C 100Base-TX rev 0x78: irq 11, address 00:08:74:48:40:d6 exphy0 at xl0 phy 24: 3Com internal media interface cbb0 at pci2 dev 1 function 0 TI PCI1420 CardBus rev 0x00: irq 11 cbb1 at pci2 dev 1 function 1 TI PCI1420 CardBus rev 0x00: irq 11 ath0 at pci2 dev 3 function 0 Atheros AR2413 rev 0x01: irq 11 ath0: AR2413 7.8 phy 4.5 rf 5.6 eeprom 5.2, WOR3W, address 00:16:cf:53:07:71 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 4 device 0 cacheline 0x8, lattimer 0x20 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 5 device 0 cacheline 0x8, lattimer 0x20 pcmcia1 at cardslot1 ichpcib0 at pci0 dev 31 function 0 Intel 82801CAM LPC rev 0x02 pciide0 at pci0 dev 31 function 1 Intel 82801CAM IDE rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: Hitachi HTS541080G9AT00 wd0: 16-sector PIO, LBA, 76319MB, 156301488 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus1 at atapiscsi0: 2 targets cd0 at scsibus1 targ 0 lun 0: TOSHIBA, DVD-ROM SD-C2612, 1D21 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 auich0 at pci0 dev 31 function 5 Intel 82801CA/CAM AC97 rev 0x02: irq 11, ICH3 AC97 ac97: codec id 0x4352595b (Cirrus Logic CS4205 rev 3) ac97: codec features mic channel, tone, simulated stereo, bass boost, 20 bit DAC, 18 bit ADC, SRS 3D audio0 at auich0 Intel 82801CA/CAM Modem rev 0x02 at pci0 dev 31 function 6 not configured usb0 at uhci0: USB revision 1.0 uhub0 at usb0 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 wsmouse1 at pms0 mux 0 pms0: Synaptics
Re: lidsuspend results in reboot
On Wed, Apr 29, 2015 at 11:18:05PM +0200, frantisek holop wrote: since the apr 24 snapshot, doing a lidsuspend results in a reboot when raising the lid. this has worked as recently back as the 12 april snapshot. can anybody reproduce this? Please try a later snapshot as there were various resume fixes that went in around the 26th. -ml OpenBSD 5.7-current (GENERIC.MP) #834: Fri Apr 24 00:00:30 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF real mem = 2137341952 (2038MB) avail mem = 2090110976 (1993MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: date 03/31/11, BIOS32 rev. 0 @ 0xfd690, SMBIOS rev. 2.4 @ 0xe0010 (67 entries) bios0: vendor LENOVO version 7BETD8WW (2.19 ) date 03/31/2011 bios0: LENOVO 1705CTO acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 97 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4629 serial 327 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpibat2 at acpi0: BAT2 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) bios0: ROM list: 0xc/0xea00! 0xcf000/0x1000 0xd/0x1000 0xdc000/0x4000! 0xe/0x1! cpu0: Enhanced SpeedStep 1663 MHz: speeds: 1667, 1333, 1000 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GM Video rev 0x03 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: msi azalia0: codecs: Analog Devices AD1981HD, 0x/0x, using Analog Devices AD1981HD audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 1 int 20 pci1 at ppb0 bus 2 em0 at pci1 dev 0 function 0 Intel 82573L rev 0x00: msi, address 00:16:d3:b6:19:57 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 1 int 21 pci2 at ppb1 bus 3 ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02: apic 1 int 22 pci3 at ppb2 bus 4 ppb3 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x02: apic 1 int 23 pci4 at ppb3 bus 12 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 1 int 16 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 1 int 17 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: apic 1 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 1 int 19 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: apic 1 int 19 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe2 pci5 at ppb4 bus 21 cbb0 at pci5 dev 0 function 0 Ricoh 5C476 CardBus rev 0xb4: apic 1 int 16 Ricoh 5C552 Firewire rev 0x09 at pci5 dev 0 function 1 not configured sdhc0 at pci5 dev 0 function 2 Ricoh 5C822 SD/MMC rev 0x18: apic 1 int 18 sdmmc0 at sdhc0
Re: acpi0: failed to allocate hibernate memory
On Fri, Apr 17, 2015 at 04:23:36PM +0200, Alessandro DE LAURENZIS wrote: Dear misc@ readers, I'm facing intermittent failures during hibernation on my Thinkpad R61. The relevant info in the dmesg [1] is: acpi0: failed to allocate hibernate memory This is a very recent snapshot, but I'm not able to confirm that the problem is new, 'cause I rarely use the suspend-to-disk feature. On the other hand, most of the times the hibernation (and resume) phase completes correctly (and I didn't find out what is triggering the fault). When it occurs, only a reboot can recover the correct behavior. TL;DR - known issue on some machines, it's about as good as it's going to get for a while. Thanks for the report. Hibernate allocates a 16MB area of memory on suspend, that will subsequently be available to be used later, during resume. We use this area for staging and unpacking the compressed memory image. We have to allocate it up front because we won't know on resume what areas are free and what areas will end up having real data restored into them. If you don't have 16MB contiguous memory free at time of hibernate, we abort with the message you noted above. As you use the machine, memory becomes more fragmented over time. There is a chance, especially on a 2GB RAM machine, that you won't have 16MB contiguous free anymore, and thus the hibernate request fails. Further complicating matters is the fact that the hibernate memory area being requested here is subject to certain alignment restrictions making the number of places the area can be placed in memory even lower. As we enter the hibernate sequence, we toss out just about everything we can, to help reduce the potential for this problem. But sometimes there are pages sprinkled around physical memory that we can't toss out that end up breaking the contiguous ranges. I'm pretty sure that's what's happening here. For what it's worth, we've seen this even on machines with more memory, it is just a matter of time before it happens on any given machine. There are a few things we could possibly do here to avoid this, like allocate discontiguous memory, or reserve the 16MB on boot. The problem with the former approach is that it is pretty tricky to do in the constraints of the subsystem presently (we are running out of bookkeeping space in the hibernate signature block which is where we'd need to store that info). The preallocation approach penalizes low-memory machines or machines that will never be hibernated. Neither approach is something I've got on the short list presently. If I had infinite time, I'd probably pursue the first approach and increase the size of the signature block at the same time. That's not a trivial amount of work though. Right now, short of fixing the problem in code by using one of the approaches outlined above or perhaps another way I'm not thinking of, your best bet is to add more memory if you can, to postpone the problem a bit. But like I said above, that's not a guarantee you won't see the problem again someday. PS if anyone wanted to tackle the discontiguous allocation approach, let me know off list and I can point you to where to get started. -ml Some additional info: - vmstat -m output: Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 1619158 3895476144731280 1295 32 4222 70421189555 640 11697 64 3398 10826711838 320 24330 128 7986 12621415473 160 5106 256 2220 12361093678 80 4008 512 2743241 504121 40 1193 1024 1772548 235523 20 63410 2048 149137 26169 10 8961 4096 622238 154197 5 143961 8192 25 10 9331 5 5072 163845 0160 5 0 32768 11 0 39 5 0 655367 0 170701 5 0 1310721 0109 5 0 2621443 0 50 5 0 Memory usage type by bucket size Size Type(s) 16 devbuf, pcb, routetbl, UFS mount, dirhash, ACPI, exec, VM swap, UVM amap, UVM aobj, USB, USB device, temp, DRM 32 devbuf, pcb, routetbl, ifaddr, sem, dirhash, ACPI, in_multi, exec, UVM amap, UVM aobj, USB, USB device, temp, AGP Memory, DRM 64 devbuf, routetbl, ifaddr, sysctl, vnodes, UFS mount, dirhash, ACPI, proc, VFS cluster, in_multi, ether_multi, VM swap, UVM amap, UVM aobj, USB, USB device, NDP, temp, DRM 128 devbuf, pcb, routetbl, UFS mount, sem, dirhash, ACPI, NFS srvsock, in_multi, ttys, pfkey data, inodedep, UVM amap, UVM aobj, USB,
Re: ThinkPad X1 Carbon Gen3
On Sat, Jun 27, 2015 at 12:37:23PM +0900, Masao Uebayashi wrote: - zzz - I can almost resume it from RAM with Security Chip (TPM) disabled in the BIOS setting. Except display remains off. With TPM enabled, I couldn't power on the machine after suspend to RAM. - ZZZ - Disabling TPM doesn't help hibernation. - I tried disabling various devices (iwm, em, xhci, ehci, ...). Didn't help instability of hibernation. - Most failures are not recognizing hibernation (`/ was not properly unmounted') - Unhibernation succeeds when you are really lucky. :) Does it start to unpack the hibernated image, then reboot? Or does it not find any image in the signature block? (eg failed to write out the image?) Your bug report leaves a lot to be desired. -ml
Re: panic during boot of 5.7 in de(4) running in Hyper-V
On Tue, Jun 23, 2015 at 02:57:51PM -0600, Tom Schutter wrote: I installed 5.7 from http://ftp3.usa.openbsd.org/pub/OpenBSD/5.7/amd64/install57.iso in a Windows Server 2012 R2 Hyper-V VM using the Legacy Network Adapter. I always get a kernel panic in the de(4) driver during boot. If I remove the legacy NIC from the VM config, then I successfully boot, but obviously with no network access. I looked into this last year but lost interest. It seems like the DMA buffer is being placed past the UVM constraint for DMA ( eg 4GB). I'm not sure why that's happening, I only spent a day or so looking at it before I got bored and moved on to something else. A side note - the same config on hyperV seems to work on i386, but I noticed some strange clock skewing using that config so I gave up on that also. Another side note - disabling de(4) in config and letting the kernel fall back to dc(4) gets past this particular panic but doesn't allow any traffic to pass. -ml What additional information can I provide to help with diagnosis and create a proper bug report? OpenBSD/amd64 BOOT 3.28 ... wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) de0 at pci0 dev 10 function 0 DEC 21140 rev 0x20panic: Non dma-reachable buffer at curaddr 0x107762b70(raw) Stopped at Debugger+0x9: leave Debugger() at Debugger+0x9 panic() at panic+0xfe _bus_dmamap_load_buffer() at _bus_dmamap_load_buffer+0x1b6 _bus_dmamap_load() at _bus_dmamap_load+0x7f tulip_busdma_init() at tulip_busdma_init+0xa0 tulip_attach() at tulip_attach+0x2a4 config_attach() at config_attach+0x1bc pci_probe_device() at pci_probe_device+0x467 pci_enumerate_bus() at pci_enumerate_bus+0xe9 config_attach() at config_attach+0x1bc end trace frame: 0x81a28e60, count: 0 RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb trace Debugger() at Debugger+0x9 panic() at panic+0xfe _bus_dmamap_load_buffer() at _bus_dmamap_load_buffer+0x1b6 _bus_dmamap_load() at _bus_dmamap_load+0x7f tulip_busdma_init() at tulip_busdma_init+0xa0 tulip_attach() at tulip_attach+0x2a4 config_attach() at config_attach+0x1bc pci_probe_device() at pci_probe_device+0x467 pci_enumerate_bus() at pci_enumerate_bus+0xe9 config_attach() at config_attach+0x1bc cpu_configure() at cpu_configure+0x1b main() at main+0x3df end trace frame: 0x0, count: -14 ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND *0 -1 0 0 7 0x10200 swapper -- Tom Schutter
Re: overheating thinkpad after resume
On Tue, Apr 14, 2015 at 10:41:56PM +0200, frantisek holop wrote: hello, i have hinted about this issue before, but it is becoming something that quite bothers me, so i thought i might ask for help. i have a thinkpad x60s. after resuming from lidsuspend, for no apparent reason the temperature keeps hanging around 70-71. if i make a reboot, it will go back to 55. not all resumings result in this higher temperature, but once it happens, it seems to keep this state after multiple lidsuspends, again, until reboot. any ideas how to track this down? no rogue interrupts, no high cpu usage... Might want to try -current, a big fix for temperature / power just went in. -ml 2 usersLoad 1.25 1.16 1.14 (1-25 of 31)Tue Apr 14 22:32:59 2015 SENSOR VALUE STATUS DESCRIPTION acpitz0.temp0 54.00 degC zone temperature acpitz1.temp0 72.00 degC zone temperature acpibtn0.indicator0On lid open acpibat0.volt0 14.40 V DC voltage acpibat0.volt1 16.43 V DC current voltage acpibat0.power00.00 W rate acpibat0.watthour0 21.75 Wh last full capacity acpibat0.watthour11.09 Wh warning capacity acpibat0.watthour20.20 Wh low capacity acpibat0.watthour3 20.91 WhOKremaining capacity acpibat0.watthour4 28.80 Wh design capacity acpibat0.raw0 0 rawOKbattery idle acpiac0.indicator0 On power supply acpithinkpad0.temp054.00 degC acpithinkpad0.temp144.00 degC acpithinkpad0.temp351.00 degC acpithinkpad0.temp432.00 degC acpithinkpad0.temp631.00 degC acpithinkpad0.fan0 3090 RPM acpidock0.indicator0 Off unknown not docked cpu0.temp0 72.00 degC aps0.temp0 44.00 degC aps0.temp1 44.00 degC aps0.indicator0 Off Keyboard Active aps0.indicator1 Off Mouse Active aps0.indicator2On Lid Open aps0.raw0 465 raw X_ACCEL aps0.raw1 512 raw Y_ACCEL aps0.raw2 465 raw X_VAR aps0.raw3 512 raw Y_VAR softraid0.drive0 onlineOKsd1 load averages: 1.51, 1.27, 1.18 61 processes: 1 running, 58 idle, 2 on processor CPU0 states: 0.0% user, 0.0% nice, 0.2% system, 0.0% interrupt, 99.8% idle CPU1 states: 3.8% user, 0.0% nice, 2.2% system, 0.0% interrupt, 94.0% idle Memory: Real: 341M/865M act/tot Free: 1129M Cache: 365M Swap: 0K/2252M PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND 29231 _x11 20 15M 25M sleep select5:30 4.64% Xorg 22368 f 20 246M 263M run poll 10:48 0.78% firefox 13203 f 20 2488K 3556K sleep kqread1:41 0.63% tmux 24019 _sndio 2 -20 440K 956K idle poll 2:33 0.00% sndiod 10611 f 20 3620K 13M sleep poll 1:16 0.00% gkrellm ... $ vmstat -i interrupt total rate irq0/clock4465583 199 irq0/ipi 8587915 384 irq130/acpi0 44740 irq81/inteldrm0 18890 irq160/azalia01437612 64 irq85/ppb0 10 irq83/uhci2 10 irq84/uhci3460 irq84/ehci0911663 40 irq80/ahci0 1419214 63 irq129/pckbc0 220 irq131/pckbc0 920 Total16828512 753 OpenBSD 5.7-current (GENERIC.MP) #798: Sun Apr 12 01:37:34 MDT 2015 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Core(TM) Duo CPU L2400 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM,PERF real mem = 2137341952 (2038MB) avail mem = 2090119168 (1993MB) mpath0 at root scsibus0 at
Re: hp laptop: acpi - power adapter problem
On Mon, Jun 15, 2015 at 11:17:04PM +0200, Riccardo Mottola wrote: Hi, on my HP laptop (dmesg below) I notice that both with acpi and with apm, it is always reported that the power adapter is connected, even if it is not. The power level of the battery seems reasonable. Can you send an acpidump please? -ml With power cord attached: hw.sensors.acpitz0.temp0=56.00 degC (zone temperature) hw.sensors.acpiac0.indicator0=On (power supply) hw.sensors.acpibat0.volt0=14.80 VDC (voltage) hw.sensors.acpibat0.volt1=12.48 VDC (current voltage) hw.sensors.acpibat0.current0=unknown (rate), UNKNOWN hw.sensors.acpibat0.amphour0=4.10 Ah (last full capacity) hw.sensors.acpibat0.amphour1=0.21 Ah (warning capacity) hw.sensors.acpibat0.amphour2=0.12 Ah (low capacity) hw.sensors.acpibat0.amphour3=4.10 Ah (remaining capacity), OK hw.sensors.acpibat0.amphour4=6.00 Ah (design capacity) hw.sensors.acpibat0.raw0=0 (battery full), OK hw.sensors.acpibtn2.indicator0=On (lid open) Without: hw.sensors.acpitz0.temp0=56.00 degC (zone temperature) hw.sensors.acpiac0.indicator0=On (power supply) hw.sensors.acpibat0.volt0=14.80 VDC (voltage) hw.sensors.acpibat0.volt1=11.84 VDC (current voltage) hw.sensors.acpibat0.current0=unknown (rate), UNKNOWN hw.sensors.acpibat0.amphour0=4.10 Ah (last full capacity) hw.sensors.acpibat0.amphour1=0.21 Ah (warning capacity) hw.sensors.acpibat0.amphour2=0.12 Ah (low capacity) hw.sensors.acpibat0.amphour3=4.00 Ah (remaining capacity), OK hw.sensors.acpibat0.amphour4=6.00 Ah (design capacity) hw.sensors.acpibat0.raw0=1 (battery discharging), OK hw.sensors.acpibtn2.indicator0=On (lid open) acpiac0 seems wrong to me. Riccardo OpenBSD 5.7 (GENERIC.MP) #881: Sun Mar 8 11:04:17 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2129461248 (2030MB) avail mem = 2068914176 (1973MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xdc010 (19 entries) bios0: vendor Hewlett-Packard version F.58 date 06/16/2008 bios0: Hewlett-Packard HP Pavilion dv6500 Notebook PC acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET MCFG TMOR APIC BOOT SLIC SSDT SSDT SSDT SSDT acpi0: wakeup devices PWRB(S4) PXSX(S3) PXSX(S4) PS2K(S3) PS2M(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz, 2394.68 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz, 2194.75 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEGP) acpiprt2 at acpi0: bus 2 (RP01) acpiprt3 at acpi0: bus 4 (RP02) acpiprt4 at acpi0: bus 8 (RP06) acpiprt5 at acpi0: bus 9 (PCIB) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0acpitz0: THR1: failed to read _CRT acpitz0: THR1: failed to read _CRT : no critical temperature defined acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model Primary serial type LION oem Hewlett-Packard acpibtn2 at acpi0: LID_ acpivideo0 at acpi0: VGA_ acpivout0 at acpivideo0: LCD_ acpivideo1 at acpi0: GFX0 cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2201, 2200, 1600, 1200, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel GM965 Host rev 0x0c ppb0 at pci0 dev 1 function 0 Intel GM965 PCIE rev 0x0c: msi pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 NVIDIA GeForce 8400M GS rev 0xa1 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) uhci0 at pci0 dev 26 function 0 Intel 82801H USB rev 0x03: apic 2 int 16 uhci1 at pci0 dev 26 function 1 Intel 82801H USB rev 0x03: apic 2 int 21 ehci0 at pci0 dev 26 function 7 Intel 82801H USB rev 0x03: apic 2 int 18 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801H HD Audio rev 0x03: msi azalia0: codecs:
Re: Why does my 5.7 laptop suspend when I close the lid?
On Tue, Jun 30, 2015 at 04:28:52PM -0400, Alan Corey wrote: Yes it was harsh, but I still don't know how to resume and I didn't appreciate having to do an unclean shutdown by holding down the power button for 10 seconds. Neither the apm or acpi man pages says how to resume (or mentions lid), I guess it depends on the hardware. I've been using OpenBSD since 2.7 and I don't like surprises. I close the Then stay on 2.7. Problem solved. You'll not be subjected to any more surprises that way. -ml lids on my laptops to carry them or use them as a writing surface. With my past few Dell laptops sound didn't work after suspend so I stopped using it. My newest is from 2008 so it didn't seem worth mentioning. I don't remember seeing the option to enable or disable in the install, it reminded me of something Windows might do. Yes, it's machdep.lidsuspend=0 to turn it off. I thought there used to be an apm.con or acpi.conf, I looked for those first. On 6/30/15, Eric Furman ericfur...@fastmail.net wrote: A lot of people worked very hard to add this feature, because most people wanted it. Search the archives On Tue, Jun 30, 2015, at 02:38 PM, Alan Corey wrote: I didn't ask it to do that and I don't know how to unsuspend. As far as I'm concerned this is an undocumented feature. If I want to suspend I'll type zzz. I haven't found a way to turn this off. -- Credit is the root of all evil. - AB1JX -- Credit is the root of all evil. - AB1JX
Re: ThinkPad X1 Carbon Gen3
On Sun, Jun 28, 2015 at 10:39:12AM +0900, Masao Uebayashi wrote: On Sat, Jun 27, 2015 at 11:45:01AM -0700, Mike Larkin wrote: On Sat, Jun 27, 2015 at 12:37:23PM +0900, Masao Uebayashi wrote: - zzz - I can almost resume it from RAM with Security Chip (TPM) disabled in the BIOS setting. Except display remains off. With TPM enabled, I couldn't power on the machine after suspend to RAM. - ZZZ - Disabling TPM doesn't help hibernation. - I tried disabling various devices (iwm, em, xhci, ehci, ...). Didn't help instability of hibernation. - Most failures are not recognizing hibernation (`/ was not properly unmounted') - Unhibernation succeeds when you are really lucky. :) Does it start to unpack the hibernated image, then reboot? I've tried 50 ZZZ and never seen this (reboot). I also believe that in some cases, unpacking failed and booted normally. Or does it not find any image in the signature block? (eg failed to write out the image?) Yes. (As mentioned above; ``not recognizing hibernation''.) Success ratio is like 10%. Still no proper bug report though. I've officially lost interest. -ml
Re: Why does my 5.7 laptop suspend when I close the lid?
On Fri, Jul 03, 2015 at 11:45:44AM +0900, Joel Rees wrote: FWIW, I just tried shutting the lid on this netbook, to see what would happen. Disks went quiet quickly enough to assume it was sleep and not hibernate. I waited maybe a minute, then opened the lid. No response. On keyboard activity, i could hear the disks spin up. Tried ssh from outside, but I had disabled password access and hadn't copied the relevant tokens to the other box. Did get a Permission denied (publickey, keyboard-interactive) response once, but a few minutes later, there was no route to host. I woud guess it went back to sleep and wouldn't wake up, except this time the disks did not go quiet. Ended up with a long press on the power button. This: vga1 at pci0 dev 1 function 0 vendor ATI, unknown product 0x9839 rev 0x00 ... is likely your problem. We can't resume something we don't even properly work with to begin with. One thing is to try 'ZZZ' which will hibernate the machine and will repost video properly on resume (usually, no promises here either). -ml Is this failure of the screen to wake up likely to be caused by my putting off installing something to manage sleep states? Is it perhaps a result of some BIOS setting? (Guess I should poke around in there.) Some of the contents of /var/log, in case anyone is interested: In /var/log/Xorg.0.log.old, these lines seem relevant. (Should I post more?): -- [ 1251.334] (==) ws: /dev/wsmouse: Buttons: 7 [ 1251.334] (**) ws: /dev/wsmouse: YAxisMapping: buttons 4 and 5 [ 1251.334] (II) XINPUT: Adding extended input device /dev/wsmouse (type: MOUSE, id 8) [ 1251.334] (**) /dev/wsmouse: (accel) keeping acceleration scheme 1 [ 1251.335] (**) /dev/wsmouse: (accel) acceleration profile 0 [ 1251.335] (**) /dev/wsmouse: (accel) acceleration factor: 2.000 [ 1251.335] (**) /dev/wsmouse: (accel) acceleration threshold: 4 [ 6931.125] (II) VESA(0): Setting up VESA Mode 0x1D4 (1366x768) [ 6931.127] (II) VESA(0): VBESetVBEMode failed [ 6931.128] (EE) Fatal server error: [ 6931.128] (EE) EnterVT failed for screen 0 [ 6931.128] (EE) [ 6931.128] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 6931.128] (EE) Please also check the log file at /var/log/Xorg.0.log for additional information. [ 6931.128] (EE) [ 6931.129] (EE) ws: /dev/wsmouse: unknown command 4 -- /var/log/messages from around that point look like this. (Again, should I post more?): -- Jul 3 08:18:37 phool savecore: no core dump Jul 3 09:00:01 phool syslogd: restart Jul 3 10:07:50 phool /bsd: uhub0 detached Jul 3 10:13:59 phool /bsd: uhub3 detached Jul 3 10:13:59 phool /bsd: video0 detached Jul 3 10:13:59 phool /bsd: uvideo0 detached Jul 3 10:13:59 phool /bsd: uhub1 detached Jul 3 10:13:59 phool /bsd: uhub4 detached Jul 3 10:13:59 phool /bsd: uhub2 detached Jul 3 10:13:59 phool /bsd: uhub0 at usb0 AMD xHCI root hub rev 3.00/1.00 addr 1 Jul 3 10:13:59 phool /bsd: uhub1 at usb3 AMD OHCI root hub rev 1.00/1.00 addr 1 Jul 3 10:13:59 phool /bsd: uhub2 at usb1 AMD EHCI root hub rev 2.00/1.00 addr 1 Jul 3 10:13:59 phool /bsd: uhub3 at usb4 AMD OHCI root hub rev 1.00/1.00 addr 1 Jul 3 10:13:59 phool /bsd: uhub4 at usb2 AMD EHCI root hub rev 2.00/1.00 addr 1 Jul 3 10:13:59 phool /bsd: uvideo0 at uhub2 Jul 3 10:13:59 phool /bsd: port 4 configuration 1 interface 0 Generic HP Webcam-50 rev 2.00/5.26 addr 2 Jul 3 10:13:59 phool /bsd: video0 at uvideo0 Jul 3 10:25:27 phool /bsd: splassert: assertwaitok: want 0 have 9 Jul 3 10:27:26 phool /bsd: splassert: bufcache_take: want 6 have 9 Jul 3 10:29:27 phool /bsd: splassert: buf_acquire: want 6 have 9 Jul 3 10:31:27 phool /bsd: splassert: buf_map: want 6 have 9 Jul 3 10:33:27 phool /bsd: splassert: reassignbuf: want 6 have 9 Jul 3 10:35:27 phool /bsd: splassert: buf_release: want 6 have 9 Jul 3 10:40:36 phool syslogd: start Jul 3 10:40:36 phool /bsd: OpenBSD 5.7-current (GENERIC_GPT.MP) #0: Sun Jun 14 23:13:31 JST 2015 Jul 3 10:40:36 phool /bsd: r...@phool.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC_GPT.MP Jul 3 10:40:36 phool /bsd: real mem = 1835790336 (1750MB) Jul 3 10:40:36 phool /bsd: avail mem = 1776336896 (1694MB) Jul 3 10:40:36 phool /bsd: mpath0 at root Jul 3 10:40:36 phool /bsd: scsibus0 at mpath0: 256 targets Jul 3 10:40:36 phool /bsd: mainbus0 at root Jul 3 10:40:36 phool /bsd: bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe4800 (43 entries) Jul 3 10:40:36 phool /bsd: bios0: vendor Insyde version F.0A date 07/16/2014 Jul 3 10:40:36 phool /bsd: bios0: Hewlett-Packard HP Pavilion 10 Notebook PC Jul 3 10:40:36 phool /bsd: acpi0 at bios0: rev 2 Jul 3 10:40:36 phool /bsd: acpi0: sleep states S0 S3 S4 S5 Jul 3 10:40:36 phool /bsd: acpi0: tables DSDT FACP UEFI HPET APIC MCFG ASF! BOOT FPDT MSDM SSDT SSDT SSDT SSDT SSDT Jul 3 10:40:36 phool /bsd: acpi0:
