Re: recent troubles with iwn(4)
On Sun, Sep 08, 2019 at 08:31:55PM +, Bryan Stenson wrote: > Hi all - > > I'm writing to "misc" rather than "bugs" as I'm not yet sure this is a > bug. I'm hoping to help triage this with assistance from this list. > > I'm running -CURRENT and the iwn(4) driver for my wireless card. Over > the past year, this has been working great, but recently (within the > last month or so), I've had issues where the NIC just stops working > after a few hours of usage. I don't have a solid steps for > reproduction. > > I realize "stops working" is not a very accurate account here...but > I'm confused on how to get more descriptive information of the > problem. When it stops, "ifconfig" shows iwn0 with an IP address, but > I'm unable to ping. Additionally, I'm not seeing any > warnings/messages in "dmesg" about the device...so I'm confused. The iwn driver on my host runnning 6.4 stable writes to /var/log/messages (as well as the system message buffer). Is there nothing in the log files on your system? --Paul
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
Yay! -Luke On Sun, Sep 8, 2019 at 8:07 PM David Gwynne wrote: > I think I see the problem. We're going to try and test this locally and > will hopefully have something committed in a few hours time. > > dlg > > > On 9 Sep 2019, at 10:33, Luke Small wrote: > > > > I have mfii too: > > dmesg | grep mfii: > > > > mfii0 at pci11 dev 0 function 0 "Symbios Logic MegaRAID SAS2208" rev > 0x05: > > msi > > mfii0: "LSI MegaRAID SAS 9271-8i", firmware 23.28.0-0010, 1024MB cache > > scsibus1 at mfii0: 64 targets > > scsibus2 at mfii0: 256 targets > > > >> On 8.9.2019. 18:19, Luke Small wrote: > >>> It doesn't work for me on the > >>> ftp.hostserver.de/archive/2019-08-29-0105/amd64/ > >>> bsd.rd! > >> > >> > >> Hi, > >> > >> do you maybe have mfii on that box ? > >> > >> I'm having same problem as Mischa and i have mfii. with bsd.rd fsck > >> stops with this command > >> > >> Which disk is the root disk? ('?' for details) [sd0] sd0 > >> Checking root filesystem (fsck -fp /dev/sd0a)... > >> > >> On other boxes without mfii bsd.rd and sysupgrade works just fine.. > >> > >> between 27.08 and 29.8 i saw this commit > >> > >> Changes by: d...@cvs.openbsd.org 2019/08/27 22:55:51 > >> > >> Modified files: > >> sys/dev/pci: mfii.c > >> > >> Log message: > >> implement a DV_POWERDOWN handler to flush cache and shutdown the > controller > >> > >> this has been in snaps for the last week without issue, and has > >> been running in production on a bunch of my boxes for a week before > >> that, also without issue. > >> > >> > >> > >
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
I think I see the problem. We're going to try and test this locally and will hopefully have something committed in a few hours time. dlg > On 9 Sep 2019, at 10:33, Luke Small wrote: > > I have mfii too: > dmesg | grep mfii: > > mfii0 at pci11 dev 0 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: > msi > mfii0: "LSI MegaRAID SAS 9271-8i", firmware 23.28.0-0010, 1024MB cache > scsibus1 at mfii0: 64 targets > scsibus2 at mfii0: 256 targets > >> On 8.9.2019. 18:19, Luke Small wrote: >>> It doesn't work for me on the >>> ftp.hostserver.de/archive/2019-08-29-0105/amd64/ >>> bsd.rd! >> >> >> Hi, >> >> do you maybe have mfii on that box ? >> >> I'm having same problem as Mischa and i have mfii. with bsd.rd fsck >> stops with this command >> >> Which disk is the root disk? ('?' for details) [sd0] sd0 >> Checking root filesystem (fsck -fp /dev/sd0a)... >> >> On other boxes without mfii bsd.rd and sysupgrade works just fine.. >> >> between 27.08 and 29.8 i saw this commit >> >> Changes by: d...@cvs.openbsd.org2019/08/27 22:55:51 >> >> Modified files: >> sys/dev/pci: mfii.c >> >> Log message: >> implement a DV_POWERDOWN handler to flush cache and shutdown the controller >> >> this has been in snaps for the last week without issue, and has >> been running in production on a bunch of my boxes for a week before >> that, also without issue. >> >> >>
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
I have mfii too: dmesg | grep mfii: mfii0 at pci11 dev 0 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi mfii0: "LSI MegaRAID SAS 9271-8i", firmware 23.28.0-0010, 1024MB cache scsibus1 at mfii0: 64 targets scsibus2 at mfii0: 256 targets > On 8.9.2019. 18:19, Luke Small wrote: > > It doesn't work for me on the > > ftp.hostserver.de/archive/2019-08-29-0105/amd64/ > > bsd.rd! > > > Hi, > > do you maybe have mfii on that box ? > > I'm having same problem as Mischa and i have mfii. with bsd.rd fsck > stops with this command > > Which disk is the root disk? ('?' for details) [sd0] sd0 > Checking root filesystem (fsck -fp /dev/sd0a)... > > On other boxes without mfii bsd.rd and sysupgrade works just fine.. > > between 27.08 and 29.8 i saw this commit > > Changes by: d...@cvs.openbsd.org2019/08/27 22:55:51 > > Modified files: > sys/dev/pci: mfii.c > > Log message: > implement a DV_POWERDOWN handler to flush cache and shutdown the controller > > this has been in snaps for the last week without issue, and has > been running in production on a bunch of my boxes for a week before > that, also without issue. > > >
Re: Postscript printer recommendations
On 14/7/19 4:09 pm, Jonathan Drews wrote: > "Unlike PCL, PostScript is device independent. This means that the > PostScript language creates all of the print data and does not rely > on the printer for print data. This allow the output to be > consistent when printed on more than one type of printer or print > device. Specifically, the graphic objects will be consistent and in > some cases of higher quality than PCL." This could be re-written: "Unlike PCL, PostScript is device independent. that the print quality is at the mercy of the PostScript interpreter implemented inside the printer. If they have done a good job, graphic objects will be consistent and in some cases of higher quality than PCL, but can equally be terrible if the firmware developer has done a shoddy job." Really it's just moving the problem. If the PostScript interpreter in the printer does a poor job of generating the raster image to be printed, it's going to look crap no matter what. That does mean that PCL printers do have an up-side in that you can at least control the PostScript→PCL end of the equation, and if the PCL is well documented, it is theoretically possible to get good quality output. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: recent troubles with iwn(4)
On Sun, 2019-09-08 at 20:31 +, Bryan Stenson wrote: > I'm running -CURRENT and the iwn(4) driver for my wireless > card. Over > the past year, this has been working great, but recently (within the > last month or so), I've had issues where the NIC just stops working > after a few hours of usage. I don't have a solid steps for > reproduction. > A simple "ifconfig iwn0 down; sh /etc/netstart iwn0" seems to fix the > problem, but I haven't had to do that in the past...it just feels > like > a recent change (iwn(4) work?) has put me in this state. Hello! I have no solution for your problem, but when I read your mail I was pretty interested, because I've been having the same issue with previous snapshots from the past year or so, but the other way around; I've had issues on certain networks, for example the network in my home, where I get disconnected or my connections times out frequently. Sometimes it would require me to do the exact thing you are suggesting, namely take down the interface with either a "ifconfig iwn0 down" or sometimes also "ifconfig iwn0 delete" and then "sh /etc/netstart". Other times it was just a matter of having to wait forever before I could connect to the wireless at home. Or rather, wait to use it, because almost anything timed out at first. Then after a while it started working as expected. This issue has completely gone away some time during the last few weeks though, which I found relieving. My hardware is a Thinkpad x230 with the following output from "pcidump -v": 3:0:0: Intel Centrino Advanced-N 6205 0x: Vendor ID: 8086, Product ID: 0085 0x0004: Command: 0006, Status: 0010 0x0008: Class: 02 Network, Subclass: 80 Miscellaneous, Interface: 00, Revision: 34 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR mem 64bit addr: 0xf1c0/0x2000 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 8086 Product ID: 1311 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: 0a Min Gnt: 00 Max Lat: 00 0x00c8: Capability 0x01: Power Management State: D0 0x00d0: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: yes 0x00e0: Capability 0x10: PCI Express Link Speed: 2.5 / 2.5 GT/s, Link Width: x1 / x1 0x0100: Enhanced Capability 0x01: Advanced Error Reporting 0x0140: Enhanced Capability 0x03: Device Serial Number Serial Number: 6c8814daa8e4 I never bothered to report it, because I rarely use this particular machine at home, and since I only had issues there I assumed that it was some kind of issue with my AP. /Magnus
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
On 8.9.2019. 18:19, Luke Small wrote: > It doesn’t work for me on the > ftp.hostserver.de/archive/2019-08-29-0105/amd64/ > bsd.rd! Hi, do you maybe have mfii on that box ? I'm having same problem as Mischa and i have mfii. with bsd.rd fsck stops with this command Which disk is the root disk? ('?' for details) [sd0] sd0 Checking root filesystem (fsck -fp /dev/sd0a)... On other boxes without mfii bsd.rd and sysupgrade works just fine.. between 27.08 and 29.8 i saw this commit Changes by: d...@cvs.openbsd.org2019/08/27 22:55:51 Modified files: sys/dev/pci: mfii.c Log message: implement a DV_POWERDOWN handler to flush cache and shutdown the controller this has been in snaps for the last week without issue, and has been running in production on a bunch of my boxes for a week before that, also without issue.
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
Could it be? (from twitter): “deraadt@ modified a couple things: At startup, unveil entire filesystem to read-only. If after privdrop, some implausible bug existed in the socket setup (mostly dns-related and setsockopt) it would be largely neutered. of course, a very restrictive pledge is installed soon af...“ On Sun, Sep 8, 2019 at 11:19 AM Luke Small wrote: > It doesn’t work for me on the > ftp.hostserver.de/archive/2019-08-29-0105/amd64/ > bsd.rd! > > On Sun, Sep 8, 2019 at 10:50 AM Luke Small wrote: > >> Mine works on 8-27 >> -- >> -Luke >> > -- > -Luke > -- -Luke
recent troubles with iwn(4)
Hi all - I'm writing to "misc" rather than "bugs" as I'm not yet sure this is a bug. I'm hoping to help triage this with assistance from this list. I'm running -CURRENT and the iwn(4) driver for my wireless card. Over the past year, this has been working great, but recently (within the last month or so), I've had issues where the NIC just stops working after a few hours of usage. I don't have a solid steps for reproduction. I realize "stops working" is not a very accurate account here...but I'm confused on how to get more descriptive information of the problem. When it stops, "ifconfig" shows iwn0 with an IP address, but I'm unable to ping. Additionally, I'm not seeing any warnings/messages in "dmesg" about the device...so I'm confused. A simple "ifconfig iwn0 down; sh /etc/netstart iwn0" seems to fix the problem, but I haven't had to do that in the past...it just feels like a recent change (iwn(4) work?) has put me in this state. I'm really wanting to help here. How can I run the iwn(4) in debug mode, or increase logging verbosity? And/or, should I try to capture packets via tcpdump? And/or, can I run an older bsd.mp (without having to downgrade packages to older versions) in order to try and "bisect" where the problem may have been introduced? The following are my kernel and wireless details: # uname -a OpenBSD e530c.siliconvortex.com 6.6 GENERIC.MP#289 amd64 # pcidump -v ... 3:0:0: Intel Centrino Wireless-N 2230 0x: Vendor ID: 8086, Product ID: 0888 0x0004: Command: 0006, Status: 0010 0x0008: Class: 02 Network, Subclass: 80 Miscellaneous, Interface: 00, Revision: c4 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR mem 64bit addr: 0xf2d0/0x2000 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 8086 Product ID: 4262 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: 0b Min Gnt: 00 Max Lat: 00 0x00c8: Capability 0x01: Power Management State: D0 0x00d0: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: yes 0x00e0: Capability 0x10: PCI Express Link Speed: 2.5 / 2.5 GT/s, Link Width: x1 / x1 0x0100: Enhanced Capability 0x01: Advanced Error Reporting 0x0140: Enhanced Capability 0x03: Device Serial Number Serial Number: 6036dded4a81 With humility, an open mind, and eagerness to learn/help: Bryan
man.openbsd.org/table.5
Not sure if its just me or not, but I was looking at the table(5) manual online and sections look odd. Particularly `Mailaddr tables' and `Addrname tables'. Thanks, Edgar
Re: Why regex doesn't work in while loop's condition?
On 9/6/19 5:27 PM, Theo de Raadt wrote: Andreas Kusalananda Kähäri wrote: On Fri, Sep 06, 2019 at 02:38:18PM -0600, Theo de Raadt wrote: Christian Weisgerber wrote: On 2019-09-06, Andreas Kusalananda Kähäri wrote: read x; while [ "$x" != [abc] ]; do echo "Not a, b or c"; break; done The shells in the OpenBSD base system do not support matching regular expressions with that syntax. You may have been thinking of bash, Just to head off crazy rumors: bash doesn't either. Doesn't bash perform this task by invisibly calling out to perl? You're thinking of zsh. No I'm thinking it is all crazy. CRAZY=true [ is not [[ man ksh [[ expression ]] Similar to the test and [ ... ] commands (described later), with the following exceptions: ... The second operand of the ‘!=’ and ‘=’ expressions are patterns (e.g. the comparison [[ foobar = f*r ]] succeeds). X=a if [[ "$X" == [abc] ]] ; then echo yes ; fi prints yes ksh is in base and is often a user's login shell
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
It doesn’t work for me on the ftp.hostserver.de/archive/2019-08-29-0105/amd64/ bsd.rd! On Sun, Sep 8, 2019 at 10:50 AM Luke Small wrote: > Mine works on 8-27 > -- > -Luke > -- -Luke
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
Mine works on 8-27 -- -Luke
Re: Impossible to remove a broken package on 6.5.
On September 6, 2019 6:46:32 PM GMT+03:00, m...@jtm.cx wrote: >On Fri, Sep 06, 2019 at 07:13:21AM -0700, Chris Cappuccio wrote: >> Angelo Rossi [angelo.rossi.home...@gmail.com] wrote: >> > >> > # pkg_delete -v kicad >> > Can't locate object method "updateset_with_new" via package >> > "OpenBSD::PkgDelete::State" at >/usr/libdata/perl5/OpenBSD/Dependencies.pm >> > line 309. >> > >> >> Your /usr/libdata/perl5/OpenBSD directory is corrupted, this should >exist >> in /usr/libdata/perl5/OpenBSD/PkgAdd.pm >> >> Your upgrade seems to have failed >> > >The upgrade probably didn't fail. I ran into the exact same issue with >kicad-20100505p11; The package is available in 6.4, but was removed >and marked broken in 6.5 due to an issue with python-wx. I think the >error message Angelo Rossi quoted is simply an issue with `pkg_delete`. >Pkg_delete doesn't know what to do with a package that isn't available >anymore. > >I didn't know what to do here either. I just let the broken kicad >package >float around on my machine :). I tried to take a stab at fixing it, >but my knowledge of pkg_add internals is limited. Have you checked if anything in pkg_check(8) can help you ? Source: https://www.openbsd.org/faq/faq15.html Best Regards, Strahil Nikolov
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
On Sun, Sep 08, 2019 at 02:41:27PM +0200, Mischa Peters wrote: > > > > On 8 Sep 2019, at 14:22, Otto Moerbeek wrote: > > > >> On Sun, Sep 08, 2019 at 02:12:07PM +0200, Mischa wrote: > >> > >> For completeness here is a successful boot on 6.5 MP#5. > > > > Can you try bisecting using bsd.rd's from the archive? > > Let me try a couple and see if I get different results. > Any recommendation on how far back to start? Alas, no, -Otto > > Mischa > > >-Otto > > > >> > >> Mischa > >> > OpenBSD/amd64 BOOT 3.43 > >> boot> > >> booting hd0a:/bsd: 10683784+2466832+34+0+675840 > >> [679209+128+857256+597608]=0xf8e4c0 > >> entry point at 0x1001000 > >> [ using 2135232 bytes of bsd ELF symbol table ] > >> Copyright (c) 1982, 1986, 1989, 1991, 1993 > >>The Regents of the University of California. All rights reserved. > >> Copyright (c) 1995-2019 OpenBSD. All rights reserved. > >> https://www.OpenBSD.org > >> > >> OpenBSD 6.5 (GENERIC.MP) #5: Thu Aug 29 20:38:30 CEST 2019 > >> > >> r...@syspatch-65-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > >> real mem = 206094401536 (196546MB) > >> avail mem = 199838711808 (190581MB) > >> mpath0 at root > >> scsibus0 at mpath0: 256 targets > >> mainbus0 at root > >> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7f42c000 (99 entries) > >> bios0: vendor Dell Inc. version "2.7.0" date 05/23/2018 > >> bios0: Dell Inc. PowerEdge R620 > >> acpi0 at bios0: rev 2 > >> acpi0: sleep states S0 S4 S5 > >> acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT > >> EINJ TCPA PC__ SRAT SSDT > >> acpi0: wakeup devices PCI0(S5) PCI1(S5) > >> acpitimer0 at acpi0: 3579545 Hz, 24 bits > >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > >> cpu0 at mainbus0: apid 0 (boot processor) > >> cpu0: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.40 MHz, 06-2d-07 > >> cpu0: > >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz > >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE > >> cpu1 at mainbus0: apid 32 (application processor) > >> cpu1: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 1200.00 MHz, 06-2d-07 > >> cpu1: > >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > >> cpu1: 256KB 64b/line 8-way L2 cache > >> cpu1: smt 0, core 0, package 1 > >> cpu2 at mainbus0: apid 2 (application processor) > >> cpu2: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 > >> cpu2: > >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > >> cpu2: 256KB 64b/line 8-way L2 cache > >> cpu2: smt 0, core 1, package 0 > >> cpu3 at mainbus0: apid 34 (application processor) > >> cpu3: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 > >> cpu3: > >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > >> cpu3: 256KB 64b/line 8-way L2 cache > >> cpu3: smt 0, core 1, package 1 > >> cpu4 at mainbus0: apid 4 (application processor) > >> cpu4: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 > >> cpu4: > >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > >> cpu4: 256KB 64b/line 8-way L2 cache > >> cpu4: smt 0, core 2, package 0 > >> cpu5 at mainbus0: apid 36 (application processor) > >> cpu5: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 > >> cpu5: > >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
> On 8 Sep 2019, at 14:22, Otto Moerbeek wrote: > >> On Sun, Sep 08, 2019 at 02:12:07PM +0200, Mischa wrote: >> >> For completeness here is a successful boot on 6.5 MP#5. > > Can you try bisecting using bsd.rd's from the archive? Let me try a couple and see if I get different results. Any recommendation on how far back to start? Mischa >-Otto > >> >> Mischa >> OpenBSD/amd64 BOOT 3.43 >> boot> >> booting hd0a:/bsd: 10683784+2466832+34+0+675840 >> [679209+128+857256+597608]=0xf8e4c0 >> entry point at 0x1001000 >> [ using 2135232 bytes of bsd ELF symbol table ] >> Copyright (c) 1982, 1986, 1989, 1991, 1993 >>The Regents of the University of California. All rights reserved. >> Copyright (c) 1995-2019 OpenBSD. All rights reserved. >> https://www.OpenBSD.org >> >> OpenBSD 6.5 (GENERIC.MP) #5: Thu Aug 29 20:38:30 CEST 2019 >> >> r...@syspatch-65-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP >> real mem = 206094401536 (196546MB) >> avail mem = 199838711808 (190581MB) >> mpath0 at root >> scsibus0 at mpath0: 256 targets >> mainbus0 at root >> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7f42c000 (99 entries) >> bios0: vendor Dell Inc. version "2.7.0" date 05/23/2018 >> bios0: Dell Inc. PowerEdge R620 >> acpi0 at bios0: rev 2 >> acpi0: sleep states S0 S4 S5 >> acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT >> EINJ TCPA PC__ SRAT SSDT >> acpi0: wakeup devices PCI0(S5) PCI1(S5) >> acpitimer0 at acpi0: 3579545 Hz, 24 bits >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat >> cpu0 at mainbus0: apid 0 (boot processor) >> cpu0: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.40 MHz, 06-2d-07 >> cpu0: >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE >> cpu1 at mainbus0: apid 32 (application processor) >> cpu1: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 1200.00 MHz, 06-2d-07 >> cpu1: >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN >> cpu1: 256KB 64b/line 8-way L2 cache >> cpu1: smt 0, core 0, package 1 >> cpu2 at mainbus0: apid 2 (application processor) >> cpu2: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 >> cpu2: >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN >> cpu2: 256KB 64b/line 8-way L2 cache >> cpu2: smt 0, core 1, package 0 >> cpu3 at mainbus0: apid 34 (application processor) >> cpu3: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 >> cpu3: >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN >> cpu3: 256KB 64b/line 8-way L2 cache >> cpu3: smt 0, core 1, package 1 >> cpu4 at mainbus0: apid 4 (application processor) >> cpu4: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 >> cpu4: >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN >> cpu4: 256KB 64b/line 8-way L2 cache >> cpu4: smt 0, core 2, package 0 >> cpu5 at mainbus0: apid 36 (application processor) >> cpu5: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 >> cpu5: >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN >> cpu5: 256KB 64b/line
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
On Sun, Sep 08, 2019 at 02:12:07PM +0200, Mischa wrote: > For completeness here is a successful boot on 6.5 MP#5. Can you try bisecting using bsd.rd's from the archive? -Otto > > Mischa > > >> OpenBSD/amd64 BOOT 3.43 > boot> > booting hd0a:/bsd: 10683784+2466832+34+0+675840 > [679209+128+857256+597608]=0xf8e4c0 > entry point at 0x1001000 > [ using 2135232 bytes of bsd ELF symbol table ] > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2019 OpenBSD. All rights reserved. https://www.OpenBSD.org > > OpenBSD 6.5 (GENERIC.MP) #5: Thu Aug 29 20:38:30 CEST 2019 > > r...@syspatch-65-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 206094401536 (196546MB) > avail mem = 199838711808 (190581MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7f42c000 (99 entries) > bios0: vendor Dell Inc. version "2.7.0" date 05/23/2018 > bios0: Dell Inc. PowerEdge R620 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S4 S5 > acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT > EINJ TCPA PC__ SRAT SSDT > acpi0: wakeup devices PCI0(S5) PCI1(S5) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.40 MHz, 06-2d-07 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE > cpu1 at mainbus0: apid 32 (application processor) > cpu1: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 1200.00 MHz, 06-2d-07 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 0, package 1 > cpu2 at mainbus0: apid 2 (application processor) > cpu2: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 0, core 1, package 0 > cpu3 at mainbus0: apid 34 (application processor) > cpu3: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 0, core 1, package 1 > cpu4 at mainbus0: apid 4 (application processor) > cpu4: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 > cpu4: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu4: 256KB 64b/line 8-way L2 cache > cpu4: smt 0, core 2, package 0 > cpu5 at mainbus0: apid 36 (application processor) > cpu5: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 > cpu5: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu5: 256KB 64b/line 8-way L2 cache > cpu5: smt 0, core 2, package 1 > cpu6 at mainbus0: apid 6 (application processor) > cpu6: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 > cpu6: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT
Re: 6.6-beta (RAMDISK_CD) #281 hangs on fsck
For completeness here is a successful boot on 6.5 MP#5. Mischa >> OpenBSD/amd64 BOOT 3.43 boot> booting hd0a:/bsd: 10683784+2466832+34+0+675840 [679209+128+857256+597608]=0xf8e4c0 entry point at 0x1001000 [ using 2135232 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2019 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.5 (GENERIC.MP) #5: Thu Aug 29 20:38:30 CEST 2019 r...@syspatch-65-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 206094401536 (196546MB) avail mem = 199838711808 (190581MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7f42c000 (99 entries) bios0: vendor Dell Inc. version "2.7.0" date 05/23/2018 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpi0: wakeup devices PCI0(S5) PCI1(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.40 MHz, 06-2d-07 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 32 (application processor) cpu1: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 1200.00 MHz, 06-2d-07 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 0, package 1 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 34 (application processor) cpu3: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 1, package 1 cpu4 at mainbus0: apid 4 (application processor) cpu4: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 0, core 2, package 0 cpu5 at mainbus0: apid 36 (application processor) cpu5: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 0, core 2, package 1 cpu6 at mainbus0: apid 6 (application processor) cpu6: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.00 MHz, 06-2d-07 cpu6: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN c
6.6-beta (RAMDISK_CD) #281 hangs on fsck
Hi All, Not sure if this is something I can change but bsd.rd #281 hangs on fsck on my machine. Trying to upgrade my Dell R620 to 6.6 to test with vmm/vmd but I am unable to because of the fsck. When I ctrl-c the fsck and try to restart the installer it hangs and the host needs a reboot. Anything I can try, test, or do to either get more information or force the upgrade? Below is the dmesg of the host. Thanx! Mischa boot> bsd.rd booting hd0a:bsd.rd: 3707595+1532928+3885304+0+598016 [374998+128+454704+303083]=0xa5cd78 entry point at 0x1001000 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2019 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.6-beta (RAMDISK_CD) #281: Sat Sep 7 13:53:50 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 206094401536 (196546MB) avail mem = 199844372480 (190586MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7f42c000 (99 entries) bios0: vendor Dell Inc. version "2.7.0" date 05/23/2018 bios0: Dell Inc. PowerEdge R620 acpi0 at bios0: ACPI 3.0 acpi0: tables DSDT FACP APIC SPCR HPET DMAR MCFG WD__ SLIC ERST HEST BERT EINJ TCPA PC__ SRAT SSDT acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz, 2800.44 MHz, 06-2d-07 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,PAGE1GB,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache tsc_timecounter_init: TSC skew=0 observed drift=0 cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0: apid 1 pa 0xfec3f000, version 20, 24 pins, remapped ioapic2 at mainbus0: apid 2 pa 0xfec7f000, version 20, 24 pins, remapped acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEX1) acpiprt2 at acpi0: bus -1 (PE1C) acpiprt3 at acpi0: bus 3 (PEX2) acpiprt4 at acpi0: bus 2 (PEX3) acpiprt5 at acpi0: bus 4 (PEX4) acpiprt6 at acpi0: bus -1 (PEX5) acpiprt7 at acpi0: bus 7 (PEX6) acpiprt8 at acpi0: bus -1 (PEX7) acpiprt9 at acpi0: bus 64 (PCI1) acpiprt10 at acpi0: bus 65 (PEXB) acpiprt11 at acpi0: bus -1 (PEXC) acpiprt12 at acpi0: bus 66 (PEXD) acpiprt13 at acpi0: bus -1 (PEXE) acpicpu at acpi0 not configured "PNP0A08" at acpi0 not configured acpicmos0 at acpi0 "PNP0A08" at acpi0 not configured "PNP0A08" at acpi0 not configured "PNP0A08" at acpi0 not configured "PNP0C14" at acpi0 not configured cpu0: using IvyBridge MDS workaround pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel E5 Host" rev 0x07 ppb0 at pci0 dev 1 function 0 "Intel E5 PCIE" rev 0x07 pci1 at ppb0 bus 1 em0 at pci1 dev 0 function 0 "Intel I350" rev 0x01: msi, address bc:30:5b:f7:50:a4 em1 at pci1 dev 0 function 1 "Intel I350" rev 0x01: msi, address bc:30:5b:f7:50:a5 em2 at pci1 dev 0 function 2 "Intel I350" rev 0x01: msi, address bc:30:5b:f7:50:a6 em3 at pci1 dev 0 function 3 "Intel I350" rev 0x01: msi, address bc:30:5b:f7:50:a7 ppb1 at pci0 dev 2 function 0 "Intel E5 PCIE" rev 0x07 pci2 at ppb1 bus 3 ppb2 at pci0 dev 2 function 2 "Intel E5 PCIE" rev 0x07 pci3 at ppb2 bus 2 mfii0 at pci3 dev 0 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x01: msi mfii0: "PERC H710 Mini", firmware 21.3.2-0005, 512MB cache scsibus0 at mfii0: 64 targets sd0 at scsibus0 targ 0 lun 0: naa.6848f690e6cb3f0024cc665a2468732c sd0: 139392MB, 512 bytes/sector, 285474816 sectors sd1 at scsibus0 targ 1 lun 0: naa.6848f690e6cb3f0024cc667325df6e29 sd1: 953344MB, 512 bytes/sector, 1952448512 sectors scsibus1 at mfii0: 256 targets ppb3 at pci0 dev 3 function 0 "Intel E5 PCIE" rev 0x07: msi pci4 at ppb3 bus 4 "Intel E5 Address Map" rev 0x07 at pci0 dev 5 function 0 not configured "Intel E5 Error Reporting" rev 0x07 at pci0 dev 5 function 2 not configured ppb4 at pci0 dev 17 function 0 "Intel C600 Virtual PCIE" rev 0x05 pci5 at ppb4 bus 5 "Inte