Re: dual separator?
Hi, On Fri, Aug 22, 2014 at 12:17:54PM -0500, Adam Thompson wrote: > On 14-08-22 12:09 PM, Claus Assmann wrote: > >On Fri, Aug 22, 2014, Adam Thompson wrote: > >>I have a large number of email "tags", but use both "+" and "-" as a > >>separator. > >>So far, I'm entering all the "-" ones into aliases; is there a better way to > >>do this? > >>In postfix, I was able to use a regex to manipulate incoming addresses to > >Hmm, it might be help to answer your question if you tell us which MTA > >you are using... (or you could switch to postfix...) > > Oops... that was meant to go to m...@opensmtpd.org, not misc@openbsd.org. > That should have made it blindingly obvious, but I'm now using smtpd(8). > And I've also discovered that the RHS in aliases(5) must be a bare userid, > and putting a "+" in there causes newaliases(8) to fail. Not sure why that > would be intended behaviour, but not sure it's a bug either. > There is currently no way of specifying the delimiter, it can only be + someone opened a ticket on our tracker and after we discuss it it might change -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: kernel page fault on 55-release
On 30/08/14(Sat) 12:28, ludovic coues wrote:
> 2014-08-30 11:58 GMT+02:00 Martin Pieuchot :
> > On 30/08/14(Sat) 11:46, ludovic coues wrote:
> >> 2014-08-30 10:53 GMT+02:00 Martin Pieuchot :
> >> > Hello Ludovic,
> >> >
> >> > On 28/08/14(Thu) 20:52, ludovic coues wrote:
> >> >> Hello,
> >> >>
> >> >> Recently, I get a kernel page fault every time I try to use the
> >> >> micronucleus [1] command line tool. It 's for uploading an hex file to
> >> >> ATtiny processor, much like arduino's avrude. The crash is pretty
> >> >> consistent, occuring every time I run `micronucleus --run`.
> >> >> I've managed to use it with success in the past on this machine with
> >> >> 55-release so it might be hardware related. I added a realtek wireless
> >> >> device since last time I've get a successful run with micronucleus.
> >> >>
> >> >> I get the following message when I run it:
> >> >> uvm_fault(0x81daaf001, 0x2, 2, 0, 1) -> e
> >> >> kernel: page fault trap, code=0
> >> >> Stopped at usbd_get_cdesc+035: movzwl 0x2 (%rax),%eax
> >> >>
> >> >> It's followed by the debugger prompt. I don't know how what to do from
> >> >> that point. I'm willing to spend time tracking the source of the
> >> >> problem but I have no idea of what I'm looking for.
> >> >
> >> > Thanks for reporting the problem. I believe this is the same issue that
> >> > has been reported by Thomas Pfaff in February [0] and fixed post 5.5 [1].
> >> >
> >> > Could you try a snapshot and tell me if you can still reproduce it?
> >> >
> >> > Cheers,
> >> > Martin
> >> >
> >> > [0] http://marc.info/?l=openbsd-bugs&m=139135208628637&w=2
> >> > [1] http://marc.info/?l=openbsd-cvs&m=139194643911061&w=2
> >>
> >> I might have failed to upgrade to snapshot but I still have the error.
> >> Right now, I got the snapshot install56.fs file, used it to run an
> >> upgrade and run sysmerge. I must have done something right as
> >> start_daemon isn't available anymore in /etc/rc.local but the error is
> >> still present.
> >
> > In this case could you send me your dmesg, the output of "usbdevs -dv"
> > and the trace when the trap occurs?
>
Thanks Ludovic,
> usbdevs -dv:
> [...]
> port 4 addr 3: high speed, power 100 mA, unconfigured,
> RTL8187B(0x8189), Realtek(0x0bda), rev 2.00, iSerialNumber
> 00e04c01
> urtw0
The problem comes from this driver that does not set any configuration
when it attaches itself to the device.
Could you test the diff below, it is a sync with urtwn(4), and tell me
if you can reproduce this problem with it?
Index: if_urtw.c
===
RCS file: /home/ncvs/src/sys/dev/usb/if_urtw.c,v
retrieving revision 1.47
diff -u -p -r1.47 if_urtw.c
--- if_urtw.c 13 Jul 2014 15:52:49 - 1.47
+++ if_urtw.c 1 Sep 2014 08:43:50 -
@@ -608,6 +608,19 @@ urtw_attach(struct device *parent, struc
sc->sc_udev = uaa->device;
sc->sc_hwrev = urtw_lookup(uaa->vendor, uaa->product)->rev;
+ if (usbd_set_config_no(sc->sc_udev, 1, 0) != 0) {
+ printf("%s: could not set configuration no\n",
+ sc->sc_dev.dv_xname);
+ return;
+ }
+
+ /* Get the first interface handle. */
+ if (usbd_device2interface_handle(sc->sc_udev, 0, &sc->sc_iface) != 0) {
+ printf("%s: could not get interface handle\n",
+ sc->sc_dev.dv_xname);
+ return;
+ }
+
printf("%s: ", sc->sc_dev.dv_xname);
if (sc->sc_hwrev & URTW_HWREV_8187) {
@@ -2297,20 +2310,6 @@ urtw_init(struct ifnet *ifp)
sc->sc_txtimer = 0;
if (!(sc->sc_flags & URTW_INIT_ONCE)) {
- error = usbd_set_config_no(sc->sc_udev, URTW_CONFIG_NO, 0);
- if (error != 0) {
- printf("%s: could not set configuration no\n",
- sc->sc_dev.dv_xname);
- goto fail;
- }
- /* get the first interface handle */
- error = usbd_device2interface_handle(sc->sc_udev,
- URTW_IFACE_INDEX, &sc->sc_iface);
- if (error != 0) {
- printf("%s: could not get interface handle\n",
- sc->sc_dev.dv_xname);
- goto fail;
- }
error = urtw_open_pipes(sc);
if (error != 0)
goto fail;
@@ -3730,20 +3729,6 @@ urtw_8187b_init(struct ifnet *ifp)
sc->sc_txtimer = 0;
if (!(sc->sc_flags & URTW_INIT_ONCE)) {
- error = usbd_set_config_no(sc->sc_udev, URTW_CONFIG_NO, 0);
- if (error != 0) {
- printf("%s: could not set configuration no\n",
- sc->sc_dev.dv_xname);
- goto fail;
- }
- /* Get the first interface handle. */
- error = usbd_device2interface_handle(sc->sc_udev,
-
Re: openbgpd & rdomain/rtable (vrf-lite)
Hello,
I tried to do a similar setup. I tried different configuration without success.
Then I found this in the manpage : "Currently the routing table must belong to
the default routing domain and nexthop verification happens on table 0."
So I think OpenBGPD is not (yet ?) able to do this.
--
Cordialement,
Pierre BARDOU
-Message d'origine-
De : Pierre Emeriaud [mailto:petrus.lt+open...@gmail.com]
Envoyé : samedi 30 août 2014 17:50
À : misc@openbsd.org
Objet : openbgpd & rdomain/rtable (vrf-lite)
Hello misc@,
I'd like to set up bgpd with multiple routing tables, a la vrf-lite (ie without
mpls and mp-bgp).
What works:
- peering within a rtable/rdomain
- receiving the routes
What doesn't work:
- nexthop is never "validated"
-> routes are never installed in fib
Configuration is pretty straitforward:
# cat bgpd.conf
AS 64751
router-id 172.22.151.130
listen on 172.22.151.130 # loopback
listen on 172.22.151.251 # interface towards peer rtable 10 group "ibgp
peering AS64751" {
remote-as 64751
neighbor 172.22.151.245 {
descr "beta"
announce self
}
}
bgpd is started as such:
route -n -T10 exec bgpd -d -v -f /etc/bgpd/bgpd.conf
Peering gets up, and routes received:
# bgpctl -n show sum
Neighbor ASMsgRcvdMsgSent OutQ Up/Down State/PrfRcvd
172.22.151.245 64751 10851 6373 0 2d05h05m338
Routes are received in rtable 0:
# bgpctl show rib in | head
flags: * = Valid, > = Selected, I = via IBGP, A = Announced, S = Stale
origin: i = IGP, e = EGP, ? = Incomplete
flags destination gateway lpref med aspath origin
I 10.0.0.0/16 172.22.151.245 100 0 64734.14918
64734.12596 65112 65530 i
I 10.1.0.0/16 172.22.151.245 100 0 64734.14918
64734.12596 65112 65530 i
I 10.8.0.0/16 172.22.151.245 100 0 64734.12699
1.10582 65053 i
I 10.11.0.0/18 172.22.151.245 100 0 64828 64609 i
I 10.11.64.0/18172.22.151.245 100 0 64828 1.10567 1.10594 i
I 10.15.0.0/16 172.22.151.245 100 0 64828 1.10604 65079 i
And indeed, 172.22.151.245 is not reachable in rtable0.
If I use "rde rib foo no evaluate", routes are put in the 'foo' rib, but still
not installed.
If I use the "rde rib foo table 10", I get the following error:
'/etc/bgpd/bgpd.conf:20: rtable 10 does not belong to rdomain 0'
I tried to use 'rdomain 10' in the config file, but that looks very
mpls-oriented (mp-bgp peering in GRT, which works fine btw).
Have I missed something, or am I asking for something currently unsupported?
Thanks, and sorry for the long post,
--
petrus
mplayer full screen problems
Hello, If I put an OpenBSD 5.5 (FVWM) box on a display via VGA cable mplayer does strange things: The "-geometry=50%:50%" doesn't work (doesn't put the videos in center). The "-fs" doesn't work. I can only use "-xy 1024" - but that is not the best, since there could be videos that are wrongly aligned with it, too much to the top, or too much to the bottom. Does anybody knows how can I use mplayer in OpenBSD from console so it will put the videos in fullscreen properly with good alignment (in center/middle of the screen)? Many thanks!
How to disable keyboard+mouse input in FVWM?
Besides gluing the USB holes on a PC, how could I disable the keyboard and mouse input for a logged in user on a OpenBSD 5.5 install with FVWM? Many thanks,
Re: How to disable keyboard+mouse input in FVWM?
On 1 September 2014 11:53, wrote: > Besides gluing the USB holes on a PC, how could I disable the keyboard > and mouse input for a logged in user on a OpenBSD 5.5 install with > FVWM? Style * NeverFocus -- Thomas Adam
Re: How to log in automatically to GUI?
Clint Pachl wrote, On 08/25/14 16:36: It seems one should be able to get getty(8) to do this using /etc/ttys. I tried: console "/usr/bin/su -l USER -c /usr/X11R6/bin/startx" xterm on secure which automatically launched X, but I didn't have access to the console (i.e., no write permission on /dev/console, no keyboard, etc.). I looked into fbtab(5), but I'm not sure how this works in this situation. Thanks to David Coppa, he set me on the right track by sharing Marc Balmer's "Starting X11 Applications on OpenBSD at Boot Time." I will summarize: Use rc.local to launch X server manually on a virtual terminal and make sure getty(8) is not listening on that VT. This setup will not require user login or authentication. It can operate as a kiosk. First, setup an unprivileged user (USER) that will automatically run X11 and any specified GUI apps. Then add an .xinitrc startup script for the USER's X11 session. Here we will launch Chrome and load a local web application. /home/USER/.xinitrc: /usr/local/bin/chrome http://localhost/app Now, just execute X11 as the unprivileged user from the system local script. Note we are running the X server on display 0 on virtual terminal 5. The startx script will run the .xinitrc above. /etc/rc.local: ( while sleep 1 dosu -l USER -c '/usr/X11R6/bin/startx -- /usr/X11R6/bin/Xorg vt05 :0' done ) & Now if Chrome crashes or quits, X will restart and relaunch Chrome. Finally, make sure getty does not interfere with this finely tuned operation. /etc/ttys: ttyC4 "/usr/libexec/getty std.9600" vt220 off
Re: How to log in automatically to GUI?
Andy Bradford wrote, On 08/27/14 08:35: Thus said Clint Pachl on Mon, 25 Aug 2014 16:36:26 -0700: If someone knows how to do this properly via getty(8), I would be very interested. I've used this successfully (not sure how proper it is): /etc/ttys: ttyC0 "/usr/libexec/getty console.nopw" vt220 on secure /etc/gettytab: console.nopw:\ :sp#9600:lo=/usr/bin/autologin: /usr/bin/autologin: #!/bin/sh exec /usr/bin/login -f "$@" FYI: "$@" equals "-p -- USER" where USER is the username entered at the login prompt. I never would have guessed that the -p option was included. I just wanted to point out that this still requires someone to enter a valid username to get a login session. Is it possible to bypass even this step and just get a user login session (i.e., auto-login)? I noticed some GETTYS (e.g., agetty) have an auto-login feature. I'm wondering if OpenBSD's getty can do do similar using the "lo" capability?
Re: openbgpd & rdomain/rtable (vrf-lite)
Hi Pierre, > I tried to do a similar setup. I tried different configuration without > success. Yup, I saw your post on misc@ a few days ago when I was looking for some pointers. > Then I found this in the manpage : "Currently the routing table must belong > to the default routing domain and nexthop verification happens on table 0." I saw that too, but as this is not entirely accurate (multiple rdomains is possible, though with mpbgp), I told myself I had to try. What solution did you ended up with? Have you tried to do the same with bird? -- petrus
Re: openbgpd & rdomain/rtable (vrf-lite)
I ended up with static routing, it was an acceptable setup in my case and I had never heard of brid. But if you succeed please tell me. -- Cordialement, Pierre BARDOU -Message d'origine- De : petrus...@gmail.com [mailto:petrus...@gmail.com] De la part de Pierre Emeriaud Envoyé : lundi 1 septembre 2014 14:35 À : BARDOU Pierre Cc : misc@openbsd.org Objet : Re: openbgpd & rdomain/rtable (vrf-lite) Hi Pierre, > I tried to do a similar setup. I tried different configuration without > success. Yup, I saw your post on misc@ a few days ago when I was looking for some pointers. > Then I found this in the manpage : "Currently the routing table must belong > to the default routing domain and nexthop verification happens on table 0." I saw that too, but as this is not entirely accurate (multiple rdomains is possible, though with mpbgp), I told myself I had to try. What solution did you ended up with? Have you tried to do the same with bird? -- petrus
Re: Problem with cwm and tabbed
On Sat 2014.08.30 at 20:51 +0200, Julian Andrej wrote: > I encountered a problem either with cwm or tabbeb > (http://tools.suckless.org/tabbed/). If I use cwm as my window manager > and start tabbed with an XEmbed supported application like xterm, surf > or st (e.g. tabbed xterm -into) and then I resize the window of > tabbed. > > Before doing something else with the application inside tabbed I try > to close the instance with CTRL+Q (which is inherited from tabbed to > close the application). The result is cwm crashing and i'll be greeted > by the xdm login window. > > Unfortunately there is no relevant (imho) output to the Xorg logs. > > Does the problem exist for others and how can I further debug it? This was pointed out to me the other day. I'm not a user of tabbed, but what I've found is that tabbed actually tries to XKillClient the cwm menu window, which is, well, bad. When one does a mouse resize with cwm, we map and reparent the menu window and draw the little geometry and resize arrow icons, then after we're done, reparent out and then unmap. tabbed sees the map, decides to manage the client; however tabbed doesn't look for UnmapNotify events thus when we unmap, tabbed still thinks it should manage it - and when it tries to close its list of windows, it attempts to close the menu window, though since it's not really there, it uses a hammer to kill it (XKillClient). One could call this a bug in tabbed. However, one might also think that cwm should create and destroy the menu window each time it is needed, as opposed to creating once, then mapping and unmapping as needed. I don't know of other window managers that do this, so ymmv. Might be worth doing the create/drestoy for the menu window in cwm anyway, but I would also ask upstream of tabbed since other things might be mapping and unmapping without destroying. Thanks, Okan
Re: kernel page fault on 55-release
2014-09-01 10:47 GMT+02:00 Martin Pieuchot : > On 30/08/14(Sat) 12:28, ludovic coues wrote: >> 2014-08-30 11:58 GMT+02:00 Martin Pieuchot : >> > On 30/08/14(Sat) 11:46, ludovic coues wrote: >> >> 2014-08-30 10:53 GMT+02:00 Martin Pieuchot : >> >> > Hello Ludovic, >> >> > >> >> > On 28/08/14(Thu) 20:52, ludovic coues wrote: >> >> >> Hello, >> >> >> >> >> >> Recently, I get a kernel page fault every time I try to use the >> >> >> micronucleus [1] command line tool. It 's for uploading an hex file to >> >> >> ATtiny processor, much like arduino's avrude. The crash is pretty >> >> >> consistent, occuring every time I run `micronucleus --run`. >> >> >> I've managed to use it with success in the past on this machine with >> >> >> 55-release so it might be hardware related. I added a realtek wireless >> >> >> device since last time I've get a successful run with micronucleus. >> >> >> >> >> >> I get the following message when I run it: >> >> >> uvm_fault(0x81daaf001, 0x2, 2, 0, 1) -> e >> >> >> kernel: page fault trap, code=0 >> >> >> Stopped at usbd_get_cdesc+035: movzwl 0x2 (%rax),%eax >> >> >> >> >> >> It's followed by the debugger prompt. I don't know how what to do from >> >> >> that point. I'm willing to spend time tracking the source of the >> >> >> problem but I have no idea of what I'm looking for. >> >> > >> >> > Thanks for reporting the problem. I believe this is the same issue that >> >> > has been reported by Thomas Pfaff in February [0] and fixed post 5.5 >> >> > [1]. >> >> > >> >> > Could you try a snapshot and tell me if you can still reproduce it? >> >> > >> >> > Cheers, >> >> > Martin >> >> > >> >> > [0] http://marc.info/?l=openbsd-bugs&m=139135208628637&w=2 >> >> > [1] http://marc.info/?l=openbsd-cvs&m=139194643911061&w=2 >> >> >> >> I might have failed to upgrade to snapshot but I still have the error. >> >> Right now, I got the snapshot install56.fs file, used it to run an >> >> upgrade and run sysmerge. I must have done something right as >> >> start_daemon isn't available anymore in /etc/rc.local but the error is >> >> still present. >> > >> > In this case could you send me your dmesg, the output of "usbdevs -dv" >> > and the trace when the trap occurs? >> > > Thanks Ludovic, > >> usbdevs -dv: >> [...] >> port 4 addr 3: high speed, power 100 mA, unconfigured, >> RTL8187B(0x8189), Realtek(0x0bda), rev 2.00, iSerialNumber >> 00e04c01 >> urtw0 > > The problem comes from this driver that does not set any configuration > when it attaches itself to the device. > > Could you test the diff below, it is a sync with urtwn(4), and tell me > if you can reproduce this problem with it? > Nope, I cannot reproduce :) Thank a lot for your time.
Re: unbound reverse DNS problem to local stub zone
On Sun, Jul 27, 2014 at 11:20:43AM +0200, Patrik Lundin wrote:
> How is/was the reverse zone configured in nsd? I am currently trying to
> debug an issue i've seen when the stub-zone in unbound is wider ("name:
> "10.in-addr.arpa") than the zone in nsd (name: "0.0.10.in-addr.arpa").
>
> To me the following is seen:
> # dig @127.0.0.1 -x 10.0.0.1 <-- works
> # dig @127.0.0.1 -x 10.0.0.2 <-- fails
> # dig @127.0.0.1 -x 10.0.0.3 <-- works
> # dig @127.0.0.1 -x 10.0.0.4 <-- works
>
> Basically the first lookup works, the second ends up at IANA (as if the
> stub-zone configuration did not exist), and any
> following lookups work again.
I have the same exact symptom, unbound.conf:
server:
interface: 127.0.0.1@53
interface: 10.10.10.1@53
verbosity: 1
do-not-query-localhost: no
do-ip6: no
auto-trust-anchor-file: "/var/unbound/etc/root.key"
access-control: 0.0.0.0/0 refuse
access-control: 127.0.0.0/8 allow
access-control: 10.10.0.0/16 allow
access-control: ::0/0 refuse
access-control: ::1 allow
hide-identity: yes
hide-version: yes
local-zone: "10.in-addr.arpa." nodefault
stub-zone:
name: "10.in-addr.arpa."
stub-addr: 127.0.0.1@5353
# dig -p53 @127.0.0.1 -x 10.10.10.2 +short # works
# dig -p53 @127.0.0.1 -x 10.10.10.1 +short # doesnt
If I dig directly to nsd, via -p5353
# dig -p5353 @127.0.0.1 -x 10.10.10.2 +short # works
# dig -p5353 @127.0.0.1 -x 10.10.10.1 +short # works
I have no good explanation as to what's going on. I've tried this on current
(as opposed to 5.5), and issue does NOT go away.
On the NSD side, I have two zones
zone:
name: 10.10.10.in-addr.arpa.
zonefile: "db.10.10.10"
zone:
name: 11.10.10.in-addr.arpa.
zonefile: "db.10.10.11"
syslogd fails to bind /dev/log with inet6
I have several machines running the August 29 i386 snapshot, one of which
is unable to create /dev/log. I'm not clear on why the code path of the
failing machine is significantly different, or, why this particular
failure occurs.
It is repeatable on the failing platform. In single user mode:
# mount -a
# syslogd
syslogd: bind: Can't assign requested address
#
ktrace shows that it is an error with inet6:
19063 syslogd CALL bind(0x5,0x783d99e0,0x1c)
19063 syslogd STRU struct sockaddr { AF_INET6, [::]:514 }
19063 syslogd RET bind -1 errno 49 Can't assign requested address
I have implemented a simple circumvention, in rc.conf.local:
syslogd_flags="-4"
Any clues to help isolate and repair would be appreciated.
OpenBSD 5.6-current (GENERIC.MP) #319: Fri Aug 29 03:07:28 MDT 2014
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
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 = 1034641408 (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: 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
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci4 at ppb3 bus 5
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM disabled
ahci0 at pci0 dev 31 function 2 "Intel 82801GBM AHCI" rev 0x02: msi, AHCI 1.1
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: SCSI3 0
Re: How to log in automatically to GUI?
Thus said Clint Pachl on Mon, 01 Sep 2014 05:24:02 -0700: > FYI: "$@" equals "-p -- USER" where USER is the username entered at > the login prompt. I never would have guessed that the -p option was > included. Yes, it does allow any USER to login without a password by just typing the username at the prompt followed by Enter---this does not exclude root, however, I don't think it would be hard to modify the script to exclude root (or any other user), or force the username, etc... > I just wanted to point out that this still requires someone to enter a > valid username to get a login session. Is it possible to bypass even > this step and just get a user login session (i.e., auto-login)? I never did figure out how to bypass this step. Andy -- TAI64 timestamp: 40005404ad11
Re: unbound reverse DNS problem to local stub zone
On Mon, Sep 01, 2014 at 08:58:11AM -0700, Arthur Mesh wrote: > > I have no good explanation as to what's going on. I've tried this on current > (as opposed to 5.5), and issue does NOT go away. > I decided to ask about this on unbound-users: https://unbound.nlnetlabs.nl/pipermail/unbound-users/2014-September/003504.html Regards, Patrik Lundin
addresses and routes configured via rtsol
I set up a small network in which an OpenBSD machine serves as a router for a collection of IPv6-only clients. Many thanks to previous responders to my questions on tunneling with gif(4). This rudimentary setup is working well: a client machine acquires an address via SLAAC and can access the IPv6 Internet. I am curious, however, about the addresses and routes that get installed on the client machine. The setup straightforward. The router is connected to an IPv6 tunnel on the Internet-facing side (using a gif(4) interface), it has IPv6 forwarding enabled, and is running rtadvd on the inward-facing interface. Note that rtadvd is using its internal defaults; I didn't create a configuration file for it because the man page The interface info and routing table is at the end of this mail and I've annotated lines of interest with numbers in brackets so that referencing these entries in questions would be clearer. The questions are: 1.) In addition to the self-assigned link-local address, the client's interface has two other addresses, both having the network prefix supplied by the router (annotation [1]). One has the same suffix as that of the link-local address. The other, marked "autoconfprivacy", is different and changes periodically (certainly on every reboot). I assume this address is formed with the rules defined in RFC 4941. As I interpret it, the RFC suggests a scheme that employs different addresses for server-oriented tasks and client-oriented tasks. The idea is that a predicable address is suitable for the former, while a randomized one is for the latter. Is that what's happening here? According to netstat(1), this seems to be the case. While surfing the web, the local address always seems to be the one with the autoconfprivacy attribute. Is rtsol(8) in charge of implementing this policy? 2.) A corollary to the above question is how the "privacy" address gets used for outbound connections. My assumption of how interfaces with multiple addresses behave is this: the interface will accept connections for any address it has been assigned, but will use the "canonical" one for connections that are initiated through that interface. Is this correct? Does IPv6 have the notion of "aliases" at all? If it does, how do you know which one is the "canonical" address. If not, how do outbound connection end up with the "correct", i.e. private, local address? 3.) The default route (annotation [2]) mystified me at first, before I realized that the gateway address was the link-local address of the router. I was aware of link-local addresses in IPv6, but I was unsure of their application and didn't expect them to come into play here. I expected the gateway to be the IPv6 address I assigned to the router's inward facing interface. It seems logical that the router's link-local address works, but why was it chosen? 4.) The /64 network route for my network has the gateway specified as "link#1" (annotation [3]). What are the "link" family of interfaces? These must be different than routes that specify one of the link-layer addresses, but how? Thanks, Chuck Output of ifconfig em0 and netstat -nrf inet6, with [annotations]: em0: flags=8843 mtu 1500 lladdr f0:de:f1:78:d5:4c priority: 0 groups: egress media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause) status: active inet6 fe80::f2de:f1ff:fe78:d54c%em0 prefixlen 64 scopeid 0x1 inet6 2001:470:1f05:204:f2de:f1ff:fe78:d54c prefixlen 64 autoconf pltime 604280 vltime 2591480 [1] inet6 2001:470:1f05:204:1039:d2fd:9b56:709 prefixlen 64 autoconf autoconfprivacy pltime 77124 vltime 595610 [1] Internet6: DestinationGatewayFlags Refs Use Mtu Prio Iface ::/104 ::1UGRS 0 0 - 8 lo0 ::/96 ::1UGRS 0 0 - 8 lo0 defaultfe80::92e2:baff:fe2b:b008%em0 UG 0 156 -56 em0 [2] ::1::1UH14 0 33144 4 lo0 ::127.0.0.0/104::1UGRS 0 0 - 8 lo0 ::224.0.0.0/100::1UGRS 0 0 - 8 lo0 ::255.0.0.0/104::1UGRS 0 0 - 8 lo0 :::0.0.0.0/96 ::1UGRS 0 0 - 8 lo0 2001:470:1f05:204::/64 link#1 UC 1 0 - 4 em0 [3] 2001:470:1f05:204::1 90:e2:ba:2b:b0:08 UHLc 0 30 - 4 em0 2001:470:1f05:204:24c5:ec52:ca52:a9e7 f0:de:f1:78:d5:4c UHL 00 - 4 lo0 2001:470
Re: syslogd fails to bind /dev/log with inet6
On Mon, Sep 01, 2014 at 01:26:07PM -0400, Josh Grosse wrote:
> I have several machines running the August 29 i386 snapshot, one of which
> is unable to create /dev/log. I'm not clear on why the code path of the
> failing machine is significantly different, or, why this particular
> failure occurs.
>
> It is repeatable on the failing platform. In single user mode:
>
> # mount -a
> # syslogd
> syslogd: bind: Can't assign requested address
> #
>
> ktrace shows that it is an error with inet6:
>
> 19063 syslogd CALL bind(0x5,0x783d99e0,0x1c)
> 19063 syslogd STRU struct sockaddr { AF_INET6, [::]:514 }
> 19063 syslogd RET bind -1 errno 49 Can't assign requested address
>
> I have implemented a simple circumvention, in rc.conf.local:
>
> syslogd_flags="-4"
>
I neglected to state that syslogd.conf is the default r1.17 from 2005, without
local modification.
OpenBSD 5.5 + FreeRADIUS 2.2: PID directory deleted on reboot?
Hi all, This is probably a very simple question, but for the life of me I have not been able to locate a solution. I am running a RADIUS server on OpenBSD 5.5 stable (+ openssl patches) using FreeRADIUS 2.2.0p2 from the ports tree. When I first installed FreeRADIUS, it worked great. However, when I rebooted the system, radiusd would no longer start. I discovered the run_dir of /var/lrun/radiusd, which houses the PID file and socket, was missing. I re-created the directory and changed its ownership to _freeradius. After that, it started working again. But whenever the system reboots, the entire /var/run/radiusd directory gets deleted somehow. The only references I could find regarding this happening with OpenBSD was on a blog, where the recommendation was simply to manually re-create the directory. There must be something I am missing here, and I feel like it’s probably quite simple. Does anybody know what I need to do in order to prevent the run dir from being deleted, or know if there is a better location for it where it won’t be automatically deleted when the system reboots? Thanks in advance for any help, it is much appreciated and OpenBSD rocks! Warm regards, Andrew
Re: mplayer full screen problems
> Hello, > If I put an OpenBSD 5.5 (FVWM) box on a display via VGA cable mplayer > does strange things: What box exactly? There are multiple architectures out there with multiple machines on each architecture. To help someone help you try to send the output of dmesg command. If you are not familiar with it, try the following command in terminal: man dmesg. This output will help people to identify your hardware and a bit of software you are currently using. > The "-geometry=50%:50%" doesn't work (doesn't put the videos in > center). > The "-fs" doesn't work. It is known that -fs doesn't work for anything you run mplayer at. > I can only use "-xy 1024" - but that is not the best, since there > could be videos that are wrongly aligned with it, too much to the top, > or too much to the bottom. > Does anybody knows how can I use mplayer in OpenBSD from console >so it > will put the videos in fullscreen properly with good alignment (in > center/middle of the screen)? > Many thanks! I am thinking you are using a laptop and you try to output the movie on its VGA plug. I did this and it is not working first try. You need to change the video output driver, see the -vo flag. I don't remember which driver I used back then, but I tried all of them and one was able to output on the VGA in fullscreen mode. If I recall, I had to disable the laptop display output, too. Select one driver, then press 'f' key and check the result.
Re: unbound reverse DNS problem to local stub zone
On Monday, September 1, 2014 17:58 CEST, Arthur Mesh
wrote:
> On Sun, Jul 27, 2014 at 11:20:43AM +0200, Patrik Lundin wrote:
> > How is/was the reverse zone configured in nsd? I am currently trying to
> > debug an issue i've seen when the stub-zone in unbound is wider ("name:
> > "10.in-addr.arpa") than the zone in nsd (name: "0.0.10.in-addr.arpa").
> >
> > To me the following is seen:
> > # dig @127.0.0.1 -x 10.0.0.1 <-- works
> > # dig @127.0.0.1 -x 10.0.0.2 <-- fails
> > # dig @127.0.0.1 -x 10.0.0.3 <-- works
> > # dig @127.0.0.1 -x 10.0.0.4 <-- works
> >
> > Basically the first lookup works, the second ends up at IANA (as if the
> > stub-zone configuration did not exist), and any
> > following lookups work again.
>
> I have the same exact symptom, unbound.conf:
>
> server:
> interface: 127.0.0.1@53
> interface: 10.10.10.1@53
> verbosity: 1
> do-not-query-localhost: no
> do-ip6: no
> auto-trust-anchor-file: "/var/unbound/etc/root.key"
>
> access-control: 0.0.0.0/0 refuse
> access-control: 127.0.0.0/8 allow
> access-control: 10.10.0.0/16 allow
> access-control: ::0/0 refuse
> access-control: ::1 allow
>
> hide-identity: yes
> hide-version: yes
>
> local-zone: "10.in-addr.arpa." nodefault
>
> stub-zone:
> name: "10.in-addr.arpa."
> stub-addr: 127.0.0.1@5353
>
>
> # dig -p53 @127.0.0.1 -x 10.10.10.2 +short # works
> # dig -p53 @127.0.0.1 -x 10.10.10.1 +short # doesnt
>
> If I dig directly to nsd, via -p5353
> # dig -p5353 @127.0.0.1 -x 10.10.10.2 +short # works
> # dig -p5353 @127.0.0.1 -x 10.10.10.1 +short # works
>
> I have no good explanation as to what's going on. I've tried this on current
> (as opposed to 5.5), and issue does NOT go away.
>
> On the NSD side, I have two zones
>
> zone:
> name: 10.10.10.in-addr.arpa.
> zonefile: "db.10.10.10"
>
> zone:
> name: 11.10.10.in-addr.arpa.
> zonefile: "db.10.10.11"
>
Not that I can explain it, but for me it helped on the unbound side to:
1. switch the local-zone from nondefault to transparent
2. make the stub-zone: name: match the zone names in nsd, for you
means, create two stub zones, for each of your zones you have in nsd.
Sebastian
Re: OpenBSD 5.5 + FreeRADIUS 2.2: PID directory deleted on reboot?
Andrew Lester writes:
> Hi all,
Hi,
> This is probably a very simple question, but for the life of me I have not
> been able to
> locate a solution. I am running a RADIUS server on OpenBSD 5.5 stable (+
> openssl patches)
> using FreeRADIUS 2.2.0p2 from the ports tree. When I first installed
> FreeRADIUS, it worked
> great. However, when I rebooted the system, radiusd would no longer start. I
> discovered
> the run_dir of /var/lrun/radiusd, which houses the PID file and socket, was
> missing. I
> re-created the directory and changed its ownership to _freeradius. After
> that, it
> started working again. But whenever the system reboots, the entire
> /var/run/radiusd
> directory gets deleted somehow.
That's a fact, /var/run is cleaned up at boot time.
> The only references I could find regarding this happening with OpenBSD was on
> a blog,
> where the recommendation was simply to manually re-create the directory.
> There must be
> something I am missing here, and I feel like it’s probably quite simple. Does
> anybody know
> what I need to do in order to prevent the run dir from being deleted, or know
> if there is
> a better location for it where it won’t be automatically deleted when the
> system reboots?
The fr package comes with an rc script that takes care of this for you:
rc_pre() {
/usr/bin/install -d -o _freeradius /var/run/radiusd
}
If you don't use it (eg. because you run radiusd -X in tmux), just add
that line to /etc/rc.local.
> Thanks in advance for any help, it is much appreciated and OpenBSD rocks!
:)
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
OpenBSD 5.5 sysctl reports hw.ncpu=1 when using 2-core processor Intel Atom CPU S1260 @ 2.00GHz
I am using OpenBSD 5.5 with motherboard Supermicro X9SBAA-F which has CPU Intel(R) Atom(TM) CPU S1260 @ 2.00GHz. Intel's website reports that my CPU has 2 cores and 4 hardware threads: http://ark.intel.com/products/71267/Intel-Atom-Processor-S1260-1M-Cache-2_00-GHz I was using the top command to observe CPU utilization and I noticed that when toggling with the '1' key, top was only showing 1 CPU on the "All CPUs" line. After noticing this, I ran the following command and received the following output: $ sysctl -a | egrep -i 'hw.machine|hw.model|hw.ncpu' hw.machine=amd64 hw.model=Intel(R) Atom(TM) CPU S1260 @ 2.00GHz hw.ncpu=1 hw.ncpufound=4 Does this output indicate that my operating system is only using one core? During the installation process I was careful to ensure that the bsd.mp was marked during the installation process. Assuming my operating system is only recognizing one core, does this mean that the installer put my processor in the single-core list and used bsd.sp? Is it more likely that I made a mistake and I simply need to install bsd.mp right now? Am I misinterpreting the clues as to whether or not the operating system is recognizing the two cores? Thank you for helping me understand my observations. I have included the contents of my email to dm...@openbsd.org below: -- Forwarded message -- From: Ryan Date: Sun, Aug 3, 2014 at 12:08 AM Subject: Supermicro X9SBAA-F To: dm...@openbsd.org System purpose: Home SFTP file server with softraid three-disk RAID1 and hard disk encryption for casual family use on LAN and public Internet. Installation experience: The Supermicro X9SBAA-F's built-in USB hardware is 3.0-only, so I had to put a USB 2.0 PCI card in to use a keyboard during installation. KVM keyboard input wouldn't work in the installation program over IPMI with or without the USB 2.0 PCI card in place. Other notes: At the time this dmesg was run, I had already moved a hardware jumper to disable the IPMI BMC for security purposes. (There's a nasty Supermicro IPMI bug concerning port 49152.) - OpenBSD 5.5-stable (GENERIC) #0: Sat Aug 2 03:42:47 UTC 2014 maintenance@rigmarole.kimternet:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 8556257280 (8159MB) avail mem = 8319922176 (7934MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe94c0 (23 entries) bios0: vendor American Megatrends Inc. version "1.0b" date 04/26/2013 bios0: Supermicro X9SBAA acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET EINJ ERST HEST BERT acpi0: wakeup devices PRP4(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 S1260 @ 2.00GHz, 1995.22 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,MOVBE,NXE,LONG,LAHF,PERF,ITSC cpu0: 512KB 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 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 acpimcfg0 at acpi0 addr 0xc000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PRP1) acpiprt2 at acpi0: bus 2 (PRP2) acpiprt3 at acpi0: bus 4 (P3P4) acpicpu0 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 175 degC acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB ipmi at mainbus0 not configured cpu0: Enhanced SpeedStep 1995 MHz: speeds: 2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200, 1100, 1000, 900, 800, 700, 600 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x0c75 rev 0x02 ppb0 at pci0 dev 1 function 0 vendor "Intel", unknown product 0x0c46 rev 0x02 pci1 at ppb0 bus 1 ahci0 at pci1 dev 0 function 0 vendor "Marvell", unknown product 0x9230 rev 0x10: msi, AHCI 1.2 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed naa.5000c50063ddbe20 sd0: 3815447MB, 512 bytes/sector, 7814037168 sectors sd1 at scsibus0 targ 1 lun 0: SCSI3 0/direct fixed naa.5000c50063dda04e sd1: 3815447MB, 512 bytes/sector, 7814037168 sectors sd2 at scsibus0 targ 2 lun 0: SCSI3 0/direct fixed naa.5000c500749d1a02 sd2: 3815447MB, 512 bytes/sector, 7814037168 sectors uk0 at scsibus0 targ 7 lun 0: ATAPI 3/processor removable ppb1 at pci0 dev 2 function 0 vendor "Intel", unknown product 0x0c47 rev 0x02 pci2 at ppb1 bus 2 vendor "Renesas", unknown product 0x0014 (class serial bus subclass USB, rev 0x03) at pci2 dev 0 function 0 not configured ppb2 at pci0 dev 3 function 0 vendor "Intel", unknown pro
Re: OpenBSD 5.5 sysctl reports hw.ncpu=1 when using 2-core processor Intel Atom CPU S1260 @ 2.00GHz
On Mon, Sep 01, 2014 at 15:51, Ryan wrote: > $ sysctl -a | egrep -i 'hw.machine|hw.model|hw.ncpu' > hw.machine=amd64 > hw.model=Intel(R) Atom(TM) CPU S1260 @ 2.00GHz > hw.ncpu=1 > hw.ncpufound=4 > > Does this output indicate that my operating system is only using one > core? During the installation process I was careful to ensure that > the bsd.mp was marked during the installation process. > > Assuming my operating system is only recognizing one core, does this > mean that the installer put my processor in the single-core list and > used bsd.sp? Is it more likely that I made a mistake and I simply > need to install bsd.mp right now? Am I misinterpreting the clues as > to whether or not the operating system is recognizing the two cores? There is a bug where bsd.rd will incorrectly detect some MP systems as single processor and use the SP kernel. The workaround is you have to shuffle kernels yourself. Then things will work as they should. mv bsd bsd.sp mv bsd.mp bsd
Re: OpenBSD 5.5 sysctl reports hw.ncpu=1 when using 2-core processor Intel Atom CPU S1260 @ 2.00GHz
If you look at the header line of the dmesg you quoted below, you will notice that it says "GENERIC" -- that is the official name of the SP (single processor) kernel. To utilize more than one CPU core, you need to be running the MP (multi-processor) kernel, as in "GENERIC.MP". On 1 Sep 2014 at 15:51, Ryan wrote: > I am using OpenBSD 5.5 with motherboard Supermicro X9SBAA-F which has > CPU Intel(R) Atom(TM) CPU S1260 @ 2.00GHz. Intel's website reports that > my CPU has 2 cores and 4 hardware threads: > > http://ark.intel.com/products/71267/Intel-Atom-Processor-S1260-1M-Cache- > 2_00-GHz > > I was using the top command to observe CPU utilization and I noticed > that when toggling with the '1' key, top was only showing 1 CPU on the > "All CPUs" line. After noticing this, I ran the following command and > received the following output: > > $ sysctl -a | egrep -i 'hw.machine|hw.model|hw.ncpu' > hw.machine=amd64 > hw.model=Intel(R) Atom(TM) CPU S1260 @ 2.00GHz > hw.ncpu=1 > hw.ncpufound=4 > > Does this output indicate that my operating system is only using one > core? During the installation process I was careful to ensure that the > bsd.mp was marked during the installation process. > > Assuming my operating system is only recognizing one core, does this > mean that the installer put my processor in the single-core list and > used bsd.sp? Is it more likely that I made a mistake and I simply need > to install bsd.mp right now? Am I misinterpreting the clues as to > whether or not the operating system is recognizing the two cores? > > Thank you for helping me understand my observations. I have included > the contents of my email to dm...@openbsd.org below: > > -- Forwarded message -- > From: Ryan > Date: Sun, Aug 3, 2014 at 12:08 AM > Subject: Supermicro X9SBAA-F > To: dm...@openbsd.org > > > System purpose: Home SFTP file server with softraid three-disk RAID1 and > hard disk encryption for casual family use on LAN and public Internet. > Installation experience: The Supermicro X9SBAA-F's built-in USB hardware > is 3.0-only, so I had to put a USB 2.0 PCI card in to use a keyboard > during installation. KVM keyboard input wouldn't work in the > installation program over IPMI with or without the USB 2.0 PCI card in > place. Other notes: At the time this dmesg was run, I had already moved > a hardware jumper to disable the IPMI BMC for security purposes. > (There's a nasty Supermicro IPMI bug concerning port 49152.) > > > - OpenBSD 5.5-stable (GENERIC) #0: Sat Aug 2 03:42:47 > UTC 2014 > maintenance@rigmarole.kimternet:/usr/src/sys/arch/amd64/compile/GENE > RIC > real mem = 8556257280 (8159MB) > avail mem = 8319922176 (7934MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe94c0 (23 entries) > bios0: vendor American Megatrends Inc. version "1.0b" date 04/26/2013 > bios0: Supermicro X9SBAA acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 > S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET EINJ ERST HEST BERT > acpi0: wakeup devices PRP4(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 S1260 @ 2.00GHz, 1995.22 > 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,MOVBE,NXE,LONG,LAHF,PERF,ITSC cpu0: > 512KB 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 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 acpimcfg0 at acpi0 addr 0xc000, > bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 > (PCI0) acpiprt1 at acpi0: bus 1 (PRP1) acpiprt2 at acpi0: bus 2 (PRP2) > acpiprt3 at acpi0: bus 4 (P3P4) acpicpu0 at acpi0: C3, C2, C1, PSS > acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: > critical temperature is 175 degC acpibtn0 at acpi0: SLPB acpibtn1 at > acpi0: PWRB ipmi at mainbus0 not configured cpu0: Enhanced SpeedStep > 1995 MHz: speeds: 2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200, > 1100, 1000, 900, 800, 700, 600 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 > dev 0 function 0 vendor "Intel", unknown product 0x0c75 rev 0x02 ppb0 at > pci0 dev 1 function 0 vendor "Intel", unknown product 0x0c46 rev 0x02 > pci1 at ppb0 bus 1 ahci0 at pci1 dev 0 function 0 vendor "Marvell", > unknown product 0x9230 rev 0x10: msi, AHCI 1.2 scsibus0 at ahci0: 32 > targets sd0 at scsibus0 targ 0 lun 0: > SCSI3 0/direct fixed naa.5000c50063ddbe20 sd0: 3815447MB, 512 > bytes/sector, 7814037168 sectors sd1 at scsibus0 targ 1 lun 0: ST4000VN000-1H41, SC42> SCSI3 0/direct fixed naa.5000c50
Re: OpenBSD 5.5 sysctl reports hw.ncpu=1 when using 2-core processor Intel Atom CPU S1260 @ 2.00GHz
On Mon, September 1, 2014 10:46 pm, Ted Unangst wrote: > On Mon, Sep 01, 2014 at 15:51, Ryan wrote: > >> $ sysctl -a | egrep -i 'hw.machine|hw.model|hw.ncpu' >> hw.machine=amd64 >> hw.model=Intel(R) Atom(TM) CPU S1260 @ 2.00GHz >> hw.ncpu=1 >> hw.ncpufound=4 >> >> Does this output indicate that my operating system is only using one >> core? During the installation process I was careful to ensure that >> the bsd.mp was marked during the installation process. >> >> Assuming my operating system is only recognizing one core, does this >> mean that the installer put my processor in the single-core list and >> used bsd.sp? Is it more likely that I made a mistake and I simply >> need to install bsd.mp right now? Am I misinterpreting the clues as >> to whether or not the operating system is recognizing the two cores? > > There is a bug where bsd.rd will incorrectly detect some MP systems as > single processor and use the SP kernel. The workaround is you have to > shuffle kernels yourself. Then things will work as they should. > > mv bsd bsd.sp > mv bsd.mp bsd Based on the provided dmesg, it appears that a GENERIC (not GENERIC.MP) kernel was compiled during the process of patching to -stable. -- Joe Gidi j...@entropicblur.com "You cannot buy skill." -- Ross Seyfried
