Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-14 Thread Alexis de BRUYN
On 13.08.2012 23:34, Matthieu Herrb wrote:
> On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote:
>> On 11.08.2012 23:33, Alexis de BRUYN wrote:
>> I still have my previous issue, but I have another one : while the
>> in-board display device is actived through my xorg.conf, the udl devices
>> are not working too.
> 
> Yes, this is a know issue. The OpenBSD-specific part of Xorg has no
> way to handle a dual-screen setup between udl and one (or more)
> regular VGA card(s) on most architectures.

Thanks Matthieu for your answer. However can it handle multi-screens
with *only* udl devices (without configuring the regular VGA card in
xorg.conf) ? I didn't succeed.

> Fixing this require quite a bit of worg though.

Can you tell me a bit more please ? Why it is not supported ?

Regards,

-- 
Alexis de BRUYN



Question about redirecting to a multiple log files from pflogd

2012-08-14 Thread C. L. Martinez
Hi all,

 I have some rules that I would like to redirect in syslog format to a
log file. I don't need to touch /var/log/pflog. To accomplish this I
have tried to start pflogd daemon with the following options:

 "-s 256 -i pflog0 -f /var/log/pflog -i pflog1 -f /tmp/test.log"

 ... but it doesn't works. After, I have tried to start another pflogd
instance with "-s 256 -i pflog1 -f /tmp/test.log":

25317 ??  S   0:49.58 pflogd: [running] -s 256 -i pflog1 -f
/tmp/test.log (pflogd)
13851 ??  Ss  0:00.23 ntpd: ntp engine (ntpd)
16445 ??  Is  0:00.03 ntpd: dns engine (ntpd)
11227 ??  Ss  0:00.02 ntpd: [priv] (ntpd)
21752 ??  Is  0:00.05 /usr/sbin/sshd
14014 ??  Ss  0:00.30 sendmail: accepting connections (sendmail)
14724 ??  Is  0:00.01 /usr/sbin/ftp-proxy
14277 ??  Ss  0:00.04 /usr/sbin/cron
11070 ??  Ss  0:35.46 sshd: root@ttyp0 (sshd)
18112 ??  Is  0:00.01 pflogd: [priv] (pflogd)
14997 ??  S   0:01.08 pflogd: [running] -s 256 -i pflog0 -f
/var/log/pflog (pflogd)

 .. but it doesn't works. /var/log/pflog doesn't register activitvy
(pflog0 and pflog1 interfaces are up)

 At this stage, I only to need to try if this approach works using
tcpdump file format in both log files ...

 Is it possible to use several pflogX interfaces an redirect all logs
to several log files?? I am using OpenBSD 5.1

Thanks.



Re: Absurdly high temperature reading - system shutdown

2012-08-14 Thread badut
HP 8530w OpenBSD 5.1 AMD64 GENERIC MP

Got this message almost every time I boot:
"acpitz2: critical temperature exceeded 5424C (56976K), shutting down"

Applied the patch mentioned here and the message disappeared:

http://old.nabble.com/acpiec-madness-%28HP-laptop-people-pay-attention-to-thi
s-one%29-to29872059.html#a29872059

dmesg after applying patch attached




- Original meddelelse -

> Fra: Theo de Raadt 
> Til: pablo caballero 
> Cc: misc@openbsd.org
> Dato: Fre, 17. jun 2011 06:15
> Emne: Re: Absurdly high temperature reading - system shutdown
>
> > On Thu, Jun 16, 2011 at 3:33 PM, Michal Mazurek
>  wrote:
> > > After moving my old laptop around I got home, booted it and got a
> very
> > > distressing message:
> > >
> > > messages.2.gz:Jun 14 22:40:09 hopek /bsd: acpitz2: Critical
> temperature
> > > 4938C (52112K), shutting down
> > >
> > > Perhaps some dust moved around, or a cable disconnected.
> > > Unfortunately, the system shut down before it booted. I booted
> bsd.rd,
> > > read some manpages and booted with -c 'disable acpitz' -
> everything
> > > worked fine. I attach a diff to only shutdown if the temperature
> is
> > > below 2000C. If it's above then it's too late to shut down anyway
> :)
> > >
> > > BTW, for no apparent reason my laptop started working fine again.
> > >
> > >
> > > Index: acpitz.c
> > >
> ===
> > > RCS file: /cvs/src/sys/dev/acpi/acpitz.c,v
> > > retrieving revision 1.43
> > > diff -u -r1.43 acpitz.c
> > > --- acpitz.c 15 Jun 2011 00:15:54 - 1.43
> > > +++ acpitz.c 16 Jun 2011 15:09:14 -
> > > @@ -326,11 +326,17 @@
> > > }
> > > /* critical trip points */
> > > if (sc->sc_crt != -1 && sc->sc_crt <= sc->sc_tmp) {
> > > - /* do critical shutdown */
> > > - printf("%s: critical temperature exceeded %dC (%dK),
> > shutting "
> > > - "down\n",
> > > - DEVNAME(sc), KTOC(sc->sc_tmp), sc->sc_tmp);
> > > - psignal(initproc, SIGUSR2);
> > > + if (KTOC(sc->sc_tmp) > 2000) {
> > > + printf("%s: absurdly high temperature %dC (%dK), "
> > > + "doing nothing\n",
> > > + DEVNAME(sc), KTOC(sc->sc_tmp), sc->sc_tmp);
> > > + } else {
> > > + /* do critical shutdown */
> > > + printf("%s: critical temperature exceeded %dC (%dK),
> > "
> > > + "shutting down\n",
> > > + DEVNAME(sc), KTOC(sc->sc_tmp), sc->sc_tmp);
> > > + psignal(initproc, SIGUSR2);
> > > + }
> > > }
> > > if (sc->sc_hot != -1 && sc->sc_hot <= sc->sc_tmp) {
> > > printf("%s: _HOT temperature\n", DEVNAME(sc));
> > >
> > > --
> > > Michal Mazurek
> > >
> > >
> >
> > I had noticed the following behaviour (maybe related or maybe not)
> in my
> > laptop:
> >
> > - When the batt goes low the system shutdown with the same message.
> > The temp is always (not 100% sure) 110C. This is 100% reproducible
> > (every time batt goes low --> system shutdown).
> >
> > I was trying to figure myself what is happening to introduce myself
> to
> > kernel code but if someone want to test something I'll glad to
> help.
>
> This diff you are writing is a workaround. It is not fixing the bug.
>
> Somewhere higher, some acpi, aml, bios, or EC behaviour has provided
> bad data, which has propogated up to the acpitz driver.
>
> We will kind of needs these workarounds until the real bugs are
> found,
> though, perhaps...
OpenBSD 5.1 (GENERIC.MP) #4: Mon Aug 13 01:48:12 CEST 2012
r...@foo.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error
bf
real mem = 8484552704 (8091MB)
avail mem = 8244531200 (7862MB)
User Kernel Config
UKC> timezone /120\^H \^H\^H \^H\^H \^H\^H \^H-120
timezone = -120, dst = 0
UKC> exit
Continuing...
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xbdec4000 (22 entries)
bios0: vendor Hewlett-Packard version "68PDV Ver. F.12" date 06/08/2010
bios0: Hewlett-Packard HP EliteBook 8530w
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG TCPA SSDT SLIC SSDT DMAR ASF! SSDT SSDT
SSDT
acpi0: wakeup devices LANC(S5) HDEF(S4) RP02(S5) WNIC(S5) RP03(S5) ECF0(S5)
RP05(S5) ECF0(S5) RP06(S5) NIC_(S5) USB1(S3) USB2(S3) USB3(S3) USB4(S3)
USB5(S3) USB6(S3) U6RM(S3) EHC1(S3) EHC2(S3) PCIB(S5) HST1(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) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.42 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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,S
SSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF
cpu0: 6MB 64b/line 16-way L2 cache
cpu0: apic clock running at 266MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz, 2793.00 MHz
cpu1:
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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,S
SSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LO

Dell Latitude E6420 issues - not working...

2012-08-14 Thread Jiri B
Hi all,

I have in my hands Dell Latitude E6420 so I tried to boot
OpenBSD snapshot and booting got stucked  on these lines...
(I retyped from a photos I made.)

The last line was one with 'scsibus1 at umass0' below, then
I touched a key and console was full of pbkbcintr lines...

How can I help to troubleshoot this?

jirib

...
uhidev1 at uhub5 port 1 configuration 1 in
 rev 2.00/54.00 addr 3
uhidev1: iclass 3/1
uhid at uhidev1 not configured
uhidev2 at uhub5 port 2 configuration 1 in
dio 400 DSP" rev 2.00/1.32 addr 4
uhidev2: iclass 3/0, 9 report ids
uhid at uhidev2 reportid 1 not configured
uhid at uhidev2 reportid 2 not configured
uhid at uhidev2 reportid 8 not configured
uhid at uhidev2 reportid 9 not configured
"Plantronics Plantronics .Audio 180 DSP" re
nfiguration 1 not configured
umass0 at uhub5 port 6 configuration 3 inter
ddr 5
umass0: using SCSI over Bulk-Only
scsibus1 at umass0: 2 targets, initiator 0
_

pckbcintr: no eki for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1
pckbcintr: no dev for slot 1



Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-14 Thread Matthieu Herrb
On Tue, Aug 14, 2012 at 10:31:24AM +0200, Alexis de BRUYN wrote:
> On 13.08.2012 23:34, Matthieu Herrb wrote:
> > On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote:
> >> On 11.08.2012 23:33, Alexis de BRUYN wrote:
> >> I still have my previous issue, but I have another one : while the
> >> in-board display device is actived through my xorg.conf, the udl devices
> >> are not working too.
> > 
> > Yes, this is a know issue. The OpenBSD-specific part of Xorg has no
> > way to handle a dual-screen setup between udl and one (or more)
> > regular VGA card(s) on most architectures.
> 
> Thanks Matthieu for your answer. However can it handle multi-screens
> with *only* udl devices (without configuring the regular VGA card in
> xorg.conf) ? I didn't succeed.

Right now, I don't see a reason why 2 udl devices wouldn't work, but
I'm not sure I ever tried it.
> 
> > Fixing this require quite a bit of worg though.
> 
> Can you tell me a bit more please ? Why it is not supported ?

On i386 and amd64, when the X server is talking to a VGA
card it bypasses the kernel completely and talks to the hardware
directly. When multiple video cards are used, there is still no
interactions with the kernel. All interaction is done through one
single file descriptor (pointing to the aperture driver xf86(4)).

Otoh, drivers like xf86-video-wsudl or xf86-video-wsfb use a specific
file descriptor (pointing to the wsdisplay device /dev/tty[CDE..]0)
per card. 

The 2 driver models can currently not co-exist in the server. 

The current work done upstreams on switching all drivers to KMS
(Kernel side Mode Settings) will eventually clean up the current
mess. Just don't hold your breath, since porting KMS to OpenBSD is
only making very slow progress.
> 
> Regards,
> 
> -- 
> Alexis de BRUYN

-- 
Matthieu Herrb



WARNING: mclpools limit reached; increase kern.maxclusters and paquet lost

2012-08-14 Thread Michel Blais

Hi misc,

I got a little error here with a sysctl value in dmesg :
WARNING: mclpools limit reached; increase kern.maxclusters

The value was at 6144 and I just change it to 9216 (50% more)

The system is also having paquet lost from 1 up to 6% and can have 
latency up to 30 ms and changing the value still have no effect on 
paquet lost.


Anyone can give me a hint how to diagnose this problem ?

Thanks

# netstat -m
166 mbufs in use:
158 mbufs allocated to data
2 mbufs allocated to packet headers
6 mbufs allocated to socket names and addresses
156/6152/9216 mbuf 2048 byte clusters in use (current/peak/max)
0/8/9216 mbuf 4096 byte clusters in use (current/peak/max)
0/8/9216 mbuf 8192 byte clusters in use (current/peak/max)
0/8/9216 mbuf 9216 byte clusters in use (current/peak/max)
0/8/9216 mbuf 12288 byte clusters in use (current/peak/max)
0/8/9216 mbuf 16384 byte clusters in use (current/peak/max)
0/8/9216 mbuf 65536 byte clusters in use (current/peak/max)
14044 Kbytes allocated to network (2% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines

# vmstat -m
Memory statistics by bucket size
Size   In Use   Free   Requests  HighWater  Couldfree
  16  893   3715  40585429512802114802
  32  387381 1188555273 640  0
  64 2022   1242   33343194 320 977818
 128 3448264   54869026 160   13336125
 256 1803341   72808225  80   12255401
 512  281399   43134794  40   19923082
1024  265147   21789606  20   16341054
2048   40  41187430  10  0
4096 2077  3   15141687   5   2028
8192   23  6  35734   5553
   163846  0   8924   5  0
   32768   11  0 24   5  0
   655362  0  3   5  0

Memory usage type by bucket size
Size  Type(s)
  16  devbuf, pcb, routetbl, UFS mount, dirhash, ACPI, exec, UVM amap,
  UVM aobj, USB, USB device, temp
  32  devbuf, pcb, routetbl, ifaddr, UFS mount, sem, dirhash, ACPI,
  in_multi, exec, UVM amap, USB, temp, DRM
  64  devbuf, routetbl, ifaddr, vnodes, dirhash, ACPI, proc, VFS 
cluster,
  in_multi, ether_multi, VM swap, UVM amap, USB, USB device, 
USB HC,

  NDP, temp, DRM
 128  devbuf, pcb, routetbl, ifaddr, sysctl, mount, sem, dirhash, ACPI,
  VFS cluster, MFS node, NFS srvsock, ttys, pfkey data, inodedep,
  VM swap, UVM amap, USB, USB device, NDP, temp
 256  devbuf, routetbl, ifaddr, ioctlops, vnodes, shm, VM map, dirhash,
  ACPI, exec, UVM amap, USB, USB device, DRM
 512  devbuf, routetbl, ifaddr, ioctlops, dirhash, NFS daemon, 
ttys, newblk,

  UVM amap, USB, temp
1024  devbuf, pcb, sysctl, ioctlops, mount, UFS mount, shm, file, proc,
  ttys, exec, UVM amap, crypto data, temp
2048  devbuf, ioctlops, UFS mount, ACPI, VM swap, UVM amap, UVM 
aobj, temp

4096  devbuf, ifaddr, ioctlops, proc, UVM amap, memdesc, temp, DRM
8192  devbuf, ACPI, ttys, pagedep, UVM amap, USB, temp
   16384  devbuf, MSDOSFS mount, indirdep, temp
   32768  devbuf, UFS quota, UFS mount, ISOFS mount, inodedep, UVM amap,
  NTFS hash
   65536  devbuf

Memory statistics by type   Type  Kern
  Type InUse MemUse HighUse  Limit Requests Limit Limit Size(s)
devbuf  3741  8850K   8914K 78644K 74700 0 
16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536
   pcb3712K 17K 78644K   5310690 0 
16,32,128,1024
  routetbl   23130K105K 78644K  15668800 0 
16,32,64,128,256,512
ifaddr   10922K 22K 78644K  1140 0 
32,64,128,256,512,4096

sysctl 2 2K  2K 78644K20 0 128,1024
  ioctlops 0 0K  4K 78644K  25744310 0 
256,512,1024,2048,4096

 mount16 9K  9K 78644K   160 0 128,1024
vnodes  137587K 87K 78644K 47500 0 64,256
 UFS quota 132K 32K 78644K10 0 32768
 UFS mount3371K 71K 78644K   330 0 
16,32,1024,2048,32768

   shm 2 2K  2K 78644K20 0 256,1024
VM map 2 1K  1K 78644K20 0  256
   sem 2 1K  1K 78644K20 0 32,128
   dirhash   13528K 29K 78644K  1530 0 
16,32,64,128,256,512
  ACPI  2144   256K275K 78644K 71580 0 
16,32,64,128,256,2048,8192

  file 0 0K  1K 78644K20 0  1024
  proc1410K 10K 78644K   140 0 64,1024,4096
   VFS cluste

Re: WARNING: mclpools limit reached; increase kern.maxclusters and paquet lost

2012-08-14 Thread Michel Blais

I juste found how to get the boot dmesg :

# cat /var/run/dmesg.boot
OpenBSD 5.0 (GENERIC) #53: Wed Aug 17 10:07:52 MDT 2011
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 4293656576 (4094MB)
avail mem = 4165275648 (3972MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf9920 (87 entries)
bios0: vendor Dell Computer Corporation version "A07" date 04/25/2008
bios0: Dell Computer Corporation PowerEdge 1850
acpi0 at bios0: rev 0
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC SPCR HPET MCFG
acpi0: wakeup devices PCI0(S5) PALO(S5) PBLO(S5) VPR0(S5) PBHI(S5) 
VPR1(S5) PICH(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) Xeon(TM) CPU 3.20GHz, 3192.63 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,CNXT-ID,CX16,xTPR,NXE,LONG

cpu0: 2MB 64b/line 8-way L2 cache
cpu0: apic clock running at 199MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
ioapic1 at mainbus0: apid 2 pa 0xfec8, version 20, 24 pins
ioapic1: misconfigured as apic 0, remapped to apid 2
ioapic2 at mainbus0: apid 3 pa 0xfec83000, version 20, 24 pins
ioapic2: misconfigured as apic 0, remapped to apid 3
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PALO)
acpiprt2 at acpi0: bus 2 (DOBA)
acpiprt3 at acpi0: bus 4 (DOBB)
acpiprt4 at acpi0: bus 5 (PBLO)
acpiprt5 at acpi0: bus 9 (VPR0)
acpiprt6 at acpi0: bus 6 (PBHI)
acpiprt7 at acpi0: bus 7 (PXB1)
acpiprt8 at acpi0: bus 8 (PXB2)
acpiprt9 at acpi0: bus 10 (PICH)
acpicpu0 at acpi0
ipmi at mainbus0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0x09
ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x09
pci1 at ppb0 bus 1
ppb1 at pci1 dev 0 function 0 "Intel IOP332 PCIE-PCIX" rev 0x06
pci2 at ppb1 bus 2
ppb2 at pci2 dev 12 function 0 "Pericom PI7C21P100 PCIX-PCIX" rev 0x01
pci3 at ppb2 bus 3
em0 at pci3 dev 4 function 0 "Intel PRO/1000MT QP (82546GB)" rev 0x03: 
apic 2 int 7, address 00:1b:21:8c:33:78
em1 at pci3 dev 4 function 1 "Intel PRO/1000MT QP (82546GB)" rev 0x03: 
apic 2 int 4, address 00:1b:21:8c:33:79
em2 at pci3 dev 6 function 0 "Intel PRO/1000MT QP (82546GB)" rev 0x03: 
apic 2 int 5, address 00:1b:21:8c:33:7a
em3 at pci3 dev 6 function 1 "Intel PRO/1000MT QP (82546GB)" rev 0x03: 
apic 2 int 6, address 00:1b:21:8c:33:7b

ppb3 at pci1 dev 0 function 2 "Intel IOP332 PCIE-PCIX" rev 0x06
pci4 at ppb3 bus 4
ppb4 at pci0 dev 4 function 0 "Intel E7520 PCIE" rev 0x09
pci5 at ppb4 bus 5
ppb5 at pci0 dev 5 function 0 "Intel E7520 PCIE" rev 0x09
pci6 at ppb5 bus 6
ppb6 at pci6 dev 0 function 0 "Intel 6700PXH PCIE-PCIX" rev 0x09
pci7 at ppb6 bus 7
em4 at pci7 dev 7 function 0 "Intel PRO/1000MT (82541GI)" rev 0x05: apic 
3 int 0, address 00:14:22:23:b6:03

ppb7 at pci6 dev 0 function 2 "Intel 6700PXH PCIE-PCIX" rev 0x09
pci8 at ppb7 bus 8
em5 at pci8 dev 8 function 0 "Intel PRO/1000MT (82541GI)" rev 0x05: apic 
3 int 1, address 00:14:22:23:b6:04

ppb8 at pci0 dev 6 function 0 "Intel E7520 PCIE" rev 0x09
pci9 at ppb8 bus 9
uhci0 at pci0 dev 29 function 0 "Intel 82801EB/ER USB" rev 0x02: apic 1 
int 16
uhci1 at pci0 dev 29 function 1 "Intel 82801EB/ER USB" rev 0x02: apic 1 
int 19
uhci2 at pci0 dev 29 function 2 "Intel 82801EB/ER USB" rev 0x02: apic 1 
int 18
ehci0 at pci0 dev 29 function 7 "Intel 82801EB/ER USB2" rev 0x02: apic 1 
int 23

usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb9 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xc2
pci10 at ppb9 bus 10
"Dell DRAC 4" rev 0x00 at pci10 dev 5 function 0 not configured
puc0 at pci10 dev 5 function 1 "Dell DRAC 4 Virtual UART" rev 0x00: 
ports: 1 com

com2 at puc0 port 0 apic 1 int 21: ns16550a, 16 byte fifo
com2: probed fifo depth: 0 bytes
"Dell DRAC 4 SMIC" rev 0x00 at pci10 dev 5 function 2 not configured
pciide0 at pci10 dev 6 function 0 "CMD Technology PCI0680" rev 0x02
pciide0: bus-master DMA support present
pciide0: channel 0 wired to native-PCI mode
pciide0: using apic 1 int 23 for native-PCI interrupt
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
sd0 at scsibus0 targ 0 lun 0:  ATAPI 0/direct removable
atapiscsi1 at pciide0 channel 0 drive 1
scsibus1 at atapiscsi1: 2 targets
cd0 at scsibus1 targ 0 lun 0:  ATAPI 5/cdrom removable
sd0(pciide0:0:0): using PIO mode 3
cd0(pciide0:0:1): using PIO mode 3
pciide0: channel 1 wired to native-PCI mode
vga1 at pci10 dev 13 function 0 "ATI Radeon VE" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
radeondrm0 at vga1: apic 1 int 18
drm0 at radeondrm0
pcib0 at pci0 dev 31 function 0 "Intel 82801EB/ER LPC" rev 

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-14 Thread Matthieu Herrb
On Tue, Aug 14, 2012 at 04:39:57PM +0200, Matthieu Herrb wrote:
> On Tue, Aug 14, 2012 at 10:31:24AM +0200, Alexis de BRUYN wrote:
> > On 13.08.2012 23:34, Matthieu Herrb wrote:
> > > On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote:
> > >> On 11.08.2012 23:33, Alexis de BRUYN wrote:
> > >> I still have my previous issue, but I have another one : while the
> > >> in-board display device is actived through my xorg.conf, the udl devices
> > >> are not working too.
> > > 
> > > Yes, this is a know issue. The OpenBSD-specific part of Xorg has no
> > > way to handle a dual-screen setup between udl and one (or more)
> > > regular VGA card(s) on most architectures.
> > 
> > Thanks Matthieu for your answer. However can it handle multi-screens
> > with *only* udl devices (without configuring the regular VGA card in
> > xorg.conf) ? I didn't succeed.
> 
> Right now, I don't see a reason why 2 udl devices wouldn't work, but
> I'm not sure I ever tried it.
>

Ok, just tried it. It fails because the privilege separation code
refuses to open /dev/ttyE0. Fixed in -current...

-- 
Matthieu Herrb



Re: Absurdly high temperature reading - system shutdown

2012-08-14 Thread Alexander Polakov
* ba...@mail.dk  [120814 19:50]:
> HP 8530w OpenBSD 5.1 AMD64 GENERIC MP
> 
> Got this message almost every time I boot:
> "acpitz2: critical temperature exceeded 5424C (56976K), shutting down"
> 
> Applied the patch mentioned here and the message disappeared:
> 
> http://old.nabble.com/acpiec-madness-%28HP-laptop-people-pay-attention-to-thi
> s-one%29-to29872059.html#a29872059

Wow. This patch does wonders. With it applied my HP 6910 boots with
keyboard and touchpad working four times out of five, and suspend works.



ipsec crypto

2012-08-14 Thread Grzegorz Patoła
Hi All,

Does anyone here know when the will be taken out of biglock and run MP ? Is
there any plan for this ?

regards,
Greg.



Re: WARNING: mclpools limit reached; increase kern.maxclusters and paquet lost

2012-08-14 Thread Michel Blais

I maybe found something, congestion seem high when I check with pftcl -si.

I don't think it's hardware related since CPU is under 50% use.

I saw this tread where Henning suggest to raise net.inet.ip.ifq.maxlen 
so I raided it to 512 instead of 256.

http://old.nabble.com/PF-congestion-question-td7088168.html

It's a old thread so I wanted to know if it's still a good idea to raise 
this sysctl value.


Thanks.

# pfctl -si
Status: Enabled for 76 days 20:03:04 Debug: err

State Table  Total Rate
  current entries   101318
  searches24892219197337496.3/s
  inserts   465241  836.8/s
  removals  363923  836.8/s
Counters
  match 8707572837 1311.7/s
  bad-offset 00.0/s
  fragment 16004630.2/s
  short 5754300.1/s
  normalize 3091520.0/s
  memory4453080.1/s
  bad-timestamp  00.0/s
  congestion  257389763.9/s
  ip-option  530500.0/s
  proto-cksum00.0/s
  state-mismatch  150447922.3/s
  state-insert  9184050.1/s
  state-limit00.0/s
  src-limit  00.0/s
  synproxy   00.0/s

Le 2012-08-14 11:39, Michel Blais a écrit :

I juste found how to get the boot dmesg :

# cat /var/run/dmesg.boot
OpenBSD 5.0 (GENERIC) #53: Wed Aug 17 10:07:52 MDT 2011
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 4293656576 (4094MB)
avail mem = 4165275648 (3972MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf9920 (87 entries)
bios0: vendor Dell Computer Corporation version "A07" date 04/25/2008
bios0: Dell Computer Corporation PowerEdge 1850
acpi0 at bios0: rev 0
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC SPCR HPET MCFG
acpi0: wakeup devices PCI0(S5) PALO(S5) PBLO(S5) VPR0(S5) PBHI(S5) 
VPR1(S5) PICH(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) Xeon(TM) CPU 3.20GHz, 3192.63 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,CNXT-ID,CX16,xTPR,NXE,LONG

cpu0: 2MB 64b/line 8-way L2 cache
cpu0: apic clock running at 199MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
ioapic1 at mainbus0: apid 2 pa 0xfec8, version 20, 24 pins
ioapic1: misconfigured as apic 0, remapped to apid 2
ioapic2 at mainbus0: apid 3 pa 0xfec83000, version 20, 24 pins
ioapic2: misconfigured as apic 0, remapped to apid 3
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PALO)
acpiprt2 at acpi0: bus 2 (DOBA)
acpiprt3 at acpi0: bus 4 (DOBB)
acpiprt4 at acpi0: bus 5 (PBLO)
acpiprt5 at acpi0: bus 9 (VPR0)
acpiprt6 at acpi0: bus 6 (PBHI)
acpiprt7 at acpi0: bus 7 (PXB1)
acpiprt8 at acpi0: bus 8 (PXB2)
acpiprt9 at acpi0: bus 10 (PICH)
acpicpu0 at acpi0
ipmi at mainbus0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0x09
ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x09
pci1 at ppb0 bus 1
ppb1 at pci1 dev 0 function 0 "Intel IOP332 PCIE-PCIX" rev 0x06
pci2 at ppb1 bus 2
ppb2 at pci2 dev 12 function 0 "Pericom PI7C21P100 PCIX-PCIX" rev 0x01
pci3 at ppb2 bus 3
em0 at pci3 dev 4 function 0 "Intel PRO/1000MT QP (82546GB)" rev 0x03: 
apic 2 int 7, address 00:1b:21:8c:33:78
em1 at pci3 dev 4 function 1 "Intel PRO/1000MT QP (82546GB)" rev 0x03: 
apic 2 int 4, address 00:1b:21:8c:33:79
em2 at pci3 dev 6 function 0 "Intel PRO/1000MT QP (82546GB)" rev 0x03: 
apic 2 int 5, address 00:1b:21:8c:33:7a
em3 at pci3 dev 6 function 1 "Intel PRO/1000MT QP (82546GB)" rev 0x03: 
apic 2 int 6, address 00:1b:21:8c:33:7b

ppb3 at pci1 dev 0 function 2 "Intel IOP332 PCIE-PCIX" rev 0x06
pci4 at ppb3 bus 4
ppb4 at pci0 dev 4 function 0 "Intel E7520 PCIE" rev 0x09
pci5 at ppb4 bus 5
ppb5 at pci0 dev 5 function 0 "Intel E7520 PCIE" rev 0x09
pci6 at ppb5 bus 6
ppb6 at pci6 dev 0 function 0 "Intel 6700PXH PCIE-PCIX" rev 0x09
pci7 at ppb6 bus 7
em4 at pci7 dev 7 function 0 "Intel PRO/1000MT (82541GI)" rev 0x05: 
apic 3 int 0, address 00:14:22:23:b6:03

ppb7 at pci6 dev 0 function 2 "Intel 6700PXH PCIE-PCIX" rev 0x09
pci8 at ppb7 bus 8
em5 at pci8 dev 8 function 0 "Intel PRO/1000MT (82541GI)" rev 0x05: 
apic 3 int 1, address 00:14:22:23:b6:04

ppb8 at pci0 dev

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-14 Thread Alexis de BRUYN
On 14.08.2012 17:58, Matthieu Herrb wrote:
> On Tue, Aug 14, 2012 at 04:39:57PM +0200, Matthieu Herrb wrote:
>> On Tue, Aug 14, 2012 at 10:31:24AM +0200, Alexis de BRUYN wrote:
>>> On 13.08.2012 23:34, Matthieu Herrb wrote:
 On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote:
> On 11.08.2012 23:33, Alexis de BRUYN wrote:
> I still have my previous issue, but I have another one : while the
> in-board display device is actived through my xorg.conf, the udl devices
> are not working too.

 Yes, this is a know issue. The OpenBSD-specific part of Xorg has no
 way to handle a dual-screen setup between udl and one (or more)
 regular VGA card(s) on most architectures.
>>>
>>> Thanks Matthieu for your answer. However can it handle multi-screens
>>> with *only* udl devices (without configuring the regular VGA card in
>>> xorg.conf) ? I didn't succeed.
>>
>> Right now, I don't see a reason why 2 udl devices wouldn't work, but
>> I'm not sure I ever tried it.
>>
> 
> Ok, just tried it. It fails because the privilege separation code
> refuses to open /dev/ttyE0. Fixed in -current...

I have reinstalled and rebuilt (incl. xenocara) 5.2/amd64, but I still
have the issue, only udl0 is working, but not the 2 others.

[   421.287] (EE) wsudl(1): We are not attached to the udl driver
[   421.287] (EE) wsudl(2): We are not attached to the udl driver

I found something different in dmesg for the 2 others, is that relevant ?

udl0 at uhub4 port 3 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 8
wsdisplay1 at udl0 mux 1
wsdisplay1: screen 0 added (std, vt100 emulation)
[...]
udl1 at uhub6 port 2 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 4
no data for est. mode 832x768x74
no data for est. mode 640x480x67
no data for est. mode 720x400x70
[...]
wsdisplay2 at udl1 mux 1
wsdisplay2: screen 0 added (std, vt100 emulation)
udl2 at uhub6 port 3 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 5
no data for est. mode 832x768x74
no data for est. mode 640x480x67
no data for est. mode 720x400x70
[...]
wsdisplay3 at udl2 mux 1
wsdisplay3: screen 0 added (std, vt100 emulation)


# cat /etc/X11/xorg.conf


Section "ServerLayout"
Identifier  "Server Layout"
Screen  0   "Screen0" 0 0
Screen  1   "Screen1" LeftOf "Screen0"
Screen  2   "Screen2" RightOf "Screen0"
Option  "Xinerama" "On"
EndSection

Section "Screen"
Identifier  "Screen0"
Device  "Card0"
EndSection

Section "Screen"
Identifier  "Screen1"
Device  "Card1"
EndSection

Section "Screen"
Identifier  "Screen2"
Device  "Card2"
EndSection

Section "Device"
Identifier  "Card0"
Driver  "wsudl"
Option  "Device" "/dev/ttyD0"
EndSection

Section "Device"
Identifier  "Card1"
Driver  "wsudl"
Option  "Device" "/dev/ttyE0"
EndSection

Section "Device"
Identifier  "Card2"
Driver  "wsudl"
Option  "Device" "/dev/ttyF0"
EndSection



Here the full log files :

# cat /var/log/Xorg.0.log


[   421.247] (--) checkDevMem: using aperture driver /dev/xf86
[   421.262] (--) Using wscons driver on /dev/ttyC4 in pcvt
compatibility mode (version 3.32)
[   421.269]
X.Org X Server 1.12.2
Release Date: 2012-05-29
[   421.269] X Protocol Version 11, Revision 0
[   421.269] Build Operating System: OpenBSD 5.2 amd64
[   421.269] Current Operating System: OpenBSD test.lan.mrs.de-bruyn.fr
5.2 GENERIC.MP#368 amd64
[   421.269] Build Date: 22 July 2012  10:13:23PM
[   421.269]
[   421.269] Current version of pixman: 0.24.4
[   421.269]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   421.269] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   421.269] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 14
18:41:59 2012
[   421.270] (==) Using config file: "/etc/X11/xorg.conf"
[   421.270] (==) Using system config directory
"/usr/X11R6/share/X11/xorg.conf.d"
[   421.270] (==) ServerLayout "Server Layout"
[   421.270] (**) |-->Screen "Screen0" (0)
[   421.270] (**) |   |-->Monitor ""
[   421.270] (**) |   |-->Device "Card0"
[   421.270] (==) No monitor specified for screen "Screen0".
Using a default monitor configuration.
[   421.270] (**) |-->Screen "Screen1" (1)
[   421.270] (**) |   |-->Monitor ""
[   421.270] (**) |   |-->Device "Card1"
[   421.270] (==) No monitor specified for screen "Screen1".
Using a default monitor configuration.
[   421.270] (**) |-->Screen "Screen2" (2)
[   421.270] (**) |   |-->Monitor ""
[   421.270] (**) |   |-->Device "Card2"
[   421.270] (==) No monitor specified for screen "Screen2".
Using a default monitor configuration.
[   421.270] (**) Option "Xinerama" "On"
[   421.2

Re: DisplayLink CONV-USB2DVI : wsudl(0): We are not attached to the udl driver

2012-08-14 Thread Matthieu Herrb
On Tue, Aug 14, 2012 at 10:35:40PM +0200, Alexis de BRUYN wrote:
> On 14.08.2012 17:58, Matthieu Herrb wrote:
> > On Tue, Aug 14, 2012 at 04:39:57PM +0200, Matthieu Herrb wrote:
> >> On Tue, Aug 14, 2012 at 10:31:24AM +0200, Alexis de BRUYN wrote:
> >>> On 13.08.2012 23:34, Matthieu Herrb wrote:
>  On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote:
> > On 11.08.2012 23:33, Alexis de BRUYN wrote:
> > I still have my previous issue, but I have another one : while the
> > in-board display device is actived through my xorg.conf, the udl devices
> > are not working too.
> 
>  Yes, this is a know issue. The OpenBSD-specific part of Xorg has no
>  way to handle a dual-screen setup between udl and one (or more)
>  regular VGA card(s) on most architectures.
> >>>
> >>> Thanks Matthieu for your answer. However can it handle multi-screens
> >>> with *only* udl devices (without configuring the regular VGA card in
> >>> xorg.conf) ? I didn't succeed.
> >>
> >> Right now, I don't see a reason why 2 udl devices wouldn't work, but
> >> I'm not sure I ever tried it.
> >>
> > 
> > Ok, just tried it. It fails because the privilege separation code
> > refuses to open /dev/ttyE0. Fixed in -current...
> 
> I have reinstalled and rebuilt (incl. xenocara) 5.2/amd64, but I still
> have the issue, only udl0 is working, but not the 2 others.

Did you get xserver/os/privsep.c rev 1.25 ? Since I did the commit at
the same time I was writing the mail, it may take a few hours more to
get make it to all the cvs mirrors.


> 
> [   421.287] (EE) wsudl(1): We are not attached to the udl driver
> [   421.287] (EE) wsudl(2): We are not attached to the udl driver
> 
> I found something different in dmesg for the 2 others, is that relevant ?
> 
> udl0 at uhub4 port 3 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 8
> wsdisplay1 at udl0 mux 1
> wsdisplay1: screen 0 added (std, vt100 emulation)
> [...]
> udl1 at uhub6 port 2 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 4
> no data for est. mode 832x768x74
> no data for est. mode 640x480x67
> no data for est. mode 720x400x70
> [...]
> wsdisplay2 at udl1 mux 1
> wsdisplay2: screen 0 added (std, vt100 emulation)
> udl2 at uhub6 port 3 "DisplayLink CONV-USB2DVI" rev 2.00/0.03 addr 5
> no data for est. mode 832x768x74
> no data for est. mode 640x480x67
> no data for est. mode 720x400x70
> [...]
> wsdisplay3 at udl2 mux 1
> wsdisplay3: screen 0 added (std, vt100 emulation)
> 
> 
> # cat /etc/X11/xorg.conf
> 
> 
> Section "ServerLayout"
> Identifier  "Server Layout"
> Screen  0   "Screen0" 0 0
> Screen  1   "Screen1" LeftOf "Screen0"
> Screen  2   "Screen2" RightOf "Screen0"
> Option  "Xinerama" "On"
> EndSection
> 
> Section "Screen"
> Identifier  "Screen0"
> Device  "Card0"
> EndSection
> 
> Section "Screen"
> Identifier  "Screen1"
> Device  "Card1"
> EndSection
> 
> Section "Screen"
> Identifier  "Screen2"
> Device  "Card2"
> EndSection
> 
> Section "Device"
> Identifier  "Card0"
> Driver  "wsudl"
> Option  "Device" "/dev/ttyD0"
> EndSection
> 
> Section "Device"
> Identifier  "Card1"
> Driver  "wsudl"
> Option  "Device" "/dev/ttyE0"
> EndSection
> 
> Section "Device"
> Identifier  "Card2"
> Driver  "wsudl"
> Option  "Device" "/dev/ttyF0"
> EndSection

did you create all the /dev/tty[EEF]0 devices with MAKEDEV this time ? 

In my tests I created explicit display sub-sections too. Generally the
xorg.conf parser is a bit flakey in this area, and rejects some
configurations for no good reason 

Here's the working xorg.conf I used (with privsep.c 1.25) for 2
devices:

Some parts may be useless, but since it took some fiddling to get this
working I stopped there. 

Section "ServerLayout"
Identifier  "L1"
Screen  0 "Screen0" 0 0
Screen  1 "Screen1" RightOf "Screen0"
EndSection

Section "Device"
Identifier  "Card0"
Driver  "wsudl"
Option  "Device" "/dev/ttyD0"
EndSection


Section "Device"
Identifier  "Card1"
Driver  "wsudl"
Option  "Device" "/dev/ttyE0"
EndSection

Section "Monitor"
Identifier "Monitor0"
EndSection

Section "Monitor"
Identifier "Monitor1"
EndSection

Section "Screen"
Identifier  "Screen0"
Device  "Card0"
Monitor "Monitor0"
SubSection  "Display"
Depth   16
Modes   "800x480"
EndSubSection
EndSection

Section "Screen"
Identifier  "Screen1"
Device  "Card1"
Monitor "Monitor1"
SubSection  "Display"
Depth   16
Modes   "1024x768"
EndSubSection
EndSection

-- 
Matthieu Herrb



About `ldapctl stats` metrics

2012-08-14 Thread Joel Carnat
Hi,

I've setup some RRDtool magic to graph ldapd(8) metrics (OpenBSD 5.1/i386).

Using `ldapctl stats`, I was expecting:
"requests" = "search requests" + "bind requests" + "modify requests"

But after a few ldapsearch/ldapadd/ldapdelete testings, it seems "requests"
grows faster than the sum of "* requests".

A simple ldapsearch increments "search" and "bind" by 1 but increments
"requests" by 3. An ldapadd increments "bind" and "modify" by 1 but increments
"requests" by 3. The ldapdelete (to suppress the previous entry) increments
"bind", "search" and "modify" by 1 but "requests" is incremented by 4.

What does "requests" counts that doesn't appear in other metrics?

TIA,
Jo



broken system with unknow command

2012-08-14 Thread Michel Blais

Hi misc,

seem like I have type the wrong command by mistake using tab to complet 
the command. Don't know which command it was but I add a lot of output 
like this :


Faulted ikernel: double fault trap, code=0
  kernel: double fault trap, code=0
Faulted in DDB; continuing...
--db_more--kernel: type 269 trap, code=0
--db_more--kernel: type 269 trap, code=0
--db_more--kernel: type 269 trap, code=0
--db_more--kernel: type 269 trap, code=0
Faulted in DDB; continuing...
--db_more--kernel: type 269 trap, code=0
--db_more--kernel: type 269 trap, codekernel: type 269 trap, code=0
Faulted  kernel: type 269 trap, code=0
   kernel: double fault trap, code=0

I was working in minicom via serial and was not able to do ctrl z and 
also not able to ping the système so I rebooted it by cutting the power 
and now :


# ifconfig em2 192.168.23.1/24
# ifconfig em3 192.168.3.222/24
# pfctl -d
pf disabled
# route flush
kernel: kernel: kernel: kernel: kernel: kernel: privileged instruction 
fault tr

ap, code=0
panic: mtx_enter: locking against myself
panic: mtx_enter: locking against myself
panic: mtx_enter: locking against myself
panic: mtx_enter: locking against myself
panic: mtx_enter: lockin>> OpenBSD/amd64 BOOT 3.17
(bios sound that system as reboot)
boot> route flush
boot: illegal argument flush
boot> route
boot>

That a little scary. I was knowing it was possible to destroy a system 
with rm -rf but first time I see something like that. Anybody have a 
idea of what happen ? I can't scroll back enough to know which command 
was typed.


Here a little more output I found will scrolling :

Stopped at  0:uvm_fault(0xfe807b1b1cc8, 0x0, 0, 1) -> e
  kernel: page fault trap, code=0
--db_more--kernel: type 269 trap, code=0
Stopped at  0:uvm_fault(0xfe807b1b1cc8, 0x0, 0, 1) -> e
  kerkernel: type 269 trap, code=0
Stopped at  0:uvm_fault(0xfe807b1b1cc8, 0x0, 0, 1) -> e
  kernel: page fault trap, code=0
--db_morkernel: type 269 trap, code=0
Stopped at  0:uvm_fault(0xfe807b1b1cc8, 0x0, 0, 1) -> e
  kernel: page fault trap, code=0
--db_mkernel: type 269 trap, code=0
Stopped at  0:uvm_fault(0xfe807b1b1cc8, 0x0, 0, 1) -> e
  kernel: page fault trap, code=0
Stopped at  kernel: type 269 trap, code=0
Stopped at  0:uvm_fault(0xfe807b1b1cc8, 0x0, 0, 1) -> e
  kernel: page fault trap, code=0
Stopped at  kernel: type 269 trap, code=0
Stopped at  0:uvm_fault(0xfe807b1b1cc8, 0x0, 0, 1) -> e
  kernel: page fault trap, code=0
Stopped at  kernel: type 269 trap, code=0
Stopped at  0:uvm_fault(0xfe807b1b1cc8, 0x0, 0, 1) -> e
  kernel: page fault trap, code=0
Stopped at  kernel: type 269 trap, code=0
Stopped at  0:uvm_fault(0xfe807b1b1cc8, 0x0, 0, 1) -> e
  kernel: page fault trap, code=0
Stopped at  db_read_bytes+0x20: movzbl  0(%rdi,%rcx,1),%eax

Thanks

Michel



Re: broken system with unknow command

2012-08-14 Thread Philip Guenther
On Tue, Aug 14, 2012 at 9:12 PM, Michel Blais  wrote:
> seem like I have type the wrong command by mistake using tab to complet the
> command. Don't know which command it was but I add a lot of output like this
> :
>
> Faulted ikernel: double fault trap, code=0
>   kernel: double fault trap, code=0
> Faulted in DDB; continuing...
> --db_more--kernel: type 269 trap, code=0
...

Wow.  Magic 8-ball says "ferociously broken hardware.  Throw it in a
ditch and try again"

...but the 8-ball is a pessimist.  I would reseat all the cards and
simms/dimms and see if it was happier afterwards.


Philip Guenther



Re: Dell Latitude E6420 issues - not working...

2012-08-14 Thread Tomas Bodzar
On Tue, Aug 14, 2012 at 4:24 PM, Jiri B  wrote:
> Hi all,
>
> I have in my hands Dell Latitude E6420 so I tried to boot
> OpenBSD snapshot and booting got stucked  on these lines...
> (I retyped from a photos I made.)
>
> The last line was one with 'scsibus1 at umass0' below, then
> I touched a key and console was full of pbkbcintr lines...

I had exactly same model and issues even in 5.0 or 5.1. Can't remember
exactly now (maybe it's in misc@ as well), but some option in BIOS
changed that behavior. Was quite hard to do eg. upgrades via bsd.rd

>
> How can I help to troubleshoot this?
>
> jirib
>
> ...
> uhidev1 at uhub5 port 1 configuration 1 in
>  rev 2.00/54.00 addr 3
> uhidev1: iclass 3/1
> uhid at uhidev1 not configured
> uhidev2 at uhub5 port 2 configuration 1 in
> dio 400 DSP" rev 2.00/1.32 addr 4
> uhidev2: iclass 3/0, 9 report ids
> uhid at uhidev2 reportid 1 not configured
> uhid at uhidev2 reportid 2 not configured
> uhid at uhidev2 reportid 8 not configured
> uhid at uhidev2 reportid 9 not configured
> "Plantronics Plantronics .Audio 180 DSP" re
> nfiguration 1 not configured
> umass0 at uhub5 port 6 configuration 3 inter
> ddr 5
> umass0: using SCSI over Bulk-Only
> scsibus1 at umass0: 2 targets, initiator 0
> _
>
> pckbcintr: no eki for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1



Re: Dell Latitude E6420 issues - not working...

2012-08-14 Thread Paulm
There's no guarantee that snapshots are functional or bootable. Have
you tried installing/booting the 5.1 release to see if that works?



On Tue, Aug 14, 2012 at 10:24:39AM -0400, Jiri B wrote:
> Hi all,
> 
> I have in my hands Dell Latitude E6420 so I tried to boot
> OpenBSD snapshot and booting got stucked  on these lines...
> (I retyped from a photos I made.)
> 
> The last line was one with 'scsibus1 at umass0' below, then
> I touched a key and console was full of pbkbcintr lines...
> 
> How can I help to troubleshoot this?
> 
> jirib
> 
> ...
> uhidev1 at uhub5 port 1 configuration 1 in
>  rev 2.00/54.00 addr 3
> uhidev1: iclass 3/1
> uhid at uhidev1 not configured
> uhidev2 at uhub5 port 2 configuration 1 in
> dio 400 DSP" rev 2.00/1.32 addr 4
> uhidev2: iclass 3/0, 9 report ids
> uhid at uhidev2 reportid 1 not configured
> uhid at uhidev2 reportid 2 not configured
> uhid at uhidev2 reportid 8 not configured
> uhid at uhidev2 reportid 9 not configured
> "Plantronics Plantronics .Audio 180 DSP" re
> nfiguration 1 not configured
> umass0 at uhub5 port 6 configuration 3 inter
> ddr 5
> umass0: using SCSI over Bulk-Only
> scsibus1 at umass0: 2 targets, initiator 0
> _
> 
> pckbcintr: no eki for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1
> pckbcintr: no dev for slot 1