Re: Livelock on recent current
On 2020-09-12 01:24, Kevin Oberman wrote: I'm happy to see that I am not crazy! This is mostly anecdotal. The freezes have occurred regularly, without question, but the details are not statistically verified. This is based on my perceptions. The only things I am really sure of is that the system is unusable on head and runs well on 12.1-Release. This system has a rather new Intel GPU, the Comet Lake, and is only supported on head with drm-devel-kmod, so moving back to 12.1 is not an option. I am curious what processor is on the T490. I am using the default keyboard layout. On terminal sessions (vt), when the keyboard is idle. I have had the system run for a couple of hours or longer with no problems. To get bigger ports to build, I usually switch to another vty and keep that one fairly busy. It will freeze when no vty is active, but as long as any is active every minute or less. I have had freezes in under a minute, but rarely. Moving on to other possibly related (or not) issues: When running on X (MATE), it may freeze whether the keyboard is active or not. OTOH, it seems to freeze less often. I've had X lock up mid-word but also run for 15 or more minutes. It eventually does freeze, but I don't think I've ever gone more than 10 minutes on an idle keyboard without a freeze without X running. Switching to a vty and keeping it fairly active still seems to keep the system alive while X is being used. X is performing very poorly. If the processors are busy, say by building a port, screen updates are very slow, often pausing for several seconds. Expose events seem to often redraw all windows which is very annoying. Several times I thought the system was frozen only to suddenly have the screen update and everything be normal, again. I also have this issue on a Carbon X1 7th Gen (type 20QDCTO1WW) on recent -CURRENT snapshots. I'll try 12-STABLE for now since the system is totally unreliable on -CURRENT. I used the default English kb layout but that didn't resolve anything. The longest I've been able to just let the live cd run (running top) when on AC before my system completely freezes is roughly about 7 hours. Then again, I've also seen even the live cd from the memstick.img freeze after a couple of seconds after login (did a tail -f on /var/log/messages and it almost immediately froze right after that). When it freezes the fan ramps up at a fairly high rpm. Unless I forcibly power down the high rpm just continues. Power mode for AC is set to max performance. Adaptive thermal management scheme for AC also set to max performance. I've tried booting both using UEFI and also legacy BIOS but in both cases I've experienced the same behaviour. Any specific settings in BIOS to perhaps avoid? I bought this ThinkPad based on the info listed on https://wiki.freebsd.org/Laptops/Thinkpad_X1_Carbon I just made the following BIOS changes: config -> power -> adaptive thermal management > scheme for AC : balanced (was : maximize performance) config -> power -> sleep state : Linux (was: windows 10) config -> intel AMT > intel AMT control : disabled (was : enabled) security -> security chip > security chip : Off (was : On) <-- security chip type : TPM 2.0 Hasn't improved anything i'm afraid. User Duffyx on the forums mentioned https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248659 So consider this an official 'me too' ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Build failure
On Tue, Oct 20, 2020 at 07:15:16AM +, you (marco) sent the following to [freebsd-current] : > > > > I checked out 05b104834ae7 (r366780) from > https://cgit-beta.freebsd.org/src.git and ran a 'make -j4 builworld and make > -j4 buildkernel' > for GENERIC-NODEBUG which also failed (buildworld was successfull). > I did update the ports tree (portsnap fetch update) right before > buildkernel and also have > drm-current-kmod installed. > > My normal procedure of updating current using BEs (using > WITH_MALLOC_PRODUCTION= in /etc/src.conf): > > make -j4 buildworld > make -j4 buildkernel > bectl create x > bectl mount x /mnt > make -j4 installkernel DESTDIR=/mnt > mergemaster -Fp -D /mnt > make -j4 installworld DESTDIR=/mnt > mergemaster -Fi -D /mnt > make -DBATCH_DELETE_OLD_FILES delete-old DESTDIR=/mnt > make -DBATCH_DELETE_OLD_FILES delete-old-libs DESTDIR=/mnt (optional) > bectl umount x > bectl activate x > shutdown -r +1 > > I do see there's an update to drm-current-kmod (g20201003) and I'm currently > on g20200914 but I don't want to > update in place in my current BE (not sure if this could solve the > errors that are thrown). > > --- linux_backlight.o --- > In file included from > /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/src/linux_backlight.c:12: > In file included from > /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux/device.h:4: > In file included from > /usr/src/sys/compat/linuxkpi/common/include/linux/device.h:44: > In file included from > /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux/backlight.h:12: > In file included from > /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux/fb.h:10: Managed to get this all sorted. I created a new BE based on r366252, mounted it and updated and upgraded pkg and all my packages (including drm-current-kmod) into that new BE. Booted to that BE and from there I did another buildkernel which succeeded. I hadn't run make cleanworld prior to the make buildkernel so still had that world built and proceeed from there. I'm now booted into my latest BE [~] uname -apKU FreeBSD harbinger 13.0-CURRENT FreeBSD 13.0-CURRENT #1 05b104834ae7-c253833(HE C-NODEBUG amd64 amd64 1300121 1300121 -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Build failure
les/drm-current-kmod/linuxkpi/gplv2/src/linux_device.c:1: In file included from /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux/device.h:4: /usr/src/sys/compat/linuxkpi/common/include/linux/device.h:219:1: error: static declaration of 'dev_set_drvdata' follows non-static declaration dev_set_drvdata(struct device *dev, void *data) ^ /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux/i2c.h:249:2: note: previous implicit declaration is here dev_set_drvdata(>dev, data); ^ In file included from /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/src/linux_device.c:1: In file included from /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux/device.h:4: /usr/src/sys/compat/linuxkpi/common/include/linux/device.h:438:1: error: static declaration of 'device_unregister' follows non-static declaration device_unregister(struct device *dev) ^ /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux/i2c.h:237:2: note: previous implicit declaration is here device_unregister(>dev); ^ 16 errors generated. *** [linux_device.o] Error code 1 make[4]: stopped in /usr/local/sys/modules/drm-current-kmod/linuxkpi 4 errors make[4]: stopped in /usr/local/sys/modules/drm-current-kmod/linuxkpi *** [modules-all] Error code 2 make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG 1 error make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem
On Sun, Sep 06, 2020 at 11:58:23AM -0400, you (Ryan Moeller) sent the following to [freebsd-current] : > > > The git hashes are the most unambiguous way to see what you have. The > svn log shows the last vendor update for zfs brought it to fd20a81b, and > the most recent version of the port is at 6fe3498ca. > > For the port I have hijacked zfs --version to show the git hash in the > version string, but the base zfs does not do this, so it is not as easy > to determine at runtime there. Nice, wasn't aware the port supported zfs --version to show the git hashes. Would definitely be nice for base ZFS to also support it at runtime. -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem
On Sun, Sep 06, 2020 at 10:22:33AM -0400, you (Ryan Moeller) sent the following
to [freebsd-current] :
>
> > I switched back to base ZFS whilst on r364030 and upgraded to r365336 and
> > deinstalled
> > openzfs and openzfs-kmod for now.
> > ZFS in base nicely auto-imported both zroot and backup pools for the 1st
> > time.
>
> I need to update the port, it's a little behind what's in base now.
Thanks Ryan
How does one verify which version of OpenZFS is actually in base?
sysutils/openzfs{-kmod} has/have 20200821, UPDATING has the 20200824 listing.
I can't find any version reference of OpenZFS in base from svn log
either.
--
Marco van Lienen -- FreeBSD enthusiast
https://keybase.io/scarcry , GnuPG id: 8580E6CB
"The Tuck Pendleton machine...zero defects."
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem
On Sat, Sep 05, 2020 at 12:02:58AM +0100, you (Graham Perrin) sent the following to [freebsd-current] : > > > FYI <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239702> > I switched back to base ZFS whilst on r364030 and upgraded to r365336 and deinstalled openzfs and openzfs-kmod for now. ZFS in base nicely auto-imported both zroot and backup pools for the 1st time. -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem
On Sat, Sep 05, 2020 at 12:02:58AM +0100, you (Graham Perrin) sent the following to [freebsd-current] : > > What's the best advice here? > > I could switch back to base ZFS in this active BE, see if the system will > > be able to import zroot and mount all my datasets and boot, then try to > > create another BE using base ZFS and then attempt to update. > > > FYI <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239702> > > >> sysutils/openzfs bectl activate … cannot promote … not a cloned > filesystem … did not successfully activate boot environment Thanks Graham -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
bectl: cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem
I'm still on r364030 using sysutils/openzfs 2020081800 (compiled from ports) pkg info -s openzfs openzfs-2020081800 15.3MiB I currently only have 1 BE and would like to attempt to upgrade to anything past r364746 I don't use encryption, won't attempt an 'zpool upgrade' of zroot so think I should be safe to move forward. # bectl list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created r364030-OpenZFS zroot/ROOT/r364030-OpenZFS NR / 15.2G 2020-08-22 22:46 create new BE # bectl create r364030-OpenZFS2 root@harbinger:~ # bectl list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created r364030-OpenZFS zroot/ROOT/r364030-OpenZFS NR / 15.2G 2020-08-22 22:46 r364030-OpenZFS@2020-08-30-19:23:04-0 - - 0 2020-08-30 19:23 r364030-OpenZFS2 zroot/ROOT/r364030-OpenZFS2- - 8K 2020-08-30 19:23 zroot/ROOT/r364030-OpenZFS@2020-08-30-19:23:04-0 - - 0 2020-08-30 19:23 activate new BE # bectl activate r364030-OpenZFS2 cannot promote 'zroot/ROOT/r364030-OpenZFS2': not a cloned filesystem Did not successfully activate boot environment r364030-OpenZFS2 # zfs get origin zroot/ROOT/r364030-OpenZFS2 NAME PROPERTY VALUE SOURCE zroot/ROOT/r364030-OpenZFS2 origin zroot/ROOT/r364030-OpenZFS@2020-08-30-19:23:04-0 - Despite the warning/erros messages listed a 'bectl list' does show that the new BE will be active on reboot # bectl list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created r364030-OpenZFS zroot/ROOT/r364030-OpenZFS N / 15.2G 2020-08-22 22:46 r364030-OpenZFS@2020-08-30-19:23:04-0 - - 0 2020-08-30 19:23 r364030-OpenZFS2 zroot/ROOT/r364030-OpenZFS2R - 8K 2020-08-30 19:23 zroot/ROOT/r364030-OpenZFS@2020-08-30-19:23:04-0 - - 0 2020-08-30 19:23 However the boot fails dropping me to the mountroot prompt. Luckily activating r364030-OpenZFS again is not a problem and the system will happily boot from that again after attempting to boot from r364030-OpenZFS2. So now I have only 1 working BE and it feels a bit tricky to try an upgrade in place. What's the best advice here? I could switch back to base ZFS in this active BE, see if the system will be able to import zroot and mount all my datasets and boot, then try to create another BE using base ZFS and then attempt to update. -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 13-CURRENT won't boot after switch to sysutils/openzfs
On Sat, Aug 22, 2020 at 10:10:14PM +, you (marco) sent the following to [freebsd-current] : > On Sat, Aug 22, 2020 at 04:48:48PM +, you (marco) sent the following to > [freebsd-current] : > > On Sat, Aug 22, 2020 at 12:31:24PM -0400, you (Ryan Moeller) sent the > > following to [freebsd-current] : > > > > > So besides not being able to > > boot from the openzfs 2020080800 package install, I can't figure out why I > > can't upgrade the openzfs pkg to 2020081800 (which is the latest one in > > ports so I presume a package also exists of that same version) > > > > If that won't work either I'll see if I can build sysutils/openzfs from > > ports but I'd rather not mix packages and ports. > > building and installing the GENERIC kernel did not do anything. > I can confirm BE r364030-OpenZFS booted with GENERIC but I got dropped > into the mountroot prompt again. > Before I got there I saw: > > Trying to mount root from zfs:zroot/ROOT/r364030-OpenZFS failed with > error 2: unknown file system. > > Guess I'll try to install sysutils/openzfs from ports next. Not happy with having to install the port but that worked. I removed openzfs and openzfs-kmod via pkg remove. Then did a 'make install clean' from sysutils/openzfs (2020081800) with r364030 BE active. Once I confirmed the port installed a newer /boot/modules/openzfs.ko I destroyed r364030-OpenZFS and created it again so it would be in sync with r364030 and it would have the latest openzfs.ko. When I imported my backup pool (single drive, 1 vdev) /etc/zfs/zpool.cache was automatically created. So now I have 2 zpool cache files [~] ls -l /boot/zfs/zpool.cache /etc/zfs/zpool.cache -rw-r--r-- 1 root wheel 1456 Aug 22 22:04 /boot/zfs/zpool.cache -rw-r--r-- 1 root wheel 3088 Aug 22 22:54 /etc/zfs/zpool.cache [~] zpool get cachefile zroot backup NAMEPROPERTY VALUE SOURCE backup cachefile - default zroot cachefile - default So the port does work even with running the GENERIC-NODEBUG kernel. Is it even possible to build a port only into a new BE and not the current one given how /usr is not mounted? Now I had to polute the active BE which could get me into trouble. I was hoping using BEs I could experiment by installing a port straight into the mounted BE. If that is possible I wouldn't mind getting some pointers on how to make that work. -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." signature.asc Description: PGP signature
Re: 13-CURRENT won't boot after switch to sysutils/openzfs
On Sat, Aug 22, 2020 at 04:48:48PM +, you (marco) sent the following to [freebsd-current] : > On Sat, Aug 22, 2020 at 12:31:24PM -0400, you (Ryan Moeller) sent the > following to [freebsd-current] : > > > > > So besides not being able to boot > from the openzfs 2020080800 package install, I can't figure out why I can't > upgrade the openzfs pkg to 2020081800 (which is the latest one in ports so I > presume a package also exists of that same version) > > > > > > Ok the pkg repo may not be updated with the new version yet, the latest > > I see is still 08. I think the problem though is you aren't using the > > GENERIC kernel, so the module from the pkg repo is failing to load at > > boot. You should build the module from ports instead, or use the GENERIC > > kernel. Let me know if that works for you! > > Okay, currently running a buildkernel which I'll install into > r364030-OpenZFS. > I'm running GENERIC-NODEBUG to see if I can squeeze a bit more > performnce out of this ThinkPad X230 > But I'll build and install GENERIC into the new BE to see if that'll make a > difference. > > These will be my steps: > > cd /usr/src (currently at r364030) > make -DMALLOC_PRODUCTION -j4 buildkernel > bectl mount r364030-OpenZFS /mnt > set openzfs_load="YES" in /mnt/boot/loader.conf and comment out zfs_load for > Base ZFS > make -DMALLOC_PRODUCTION -j4 installkernel DESTDIR=/mnt > mergemaster -Fp -D /mnt /* don't think is needed since I haven't buildworld > from updated sources beyond r364030 > mergemaster -Fi -D /mnt /* don't think is needed since I haven't buildworld > from updated sources beyond r364030 > make -DBATCH_DELETE_OLD_FILES delete-old DESTDIR=/mnt > bectl umount r364030-OpenZFS > bectl activate r364030-OpenZFS > shutdown -r now > > If that won't work either I'll see if I can build sysutils/openzfs from ports > but I'd rather not mix packages and ports. building and installing the GENERIC kernel did not do anything. I can confirm BE r364030-OpenZFS booted with GENERIC but I got dropped into the mountroot prompt again. Before I got there I saw: Trying to mount root from zfs:zroot/ROOT/r364030-OpenZFS failed with error 2: unknown file system. Guess I'll try to install sysutils/openzfs from ports next. -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." signature.asc Description: PGP signature
Re: 13-CURRENT won't boot after switch to sysutils/openzfs
On Sat, Aug 22, 2020 at 12:31:24PM -0400, you (Ryan Moeller) sent the following to [freebsd-current] : > > > So besides not being able to boot from the openzfs 2020080800 package > > install, I can't figure out why I can't upgrade the openzfs pkg to > > 2020081800 (which is the latest one in ports so I presume a package also > > exists of that same version) > > > Ok the pkg repo may not be updated with the new version yet, the latest > I see is still 08. I think the problem though is you aren't using the > GENERIC kernel, so the module from the pkg repo is failing to load at > boot. You should build the module from ports instead, or use the GENERIC > kernel. Let me know if that works for you! Okay, currently running a buildkernel which I'll install into r364030-OpenZFS. I'm running GENERIC-NODEBUG to see if I can squeeze a bit more performnce out of this ThinkPad X230 But I'll build and install GENERIC into the new BE to see if that'll make a difference. These will be my steps: cd /usr/src (currently at r364030) make -DMALLOC_PRODUCTION -j4 buildkernel bectl mount r364030-OpenZFS /mnt set openzfs_load="YES" in /mnt/boot/loader.conf and comment out zfs_load for Base ZFS make -DMALLOC_PRODUCTION -j4 installkernel DESTDIR=/mnt mergemaster -Fp -D /mnt /* don't think is needed since I haven't buildworld from updated sources beyond r364030 mergemaster -Fi -D /mnt /* don't think is needed since I haven't buildworld from updated sources beyond r364030 make -DBATCH_DELETE_OLD_FILES delete-old DESTDIR=/mnt bectl umount r364030-OpenZFS bectl activate r364030-OpenZFS shutdown -r now If that won't work either I'll see if I can build sysutils/openzfs from ports but I'd rather not mix packages and ports. -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." signature.asc Description: PGP signature
Re: 13-CURRENT won't boot after switch to sysutils/openzfs
On Sat, Aug 22, 2020 at 09:47:49AM -0400, you (Ryan Moeller) sent the following
to [freebsd-current] :
>
> On 8/22/20 9:29 AM, Ryan Moeller wrote:
> >>
> >> When switching from base ZFS to sysutils/openzfs 2020080800 the boot
> >> process fails.
> >
> > The most recent version (2020081800) fixes this.
> >
> > -Ryan
> >
> Sorry, pre-coffee. I don't think the issue I had in mind there (OpenZFS
> uses /etc/zfs/zpool.cache instead of /boot/zfs/zpool.cache, we added a
> fallback) explains your problem.
>
> Did you install openzfs from the pkg repo?
I installed openzfs from the latest FreeBSD repo
(pkg+http://pkg.FreeBSD.org/${ABI}/latest)
current BEs
[~] bectl list -aDs
BE/Dataset/Snapshot Active Mountpoint Space Created
r364030
zroot/ROOT/r364030 NR / 15.2G 2020-08-11
08:25
r364030@2020-08-22-15:52:19-0 - - 31.4M 2020-08-22
15:52
r364030-OpenZFS
zroot/ROOT/r364030-OpenZFS - /mnt 419M 2020-08-22
15:52
zroot/ROOT/r364030@2020-08-22-15:52:19-0 - - 31.4M 2020-08-22
15:52
Just did a 'pkg update' on my active BE.
I don't know what is happening here, can't seem to upgrade openzfs:
[~] pkg version | grep openzfs
openzfs-2020080800 <
openzfs-kmod-2020080800<
So there should be an update for sysutils/openzfs and openzfs-kmod but running
a 'pkg upgrade' doesn't list openzfs for an upgrade.
After creating and mounting the new BE I've also tried:
[~] d bectl mount r364030-OpenZFS /mnt
[~] d pkg -r /mnt update -f
[~] d pkg -r /mnt upgrade
Openzfs isn't listed for an upgrade.
After the pkg upgrade, running pkg version claims :
[~] pkg -r /mnt version | grep openzfs
openzfs-2020080800 =
openzfs-kmod-2020080800=
[~] d pkg -r /mnt upgrade -f openzfs
[~] d pkg -r /mnt upgrade -f openzfs
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):
Installed packages to be REINSTALLED:
openzfs-2020080800
Number of packages to be reinstalled: 1
2 MiB to be downloaded.
Proceed with this action? [y/N]:
So besides not being able to boot from the openzfs 2020080800 package install,
I can't figure out why I can't upgrade the openzfs pkg to 2020081800 (which is
the latest one in ports so I presume a package also exists of that same version)
--
Marco van Lienen -- FreeBSD enthusiast
https://keybase.io/scarcry , GnuPG id: 8580E6CB
"The Tuck Pendleton machine...zero defects."
signature.asc
Description: PGP signature
13-CURRENT won't boot after switch to sysutils/openzfs
I'm running r364030. [~] uname -apKU FreeBSD harbinger 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r364030: Tue Aug 11 07:15:59 UTC 2020 root@harbinger:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 amd64 1300105 1300105 When switching from base ZFS to sysutils/openzfs 2020080800 the boot process fails. These are the steps I took: - bectl create r364030-OpenZFS - bectl mount r364030-OpenZFS /mnt - edit /mnt/boot/loader.conf to use openzfs_load="YES" instead of zfs_load. - bectl activate r364030-OpenZFS - bectl umount r364030-OpenZFS - shutdown -r now The boot process shows: Loader variables: vfs.root.mountfrom=zfs:zroot/ROOT/r364030-OpenZFS But in the end never boots and drops me to the mountroot prompt I've tried several options to make it boot but when I just enter (empty line) I get the following: panic: mountroot: unable to (re-)mount root pls see https://bsd.to/C4yL -- Marco van Lienen -- FreeBSD enthusiast https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." signature.asc Description: PGP signature
Re: imported zpool not persistent across reboot
On Sat, May 30, 2020 at 11:17:53PM +0200, you (claudiu vasadi) sent the following to [freebsd-current] : > zpool set cachefile=/boot/zfs/zpool.cache The cachefile property is something I thought about but didn't think it to be the solution because the default zroot pool also doesn't have the cachefile property set: [~] zpool get cachefile zroot backup NAMEPROPERTY VALUE SOURCE backup cachefile - default zroot cachefile - defaul Come to think of it, because I'm still on base ZFS and having imported the backup pool as readonly, I can't even set any property for the backup pool. So the only way for me to get this backup pool imported properly is to switch to the sysutils/openzfs port. -- Marco van Lienen -- Unix SysAdmin https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgp5LAKAzflUp.pgp Description: PGP signature
Re: imported zpool not persistent across reboot
On Sat, May 30, 2020 at 10:05:39PM +0200, you (Ronald Klop) sent the following to [freebsd-current] : > On Fri, 29 May 2020 16:37:03 +0200, marco wrote: > > >I'm on -CURRENT (r361307) and using base ZFS. > >I imported a zpool that was created on SmartOS with some unsupported > >feature flags so had to import it read-only. > > > What was the exact command you used to import the pool? > > Regards, > Ronald. zpool import -o readonly=on backup -- Marco van Lienen -- Unix SysAdmin https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgpG95H50QXGM.pgp Description: PGP signature
Re: ZFS BE not booting
On Thu, May 28, 2020 at 06:41:25PM +0300, you (Andrey Fesenko) sent the following to [freebsd-current] : > > - mergemaster -Fi > > - make delete-old > > - final reboot > > > > too more reboot > > make buildworld > make buildkernel > beadm create xxx > beadm mount xxx /mnt > make installkernel DESTDIR=/mnt > mergemaster -Fp -D /mnt > make installworld DESTDIR=/mnt > mergemaster -Fi -D /mnt > make delete-old DESTDIR=/mnt > make delete-old-libs DESTDIR=/mnt > make reinstall of graphics/drm-current-kmod (add key destdir) > beadm umount xxx > beadm activate xxx > reboot Interesting method, thank you -- Marco van Lienen -- Unix SysAdmin https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgpSpJy2cim9U.pgp Description: PGP signature
Re: Office Hours today @ 18:00 UTC - Core Candidates
On Wed, May 27, 2020 at 10:35:14AM -0400, you (Allan Jude) sent the following to [freebsd-current] : > Sorry for the late notice, I thought I sent this last week. > > After the slate of candidates was finalized last week, I invited all of > them to join a live stream today at 18:00 UTC to answer questions from > the FreeBSD Community. > > You can watch the live stream and chat here: > > https://live.freebsd.org/FreeBSD/officehours/ > > Or join the chat directly via irc: > > irc.geekshed.net #freebsd > > The live stream supports 'DVR', so can be rewound and watched after the > live session is over. Couildn't watch it live but did watch it today on youtube. Good conversation touching some solid topics. Great to see gnn make another run for the core tream. -- Marco van Lienen -- Unix SysAdmin https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgpgeFOb7uDFL.pgp Description: PGP signature
Re: ZFS BE not booting
On Thu, May 28, 2020 at 07:56:10AM +, you (marco) sent the following to [freebsd-current] : > make[1]: stopped in /usr/src > *** [installworld] Error code 2 > > make: stopped in /usr/src > > make: stopped in /usr/src > > Not sure how I ended up in that situation exactly. > Think I'm going to destroy that r360723 BE for now and create a new one > for a later revision and do the build world, kernel and install kernel > dance and will make notes of all the steps I've taken should the update > fail at some point. > I decided creating a new BE for r361307 and am now running that revision using the following steps: - destroyed the BE - created a new one for r361307 and activated it - rebooted - updated /usr/src to r361307 - make buildworld - make buildkernel - make installkernel - portsnap fetch update - make reinstall of graphics/drm-current-kmod - mergemaster -Fp - reboot - make installworld - mergemaster -Fi - make delete-old - final reboot [~] bectl list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created r359556 zroot/ROOT/r359556 - - 440K 2020-04-03 20:05 zroot/ROOT/r361307@2020-05-28-07:40:34-0 - - 6.35G 2020-05-28 07:40 r361307 zroot/ROOT/r361307 NR / 19.7G 2020-05-28 07:40 r361307@2020-05-28-07:40:34-0 - - 6.35G 2020-05-28 07:40 -- Marco van Lienen -- Unix SysAdmin https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgpBR473taCoy.pgp Description: PGP signature
Re: ZFS BE not booting
On Mon, May 25, 2020 at 03:52:49PM -0500, you (Clay Daniels) sent the following to [freebsd-current] : > > > [... snip ...] > > > Is there something I'm perhaps missing regarding loader.conf > and/or rc.conf ? > >I may be wrong, but it looks like a "framebuffer problem" that is most >often associated with amdgpu, but may help your i915 intel graphics >too. >Just try adding this to /boot/loader.conf : >hw.syscons.disable=1 >� Sorry for late reply. I haven't tried this but followed Allan's instruction to update drm-kmod port which was necessary. Unfortunately then installworld failed (details in reply to Allan's mail). M -- Marco van Lienen -- Unix SysAdmin https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgp4KftKnDyOP.pgp Description: PGP signature
Re: ZFS BE not booting
On Tue, May 26, 2020 at 06:32:28PM -0400, you (Allan Jude) sent the following to [freebsd-current] : > > Hmm, with the r359556 BE currently active, to my surprise 'svn info' on > > /usr/src is showing it's at r360723 instead of r359556. > > IIRC after creating the r360723 BE I mounted it, cd'd into > > /tmp/be_mount.x/usr/src and ran a 'svn up -r 360723'. > > I might be mistaken in that step, can't remember. > > Perhaps I activated r360723, rebooted into it and did a 'svn up -r > > 360723' from /usr/src. > > > > If /usr is not a part of a BE how does one keep different versions of > > /usr/src if I mean to do src upgrades using BEs ? > > > > Looks like the problem is the graphics driver. When you rebuild your > kernel you also need to update the drm-kmod port to match your kernel > version. > > -- > Allan Jude > Thanks Allan that solved that step. I had to make reinstall (did a make install first but it failed to register and make advised me to make deinstall / reinstall. I indeed did update graphics/drm-current-kmod when updating to r359556 with only the default BE but forgot about having done that. System not booted into r360723 BE with freshly installed kernel, hower installworld failed with: rm -f /usr/share/openssl/man/man7/Ed448.7 /usr/share/openssl/man/man7/Ed448.7.gz; install -l h -o root -g wheel -m 444 /usr/share/openssl/man/man7/Ed25519.7.gz /usr/share/openssl/man/man7/Ed448.7.gz rm -f /usr/share/openssl/man/man7/X448.7 /usr/share/openssl/man/man7/X448.7.gz; install -l h -o root -g wheel -m 444 /usr/share/openssl/man/man7/X25519.7.gz /usr/share/openssl/man/man7/X448.7.gz A failure has been detected in another branch of the parallel make make[6]: stopped in /usr/src/secure/lib/libcrypto *** [realinstall_subdir_secure/lib/libcrypto] Error code 2 make[5]: stopped in /usr/src/secure/lib 1 error make[5]: stopped in /usr/src/secure/lib *** [realinstall_subdir_secure/lib] Error code 2 make[4]: stopped in /usr/src/secure 1 error make[4]: stopped in /usr/src/secure *** [realinstall_subdir_secure] Error code 2 make[3]: stopped in /usr/src 4 errors make[3]: stopped in /usr/src *** [reinstall] Error code 2 make[2]: stopped in /usr/src 1 error make[2]: stopped in /usr/src *** [installworld] Error code 2 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [installworld] Error code 2 make: stopped in /usr/src make: stopped in /usr/src Not sure how I ended up in that situation exactly. Think I'm going to destroy that r360723 BE for now and create a new one for a later revision and do the build world, kernel and install kernel dance and will make notes of all the steps I've taken should the update fail at some point. M -- Marco van Lienen -- Unix SysAdmin https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgp5zOIr1FTyb.pgp Description: PGP signature
Re: ZFS BE not booting
On Mon, May 25, 2020 at 08:13:16PM +, you (marco) sent the following to [freebsd-current] : > > I took 3 pictures of the system dropping to the debugger for r360723. > 1st 2 pictures are right before the panic and the final the panic screen > itself. > It seems the panic occurs right before the system normally switches to > the framebuffer device. > > https://pasteboard.co/Ja3koTn.jpg 1st screen > https://pasteboard.co/Ja3mlVy.jpg 2nd screen > https://pasteboard.co/Ja3n8kv.jpg final screen > > thanks so far > > Marco > Hmm, with the r359556 BE currently active, to my surprise 'svn info' on /usr/src is showing it's at r360723 instead of r359556. IIRC after creating the r360723 BE I mounted it, cd'd into /tmp/be_mount.x/usr/src and ran a 'svn up -r 360723'. I might be mistaken in that step, can't remember. Perhaps I activated r360723, rebooted into it and did a 'svn up -r 360723' from /usr/src. If /usr is not a part of a BE how does one keep different versions of /usr/src if I mean to do src upgrades using BEs ? -- Marco van Lienen -- Unix SysAdmin https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgpacyaMKfiqn.pgp Description: PGP signature
Re: ZFS BE not booting
On Mon, May 25, 2020 at 10:28:39AM -0500, you (Kyle Evans) sent the following to [freebsd-current] : > On Mon, May 25, 2020 at 3:51 AM marco > wrote: > > > > [... snip ...] > > Is there something I'm perhaps missing regarding loader.conf and/or rc.conf > > ? > > It could just be these 2 specific revisions and will try another revision > > but perhaps I need to do something setting the zfs bootcode again using > > gpart ? > > Your procedure looks fine to me; beyond that, it's hard to know the > exact cause without seeing the nature of the panic. BEs don't > typically require frobbing any configuration files for standard > updates like this, at least. Any chance you can grab a picture of it > or at least transcribe the initial part of the panic message? > > Thanks, > > Kyle Evans I took 3 pictures of the system dropping to the debugger for r360723. 1st 2 pictures are right before the panic and the final the panic screen itself. It seems the panic occurs right before the system normally switches to the framebuffer device. https://pasteboard.co/Ja3koTn.jpg 1st screen https://pasteboard.co/Ja3mlVy.jpg 2nd screen https://pasteboard.co/Ja3n8kv.jpg final screen thanks so far Marco -- Marco van Lienen -- Unix SysAdmin https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgpyYs1kCAH4m.pgp Description: PGP signature
ZFS BE not booting
returning FreeBSD user here, using bectl for the 1st time on a thinkpad x230 with 16GB of RAM. bectl list -aDs BE/Dataset/Snapshot Active Mountpoint Space Created r359556 zroot/ROOT/r359556 NR / 12.2G 2020-04-03 20:05 r359556@2020-05-22-22:20:00-0 - - 61.1M 2020-05-22 22:20 r360723 zroot/ROOT/r360723 - - 6.25G 2020-05-22 22:20 zroot/ROOT/r359556@2020-05-22-22:20:00-0 - - 61.1M 2020-05-22 22:20 I created r360723 using bectl whilst being on r359556 and am still using base ZFS. I'm running GENERIC-NODEBUG on this thinkpad x230. [~] uname -v FreeBSD 13.0-CURRENT #2 r359556: Mon Apr 13 13:35:31 UTC 2020 root@harbinger:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG I activate and boot into the newly created BE, run svn up -r 360723 from /usr/src and doing the upgrade steps (same steps were used in previous upgrades leading to r359556 without the use of BEs). make -DMALLOC_PRODUCTION -j4 buildworld make -DMALLOC_PRODUCTION -j4 buildkernel KERNCONF=GENERIC-NODEBUG make -DMALLOC_PRODUCTION -j4 installkernel KERNCONF=GENERIC-NODEBUG Then I reboot but the boot process drops me into the debugger (unfort. I don't have the capture of the reason). I've tried upgrading to both r360723 and r361307 (I pick those revisions from the released snapshots, no other reason) but both produce the same result. Loading kernel.old from the r360723 BE works fine. Is there something I'm perhaps missing regarding loader.conf and/or rc.conf ? It could just be these 2 specific revisions and will try another revision but perhaps I need to do something setting the zfs bootcode again using gpart ? cheers -- Marco van Lienen -- Unix SysAdmin -- https://lordsith.net/ https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgpRvUYfREP72.pgp Description: PGP signature
Re: Trying to compiles today Current
On Sun, 29 Mar 2020 15:36:22 +0200
Willem Jan Withagen wrote:
> I keep getting errors in building my ports from portsbuilder.
> But it is with Current/Clang10.
>
> So I'm trying to get a server at that level, but building world
> keeps giving me:
> --- all_subdir_cddl ---
> ld:
> error: /usr/obj/usr/srcs/head/amd64.amd64/tmp/usr/lib/libuutil.so:
> undefined reference to __assfail cc: error: linker command failed
> with exit code 1 (use -v to see invocation) *** [zfs.full] Error code
> 1
>
>
> Completely cleared src and obj, but the error persists.
>
> Current on this system is:
> FreeBSD 13.0-CURRENT #0 r358358: Thu Feb 27 04:40:39 UTC 2020
> r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
>
> How to fix this?
In my case a leftover CFLAGS=-O0 in /etc/make.conf was the culprit
('=' instead of '+=' not being a typo). As another side effect, build
world took about four times as long as usual, before it errored out.
While at it, I of also ran into what's described
in
https://lists.freebsd.org/pipermail/freebsd-current/2018-December/072531.html,
before removing DEBUG_FLAGS from /etc/make.conf.
Conditionalizing the flags to only be pulled in for the directories I
actually wanted them to be relevant for would certainly have helped.
MfG CoCo
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Pkg repository is broken...
On Sun, Mar 01, 2020 at 04:50:59PM -0500, you (Brennan Vincent) sent the following to [freebsd-current] : > Apparently something has its ABI erroneously listed as FreeBSD:13.0:amd64 > instead of FreeBSD:13:amd64. > > ``` > $ sudo pkg update -f > Updating FreeBSD repository catalogue... > Fetching meta.conf: 100%163 B 0.2kB/s00:01 > Fetching packagesite.txz: 100%6 MiB 6.4MB/s00:01 > Processing entries: 72% > pkg: wrong architecture: FreeBSD:13.0:amd64 instead of FreeBSD:13:amd64 > pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:13.0:amd64 > Processing entries: 100% > Unable to update repository FreeBSD > Error updating repositories! > ``` Ran into this very same problem today too. Just learned on #freebsd that the repos are temporarily borked and people are working hard to fix it. I even tried bootstrapping pkg like: env ABI=FreeBSD:13:amd64 pkg bootstrap -f (pkg 1.13.2 already installed) to no avail. Hoping things get sorted soon. -- Marco van Lienen -- Unix SysAdmin -- https://lordsith.net/ https://keybase.io/scarcry , GnuPG id: 8580E6CB "The Tuck Pendleton machine...zero defects." pgpSXjInQ3g5x.pgp Description: PGP signature
Re: UFS journal error on 10.0-CURRENT
On Thu, 30 Aug 2012, Jakub Lach wrote: If I were you, I would try regular fsck, as here (9-STABLE) using journal has left me with fs inconsistencies. Could you elaborate on the inconsistencies you encountered ? MfG CoCo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gstat don't work after update to 10.0-CURRENT
On Sat, Apr 21, 2012 at 09:33:58AM -0400, you (Ryan Stone) sent the following to [freebsd-current] : I believe that this was fixed in r234107 I updated to r234515 today on amd64 and I can confirm gstat(8) works again. -- marco Proud recurring donor of the FreeBSD Foundation You can have any color you want, as long as it is black! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
netstat: no namelist on amd64 (r234515)
On both r233779 and r234515 on my 10-CURRENT amd64 home box netstat returns: no namelist This is a Q9550 system and I rebuilt both world and kernel using clang with -j8 The last revision netstat was functioning for me was r230839. I went from r230839 to r233779 so no other updates went in between those 2 revisions. -- marco Proud recurring donor of the FreeBSD Foundation You can have any color you want, as long as it is black! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gstat don't work after update to 10.0-CURRENT
On Tue, Apr 10, 2012 at 11:52:57AM +, you (Anton Yuzhaninov) sent the following to [freebsd-current] : On Tue, 10 Apr 2012 15:19:37, Anton Yuzhaninov wrote: AY gstat don't work after update to 10.0-CURRENT r233947 AY It don't show any providers, and don't print any errors: AY # gstat -b AY dT: 1.166s w: 1.000s AY L(q) ops/sr/s kBps ms/rw/s kBps ms/w %busy Name AY # After reverting r233646 gstat show: dT: 1.001s w: 1.000s L(q) ops/sr/s kBps ms/rw/s kBps ms/w %busy Name 0 0 0 00.0 0 00.00.0 ada0 0 0 0 00.0 0 00.00.0 ada0s1 0 0 0 00.0 0 00.00.0 ada1 1392392 19032.3 0 00.0 91.6 ada2 0 0 0 00.0 0 00.00.0 ada1s1 1392392 19032.4 0 00.0 92.5 ufs/backup 0 0 0 00.0 0 00.00.0 mirror/gm0 0 0 0 00.0 0 00.00.0 mirror/gm0a 0 0 0 00.0 0 00.00.0 mirror/gm0b 0 0 0 00.0 0 00.00.0 mirror/gm0d so problem somewhere in http://svn.freebsd.org/changeset/base/233646 I'm also seeing the same behaviour. I updated my 10-CURRENT from r230839 (gstat worked here still) to r233779 where it's broken. -- marco Proud recurring donor of the FreeBSD Foundation You can have any color you want, as long as it is black! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Updating /usr/src/sys to CURRENT
On Thu, Mar 01, 2012 at 01:25:15PM -0600, you (Ismael Farf??n) sent the following to [freebsd-current] : Also, I just found this, I don't know if there is a better way of updating src/sys http://www.rhyous.com/2009/12/25/how-to-download-freebsd-current-or-freebsd-stable-using-svn/ I would definitely suggest using svn(1). Being able to report the actual checked out revision when posting ones problem(s) to this list is more acurate then stating my machine is built from source csup about 2 hours ago. -- Sincerely, marco Proud recurring donor of the FreeBSD Foundation You can have any color you want, as long as it is black! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[cft] Small patch for calendar(1)
Hi,
for a while now, calendar(1) seems to have forgotten how to handle what
the man page describes as: 'A month without a day matches the first of
that month.'
A notable result of this is, that the output of 'calendar -f
/usr/share/calendar/calendar.all' is always headed by 'Unprocessed'
error messages.
The attached patch tries to help calendar(1) remember how to do this as
is described in the man page.
Since I'm not an avid calendar(1) user, I'd very much like others to
review and try out the patch, before I go pester commiters by opening a PR.
MfG CoCo
--- src/usr.bin/calendar/parsedata.c.orig 2011-12-31 11:36:40.0
+0100
+++ src/usr.bin/calendar/parsedata.c2011-12-31 11:57:55.0 +0100
@@ -174,11 +174,22 @@
}
if (isonlydigits(date, 1)) {
/* Assume month number only */
- *flags |= F_MONTH;
+ *flags |= (F_MONTH | F_DAYOFMONTH);
+ *idayofmonth = 1;
*imonth = (int)strtol(date, (char **)NULL, 10);
strcpy(month, getmonthname(*imonth));
return(1);
}
+ if ((checkmonth(date, len, offset, pmonth) != 0)) {
+ /* Assume month name only */
+ *flags |= (F_MONTH | F_DAYOFMONTH);
+ *idayofmonth = 1;
+ *imonth = offset;
+ strcpy(month, getmonthname(*imonth));
+ return(1);
+ }
+
+
return (0);
}
}
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: make installworld fails on releng9
On Thu, 27 Oct 2011, Chuck Burns wrote: I had some issues while running make installworld after I sync'd to the latest releng9, on my RC1 install. Now, it appears to failed, while trying to create some links, chfn chsh ypchpass ypchfn ypchsh. These are supposed to be hardlinked to /usr/bin/chpass, except that, since the other files already exist, and are immutable, make installworld was unable to do anything, so I wound up removing the immutable flag on these files and re- running make installworld. I didn't see any mention of this little.. issue, in UPDATING, or in the - current mailing list (yes, I know, 9.0 is no longer technically, current, but since it isn't released yet, I figure it's close enough) I'm seeing this on head (226827, amd64), also. MfG CoCo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
AMD X2/Opteron Rev E workaround ?
Hi, it's been a while since this topic was touched, see http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013129.html. I coulnd't find anything more recent than the following commit, which prints a warning message, if a suspectible CPU model is detected: http://svn.freebsd.org/viewvc/base?view=revisionrevision=198868 If someone has any patches, even very preliminary ones, I'd be more than happy to give them a thorough try on otherwise unused machines. MfG CoCo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [HEADSUP] ZFS version 15 committed to head
On Tue, Jul 13, 2010 at 04:02:42PM +0200, you (Martin Matuska) sent the following to the -current list: Dear community, Feel free to test everything and don't forget to report any bugs found. When I create a raidz pool of 3 equally sized hdd's (3x2Tb WD caviar green drives) the reported available space by zpool and zfs is VERY different (not just the known differences). On a 9.0-CURRENT amd64 box: # uname -a FreeBSD trinity.lordsith.net 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Tue Jul 13 21:58:14 UTC 2010 r...@trinity.lordsith.net:/usr/obj/usr/src/sys/trinity amd64 # zpool create pool1 raidz ada2 ada3 ada4 # zpool list pool1 NAMESIZE USED AVAILCAP HEALTH ALTROOT pool1 5.44T 147K 5.44T 0% ONLINE - # ada drives dmesg output: ada2 at ahcich4 bus 0 scbus5 target 0 lun 0 ada2: WDC WD20EARS-00MVWB0 50.0AB50 ATA-8 SATA 2.x device ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada3 at ahcich5 bus 0 scbus6 target 0 lun 0 ada3: WDC WD20EARS-00MVWB0 50.0AB50 ATA-8 SATA 2.x device ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada3: Command Queueing enabled ada3: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada4 at ahcich6 bus 0 scbus7 target 0 lun 0 ada4: WDC WD20EADS-11R6B1 80.00A80 ATA-8 SATA 2.x device ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada4: Command Queueing enabled ada4: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) zfs list however only shows: # zfs list pool1 NAMEUSED AVAIL REFER MOUNTPOINT pool1 91.9K 3.56T 28.0K /pool1 I just lost the space of an entire hdd! To rule out a possible drive issue I created a raidz pool based on 3 65m files. # dd if=/dev/zero of=/file1 bs=1m count=65 # dd if=/dev/zero of=/file2 bs=1m count=65 # dd if=/dev/zero of=/file3 bs=1m count=65 # zpool create test raidz /file1 /file2 /file3 # # zpool list test NAME SIZE USED AVAILCAP HEALTH ALTROOT test 181M 147K 181M 0% ONLINE - # zfs list test NAME USED AVAIL REFER MOUNTPOINT test 91.9K 88.5M 28.0K /test When I create a non-redundant storage pool using the same 3 files or 3 drives the available space reported by zfs is what I'm expecting to see though so it looks like creating a raidz storage pool is showing very weird behavior. This doesn't have as much to do with the ZFS v15 bits commited to -HEAD since I have the exact same behavior on a 8.0-RELEASE-p2 i386 box with ZFS v14. A friend of mine is running osol build 117 but he created his raidz pool on an even older build though. His raidz pool also uses 3 equally-sized drives (3x2Tb) and his raidz pool is showing: % zfs list -r pool2 NAMEUSED AVAIL REFER MOUNTPOINT pool2 3.32T 2.06T 3.18T /export/pool2 % df -h pool2 Filesystem size used avail capacity Mounted on pool2 5.4T 3.2T 2.1T61%/export/pool2 To run further tests he also created a test raidz pool using 3 65m files: % zfs list test2 NAMEUSED AVAIL REFER MOUNTPOINT test2 73.5K 149M21K /test2 So on osol build 117 the available space is what I'm expecting to see whereas on FreeBSD 9.0-CURRENT amd64 and 8.0-RELEASE-p2 i386 Is someone having the same issues? Cheers, marco pgpQwcquU4UgC.pgp Description: PGP signature
Re: [HEADSUP] ZFS version 15 committed to head
On Sat, Jul 17, 2010 at 12:25:56PM +0200, you (Stefan Bethke) sent the following to the -current list: Am 17.07.2010 um 12:14 schrieb Marco van Lienen: # zpool list pool1 NAMESIZE USED AVAILCAP HEALTH ALTROOT pool1 5.44T 147K 5.44T 0% ONLINE - ... zfs list however only shows: # zfs list pool1 NAMEUSED AVAIL REFER MOUNTPOINT pool1 91.9K 3.56T 28.0K /pool1 I just lost the space of an entire hdd! zpool always shows the raw capacity (without redundancy), zfs the actual available capacity. I have read many things about those differences, but why then does zfs on opensolaris report more available space whereas FreeBSD does not? That would imply that my friend running osol build 117 couldn't fill up his raidz pool past the 3.56T. marco pgpQK6Bhz2NSv.pgp Description: PGP signature
Re: RAIDZ capacity (was ZFS version 15 committed to head)
On Sat, Jul 17, 2010 at 01:04:52PM +0200, you (Stefan Bethke) sent the following to the -current list: I have read many things about those differences, but why then does zfs on opensolaris report more available space whereas FreeBSD does not? That would imply that my friend running osol build 117 couldn't fill up his raidz pool past the 3.56T. You didn't show us how your friends pool is set up. With RAIDZ1, the capacity of one of the devices in the pool is used for redundancy, with RAIDZ2 it's two disks worth. So three 2TB disks with RAIDZ1 gives you 4TB net capacity. If you don't care about redundancy, use a simple concatenation, i. e. don't specify mirror, raidz or raidz2 when creating the pool. My friend created his raidz pool just the same way as I did: zpool create pool2 raidz c0d0 c0d1 c0d2 So just 3 dedicated drives. I also posted the example of creating a test raidz pool based on 3 65Mb files. On osol there is more available space being reported by 'zfs list' on that test raidz pool When I created a similar test raidz pool also based on 3 65Mb files, 'zfs list' on my FreeBSD boxes (9.0-CURRENT amd64 and 8.0-RELEASE-p2 i386) is showing much less available space. So regardless whether we use whole disks or simply files for testing purposes, 'zfs list' on the osol system is reporting more available space. cheers, marco pgpvoeRVwVWU8.pgp Description: PGP signature
Re: [HEADSUP] ZFS version 15 committed to head
On Sat, Jul 17, 2010 at 10:12:10AM -0700, you (Freddie Cash) sent the following to the -current list: I have read many things about those differences, but why then does zfs on opensolaris report more available space whereas FreeBSD does not? That would imply that my friend running osol build 117 couldn't fill up his raidz pool past the 3.56T. You used different commands to check the disk space on OSol (zpool vs df). Try the same commands on both FreeBSD and OSol (zpool and zfs) and you'll see the same results. I guess you missed my original mail of this thread in which I also showed the output of 'zfs list -r pool2' on osol where clearly there is more available space shown then on FreeBSD. % zfs list -r pool2 NAMEUSED AVAIL REFER MOUNTPOINT pool2 3.32T 2.06T 3.18T /export/pool2 df works differently on OSol than it does on FreeBSD, you can't compare them. HTH ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Me too]: rc scripts run double on boot?
| Of course, make sure you don't have local changes in /etc/rc.d first. Shouldn't these be placed in /usr/local/etc/rc.d -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting Internet Solutions ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IBM Blade
On Tuesday 18 November 2003 17:56, Blaz Zupan wrote: FreeBSD 5.x (or 4.x) on an IBM HS20 Blade? I would surely be interested in pointers if possible. I tried but failed miserably. There were two problems: 1. It is impossible to boot from CD. Neither 4.8 nor 5.1 boot from CD. Booting from floppy works but is of course cumbersome. I've made the installation using the pxe network installation http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/index.html and it worked without problem. 2. After boot, keyboard did not work. The problem is that although the keyboard is actually a USB keyboard, the AT port is still connected so FreeBSD detects the normal keyboard as well, so the nonexisting AT keyboard becomes /dev/kbd0 while the real (USB) keyboard becomes /dev/kbd1. This was a bug in both 4.8 and 5.1 and it is supposedly fixed in 4.9. I'll have the possibility to test 4.9 on the blade soon now and I'll be able to test it. I've solved DISABLING every kind of usb from the kernel. but making so I lost the floppy and the cdrom. :-( I've not tried with 4.9 but only with 4.8 R Both the fiberchannel and ethernet seem to be detected during bootup, but I don't know if they actually work... the ethernet worked fine. Ciao Marco ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
CF cards / ATAng / interrupt code still broken
Hello, as reproducable seen on my IBM Thinkpad, current as of some days ago has problems to boot with my 128MB noname CF card inserted. The panic output is very similar the problem Alex Dupre reported in mid of september, but Sorens patch which should be tried to get this stuff fixed but the patch does not help. These messages get logged while booting verbose: (... beginning removed because it's probably not interesting) pccard0: CIS version PCCARD 2.0 or 2.1 pccard0: CIS info: CF, 128MB, pccard0: Manufacturer code 0xa, product 0x0 pccard0: function 0: fixed disk, ccr addr 200 mask f pccard0: function 0, config table entry 0: memory card; irq mask 0; memspace 0-7ff; mwait_required rdybsy_active powerdown pccard0: function 0, config table entry 1: I/O card; irq mask ; iomask 4, iospace 0-f; memspace 0-7ff; rdybsy_active io8 io16 irqshare irqpulse irqlevel powerdown pccard0: function 0, config table entry 2: I/O card; irq mask 4000; iomask a, iospace 1f0-1f7 3f6-3f7; memspace 0-7ff; rdybsy_active io8 io16 irqshare irqpulse irqlevel powerdown pccard0: function 0, config table entry 3: I/O card; irq mask 4000; iomask a, iospace 170-177 376-377; memspace 0-7ff; rdybsy_active io8 io16 irqshare irqpulse irqlevel powerdown pccard0: Allocation failed for cfe 0 ata2: CF 128MB at port 0x100-0x10f irq 11 function 0 config 1 on pccard0 ata2: reset tp1 mask=01 ostat0=50 ostat1=b7 ata2-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 mask=01 stat0=50 stat1=00 devices=0x1ATA_MASTER ata2: [MPSAFE] ata2: spurious interrupt - status=0x50 error=0x01 ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ata0-master: setting PIO4 on Intel PIIX4 chip ata0-master: setting UDMA33 on Intel PIIX4 chip GEOM: create disk ad0 dp=0xc2972b60 ad0: TOSHIBA MK6021GAS/GA023A ATA-5 disk at ata0-master ad0: 57231MB (117210240 sectors), 116280 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA33 GEOM: new disk ad0 ata2-master: pio=0x08 wdma=0x udma=0x cable=40pin ad4: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED ad4: FAILURE - SETFEATURES status=51READY,DSC,ERROR error=4ABORTED GEOM: create disk ad4 dp=0xc297a260 ad4: ^A/.65 ATA-0 disk at ata2-master Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc06650cb stack pointer = 0x10:0xc0821c2c frame pointer = 0x10:0xc0821cac code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) kernel: type 18 trap, code=0 Stopped at __qdivrem+0x3b: divl%ecx,%eax db trace __qdivrem(0,0,0,0,0) at __qdivrem+0x3b __udivdi3(0,0,0,0,0) at __udivdi3+0x2e ad_print(c297a200,c297a260,1,0,0,0,f,c2a0a400,0,0) at ad_print+0xbd ad_attach(c2a0a4a4,2,c1292040,c06d1650,c0821d80) at ad_attach+0x40b ata_boot_attach(0,826000,c0821d80,c0504e2a,0) at ata_boot_attach+0x47 run_interrupt_driven_config_hooks(0,81e000,81ec00,81e000,0) at run_interrupt_driven_config_hooks+0x2b mi_startup() at mi_startup+0xb5 begin() at begin+0x2c db If I insert the card after the system is up and running the panic does not appear, probably because ATAng does not get the information about a newly inserted drive? At least atacontrol list does not display any drives: desire:~sudo atacontrol list ATA channel 0: Master: ad0 TOSHIBA MK6021GAS/GA023A ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: no device present Slave: no device present If there are further patches available I would like to test them in order to use my CF card again ;) -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting Internet Solutions ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS-UP new statfs structure
Just for a short note: cfsd (ports/security/cfs) should be recompiled as well after those statfs changes. -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting Internet Solutions ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: features of ICH5/ICH5-R supported in -current or 5.1-RELEASE?
Seems as if someone is going to buy an ASUS P4P800 ;) I don't know if the 3Com nic is supported, but actually it seems to be based on SysKonnect SK-98xx which is already supported. 3Com (and Asus) provide Linux drivers for this card, therefore it could be ported if it's not already running. Probably I could test it during the next weeks... -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting Internet Solutions ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hyperthreading
In order to give some values to compare: I was recently running an P4 3.06 GHz with Hyperthreading (actually it was Linux, but I will repeat the tests with current when I have time for such games :) Running ubench 0.32 on this HTT enabled machine (i865PE) showed some interesting details when accessing memory: ubench (without parameter): cpu: 111742, memory: 178587, average: 145164 ubench -s (single cpu): cpu: 101993, memory: 135693, average: 118843 With Hyperthreading disabled: ubench (without parameter): cpu: 100878, memory: 133539, average: 117208 ubench -s (single cpu): cpu: 102041, memory: 135296, average: 118668 As you can see, the system has an amazingly improved memory performance when hyperthreading enabled (about 25%) but the overall calculating speed increases only about 9%. Probably you can run ubench on your HTT system earlier than me and post the results here. -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting Internet Solutions ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
bug in ftp client?
I don't know since when this happens, but I've noticed, that the ETA time looks strange: While fetching this file: lrwxr-xr-x 1 ftp ftp 36 Jun 27 15:43 live-current.iso - live-5.1-CURRENT-20030627-JPSNAP.iso -rw-r--r-- 1 ftp ftp 238714880 Jun 27 15:42 live-5.1-CURRENT-20030627-JPSNAP.iso ftp get live-current.iso local: live-current.iso remote: live-current.iso 227 Entering Passive Mode (211,14,6,234,230,179) 150 Opening BINARY mode data connection for 'live-current.iso' (238714880 bytes). 7% |** | 17666 KB 64.94 KB/s 55:00:17 ETA So getting a file of about 227MB with 64.94 KB/s takes 55 hours? And when the time goes by and one minute finishes, it's not getting 54:59:59 but instead the ETA shows 54:00:59. -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting Internet Solutions ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HDD Problem
On Wed, 27 Dec 2000, Soren Schmidt wrote: It seems David W. Chapman Jr. wrote: You guys are not overclocking are you ?? I've recently seen the same problem on 4.2-stable, probably a early version of it, I go to make my kernel and it locks up for a few mins, then I get some ata error and then it says resetting devices and it all runs ok, it resets the ata devices during boot also. - Original Message - From: "Ben Jackson" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, December 27, 2000 2:28 PM Subject: Re: HDD Problem I've heard tell that there are problems with the VIA chipset and UDMA on FreeBSD. Is this true, and if so, what is the problem with? FreeBSD 4.2-STABLE #0: Fri Dec 8 01:52:44 EST 2000 atapci0: VIA 82C686 ATA66 controller port 0xe000-0xe00f at device 7.1 on pci0 ad0: 19546MB FUJITSU MPF3204AT [39714/16/63] at ata0-master UDMA66 Sounds similar to the problem I've had with the HPT controller on my Abit BP6. If you look at the -stable archives from the last few days you'll see some suggestions. I should really move this drive to one of the ATA33 controllers since the drive itself only (??) does about 30M/s sustained anyway. atapci1: HighPoint HPT366 ATA66 controller port 0xd800-0xd8ff,0xd400-0xd403,0xd000-0xd007 irq 18 at device 19.0 on pci0 ata2: at 0xd000 on atapci1 ad4: 29311MB Maxtor 53073U6 [59554/16/63] at ata2-master UDMA66 The drive has enough space and I have 512MB RAM. If I hit the system hard, lets say, rm -rf /usr/ports, the system locks up. I have to hit mine harder. The more I upgrade FreeBSD, the more times it successfully resets the devices after a read timeout, but eventually it hangs while resetting. With 4.2 (or maybe it's softupdates) it manages to save some of the errors in /var/log/messages. No page faults. Haven't had a persistant kernel "page not present" problem since FreeBSD 1.1.5. Also, my UDMA66 problem is happening on a machine with ECC mem. Another datapoint: my desktop machine (until yesterday running 3.4) has an IBM disk in it which likes to spin down on its own, causing timeouts on the first access afterwards. It's irritating (though not enough that I've investigated jumpering it for always-on) but it has never hung the system. --Ben To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth 2583e54c unsubscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
3.0-CURRENT - RELENG_3: trouble ?
Hello all, I'm running 3.0-CURRENT at the moment, last timme I built world is about 2 or 3 weeks ago I guess. What I want to do is go to 3.0-RELEASE and from then start keeping track of the 3.x-STABLE branch. Since I've read a lot about various problems people had with this I now wonder: is it safe to CVSUP to RELENG_3 right now or will bad things happen? I don't want to mess up my system. If someone could give me some guidelines on how to get going on the above described track or point me to a webpage/document or anything else that describes what to do I'd be eternally grateful. At the moment it's very unclear to me what to do and whether I'll be able to boot and/or login to my system after I went to RELENG_3. I'm running 3.0-CURRENT with everything ELF including the kernel. Any assistance is highly appreciated, Regards, Marco -- QQWT!^9QQQ QP' _%7? WindowMaker, the choice of a GNUstep Generation. PWQQ, http://www.windowmaker.org/ 'mWQh Marco's WindowMaker icons: .__s_QWQQ http://marco.shada.com/wmaker/ . ]QQQ@ L )WQQ( Marco van Hylckama Vlieg !`_ajQ@( ma...@windowmaker.org ?TUVY` To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
FreeBSD include paths
Hello all, I got a nagging question... Very often when trying to compile packages I find myself editing makefiles and having to add really obvious include paths like /usr/local/include or /usr/X11R6/include in order to get the package installed. Now I wonder, why doesn't the system itself have these include paths enabled by default? Is there a way to fix these ever occuring annoyances when compiling programs? Thanks in advance, Marco -- QQWT!^9QQQ QP' _%7? WindowMaker, the choice of a GNUstep Generation. PWQQ, http://www.windowmaker.org/ 'mWQh Marco's WindowMaker icons: .__s_QWQQ http://marco.shada.com/wmaker/ . ]QQQ@ L )WQQ( Marco van Hylckama Vlieg !`_ajQ@( ma...@windowmaker.org ?TUVY` To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
