Panic - sensor installed twice
I just installed a new snapshot and gave the system a reboot. Unfortunately the kernel panicked with an interesting message: sensor installed twice. I guess this panic is intended because of a commit (1.31) to src/sys/kern/kern_sensors.c a couple of days ago. A trace, etc. is included below. I tend to believe that this panic has something to do with lm as disabling this device solves the issue described. Dmesg show something interesting: lm2 at wbsio0 port 0xca0/8: W83627DHG lm1: disabling sensors due to alias with lm2 I have no idea what this means. Perhaps registration of lm1 and lm2 counts as a double install of a sensor? Any ideas how to solve this issue without disabling lm? -- Björn Ketelaars GPG key: 0x4F0E5F21 Loading. probing: pc0 com0 com1 mem[613K 2037M a20=on] OpenBSD/amd64 BOOT 3.28 booting hd0a:/bsd: 6659808+2126028+247720+0+592960 [72+553368+368348]=0xa10f80 entry point at 0x1000160 [7205c766, 3404, 24448b12, 8fe0a304] [ using 922432 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 Auto-DetThe Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org S.M.A.R.T. Capable and Status OK 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 = 2120744960 (2022MB) avail mem = 2060541952 (1965MB) warning: no entropy supplied by boot loader mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x9ac00 (19 entries) bios0: vendor American Megatrends Inc. version 1.2a date 02/21/12 bios0: Supermicro X7SPA-H acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET GSCI EINJ BERT ERST HEST acpi0: wakeup devices P0P1(S4) PS2K(S4) PS2M(S4) USB0(S4) USB1(S4) USB2(S4) USB5(S4) EUSB(S4) USB3(S4) USB4(S4) USB6(S4) USBE(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(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) Atom(TM) CPU D510 @ 1.66GHz, 1666.88 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 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.67 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 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.67 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 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.67 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 4 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 1, remapped to apid 4 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (P0P1) acpiprt2 at acpi0: bus 1 (P0P4) acpiprt3 at acpi0: bus 2 (P0P8) acpiprt4 at acpi0: bus 3 (P0P9) acpicpu0 at acpi0 acpicpu1 at acpi0 acpicpu2 at acpi0 acpicpu3 at acpi0 acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB ipmi at mainbus0 not configured 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 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 Skipping LVDS initialization for Supermicro X7SPA-H No connectors reported connected with modes Cannot find any crtc or sizes - going 1024x768 inteldrm0: 1024x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel Pineview Video rev 0x02 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x02: apic 4 int 16 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x02: apic 4 int 21 uhci2 at pci0 dev 26 function 2
Re: ping6 to Link Local disturbed by pf set skip?
On 2014-11-07 14:35, Pieter Verberne wrote: My problem: `ping6 fe80::200:24ff:fecd:7df8%pppoe0` with pf disabled is no problem. ping6, with pf enabled and 'set skip on lo0' does not work very well: I could reproduce this very easily with a clean -current installation. OpenBSD 5.6-current (GENERIC) #492: Fri Nov 7 10:21:36 MST 2014 # ifconfig vether0 create # ifconfig vether0 inet 1.1.1.1 255.0.0.0 # ifconfig vether0 inet6 eui64 # ifconfig vether0 vether0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr fe:e1:ba:d0:bd:e1 priority: 0 groups: vether media: Ethernet autoselect status: active inet 1.1.1.1 netmask 0xff00 broadcast 1.255.255.255 inet6 fe80::fce1:baff:fed0:bde1%vether0 prefixlen 64 scopeid 0x5 # ping6 fe80::fce1:baff:fed0:bde1%vether0 PING6(56=40+8+8 bytes) fe80::fce1:baff:fed0:bde1%vether0 -- fe80::fce1:baff:fed0:bde1%vether0 16 bytes from fe80::fce1:baff:fed0:bde1%vether0, icmp_seq=0 hlim=64 time=0.407 ms 16 bytes from fe80::fce1:baff:fed0:bde1%vether0, icmp_seq=24 hlim=64 time=0.216 ms 16 bytes from fe80::fce1:baff:fed0:bde1%vether0, icmp_seq=46 hlim=64 time=0.316 ms 16 bytes from fe80::fce1:baff:fed0:bde1%vether0, icmp_seq=67 hlim=64 time=0.276 ms ^C --- fe80::fce1:baff:fed0:bde1%vether0 ping6 statistics --- 78 packets transmitted, 4 packets received, 94.9% packet loss round-trip min/avg/max/std-dev = 0.216/0.304/0.407/0.069 ms comment out 'set skip on lo' (hmm, default pf.conf says 'lo', not 'lo0') sudo pfctl -f /etc/pf.conf # ping6 fe80::fce1:baff:fed0:bde1%vether0 PING6(56=40+8+8 bytes) fe80::fce1:baff:fed0:bde1%vether0 -- fe80::fce1:baff:fed0:bde1%vether0 16 bytes from fe80::fce1:baff:fed0:bde1%vether0, icmp_seq=0 hlim=64 time=0.215 ms 16 bytes from fe80::fce1:baff:fed0:bde1%vether0, icmp_seq=1 hlim=64 time=0.372 ms ... 16 bytes from fe80::fce1:baff:fed0:bde1%vether0, icmp_seq=35 hlim=64 time=0.218 ms 16 bytes from fe80::fce1:baff:fed0:bde1%vether0, icmp_seq=36 hlim=64 time=0.207 ms ^C --- fe80::fce1:baff:fed0:bde1%vether0 ping6 statistics --- 37 packets transmitted, 37 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.195/0.262/0.391/0.055 ms while ping is running and 'set skip on lo' is set: # pfctl -s all FILTER RULES: block return all pass all flags S/SA block return in on ! lo0 proto tcp from any to any port 6000:6010 STATES: all tcp 192.168.56.2:22 - 192.168.56.1:30613 ESTABLISHED:ESTABLISHED all tcp 192.168.56.2:22 - 192.168.56.1:30698 ESTABLISHED:ESTABLISHED all ipv6-icmp fe80::fce1:baff:fed0:bde1[128] - fe80::fce1:baff:fed0:bde1[6521] 0:0 all ipv6-icmp fe80::fce1:baff:fed0:bde1[6521] - fe80::fce1:baff:fed0:bde1[128] 0:0 all udp 192.168.56.255:137 - 192.168.56.1:137 NO_TRAFFIC:SINGLE INFO: Status: Enabled for 0 days 00:13:27 Debug: err State Table Total Rate current entries5 searches28083.5/s inserts 340.0/s removals 290.0/s Counters match1010.1/s bad-offset 00.0/s fragment 00.0/s short 00.0/s normalize 00.0/s memory 00.0/s bad-timestamp 00.0/s congestion 00.0/s ip-option 00.0/s proto-cksum00.0/s state-mismatch 00.0/s state-insert 420.1/s state-limit00.0/s src-limit 00.0/s synproxy 00.0/s translate 00.0/s TIMEOUTS: tcp.first 120s tcp.opening 30s tcp.established 86400s tcp.closing 900s tcp.finwait 45s tcp.closed 90s tcp.tsdiff 30s udp.first60s udp.single 30s udp.multiple 60s icmp.first 20s icmp.error 10s other.first 60s other.single 30s other.multiple 60s frag 60s interval 10s adaptive.start 6000 states adaptive.end 12000 states src.track 0s LIMITS: stateshard limit1 src-nodes hard limit1 frags hard limit 1536 tableshard limit 1000 table-entries hard limit
devtree: A utility for printing device trees
Hi misc, I've written a small utility for pretty-printing a tree of system devices based on dmesg(8) output. It's nothing fancy, but my apropos(1) and web searches didn't bring up anything to do the job. I thought it might be of interest to other newcomers to OpenBSD like myself who are exploring how the system fits together, so I've put it up on the web: http://www.sjm.so/projects/openbsd_devtree.shtml It also has the potential to provide an easy way to diff the hardware in two different systems, or on the same system running two different OpenBSD versions, since it sorts nodes alphabetically when printing them. I'm not sure if it'd be worth making a port for it, given that it's a single Perl file + man page, but if there's enough interest I'd be happy to try my hand at that.
Re: question about hosts.equiv and ssh
On Fri, Nov 07, 2014 at 09:14:05PM -0500, System Administrator wrote: In OpenBSD 5.6, the prototype and man-page for hosts.equiv(5) have disappeared. However, this file is still referenced in sshd_config(5) and (if I'm searching the sources correctly) in /usr/src/usr.bin/ssh auth-rhosts.c which is included in the sshd/Makefile. Is the removal accidental or an indication that its use is deprecated? If the latter, what is the [new] recommended best practices for HostBasedAuthentication within a cluster of trusted servers? Thanks in advance. hi! back in april i asked about the refs to this file in the ssh docs. damien miller told me hosts.equiv is still relevant to host-based logins using key authentication, and that the reference should definitely stay. and the removal of hosts.equiv(5) was not accidental. i couldn;t comment on best practices, but i believe the docs are correct. it could be that ssh(1) etc. need to explain a bit more about how hosts.equiv work, but i'm not sure. jmc
Re: devtree: A utility for printing device trees
On 11/08/2014 03:21 AM, Steven McDonald wrote: t my apropos(1) and web searches didn't bring up anything to do the job. Might have been a keyword issue. In KDE there is Kinfocenter. There is also lsdev and lspci with the -t option. -- Those who do not understand Unix are condemned to reinvent it, poorly.
devtree: A utility for printing device trees
There is also dmassage -t which is a package that can be installed.
Re: Remove print/acroread
I'd like to rm print/acroread from cvs. I don't see the point of keeping it, while we have other working pdf readers. I don't even understand why we have it at all. OK to remove it. You don't use pdf form filling. Over the last few years, I've seen people want to do strange things with pdf. Most things related to display work with default tools. afaik, password did not work with anything BUT acrobat reader AND now mutools. Can you please share an example of filling a PDF form with mutools?
Re: CVS: cvs.openbsd.org: src
On 24.10.2014 00:33, Robert Peichaer wrote: CVSROOT:/cvs Module name:src Changes by: r...@cvs.openbsd.org2014/10/23 15:33:21 Modified files: distrib/miniroot: dot.profile install.sub distrib/notes : m4.common share/man/man8 : autoinstall.8 Log message: Extend autoinstall(8) feature: - Ask for responsefile location (url or local path) if dhcp discovery fails for location or mode. If 'next-server' is found in dhcp lease file, provide a default url http://next-server/install.conf. - Ask for installer mode if the specified response file name does not match *install.conf or *upgrade.conf. - If present, use /auto_install.conf or /auto_upgrade.conf as response file for unattended installation or upgrade. - Automatically start installer in unattended mode if either one of these files is present when the system boots. - Document changes in manpage and installation notes. OK krw@ deraadt@ I'm following -current and decided to try autoinstall(8) from /auto_upgrade.conf when I moved to newer snapshot. I made a custom auto_upgrade.conf on my root [sd2a] partition but when I boot a newer bsd.rd, auto_upgrade.conf is not on the miniroot. I escaped to shell, mounted sd2a on /mnt and copied auto_upgrade.conf to miniroot. Then Autoupgrade completed as it should. The question is whether there are any easier steps to make auto_upgrade from local file, not by using dhcp/tftp/http? Thanks, Atanas
search mailing list
Is there an archive of the mailing list that is keyword searchable? thanks
Re: search mailing list
On Sat, Nov 08, 2014 at 03:21:00PM -0600, Edgar Pettijohn wrote: Is there an archive of the mailing list that is keyword searchable? http://www.openbsd.org/mail.html At the bottom of the page. The first two entries. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: CVS: cvs.openbsd.org: src
On Sat, 08 Nov 2014 22:57:41 +0200 Atanas Vladimirov vl...@bsdbg.net wrote:
On 24.10.2014 00:33, Robert Peichaer wrote:
CVSROOT:/cvs
Module name:src
Changes by: r...@cvs.openbsd.org2014/10/23 15:33:21
Modified files:
distrib/miniroot: dot.profile install.sub
distrib/notes : m4.common
share/man/man8 : autoinstall.8
Log message:
Extend autoinstall(8) feature:
- Ask for responsefile location (url or local path) if dhcp discovery
fails for location or mode. If 'next-server' is found in dhcp lease
file, provide a default url http://next-server/install.conf.
- Ask for installer mode if the specified response file name does not
match *install.conf or *upgrade.conf.
- If present, use /auto_install.conf or /auto_upgrade.conf as response
file for unattended installation or upgrade.
- Automatically start installer in unattended mode if either one of
these files is present when the system boots.
- Document changes in manpage and installation notes.
OK krw@ deraadt@
I'm following -current and decided to try autoinstall(8) from
/auto_upgrade.conf when I moved to newer snapshot.
I made a custom auto_upgrade.conf on my root [sd2a] partition but when I
boot a newer bsd.rd,
auto_upgrade.conf is not on the miniroot. I escaped to shell, mounted
sd2a on /mnt and copied auto_upgrade.conf to miniroot.
Then Autoupgrade completed as it should.
The question is whether there are any easier steps to make auto_upgrade
from local file, not by using dhcp/tftp/http?
Thanks,
Atanas
you can make your own bsd.rd. this is a method i have used for custom
auto-installs for years (among other uses).
make sure to get the src{,sys}.tar.gz files for whatever snapshot you are
using.
# cp auto_upgrade.conf /usr/src/distrib/miniroot/
to '/usr/src/distrib/miniroot/list', add the line:
COPY${CURDIR}/auto_upgrade.conf auto_upgrade.conf
# cd /usr/src make obj
# cd /usr/src/distrib/special/libstubs make
# cd /usr/src/distrib/`arch -s`/ramdisk_cd make
this should leave you with with a bsd.rd in obj/, just drop it in as a
replacement for the install one.
Question about /etc/mail post 5.6 upgrade
Hello, I recently upgraded from 5.5 to 5.6. I was surprised to see that the various apparently sendmail-specific files in /etc/mail are not in the ‘Files to delete and move’ list in upgrade56.html, now that sendmail is no longer in base. I suspect that either there are other reasons to keep the contents of this directory as-is post 5.6 upgrade, or I missed a step in the upgrade guide. I’m new to OpenBSD, so clue sticks are welcome. - Eric
