Re: qwx0: failed to send/start with QCNFA765
On Thu, 22 Feb 2024 17:17:45 +0100 Stefan Sperling wrote: > On Thu, Feb 22, 2024 at 03:28:42PM +0100, Marco van Hulten wrote: > > On Thu, 22 Feb 2024 13:29:27 +0100 Stefan Sperling wrote: > > > Can you reproduce this on non-WPA-Enterprise networks, > > > i.e. without eduraom / wpaakms 802.1x? > > > > Did not succeed in reproducing so far. > > I figured out the scan command error, details and patch below. > > The good news is that this is just a cosmetic issue. > Let me know if you still see any issues with the patch applied. > qwx0: failed to send WMI_START_SCAN_CMDID > qwx0: failed to start hw scan: 58 Today, after installing the latest snapshot, I do not get this error anymore. Does it contain the patch? Wi-Fi to normal access points is working fine. Still a problem with eduroam, but I think that should be unrelated to qwx(4). Marco
Re: qwx0: failed to send/start with QCNFA765
On Thu, 22 Feb 2024 13:29:27 +0100 Stefan Sperling wrote: > On Thu, Feb 22, 2024 at 11:35:35AM +0100, Marco van Hulten wrote: > > Hello, > > > > The Qualcomm QCNFA765 (support recently added) in my ThinkPad P14s > > worked for some time, but now it mostly does not and I get these kernel > > messages: > > > > qwx0: failed to send WMI_START_SCAN_CMDID > > qwx0: failed to start hw scan: 58 > > > > This happens when I run this command: > > > > ifconfig qwx0 nwid eduroam wpa wpaakms 802.1x up > > > > dmesg is attached. Is this a bug or am I doing something wrong? > > > > Similar, when I first scan and then try to join an open network, > > following qwx(4), > > > > qwx0: failed to send WMI_11D_SCAN_START_CMDID: 58 > > qwx0: failed to start 11d scan; vdev: 0 ret: 58 > > qwx0: failed to send WMI_START_SCAN_CMDID > > qwx0: failed to start hw scan: 58 > > > > Sometimes it works again; I cannot put my finger what triggers the > > problem. > > Please show a full trace that appears after you run 'ifconfig qwx0 debug'. Just 'ifconfig qwx0 debug' doesn't give any output (terminal or console). I don't know if it should. The commands 'ifconfig qwx0 down; ifconfig qwx0 up debug' resulted on console: qwx0: ASSOC -> RUN qwx0: INIT -> SCAN qwx0: end active scan qwx0: - 1c:9e:cc:3b:d3:b0 11 +171 54M ess privacy rsn! "Vodafone-D3AC"! qwx0: - 1c:9e:cc:3b:d3:b8 100 +169 54M ess privacy rsn! "Vodafone-D3AC"! qwx0: - 1c:ed:6f:bb:ea:bf 100 +172 54M ess privacy rsn! "fHome"! qwx0: - 1c:ed:6f:bb:ea:c1 60 +168 54M ess privacy rsn! "fHome"! qwx0: - 26:7b:cb:c6:10:0a 48 +208 54M ess privacy rsn! "DIRECT-WTBDGP14SmsWV"! qwx0: - 6e:63:9c:51:08:fd6 +173 54M ess no! rsn! "Vodafone Hotspot"! qwx0: - 74:88:bb:4f:74:8d 48 +206 54M ess no! rsn! "gast-bonnet"! qwx0: - 74:88:bb:4f:74:8e 48 +206 54M ess no! rsn! "bonnet"! qwx0: + 74:88:bb:4f:74:8f 48 +206 54M ess privacy rsn "eduroam" qwx0: + 74:88:bb:9c:32:605 +188 54M ess privacy rsn "eduroam" qwx0: - 74:88:bb:9c:32:6d 140 +178 54M ess no! rsn! "gast-bonnet"! qwx0: - 74:88:bb:9c:32:6e 140 +178 54M ess no! rsn! "bonnet"! qwx0: + 74:88:bb:9c:32:6f 140 +178 54M ess privacy rsn "eduroam" qwx0: + 74:88:bb:d0:63:c05 +183 54M ess privacy rsn "eduroam" qwx0: - 74:88:bb:d0:63:c15 +183 54M ess no! rsn! "bonnet"! qwx0: - 74:88:bb:d0:63:c25 +183 54M ess no! rsn! "gast-bonnet"! qwx0: - 74:88:bb:d0:63:cd 36 +184 54M ess no! rsn! "gast-bonnet"! qwx0: - 74:88:bb:d0:63:ce 36 +184 54M ess no! rsn! "bonnet"! qwx0: + 74:88:bb:d0:63:cf 36 +184 54M ess privacy rsn "eduroam" qwx0: - ce:9e:a2:2b:a0:be 11 +171 54M ess privacy rsn! 0x00! qwx0: SCAN -> AUTH qwx0: sending auth to 74:88:bb:4f:74:8f on channel 48 mode 11a qwx0: AUTH -> ASSOC qwx0: sending assoc_req to 74:88:bb:4f:74:8f on channel 48 mode 11a qwx0: ASSOC -> RUN qwx0: associated with 74:88:bb:4f:74:8f ssid "eduroam" channel 48 start 9Mb short preamble short slot time qwx0: missed beacon threshold set to 30 beacons, beacon interval is 100 TU > Can you reproduce this on non-WPA-Enterprise networks, > i.e. without eduraom / wpaakms 802.1x? Did not succeed in reproducing so far. I tried a network without a mention of "802.1x", namely from detekti# ifconfig qwx0 scan qwx0: flags=808847 mtu 1500 lladdr 04:7b:cb:b6:bf:14 index 2 priority 4 llprio 3 groups: wlan egress media: IEEE802.11 autoselect mode 11a (OFDM9 mode 11a) status: no network ieee80211: nwid eduroam chan 48 bssid 74:88:bb:4f:74:8f -52dBm wpaprotos wpa2 wpaakms 802.1x wpaciphers ccmp wpagroupcipher ccmp nwid DIRECT-WTBDGP14SmsWV chan 36 bssid 26:7b:cb:c6:10:0a -47dBm HT-MCS15 privacy,spectrum_mgmt,wpa2 !wpaproto nwid gast-bonnet chan 1 bssid 74:88:bb:4f:74:82 -50dBm HT-MCS23 spectrum_mgmt,radio_measurement nwid eduroam chan 1 bssid 74:88:bb:4f:74:80 -50dBm HT-MCS23 privacy,spectrum_mgmt,radio_measurement,wpa2,802.1x [...] I selected 'gast-bonnet': detekti# ifconfig qwx0 join gast-bonnet debug detekti# ifconfig qwx0 qwx0: flags=808806 mtu 1500 lladdr 04:7b:cb:b6:bf:14 index 2 priority 4 llprio 3 groups: wlan egress media: IEEE802.11 autoselect mode 11a (OFDM9 mode 11a) status: no network ieee80211: nwid eduroam wpaprotos wpa2 wpaakms 802.1x wpaciphers ccmp wpagroupcipher
qwx0: failed to send/start with QCNFA765
Hello, The Qualcomm QCNFA765 (support recently added) in my ThinkPad P14s worked for some time, but now it mostly does not and I get these kernel messages: qwx0: failed to send WMI_START_SCAN_CMDID qwx0: failed to start hw scan: 58 This happens when I run this command: ifconfig qwx0 nwid eduroam wpa wpaakms 802.1x up dmesg is attached. Is this a bug or am I doing something wrong? Similar, when I first scan and then try to join an open network, following qwx(4), qwx0: failed to send WMI_11D_SCAN_START_CMDID: 58 qwx0: failed to start 11d scan; vdev: 0 ret: 58 qwx0: failed to send WMI_START_SCAN_CMDID qwx0: failed to start hw scan: 58 Sometimes it works again; I cannot put my finger what triggers the problem. According to fw_update, qwx firmware is installed. Kind regards, Marco dmesg.P14s Description: Binary data
dmesg of ThinkPad P14s G3 (AMD)
Works: - Camera - Audio - Touchscreen - Touchpad, red nub and buttons - Ethernet - HDMI output - Hibernation (ZZZ) Doesn't work: - Wi-Fi (soldered) - Microphone - Suspend (zzz): no S3 Works well otherwise. Work-around for Wi-Fi: I use a phone with USB tethering for wireless network. Work-around for microphone: external headset. OpenBSD 7.3-current (GENERIC.MP) #1318: Thu Jul 27 17:39:18 MDT 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 12619960320 (12035MB) avail mem = 12217798656 (11651MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0x73688000 (70 entries) bios0: vendor LENOVO version "R23ET65W (1.35 )" date 03/21/2023 bios0: LENOVO 21J5002WGE efi0 at bios0: UEFI 2.7 efi0: Lenovo rev 0x1290 acpi0 at bios0: ACPI 6.3 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT SSDT TPM2 MSDM BATB HPET APIC MCFG SBST WSMT SSDT CRAT CDIT VFCT FPDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI SSDT IVRS SSDT SSDT BGRT acpi0: wakeup devices GPP5(S4) GPP6(S0) GPP7(S0) LID_(S4) SLPB(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 7 PRO 6850U with Radeon Graphics, 2700.01 MHz, 19-44-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Ryzen 7 PRO 6850U with Radeon Graphics, 2700.00 MHz, 19-44-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache cpu1: smt 1, core 0, package 0 tsc: cpu0/cpu1: sync test failed timecounter: active counter changed: tsc -> acpihpet0 cpu2 at mainbus0: apid 2 (application processor) cpu2: AMD Ryzen 7 PRO 6850U with Radeon Graphics, 2700.00 MHz, 19-44-01 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: AMD Ryzen 7 PRO 6850U with Radeon Graphics, 2700.01 MHz, 19-44-01 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache cpu3: smt 1, core 1, package 0 cpu4 at mainbus0: apid 4 (application processor) cpu4: AMD Ryzen 7 PRO 6850U with Radeon Graphics, 2700.00 MHz, 19-44-01 cpu4:
Cologne/Bonn BSD user group?
Hello, Is anyone interested helping setting up a user group in or around Bonn? Marco, Bonn (Germany)
Re: Julia on OpenBSD?
Je Fri, 13 Jul 2018 10:21:06 -0400 skribis Predrag: > What are you trying to do with Julia? If you are just trying to do > science it is probably a bad choice. Jeff Bezanson came here to Carnegie > Mellon University to give a talk 2 years ago and I was not too > impressed (arguably I am more interested in science than in computer > language design). They had immense momentum 5-6 years ago but I think > the enthusiasm is dissipating at least among scientist. It seems so, but that's of course the perception we have of (fellow) scientists having a certain perception. I am using Julia for scientific computing, though nothing that couldn't be achieved with, for instance, Python. Our general circulation models (at our and similar institutes) are written in Fortran. There has been some development in using C++ for such models, but just as the best our IT department is offering on our computers is Ubuntu, ultimately we use Fortran probably for many years to come for our modelling. It is not all too bad, because most of it is Fortran 95/2003, which are probably decent enough for scientific computing. For the statistics on the model output I use Julia. This works fine. What makes Julia, or any other language, good or bad for scientific computing? Probably it is for a large part perception, and momentum. Could it be that enthusiasm is dissipating, or at least it seems so, because of a couple of negative blog posts that pop up quite high in the search engines of the web? Or is it that they sort of promissed a 1.0 version over a year ago but it has yet to emerge? (Of course one shouldn't care so much about version numbers -- surely a stable API is a good thing but maybe one cannot get a stable language out as fast as they want.) Or is it more of a system design issue, probably not the language but the packaging of Julia and all its dependencies? Except for having designed a language with surely very interesting properties, they try to incorporate everything useful for scientific computing, so they have to have, just to give an example, seemless integration of old and proven linear algebra packages. Marco
Re: New laptop recommendations
Robert, On 25 Jun 22:01 Robert Gilaard wrote: > I am just researching this as well and have settled on the Dell > laptops because they come pre-configured with Ubuntu and therefore I > assume they will be opensource friendly. It could be fine, but I would not just assume this. The pre-configured Ubuntu may contain proprietary drivers, which you may not want to use, and are not included in OpenBSD. > I have short listed:1. Dell > Precision 7520 ($1502)2. Dell Precision 7720 ($1412)3. Dell Precision > 3520 ($1352) Prices are based on my hardware choices so ymmv. I have a Dell Latitude E7470, which had serveral power management related issues in spring last year (e.g. hanging when waking up from suspend). The worst of these issues disappeared because OpenBSD and Ubuntu (also installed as it is officially provided by my employer) got support for the hardware over the summer of 2017. There is still the issue of an OpenBSD segfault when I attach/detach the laptop to/from my docking station. In retrospect, I wish I took the similarly spec'ed Lenovo Thinkpad that my employer also offered, because Thinkpads are said to be "opensource friendly" (but that may be just as well be wishful thinking). Marco
Re: programs crash on Dell Latitude E7470
Just wrapping up my ports tree issue, which is now resolved: On 31 May 17:55 Marco van Hulten wrote: > Now I get other problems: > > marco@ultron:/usr/ports/productivity/calcurse$ make > Fatal: Missing support for module x11/tk. (in lang/python/3.6) > Fatal: Missing support for module x11/tk. (in lang/python/3.6) > *** Error 1 in /usr/ports/lang/python/3.6 > (/usr/ports/infrastructure/mk/bsd.port.mk:3462 '.BEGIN': @exit 1) > Problem with dependency lang/python/3.6 *** Error 1 in . > (/usr/ports/infrastructure/mk/bsd.port.mk:2057 > '/usr/ports/pobj/calcurse-4.3.0/.dep-lang-python-3.6') *** Error 1 > in /usr/ports/productivity/calcurse > (/usr/ports/infrastructure/mk/bsd.port.mk:2380 'all') > > I have x11/tk and Python 3.6 installed. > > I should've said I don't regularly build packages, but it shouldn't be > that hard :-) I made sure there is no permission issue (in case I did a cvs up as root or so), and updated the tree. Building and installing works fine now. Concerning the calcurse issue, I have to wait (I also informed the port maintainer). Thanks for the help, Marco
Re: programs crash on Dell Latitude E7470
On 31 May 16:32 Stuart Henderson wrote:
> On 2018/05/31 17:24, Marco van Hulten wrote:
> > Stuart,
> >
> > On 31 May 15:10 Stuart Henderson wrote:
> > > The gdb output there doesn't include anything that will help track
> > > things down. At least a backtrace is needed ("bt" at the gdb
> > > prompt), but there will be more information included in the
> > > backtrace if you build from ports like this
> > >
> > > pkg_delete calcurse
> > > cd /usr/ports/productivity/calcurse
> > > make clean
> > > make DEBUG=-g repackage
> > > make install
> > >
> > > Since it's threaded you might get something more useful with
> > > "thread apply all bt full".
> >
> > I'll send that to them but so far have not recompiled it, because
> > of an issue with the source tree:
> >
> > marco@ultron:/usr/ports/productivity/calcurse$ make clean
> > Fatal: Unknown flavor(s) centered_tilde (in productivity/calcurse)
> >(No flavors for this port). (in productivity/calcurse)
> > *** Error 1 in /usr/ports/productivity/calcurse
> > (/usr/ports/infrastructure/mk/bsd.port.mk:3462 '.BEGIN': @exit 1)
> >
> > I tried checking out a clean ports tree (download + cvs up), but it
> > resulted in the same error. Same for just the "make" command in any
> > port, for instance /usr/ports/mail/z-push/.
>
> Perhaps you have something setting this FLAVOR in /etc/mk.conf or the
> shell environment?
Yes, I had that set as a shell variable. I don't know why I ever put
that there.
Now I get other problems:
marco@ultron:/usr/ports/productivity/calcurse$ make
Fatal: Missing support for module x11/tk. (in lang/python/3.6)
Fatal: Missing support for module x11/tk. (in lang/python/3.6)
*** Error 1 in /usr/ports/lang/python/3.6
(/usr/ports/infrastructure/mk/bsd.port.mk:3462 '.BEGIN': @exit 1)
Problem with dependency lang/python/3.6
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2057
'/usr/ports/pobj/calcurse-4.3.0/.dep-lang-python-3.6')
*** Error 1 in /usr/ports/productivity/calcurse
(/usr/ports/infrastructure/mk/bsd.port.mk:2380 'all')
I have x11/tk and Python 3.6 installed.
I should've said I don't regularly build packages, but it shouldn't be
that hard :-)
Marco
Re: programs crash on Dell Latitude E7470
Stuart,
On 31 May 15:10 Stuart Henderson wrote:
> The gdb output there doesn't include anything that will help track
> things down. At least a backtrace is needed ("bt" at the gdb prompt),
> but there will be more information included in the backtrace if you
> build from ports like this
>
> pkg_delete calcurse
> cd /usr/ports/productivity/calcurse
> make clean
> make DEBUG=-g repackage
> make install
>
> Since it's threaded you might get something more useful with
> "thread apply all bt full".
I'll send that to them but so far have not recompiled it, because of an
issue with the source tree:
marco@ultron:/usr/ports/productivity/calcurse$ make clean
Fatal: Unknown flavor(s) centered_tilde (in productivity/calcurse)
(No flavors for this port). (in productivity/calcurse)
*** Error 1 in /usr/ports/productivity/calcurse
(/usr/ports/infrastructure/mk/bsd.port.mk:3462 '.BEGIN': @exit 1)
I tried checking out a clean ports tree (download + cvs up), but it
resulted in the same error. Same for just the "make" command in any
port, for instance /usr/ports/mail/z-push/.
> Normally I'd suggest reporting to the port maintainer first
> (perhaps CC po...@openbsd.org) and see if they have an idea,
> but since it's already reported upstream it would be good to
> followup there with the backtrace as well.
Yes, that would have been better!
Marco
Re: programs crash on Dell Latitude E7470
On 31 May 10:15 Stuart Henderson wrote: > On 2018/05/31 10:06, Marco van Hulten wrote: > > Stuart, > > > > [...] > > > > I now see there are some limits [...] as normal user > > [now given from ksh(1)] $ ulimit -a time(cpu-seconds)unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 786432 stack(kbytes)4096 lockedmem(kbytes)5303878 memory(kbytes) 15888396 nofiles(descriptors) 512 processes128 I put myself in login class "staff", which increased limits, and then increased limits a bit further where I could: $ ulimit -a time(cpu-seconds)unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 15728640 stack(kbytes)4096 lockedmem(kbytes)5503878 memory(kbytes) 15888396 nofiles(descriptors) 1024 processes512 >From this shell I started abiword, and get an immediate crash: $ rm -rf ~/.config/abiword $ abiword Abort trap (core dumped) $ gdb abiword abiword.core [...] Loaded symbols for /usr/local/lib/abiword-3.0/plugins/pdf.so #0 thrkill () at -:3 3 -: No such file or directory. in - (gdb) whereas calcurse stops in rthread.c, which I thought could be a calcurse bug so I reported it [1], but I'm not sure at all anymore. [1]: https://lists.calcurse.org/bugs/msg00261.html Two days or so ago Firefox and Claws Mail crashed at arbitrary moments. Just maybe this behaviour will stop now. > Limits are grouped by login class (5th field in master.passwd). root > is usually in "daemon" and the initial user created during install is > in "staff" (default 1.5GB for datasize-cur, no limit for > datasize-max). Users that you've added separately are likely to be in > the default class (768MB datasize-cur and datasize-max). > > datasize-cur is a "soft limit", a user can increase it themselves with > "ulimit -d " up to the hard limit in datasize-max. I learnt something! > I'd start by putting the relevant user/s into "staff" class (as root, > vipw, or "chsh " and edit the Class: line), logout/login and > retry. If it needs more than this, it maybe better to raise the soft > limit for the individual program by using a shell alias or wrapper > script rather than raising it across the board (OpenBSD doesn't cope > very well if the entire system runs out of memory and this is a useful > brake on runaway processes). For example you could use an alias like > this: > > alias firefox="(ulimit -d $((3*1024*1024)); /usr/local/bin/firefox)" Thanks, I'll do that when appropriate. At the moment it does not seem to be a memory limitation issue. By decreasing ulimit -d $((128*1024)), I can reproduce an immediate crash of firefox-esr and get the same traceback message as generated by abiword above. But there I *increased* the limits. Thanks for the apropos(1) tip! Marco
Re: Dell Latitude and E-Port II: system hangs
On 25 May 17:22 Marco van Hulten wrote:
> On 25 May 13:50 Marco van Hulten wrote:
> > I have a Dell Latitude E7470 with the latest OpenBSD snapshot. It
> > boots fine when not connected to a docking station. When I connect
> > it to a DELL E-Port II (Model No: PR03X) docking station, it
> > crashes with the following kernel error:
> >
> > error: [drm:pid8048:i915_gem_init_hw] *ERROR* Failed to initialize
> > GuC, error -9 (ignored) error:
> > [drm:pid73911:intel_dp_link_training_clock_recovery] *ERROR* too
> > many full retries, give up error:
> > [drm:pid73911:intel_dp_aux_wait_done] *ERROR* dp aux hw did not
> > signal timeout (has irq: 1)! error:
> > [drm:pid73911:intel_dp_set_idle_link_train] *ERROR* Timed out
> > waiting for DP idle patterns
>
> This specific issue appears to have disappeared (for now). I'm typing
> this on the laptop, running OpenBSD, with the docking station
> attached.
During the last boot, just after fs check, I got this:
kernel: double fault trap, code=0
Stopped at Xsyscall+0x3: movq %r15,%gs:0x8
ddb{0}>
The system was unresponsive. Next boot, it came up (writing this
e-mail on the system, dmesg attached), but the console log shows issues:
error: [drm:pid47136:intel_pipe_update_start] *ERROR* Potential atomic update
failure on pipe B
error: [drm:pid38604:check_wm_state] *ERROR* mismatch in DDB state pipe A plane
1 (expected (0,860), found (0,438))
error: [drm:pid38604:check_wm_state] *ERROR* mismatch in DDB state pipe A
cursor (expected (860,892), found (438,446))
WARNING !wm_changed failed at /usr/src/sys/dev/pci/drm/i915/intel_pm.c:3609
WARNING !wm_changed failed at /usr/src/sys/dev/pci/drm/i915/intel_pm.c:3609
Possibly, only the first one sits close to the hardware (I don't know).
The other four messages sugges interaction with the window manager
(current spectrwm package).
Marco
OpenBSD 6.3-current (GENERIC.MP) #52: Wed May 30 13:42:02 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16811323392 (16032MB)
avail mem = 16293675008 (15538MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xeb460 (106 entries)
bios0: vendor Dell Inc. version "1.12.3" date 12/11/2016
bios0: Dell Inc. Latitude E7470
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT LPIT SSDT SSDT SSDT DBGP
DBG2 SSDT UEFI SSDT SSDT MSDM SLIC TCPA DMAR ASF!
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4)
PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4)
PXSX(S4) RP13(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.86 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
using xsaveopt
cpu0: apic clock running at 23MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.11 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.11 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-6300U
Re: programs crash on Dell Latitude E7470
Stuart, On 29 May 14:18 Stuart Henderson wrote: > On 2018-05-28, Marco van Hulten wrote: > >> Sounds like ether you're running out of system memory, or running > >> into ulimit limits. > > > > `ulimit` == unlimited > > ulimit [-acdfHlmnpSst > [value]] ... Display or set process limits. If no options are used, > the file size limit (-f) is assumed. > > What does ulimit -a say? I now see there are some limits (root, using ksh): # ulimit -a time(cpu-seconds)unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 33554432 stack(kbytes)8192 lockedmem(kbytes)5303876 memory(kbytes) 15888388 nofiles(descriptors) 128 processes1310 and as normal user, using Bash: $ ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) 786432 file size (blocks, -f) unlimited max locked memory (kbytes, -l) 5303876 max memory size (kbytes, -m) 15888388 open files (-n) 512 pipe size(512 bytes, -p) 1 stack size (kbytes, -s) 4096 cpu time (seconds, -t) unlimited max user processes (-u) 128 virtual memory (kbytes, -v) 790528 Apropos, why doesn't "apropos ulimit" show up ksh(1)? Only shortly after typing "which ulimit", I realised that ulimit is part of the shell. Marco
Re: programs crash on Dell Latitude E7470
viq, Thanks so far for your suggestions. On 27 May 09:18 viq wrote: > On 18-05-25 14:15:08, Marco van Hulten wrote: > > Hello— > > > > I have a Dell Latitude E7470 with the latest OpenBSD snapshot. > > > > $ uname -a > > OpenBSD ultron.hulten.org 6.3 GENERIC.MP#45 amd64 > > > > dmesg is attached. > > > > Applications crash. For instance for Claws Mail: > > > > Segmentation fault (core dumped) claws-mail > > > > For Firefox there might be more useful output: > > > > ... > > runSafeSyncWithoutClone@resource://gre/modules/ExtensionUtils.jsm:73:129 > > runSafeWithoutClone@resource://gre/modules/ExtensionCommon.jsm:133:38 > > wrapPromise/<@resource://gre/modules/ExtensionCommon.jsm:312:13 > > ]] > > runSafe failure: cloning into [object Sandbox]: out of memory > > Sounds like ether you're running out of system memory, or running into > ulimit limits. `ulimit` == unlimited Memory consumption stays far below available real memory, never seen swapping (but I have 8 GB of swap). > Probably running memtest wouldn't go amiss either. I did one pass, which took 1h30 or so. No errors. I used stress(1) from packages. This stress --cpu 4 --io 4 --vm 2 --vm-bytes 700M --timeout 60s did not appear to cause issues except for the screen (connected to a docking station) two or three times about 1 second going black and coming back up again. Firefox, for instance, did not crash during this test. Bottom of dmesg (this time attached) says "CPU pipe B FIFO underrun". Marco OpenBSD 6.3-current (GENERIC.MP) #45: Thu May 24 19:22:57 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16811323392 (16032MB) avail mem = 16293687296 (15538MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xeb460 (106 entries) bios0: vendor Dell Inc. version "1.12.3" date 12/11/2016 bios0: Dell Inc. Latitude E7470 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT LPIT SSDT SSDT SSDT DBGP DBG2 SSDT UEFI SSDT SSDT MSDM SLIC TCPA DMAR ASF! acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.92 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.13 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.13 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2095.13 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F
Re: programs crash on Dell Latitude E7470
Hello, some more information, On 25 May 14:15 Marco van Hulten wrote: > I have a Dell Latitude E7470 with the latest OpenBSD snapshot. > > [...] I also updated the software packages to the snapshot (pkg_add -u); problem persists. > Applications crash. For instance for Claws Mail: > > Segmentation fault (core dumped) claws-mail > [...] This happens at apparantly arbitrary moments, with or without user interaction, usually within 20 minutes or so after starting the program (same behaviour of Firefox, Claws Mail, Gajim, ...). Marco
Re: Dell Latitude and E-Port II: system hangs
Hello, responding to my own post, On 25 May 13:50 Marco van Hulten wrote: > I have a Dell Latitude E7470 with the latest OpenBSD snapshot. It > boots fine when not connected to a docking station. When I connect it > to a DELL E-Port II (Model No: PR03X) docking station, it crashes with > the following kernel error: > > error: [drm:pid8048:i915_gem_init_hw] *ERROR* Failed to initialize > GuC, error -9 (ignored) error: > [drm:pid73911:intel_dp_link_training_clock_recovery] *ERROR* too many > full retries, give up error: [drm:pid73911:intel_dp_aux_wait_done] > *ERROR* dp aux hw did not signal timeout (has irq: 1)! error: > [drm:pid73911:intel_dp_set_idle_link_train] *ERROR* Timed out waiting > for DP idle patterns This specific issue appears to have disappeared (for now). I'm typing this on the laptop, running OpenBSD, with the docking station attached. There is still a current issue with the docking station. When I connect or disconnect, the laptop freezes (no kernel messages show up), and I can only do a hard shutdown by pressing the power button for about 5 s or so. Marco
programs crash on Dell Latitude E7470
Hello—
I have a Dell Latitude E7470 with the latest OpenBSD snapshot.
$ uname -a
OpenBSD ultron.hulten.org 6.3 GENERIC.MP#45 amd64
dmesg is attached.
Applications crash. For instance for Claws Mail:
Segmentation fault (core dumped) claws-mail
For Firefox there might be more useful output:
...
runSafeSyncWithoutClone@resource://gre/modules/ExtensionUtils.jsm:73:129
runSafeWithoutClone@resource://gre/modules/ExtensionCommon.jsm:133:38
wrapPromise/<@resource://gre/modules/ExtensionCommon.jsm:312:13
]]
runSafe failure: cloning into [object Sandbox]: out of memory
runSafeSync@resource://gre/modules/ExtensionUtils.jsm:102:86
runSafe@resource://gre/modules/ExtensionCommon.jsm:123:32
_fireCommon/<@resource://gre/modules/ExtensionUtils.jsm:667:49
Assertion failure: [unhandlable oom] Failed to allocate object while
tenuring., at
/usr/obj/ports/firefox-esr-52.8.0/firefox-52.8.0esr/js/src/jscntxt.cpp:1153
[Child 68754] ###!!! ABORT: Aborting on channel error.: file
/usr/obj/ports/firefox-esr-52.8.0/firefox-52.8.0esr/ipc/glue/MessageChannel.cpp,
line 2152
[Child 68754] ###!!! ABORT: Aborting on channel error.: file
/usr/obj/ports/firefox-esr-52.8.0/firefox-52.8.0esr/ipc/glue/MessageChannel.cpp,
line 2152
Segmentation fault (core dumped)
Other programs gave a segfault as well; my guess is these segfaults
have a common reason. There are core files
{abiword,calcures,chrome,claws-mail,conkey,firefox-esr}.core in my
homedir. Is it useful to provide a traceback of one or more? Here is
just the last few lines of one of them (abiword), and the only one that
give a hint to the issue, as far as I can see:
...
#0 _libc_towctrans (c=-247532, desc=0x6) at
/usr/src/lib/libc/locale/iswctype.c:195
195 /usr/src/lib/libc/locale/iswctype.c: No such file or directory.
in /usr/src/lib/libc/locale/iswctype.c
(gdb)
Any help is appreciated.
—Marco
Dell Latitude and E-Port II: system hangs
Hello— I have a Dell Latitude E7470 with the latest OpenBSD snapshot. It boots fine when not connected to a docking station. When I connect it to a DELL E-Port II (Model No: PR03X) docking station, it crashes with the following kernel error: error: [drm:pid8048:i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -9 (ignored) error: [drm:pid73911:intel_dp_link_training_clock_recovery] *ERROR* too many full retries, give up error: [drm:pid73911:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout (has irq: 1)! error: [drm:pid73911:intel_dp_set_idle_link_train] *ERROR* Timed out waiting for DP idle patterns Is this an issue with the docking station, the laptop or OpenBSD? Does someone have an idea how this issue can be solved? $ uname -a OpenBSD ultron.hulten.org 6.3 GENERIC.MP#45 amd64 —Marco
snapshot kernel crash amd64
Hello, I had installed OpenBSD 6.1 on a Dell Latitude E7470 laptop (amd64, Skylake architecture). It could work on it but there were some shortcomings (video was slow). Today I upgraded to the latest snapshot, and I have rebooted successfully, once, after which I updated packages. When I boot up the system now, it gets stuck at the kernel messages, the last three lines being (typing it over): vmm0 at mainbus0: VMX/EPI error: [drm:pid96670:intel_dp_link_training_clock_recovery] *ERROR* too many full retries, give up error: [drm:pid96670:intel_dp_set_idle_link_train] *ERROR* Timed out waiting for DP idle patterns I do not remember what I have done to break the system. There are several reasons why I think it is my fault, and not a bug: 1. I have booted once successfully in the system (and everything worked great); 2. it happens also for the old kernel (obsd) (and also bsd.sp). A package upgrade cannot break the system to this extend. What could it be then? It would be difficult to include dmesg etc., because the system doesn't boot up. - Marco
