OpenBSD on Macbook Pro : / not properly unmounted at each reboot
Hi list, I have just installed amd64 -current on a Macbook Pro from late 2013 (dmesg below) and am slightly worried by 1) some of the things I read in the dmesg and 2) having to run fsck_ffs(8) at each reboot in single user mode. The laptop has an SSD, partitioned in 4 : ESP, OSX, OSX recovery and OpenBSD. I configured it so that it starts in USB 2 emulation mode. The OpenBSD install is the default one as regards disklabel. Each time, I shut OpenBSD down, I get the config_active_children... lines at the end of the dmesg below. Upon reboot, hot or cold, the system complains that / has not been unmounted properly. Automatic file system check succeeds on / but fails on /var. It drops to single user mode, where I need to run fsck_ffs manually and only then go multi-user. Has any one experienced a similar behaviour? Are some errors/warnings in the dmesg I can/should do something about? Thanks in advance for your feedback. Alexis OpenBSD 5.7-beta (GENERIC.MP) #834: Tue Feb 3 18:08:48 MST 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error ff real mem = 4182765568 (3988MB) avail mem = 4067536896 (3879MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (43 entries) bios0: vendor Apple Inc. version "MBP111.88Z.0138.B11.1408291433" date 08/29/2014 bios0: Apple Inc. MacBookPro11,1 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC SBST ECDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT MCFG DMAR acpi0: wakeup devices P0P2(S3) EC__(S3) HDEF(S3) RP01(S3) RP02(S3) RP03(S4) ARPT(S4) RP05(S3) RP06(S3) EHC1(S3) EHC2(S3) XHC1(S3) ADP1(S3) LID0(S3) 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) i5-4258U CPU @ 2.40GHz, 2300.31 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE, BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID 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 100MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz, 2300.01 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE, BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID 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-4258U CPU @ 2.40GHz, 2300.01 MHz cpu2: 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE, BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID 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-4258U CPU @ 2.40GHz, 2300.01 MHz cpu3: 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEA DLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE, BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xe000, bus 0-155 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P2) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 3 (RP03) acpiprt5 at acpi0: bus 5 (RP05) acpiprt6 at acpi0: bus 4 (RP06) acpicpu0 at acpi0: C3, C1, PSS acpicpu1 at acpi0: C3, C1, PSS acpicpu2 at acpi0: C3, C1, PSS acpicpu3 at acpi0: C3, C1, PSS acpibat0 at acpi0: BAT0 model "3545797981023400290" type 3545797981528607052 oem "3545797981528673619" acpiac0 at acpi0: AC unit online acpibtn0 at acpi0: LID0 acpibtn1 at acpi0: PWRB acpibtn2 at acpi0: SLPB acpivideo0 at acpi0: IGPU acpivout0 at acpivideo0: DD01 cpu0: Enhanced SpeedStep 2300 MHz: speeds: 2401, 2400, 2300, 2000, 1800, 1500, 1300, 1100, 900, 768 MHz memory map conflict 0xe00f8000/0x1000 memory map conflict 0xfed1c00
Re: xenocara source
You can simply add a newline like /xenocara/// # I don't really remember the syntax in the list of directories in a file under /usr/src/CVS thus making all of your sources updated at once without any error. _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail http://mail.yahoo.fr
disklabel != /dev content
Hi list ! I recently jumped into the OpenBSD's world from GNU/Linux's one. I am still not familiar with some of OpenBSD's practices and encounter some problems. Well, here is the point : I have just installed OpenBSD-4.1-release on a IBM Thinkpad T22 laptop. Some mistakes (which I'd better not talk about ;) lead me to change my partitions layout : I had a 10M wd0h and a 9G wd0i. I deleted wd0i and expanded wd0h. All this has been done by accessing the disk through a shell on the install CD. Now, disklabel(8) run from the on-disk system show the right size for wd0h. But the mounted wd0h partition still seems to have its ancient size (10M). I tried to delete the /dev/wd0h node and re-create it : no improvement. (df still shows 10M available). I found that the system had a static layout of the disk, created during installation, but don't know how to update it. Moreover it seems to have already been partially updated (in disklabel(8)). Any pointer ? _ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
Re: disklabel != /dev content [SOVLED]
Thank you all for your answers.
As some of you suggested, I used newfs(8) on wd0h
since my wd0{h,i} partitions did not contain anything
interesting. It updated the partition layout from the
disklabel and all works fine now.
Thanks again.
_
Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
Formating errors on XkbBell man page [from [EMAIL PROTECTED]
> renaming the files is probably not a great option, so unless someone > hacks in the support to man(1), it will probably stay that way. Why so ? I mean : why isn't renaming files a suitable option ? Apologies for such a candid question if it turns out to be labelled as ``stupid''. Right now, man(1) looks at the file name and decides what its fate will be according to a series of rules given in man.conf(5). This at least is what comes first after having read both manpages. I've not read the code. Making man(1) support X conventions would require 1/ a change in man.conf(5) format - a new keyword would be needed-and 2/ man(1) to look *into* the file. A sh(1) script could handle it automatically. The one that follows targets an existing setup, it just stands as a proof of concept : ### #!/bin/sh for file in $(find .) ; do if test ! -d $file ; then if test "$(head -1 $file | \ sed -e 's/"/\"/' -e "s/\'/\\\'/")" = "\'\\\" t" ; then # name-chaging code here fi fi done exit 0 ### I'd be interested in working on that if others consider it a reliable solution. Hyjial _ Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr
Re : Formating errors on XkbBell man page [from [EMAIL PROTECTED]
Fine. I am surely blind to most bits of effort developers have to put in. I will have a go at it. _ Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr
Re : Formating errors on XkbBell man page [from [EMAIL PROTECTED]
Hi,
After having spend some time reading man (1) code, the following
proposal
comes :
Create a keyword for man.conf (5) - _ibuild for example - for lines
like : ``_ibuild - a letter - - associated command -''
The letter
would appear on the first line of the manpage file and
would be separated from
the leading ``{.,'}\"'' by white spaces and single.
man (1) would accept both
(in fact, it would go to the first blank character
and start from there). This
would be triggered only in case of a
.[1-9n]{,[a-z]}{,.{gz,Z}} extension. man
(1) would insert the command
given by the ``_ibuild'' line right before the ``
{,|} /usr/bin/nroff -man'',
removing the trailing ``%s'' as needed.
Triggering
the in-file inquiry would be more easily implemented as
a config file setting
- a ``_iext (extension list)'' line -
As an additionnal possibility, why not
allow skipping in-file inquiry
for some directories - those in ``base'' mostly
- using an ``_iskip''
keyword in man.conf (5).
Suggestions ?
Personnaly I find
it a bit intrusive for man.conf (5).
Cheers.
Why Perl for pkg_* tools ?
Hi list ! Reading through OpenBSD's codebase, I have noticed that the code living under src/usr.sbin/pkg_add is written in Perl. Perl is distributed under the Artistic license, though. The latter is not as permissive as the BSD license under which monst of OpenBSD is released. No doubt that is the reason why Perl lives in src/gnu. Why have such a tool using a non-BSD package when there was choice not to do so ? What technical reasons have lead the developers to elect this language ? I am just curious about the fact and didn't manage to find information in tech@ and mis@ archives. Thanks in advance. Hyjial. __ Do You Yahoo!? En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicitis http://mail.yahoo.fr Yahoo! Mail
sys/tcp.h does not compile with _POSIX_SOURCE
Hi list ! There is a u_int on line 50 of sys/tcp.h. u_int is defined only if __BSD_VISIBLE is which it is not is _POSIX_SOURCE is defined. Is this intended ? Hit into this when trying to build a program which uses libsoup. Thanks, hyjial
Re: re(4) panic on 13 Jan 2009 snap
Hi !
I got the same issue, before last revision of src/sys/dev/pci/ppb.c by
Mark (kettenis@). Yet your trace and ps output is rather different
from what I got back then. I am not familiar enough with the kernel
internals to state about the similarity of our situations. The issue
still shows up if I don't disable apm at boot. Have you done so ?
Regards.
hyjial
2009/1/19 Bryan :
> Greetings,
>
>
> I am still having issues with the re(4) interface on my server. I
> mentioned this on the list, and was told that the re(4) fix was in. I
> am running the 13 Jan 2009 snapshot, and I can still reproduce the
> error on a regular basis. It goes like this...
>
> 1. push the power button
> 2. boot openbsd
> 3. panic
>
> panic: config_detach: forced detach of re0 failed (45)
> Stopped atDebugger+0x4: leave
>
> 4. issue "boot sync"
> 5. system restarts
> 6. re(4) starts with no issues
>
> if I shutdown, or do a warm reboot, I have to do step 4 and restart the
> system.
>
> I do have a picture of the error I receive when the system is going to
> panic. As I have no console, and puc(4) is useless for console use,
> the picture can be found here:
>
> http://picasaweb.google.com/lh/photo/Das3TsaFIvV1I-zKTHvaog?feat=directlink
>
> I also did a ps, and trace of the system. here is the photo of that.
>
> http://picasaweb.google.com/lh/photo/l7IN31cOVXa1y8yn74aA8w?feat=directlink
>
> If someone has any other ideas, please let me know. The dmesg below is
> when the server will come up after a "boot sync" and a warm restart.
>
> I do intend on updating to the latest snapshot (jan 18th) in the next
> few minutes.
>
> Regards,
> Bryan Brake
>
> OpenBSD 4.4-current (GENERIC.MP) #35: Tue Jan 13 10:19:47 MST 2009
>t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
> cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 1 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> real mem = 3488833536 (3327MB)
> avail mem = 3384754176 (3227MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 10/23/08, BIOS32 rev. 0 @ 0xf0010,
> SMBIOS
> rev. 2.5 @ 0xf06e0 (54 entries)
> bios0: vendor American Megatrends Inc. version "5.32" date 10/23/2008
> bios0: HP-Pavilion FK484AV-ABA m9400t
> acpi0 at bios0: rev 0
> acpi0: tables DSDT FACP APIC MCFG OEMB HPET GSCI SLIC SSDT
> acpi0: wakeup devices P0P2(S4) P0P1(S4) PS2K(S3) PS2M(S3) USB0(S3) USB1(S3)
> USB2
> (S3) USB5(S3) EUSB(S3) USB3(S3) USB4(S3) USBE(S3) GBE_(S4) P0P4(S4) P0P5(S4)
> P0P
> 6(S4) P0P7(S4) P0P8(S4) P0P9(S4) SLPB(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: apic clock running at 266MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 0 GHz
> cpu1:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 0 GHz
> cpu2:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 0 GHz
> cpu3:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (P0P1)
> acpiprt2 at acpi0: bus 3 (P0P4)
> acpiprt3 at acpi0: bus -1 (P0P5)
> acpiprt4 at acpi0: bus 2 (P0P6)
> acpiprt5 at acpi0: bus -1 (P0P7)
> acpiprt6 at acpi0: bus -1 (P0P8)
> acpiprt7 at acpi0: bus -1 (P0P9)
> acpicpu0 at acpi0
> acpicpu1 at acpi0
> acpicpu2 at acpi0
> acpicpu3 at acpi0
> acpibtn0 at acpi0: SLPB
> acpibtn1 at acpi0: PWRB
> bios0: ROM list: 0xc/0xe200 0xce800/0x1000
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x02
> ppb0 at pci0 dev 1 function 0 "Intel 82G33 PCIE" rev 0x0
Re: installboot: broken MBR
Hi ! Can you send the output of ``./installboot -v -n boot biosboot (your disk dev)'' from the installation medium ? Notice that must be run from the /usr/mdec directory of your installed system, otherwise, installboot(8) will complain about cross-device installation. As a temporay workaround, and only if you get something like ``extended partition ...: type ... offset ...'' before getting ``broken MBR'' in the output, you can swap the two partition entries sda1 and sda2 (via the swap command in fdisk(8)) and re-run installboot(8) (the above command, without the ``-n'' switch). Cheers ! hyjial. N.B.: installboot(8)---at least on i386---would not find an OpenBSD partition in an extended one. It gets confused with offsets when recursing through the extended partition. I have been working on the issue some months ago and ran out of time. I will get back to it ASAP.
