Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable
On Tue, 6 Mar 2018 16:53:46 +0100 Torfinn Ingolfsen wrote: > On Fri, 2 Mar 2018 11:33:57 -0800 > Pete Wright wrote: > > > > > Hey there - thanks for testing! I would recommend posting an issue on > > the Github repo for this. If you could be sure to include which > > revision you are running (11-stable or 12-current revision) in addition > > to the version of the port/pkg you have install that'd be helpful. > > Done. > Issue 38: https://github.com/FreeBSDDesktop/kms-drm/issues/38 > Update: I just upgraded to latest versions of the modules from the ports tree: May 17 13:25:17 kg-z30b pkg-static: gpu-firmware-kmod-g20180319_1 installed May 17 13:28:42 kg-z30b pkg-static: drm-next-kmod-4.11.g20180505_1 installed and the lag in the console is now gone. Thanks! Oh, and I added a comment on Issue 38 in Github. -- Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable
On Fri, 2 Mar 2018 11:33:57 -0800 Pete Wright <p...@nomadlogic.org> wrote: > > Hey there - thanks for testing! I would recommend posting an issue on > the Github repo for this. If you could be sure to include which > revision you are running (11-stable or 12-current revision) in addition > to the version of the port/pkg you have install that'd be helpful. Done. Issue 38: https://github.com/FreeBSDDesktop/kms-drm/issues/38 HTH -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [CFT] [X11] graphics/drm-next-kmod now builds, loads and works on FreeBSD-11-stable
On Sun, 18 Feb 2018 21:35:24 +0100 Hans Petter Selasky <h...@selasky.org> wrote: > Hi FreeBSD desktop users! > > During the past week and over the weekend all parts needed for building, > loading and using graphics/drm-next-kmod on FreeBSD-11-stable have been > completed! > Thanks for the hard work by all involved! Tested a few days ago, reported in the forum post here: https://forums.freebsd.org/threads/using-drm-next-kmod-on-freebsd-11-stable.64731/#post-378702 TL;DR - it works on a Toshiba Satellite Z30-B-10W (Broadwell-U, Intel HD Graphics 5500). One issue - the text console (before starting Xorg) has serious lag, you can type a command before anything shows on the screen. Should I open an issue for this on Github? HTH -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 11.1-release - verbose boot causes the machine to restart
FWIW, I just upgraded the machine[1] to FreeBSD 11.1-release-p6 via freebsd-update and the "reboot-on-verbose-boot" problem is no longer there. Now both normal and verbose dmesg output can be found on the FreeBSD page[2] for this machine. References: 1) https://sites.google.com/site/tingox/asrock_beebox-s_7100u 2) https://sites.google.com/site/tingox/asrock_beebox-s_7100u_fbsd -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 11.1-release - verbose boot causes the machine to restart
On Wed, 31 Jan 2018 16:41:55 -0600 Adam Vande More <amvandem...@gmail.com> wrote: > On Wed, Jan 31, 2018 at 3:58 PM, Torfinn Ingolfsen < > torfinn.ingolf...@getmail.no> wrote: > > > Ok, this I haven't seen before. > > I just installed FreeBSD 11.1-release on a quite new machine[1]. The > > machine is an ASRock BeeBox-S 7100U, a quite "normal" NUC-form machine with > > a i3-7100U (Kaby Lake) and an internal SSD. > > Installation went great (I only had to manually copy /boot/boot1.efi to > > the correct EFI partition. Yes - there are other operating systems on the > > internal SSD), and the machine boots and works normally. > > > > However, if I select verbose boot from the boot menu, the kernel starts > > spitting out kernel messages and after a while the machine restarts. > > Afterwards (after a normal boot) there is no sign of this unusal activity > > either in dmesg output, /var/log/messages or /var/crash. > > > > Is this something developers want to know more about? If so, pointers on > > howe to debug this further is appreciated. > > Details (including dmesg outpuyt from a normal boot) on the FreeBSD > > page[2] of this machine. > > > > References: > > 1) https://sites.google.com/site/tingox/asrock_beebox-s_7100u > > 2) https://sites.google.com/site/tingox/asrock_beebox-s_7100u_fbsd > > > > > Is it a panic reboot? I don't think so - there are no indications of that. -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 11.1-release - verbose boot causes the machine to restart
Ok, this I haven't seen before. I just installed FreeBSD 11.1-release on a quite new machine[1]. The machine is an ASRock BeeBox-S 7100U, a quite "normal" NUC-form machine with a i3-7100U (Kaby Lake) and an internal SSD. Installation went great (I only had to manually copy /boot/boot1.efi to the correct EFI partition. Yes - there are other operating systems on the internal SSD), and the machine boots and works normally. However, if I select verbose boot from the boot menu, the kernel starts spitting out kernel messages and after a while the machine restarts. Afterwards (after a normal boot) there is no sign of this unusal activity either in dmesg output, /var/log/messages or /var/crash. Is this something developers want to know more about? If so, pointers on howe to debug this further is appreciated. Details (including dmesg outpuyt from a normal boot) on the FreeBSD page[2] of this machine. References: 1) https://sites.google.com/site/tingox/asrock_beebox-s_7100u 2) https://sites.google.com/site/tingox/asrock_beebox-s_7100u_fbsd -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: reset not working like 70% of the time
On Wed, 25 Jan 2017 15:24:55 +0500 "Eugene M. Zheganin" <e...@norma.perm.ru> wrote: > I'm seeing all of these in my konsole terminal window while working with Does it also happen if you use another terminal emulator insted of konsole? -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Building FreeBSD 11.0-stable on FreeBSD 10.1-stable fails
I am trying to build FreeBSD 11.0-stable on a machine which runs: tingo@kg-v7$ uname -a FreeBSD kg-v7.kg4.no 10.1-STABLE FreeBSD 10.1-STABLE #0 r278322: Fri Feb 6 21:36:01 CET 2015 r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 I have emptied /usr/src and /usr/obj and fetched the latest stable/11 via subversion: tingo@kg-v7$ egrep "^BRANCH|^REVISION" /usr/src/sys/conf/newvers.sh REVISION="11.0" BRANCH="STABLE" But building it (per the procedure in the handbook) fails at the buildworld stage. Both 'make -j5 buildworld' and 'make buildworld' fails, like this: c++: error: unable to execute command: Segmentation fault (core dumped) c++: error: clang frontend command failed due to signal (use -v to see invocation) FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 Target: x86_64-unknown-freebsd10.1 Thread model: posix c++: note: diagnostic msg: PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed source, and associated run script. c++: note: diagnostic msg: PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: c++: note: diagnostic msg: /tmp/CGBlocks-abcdc1.cpp c++: note: diagnostic msg: /tmp/CGBlocks-abcdc1.sh c++: note: diagnostic msg: *** Error code 254 Stop. bmake[4]: stopped in /usr/src/lib/clang/libclangcodegen *** Error code 1 Stop. bmake[3]: stopped in /usr/src/lib/clang *** Error code 1 Stop. bmake[2]: stopped in /usr/src *** Error code 1 Stop. bmake[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src So I cleaned out /usr/obj again and tried this (fro /usr/src/UPDATING): root@kg-v7# make WITHOUT_CLANG=y WITH_GCC=y -j5 buildworld [..] *** [CGClass.o] Error code 254 bmake[4]: stopped in /usr/src/lib/clang/libclangcodegen 2 errors bmake[4]: stopped in /usr/src/lib/clang/libclangcodegen *** [all_subdir_lib/clang/libclangcodegen] Error code 2 bmake[3]: stopped in /usr/src/lib/clang --- all_subdir_lib/clang/libclangedit --- A failure has been detected in another branch of the parallel make bmake[4]: stopped in /usr/src/lib/clang/libclangedit *** [all_subdir_lib/clang/libclangedit] Error code 2 bmake[3]: stopped in /usr/src/lib/clang --- all_subdir_lib/clang/libclangast --- A failure has been detected in another branch of the parallel make bmake[4]: stopped in /usr/src/lib/clang/libclangast *** [all_subdir_lib/clang/libclangast] Error code 2 bmake[3]: stopped in /usr/src/lib/clang --- all_subdir_lib/clang/libclangfrontend --- A failure has been detected in another branch of the parallel make bmake[4]: stopped in /usr/src/lib/clang/libclangfrontend *** [all_subdir_lib/clang/libclangfrontend] Error code 2 bmake[3]: stopped in /usr/src/lib/clang 4 errors bmake[3]: stopped in /usr/src/lib/clang *** [cross-tools] Error code 2 bmake[2]: stopped in /usr/src 1 error bmake[2]: stopped in /usr/src *** [_cross-tools] Error code 2 bmake[1]: stopped in /usr/src 1 error bmake[1]: stopped in /usr/src *** [buildworld] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src So, is there a way to fix this without building an updated stable/10 as an intermediary step? References: FreeBSD forum thread: https://forums.freebsd.org/threads/58082/ -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: aibs(4) / atk0110 support for newer systems
On Thu, 6 Oct 2016 00:37:16 +0300 Andriy Gapon <a...@freebsd.org> wrote: > On 05/10/2016 23:28, Torfinn Ingolfsen wrote: > > #6 0x80cd0081 in calltrap () > > at /usr/src/sys/amd64/amd64/exception.S:238 > > #7 0x81bcb078 in aibs_add_sensor () from /boot/kernel/aibs.ko > > #8 0x81bcb4b4 in aibs_attach_sif () from /boot/kernel/aibs.ko > > Argh, I've just spotted a very silly typo. > Could you please replace '0' with 'o' in > err = aibs_add_sensor(sc, 0, [i], ); > ? Yes, that fixes it - aibs.ko no longer panics my machine when I load it. Output from /var/log/messages: Oct 14 20:32:18 kg-core1 kernel: aibs0: on acpi0 Oct 14 20:32:18 kg-core1 kernel: aibs0: v0: 0x0602Vcore Voltage 850 / 1600 Oct 14 20:32:18 kg-core1 kernel: aibs0: v1: 0x06020001 +3.3 Voltage 2970 / 3630 Oct 14 20:32:18 kg-core1 kernel: aibs0: v2: 0x06020002 +5 Voltage 4500 / 5500 Oct 14 20:32:18 kg-core1 kernel: aibs0: v3: 0x06020003 +12 Voltage 10200 / 13800 Oct 14 20:32:18 kg-core1 kernel: aibs0: t0: 0x0603 CPU Temperature 600 / 950 Oct 14 20:32:18 kg-core1 kernel: aibs0: t1: 0x06030001 MB Temperature 450 / 750 Oct 14 20:32:18 kg-core1 kernel: aibs0: f0: 0x0604CPU FAN Speed 600 / 7200 Oct 14 20:32:18 kg-core1 kernel: aibs0: f1: 0x06040001CHASSIS FAN Speed 600 / 7200 it looks almost the same as it did previously: tingo@kg-core1$ grep aibs /tmp/c1-dmesg-9.3-stable-20160826.txt aibs0: on acpi0 aibs0: V0: 0x0602Vcore Voltage 850 / 1600 0x1 aibs0: V1: 0x06020001 +3.3 Voltage 2970 / 3630 0x1 aibs0: V2: 0x06020002 +5 Voltage 4500 / 5500 0x1 aibs0: V3: 0x06020003 +12 Voltage 10200 / 13800 0x1 aibs0: T0: 0x0603 CPU Temperature 600 / 950 0x10001 aibs0: T1: 0x06030001 MB Temperature 450 / 750 0x10001 aibs0: F0: 0x0604CPU FAN Speed 600 / 7200 0x10001 aibs0: F1: 0x06040001CHASSIS FAN Speed 600 / 7200 0x10001 and from sysctl dev.aibs root@kg-core1# sysctl dev.aibs dev.aibs.0.volt.0: 1404 850 1600 dev.aibs.0.volt.1: 3265 2970 3630 dev.aibs.0.volt.2: 5070 4500 5500 dev.aibs.0.volt.3: 12028 10200 13800 dev.aibs.0.temp.0: 51.9C 59.9C 94.9C dev.aibs.0.temp.1: 30.9C 44.9C 74.9C dev.aibs.0.fan.0: 2678 600 7200 dev.aibs.0.fan.1: 2678 600 7200 dev.aibs.0.%parent: acpi0 dev.aibs.0.%pnpinfo: _HID=ATK0110 _UID=16843024 dev.aibs.0.%location: handle=\_SB_.PCI0.SBRG.ASOC dev.aibs.0.%driver: aibs dev.aibs.0.%desc: ASUSTeK AI Booster (ACPI ASOC ATK0110) -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: aibs(4) / atk0110 support for newer systems
On Tue, 11 Oct 2016 14:29:34 +0300 Andriy Gapon <a...@freebsd.org> wrote: > On 06/10/2016 00:37, Andriy Gapon wrote: > > On 05/10/2016 23:28, Torfinn Ingolfsen wrote: > >> #6 0x80cd0081 in calltrap () > >> at /usr/src/sys/amd64/amd64/exception.S:238 > >> #7 0x81bcb078 in aibs_add_sensor () from /boot/kernel/aibs.ko > >> #8 0x81bcb4b4 in aibs_attach_sif () from /boot/kernel/aibs.ko > > > > Argh, I've just spotted a very silly typo. > > Could you please replace '0' with 'o' in > > err = aibs_add_sensor(sc, 0, [i], ); > > ? > > Ping. Done - see other messages in this thread. Sorry about the delay. -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: aibs(4) / atk0110 support for newer systems
On Mon, 3 Oct 2016 23:05:48 +0300 Andriy Gapon <a...@freebsd.org> wrote: > Yes, it does. Thank you! > It seems like a couple of minor changes are not in the source tree that you > are > using. One is some casts in a diagnostic printf and the other is a different > rounding of 0C in Kelvins. > I've generated a patch that should apply to your tree: > https://people.freebsd.org/~avg/aibs-ggrp-gitm.93.diff > Please try. The patch applied cleanly (I removed the old one with patch -R first): root@kg-core1# patch -p0 < /home/tingo/dl/aibs-ggrp-gitm.93.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: sys/dev/acpi_support/atk0110.c |=== |--- sys/dev/acpi_support/atk0110.c(revision 306109) |+++ sys/dev/acpi_support/atk0110.c(working copy) -- Patching file sys/dev/acpi_support/atk0110.c using Plan A... Hunk #1 succeeded at 28. Hunk #2 succeeded at 52. Hunk #3 succeeded at 78. Hunk #4 succeeded at 91. Hunk #5 succeeded at 124. Hunk #6 succeeded at 134. Hunk #7 succeeded at 362. Hunk #8 succeeded at 370. Hunk #9 succeeded at 377. Hunk #10 succeeded at 391. Hunk #11 succeeded at 435. Hunk #12 succeeded at 450. Hunk #13 succeeded at 457. Hunk #14 succeeded at 488. Hunk #15 succeeded at 495. done However, build fails: root@kg-core1# pwd /sys/modules/acpi/aibs root@kg-core1# make Warning: Object directory not changed from original /usr/src/sys/modules/acpi/aibs @ -> /usr/src/sys machine -> /usr/src/sys/amd64/include x86 -> /usr/src/sys/x86/include :> opt_acpi.h awk -f @/tools/makeobjops.awk @/dev/acpica/acpi_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/kern/device_if.m -h :> opt_ddb.h cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/src/sys/modules/acpi/aibs/../../../dev/acpi_support/atk0110.c -o atk0110.o cc1: warnings being treated as errors /usr/src/sys/modules/acpi/aibs/../../../dev/acpi_support/atk0110.c: In function 'aibs_attach': /usr/src/sys/modules/acpi/aibs/../../../dev/acpi_support/atk0110.c:252: warning: 's_idx' may be used uninitialized in this function /usr/src/sys/modules/acpi/aibs/../../../dev/acpi_support/atk0110.c:252: note: 's_idx' was declared here /usr/src/sys/modules/acpi/aibs/../../../dev/acpi_support/atk0110.c:256: warning: 'so' may be used uninitialized in this function /usr/src/sys/modules/acpi/aibs/../../../dev/acpi_support/atk0110.c:256: note: 'so' was declared here /usr/src/sys/modules/acpi/aibs/../../../dev/acpi_support/atk0110.c:253: warning: 'name' may be used uninitialized in this function /usr/src/sys/modules/acpi/aibs/../../../dev/acpi_support/atk0110.c:253: note: 'name' was declared here *** [atk0110.o] Error code 1 Stop in /usr/src/sys/modules/acpi/aibs. Do I have to do something more in order to build the new module? -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: aibs(4) / atk0110 support for newer systems
On Sat, 1 Oct 2016 00:08:15 +0300 Andriy Gapon <a...@freebsd.org> wrote: > On 30/09/2016 21:59, Torfinn Ingolfsen wrote: > > As I used '-C' as an argument to patch, there isn't one: > > root@kg-core1# l /sys/dev/acpi_support/atk0110.c.rej > > ls: /sys/dev/acpi_support/atk0110.c.rej: No such file or directory > > Right. So, I guess I have to specifically ask to not use -C option? :-) Sorry for the delay. I was distracted by other things. root@kg-core1# cd / root@kg-core1# patch -p1 < /home/tingo/dl/aibs-ggrp-gitm.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |diff --git a/sys/dev/acpi_support/atk0110.c b/sys/dev/acpi_support/atk0110.c |index e79a0e00e3577..743684100f737 100644 |--- a/sys/dev/acpi_support/atk0110.c |+++ b/sys/dev/acpi_support/atk0110.c -- Patching file sys/dev/acpi_support/atk0110.c using Plan A... Hunk #1 succeeded at 28. Hunk #2 succeeded at 52. Hunk #3 succeeded at 78. Hunk #4 succeeded at 124. Hunk #5 succeeded at 362. Hunk #6 succeeded at 370. Hunk #7 failed at 391. Hunk #8 succeeded at 435. Hunk #9 succeeded at 450. Hunk #10 failed at 488. 2 out of 10 hunks failed--saving rejects to sys/dev/acpi_support/atk0110.c.rej HTH -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> atk0110.c.rej Description: Binary data ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: aibs(4) / atk0110 support for newer systems
On Fri, 30 Sep 2016 19:00:09 +0300 Andriy Gapon <a...@freebsd.org> wrote: > On 30/09/2016 15:57, Torfinn Ingolfsen wrote: > > On Fri, 30 Sep 2016 14:30:02 +0300 > > Andriy Gapon <a...@freebsd.org> wrote: > > > >> Testing the patch should be as easy as building, installing and loading > >> aibs > >> module (found in sys/modules/acpi/aibs). Well, also don't forget to apply > >> the > >> patch with patch -p1 :-) > > > > The patch doesn't apply cleanly on FreeBSD 9.3-stable: > > root@kg-core1# patch -C -p1 < /home/tingo/dl/aibs-ggrp-gitm.diff > > Hmm... Looks like a unified diff to me... > > The text leading up to this was: > > -- > > |diff --git a/sys/dev/acpi_support/atk0110.c > > b/sys/dev/acpi_support/atk0110.c > > |index e79a0e00e3577..743684100f737 100644 > > |--- a/sys/dev/acpi_support/atk0110.c > > |+++ b/sys/dev/acpi_support/atk0110.c > > -- > > Patching file sys/dev/acpi_support/atk0110.c using Plan A... > > Hunk #1 succeeded at 28. > > Hunk #2 succeeded at 52. > > Hunk #3 succeeded at 78. > > Hunk #4 succeeded at 124. > > Hunk #5 succeeded at 362. > > Hunk #6 succeeded at 370. > > Hunk #7 failed at 391. > > Hunk #8 succeeded at 435. > > Hunk #9 succeeded at 450. > > Hunk #10 failed at 488. > > 2 out of 10 hunks failed--saving rejects to > > sys/dev/acpi_support/atk0110.c.rej > > done > > > > I'm running > > root@kg-core1# uname -a > > FreeBSD kg-core1.kg4.no 9.3-STABLE FreeBSD 9.3-STABLE #3 r304838: Fri Aug > > 26 12:11:25 CEST 2016 r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC > > amd64 > > Please show the .rej file. As I used '-C' as an argument to patch, there isn't one: root@kg-core1# l /sys/dev/acpi_support/atk0110.c.rej ls: /sys/dev/acpi_support/atk0110.c.rej: No such file or directory -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: aibs(4) / atk0110 support for newer systems
On Fri, 30 Sep 2016 14:30:02 +0300 Andriy Gapon <a...@freebsd.org> wrote: > Testing the patch should be as easy as building, installing and loading aibs > module (found in sys/modules/acpi/aibs). Well, also don't forget to apply the > patch with patch -p1 :-) The patch doesn't apply cleanly on FreeBSD 9.3-stable: root@kg-core1# patch -C -p1 < /home/tingo/dl/aibs-ggrp-gitm.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |diff --git a/sys/dev/acpi_support/atk0110.c b/sys/dev/acpi_support/atk0110.c |index e79a0e00e3577..743684100f737 100644 |--- a/sys/dev/acpi_support/atk0110.c |+++ b/sys/dev/acpi_support/atk0110.c -- Patching file sys/dev/acpi_support/atk0110.c using Plan A... Hunk #1 succeeded at 28. Hunk #2 succeeded at 52. Hunk #3 succeeded at 78. Hunk #4 succeeded at 124. Hunk #5 succeeded at 362. Hunk #6 succeeded at 370. Hunk #7 failed at 391. Hunk #8 succeeded at 435. Hunk #9 succeeded at 450. Hunk #10 failed at 488. 2 out of 10 hunks failed--saving rejects to sys/dev/acpi_support/atk0110.c.rej done I'm running root@kg-core1# uname -a FreeBSD kg-core1.kg4.no 9.3-STABLE FreeBSD 9.3-STABLE #3 r304838: Fri Aug 26 12:11:25 CEST 2016 r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 11.0 stuck on high network load
On Wed, 28 Sep 2016 12:06:47 +0200 Julien Charbon <julien.char...@gmail.com> wrote: > > I am still trying to reproduce your issue, without success so far. All: please remember to trim your quotes. Thank you. Carry on. -- Regards, Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /dev/led soekris 6501.
On Thu, 3 Mar 2016 08:10:54 +0100 Peter Ankerstål <pe...@pean.org> wrote: > I see. To my understanding this works on older soekris hardware but I > havent tested it myself. In that case, I would report it in Bugzilla. (I wasn't aware of led(4) - thanks!) -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /dev/led soekris 6501.
On Wed, 2 Mar 2016 19:18:20 -0800 Tom Samplonius <t...@samplonius.org> wrote: > > >> > >> How come there is no support for “ready" and “error" leds on the soekris > >> 6501 even though it seems fairly easy to control them? > >> > > > > a) perhaps no developer have that board? > > b) nobody has written the necessary code to do so? > > > > c) There is no generally accepted meaning for what “ready” or “error” LEDs > might mean in FreeBSD, so implementing a driver for these LEDs may be a > solution in a search of a problem. That part (interpretation) is irrelevant to the OPs question - he asked for a way to control them, not to interpret them. -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /dev/led soekris 6501.
On Wed, 2 Mar 2016 18:21:15 +0100 Peter Ankerstål <pe...@pean.org> wrote: > Hi! > > How come there is no support for “ready" and “error" leds on the soekris 6501 > even though it seems fairly easy to control them? > > Please see > http://www.mail-archive.com/soekris-tech@lists.soekris.com/msg06738.html and > http://ross.vc/?p=183 a) perhaps no developer have that board? b) nobody has written the necessary code to do so? There is a finite (and quite small) number of FreeBSD developers. There is a large (maybe infinite?) number of boards, SBC's, computers, toasters and so on that could run FreeBSD... -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS - poor performance with "large" directories
On Wed, 25 Nov 2015 16:24:48 +0100 Albert Cervin <alb...@acervin.com> wrote: > Just to close this off, when using Samba with ZFS it seems to be very > important (if you have many files in a directory) to make it case > sensitive as per: > https://wiki.samba.org/index.php/Performance_tuning#Handling_Large_Directories. > > Everything is now roses and works as expected. > > Sorry ZFS that I accused you! ;) Thanks for telling us what the problem (and fix) was. -- Torfinn Ingolfsen <torfinn.ingolf...@getmail.no> ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 10.1-stable: repeatable panic when trying to copy files from an ext3 filesystem mounted read-only
Hello, I get a repeatable panic when trying to cpy files from an ext3 filesystewm which is mounted read-only. Listing files works ok. Details: root@kg-u35jc# uname -a FreeBSD kg-u35jc.kg4.no 10.1-STABLE FreeBSD 10.1-STABLE #0 r283269: Fri May 22 09:14:57 CEST 2015 r...@kg-u35jc.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 Steps to reproduce: # kldload ext2fs # mount -r -t ext2fs /dev/ada0s5 /mnt # cp /mnt/whatever-file somedir Results in a nice panic: root@kg-u35jc# cat /var/crash/info.0 Dump header from device /dev/ada0s3b Architecture: amd64 Architecture Version: 2 Dump Length: 1075154944B (1025 MB) Blocksize: 512 Dumptime: Mon May 25 20:07:55 2015 Hostname: kg-u35jc.kg4.no Magic: FreeBSD Kernel Dump Version String: FreeBSD 10.1-STABLE #0 r283269: Fri May 22 09:14:57 CEST 2015 r...@kg-u35jc.kg4.no:/usr/obj/usr/src/sys/GENERIC Panic String: __lockmgr_args: recursing on non recursive lockmgr getblk @ (null):0 Dump Parity: 3531684913 Bounds: 0 Dump Status: good which is easy to reproduce: root@kg-u35jc# cat /var/crash/info.1 Dump header from device /dev/ada0s3b Architecture: amd64 Architecture Version: 2 Dump Length: 478572544B (456 MB) Blocksize: 512 Dumptime: Mon May 25 20:24:29 2015 Hostname: kg-u35jc.kg4.no Magic: FreeBSD Kernel Dump Version String: FreeBSD 10.1-STABLE #0 r283269: Fri May 22 09:14:57 CEST 2015 r...@kg-u35jc.kg4.no:/usr/obj/usr/src/sys/GENERIC Panic String: __lockmgr_args: recursing on non recursive lockmgr getblk @ (null):0 Dump Parity: 4100829037 Bounds: 1 Dump Status: good Is this a known problem ( I tried searching, but didn't find anything), or should I put it into Bugzilla? (core.txt.[01] are available, but largish at over 200K each, so I didn't try to get the mailing list to accept them) -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9.2-PRE: switch off that stupid Nakatomi Socrates
On Fri, 27 Sep 2013 19:17:44 -0700 Alfred Perlstein alf...@freebsd.org wrote: On 9/27/13 7:14 PM, Freddie Cash wrote: Lighten up. Go outside, take a deep breath of fresh air. Move on. Life is too short for this. :) Agreed. When it stop being fun, then it will see a decline in participation. Hear, hear! Everybody should remember this! -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard
On Sun, 22 Sep 2013 20:28:08 + Thomas Mueller mueller6...@bellsouth.net wrote: I've been unable to establish Internet connection from a new computer with Realtek 811E Ethernet despite this Ethernet chip working on another computer with another MSI motherboard. In additiin to the information you have already provided, you should also provide relevant output from pciconf, like so: root@kg-core1# pciconf -lv | grep -A 4 re0 re0@pci0:2:0:0: class=0x02 card=0x84321043 chip=0x816810ec rev=0x06 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet (substitute the name of your interface for re0) and also ifconfig output like this: root@kg-core1# ifconfig re0 re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE ether 50:46:5d:8b:a2:ea inet 10.1.150.50 netmask 0x broadcast 10.1.255.255 media: Ethernet autoselect (1000baseT full-duplex) status: active (again, substitute the name of your interface for re0) As far as fault-finding tricks go, here is one that have helped me on several occasions in the past: before doing anything with a network interface (in other words, before starting DHCP), try doing a 'ifconfig interface up' for example ifconfig re0 up After that, use the interface normally. If it works, you have found a bug related to the driver and the specific hardware revsion of you card. Create a PR for it. HTH -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Suggest changing dirhash defaults for FreeBSD 9.2.
On Tue, 27 Aug 2013 23:58:10 -0400 Robert Burmeister robert.burmeis...@utoledo.edu wrote: As 64 bit platforms tend to have more RAM and use ZFS, Do you have any numbers for the 64 bit platforms tend to use ZFS? If not, I will suggest that this is just a theory. FWIW, I haven't abandoned UFS on 64-bit platforms yet (I use ZFS were I need it). Oh, and all people - please trim your quotes. -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
There is an error in chmod(1)
There is an error in the chmod(1) man page. tingo@kg-v2$ uname -a FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27 23:50:55 CEST 2012 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 tingo@kg-v2$ apropos ^sticky sticky(7)- sticky text and append-only directories tingo@kg-v2$ man 1 chmod | grep sticky 1000(the sticky bit). See chmod(2) and sticky(8). t The sticky bit. setmode(3), symlink(7), chown(8), mount(8), sticky(8) HTH -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: fusefs-kmod does not work on 8-STABLE?
On Wed, 10 Apr 2013 06:33:10 -0500 Mark Felder f...@feld.me wrote: FUSE is pretty bad outside of FreeBSD 10 where it's rewritten and part of the kernel. If your environment would be OK with making the leap to FreeBSD 10 I'd recommend it. Ate there any bugreports or known problems? Except for one machine (see this thread[1]), it works fine (good enough) for me on a number of FreeBSD machines, and have done so for some years now. I haven't tested fusefs much under FreeBSD 9.0 and newer, I mostly use it with FreeBSD 8.x. I'm only using sshfs and gphotofs. References: 1) http://forums.freebsd.org/showthread.php?t=37302 -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Sanity Check on Mac Mini
On Sat, 09 Mar 2013 16:46:37 -0800 Doug Hardie bc...@lafn.org wrote: I have documented what I have completed and what remains to be done for the install of 9.1 on a Mini. I wrote this as a section of the Handbook, although its not in the right format as I don't know what that format is. I believe this needs to be retained in the documentation somewhere easily found for those who need it in the future. Nice. Perhaps you should qualify that this is for an Intel Mac mini (as opposed to a PowerPC / G4 Mac mini)? HTH -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8: amdtemp module and newer CPUs not working. MFC?
On Wed, 20 Feb 2013 22:29:05 -0800 (PST) Don Lewis truck...@freebsd.org wrote: Updating amdtemp is on my TODO list. It has some issues even on -CURRENT. This is kind of far down my priority list because on most of my AMD machines, I can also get the temperature without amdtemp: % sysctl hw.acpi.thermal.tz0.temperature hw.acpi.thermal.tz0.temperature: 30.0C In addition to what has already been mentioned in this thread, on most of *my* AMD machines hw.acpi.thernal yields nothing. Typical example: root@kg-quiet# sysctl hw.acpi.thermal.tz0.temperature sysctl: unknown oid 'hw.acpi.thermal.tz0.temperature' root@kg-quiet# sysctl hw.acpi.thermal sysctl: unknown oid 'hw.acpi.thermal' Typically, hw.acpi doesn't contain useful data: root@kg-quiet# sysctl hw.acpi hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S3 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: NONE hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 1 hw.acpi.reset_video: 0 hw.acpi.cpu.cx_lowest: C1 HTH -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RELENG_8: amdtemp module and newer CPUs not working. MFC?
Hello, I'm running FreeBSD 8.3-stable on a machine with an AMD A8-5600K cpu. tingo@kg-quiet$ uname -a FreeBSD kg-quiet.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #2: Fri Jan 4 19:18:15 CET 2013 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 tingo@kg-quiet$ dmesg | grep CPU | head -1 CPU: AMD A8-5600K APU with Radeon(tm) HD Graphics(3618.02-MHz K8-class CPU) Unfortunately, the amdtemp.ko module doesn't work: tingo@kg-quiet$ kldstat | grep temp 101 0x8123e000 f0f amdtemp.ko tingo@kg-quiet$ sysctl dev.amdtemp sysctl: unknown oid 'dev.amdtemp' Based on a thread[1] on the forums, amdtemp.c from -CURRENT work. But it doesn't compile under FreeBSD 8.3-stable: root@kg-quiet# cd /usr/src/sys/dev/amdtemp root@kg-quiet# ls -l /home/tingo/dl/amd* lrwxr-xr-x 1 tingo users 25 Feb 17 13:20 /home/tingo/dl/amdtemp.c - amdtemp.c?revision=246128 -rw-r--r-- 1 tingo users 14509 Feb 17 13:17 /home/tingo/dl/amdtemp.c?revision=246128 root@kg-quiet# mv amdtemp.c amdtemp.c_old root@kg-quiet# cp /home/tingo/dl/amdtemp.c . root@kg-quiet# cd /usr/src/sys/modules/amdtemp root@kg-quiet# make Warning: Object directory not changed from original /usr/src/sys/modules/amdtemp @ - /usr/src/sys machine - /usr/src/sys/amd64/include awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/amdtemp/../../dev/amdtemp/amdtemp.c /usr/src/sys/modules/amdtemp/../../dev/amdtemp/amdtemp.c:50:28: error: x86/pci_cfgreg.h: No such file or directory cc1: warnings being treated as errors /usr/src/sys/modules/amdtemp/../../dev/amdtemp/amdtemp.c: In function 'amdtemp_attach': /usr/src/sys/modules/amdtemp/../../dev/amdtemp/amdtemp.c:314: warning: implicit declaration of function 'pci_cfgregread' /usr/src/sys/modules/amdtemp/../../dev/amdtemp/amdtemp.c:314: warning: nested extern declaration of 'pci_cfgregread' *** Error code 1 Stop in /usr/src/sys/modules/amdtemp. Are there any plans to MFC this module? References: 1) http://forums.freebsd.org/showthread.php?t=37775 -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Spontaneous reboots on Intel i5 and FreeBSD 9.0
On Fri, 18 Jan 2013 11:26:33 +0200 Marin Atanasov Nikolov dna...@gmail.com wrote: The only error I'm able to find in /var/log/messages during boot-time is this: --- Jan 18 11:03:19 tsunami kernel: acpi0: _ASUS_ Notebook on motherboard Jan 18 11:03:19 tsunami kernel: ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110527/psargs-392) Jan 18 11:03:19 tsunami kernel: ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20110527/nsinit-380) --- Not sure if this is the root cause for this, cause I've seen this error before and at that time there were no reboots happening (months ago). Also I find it strange that it says Notebook above, as this is a desktop machine... FWIW, the part above is a red herring / false alarm; it is caused by a bad / incorrect implementation of acpi on your machine. Blame those who wrote the bios ... -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Custom Kernel for FreeBSD Installation
On Tue, 11 Dec 2012 09:26:03 -0500 xenophon\\+freebsd xenophon+free...@irtnog.org wrote: How do I go about replacing the kernel on the FreeBSD installation CDs? Not an answer to your question, but do you need to? Can't the DL380 G3 boot from something else, like a usb image? HTH -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Increasing the DMESG buffer....
On Wed, 21 Nov 2012 18:25:22 +0100 Willem Jan Withagen w...@digiware.nl wrote: Why bother... Because FreeBSD also runs on hardware with minimal memory? Because FreeBSD is a stable, sane operating system and we want to keep it that way? Because it breaks POLA? Because it make developers act sloppy? I'm sorry (I'm not picking on you in particular, but this comment represents a growing trend in attitude), but more and more people today are becoming careless in the way they think (or not think). I do not want FreeBSD to suffer because of that. If you are a FreeBSD developer or user; be vigilant! Don't let the sloppyness silnently slip into or favorite operating system, or the way we handle it! /soapbox -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9.1 and intel graphics
Hello, On Sun, 21 Oct 2012 05:10:53 -0400 Thomas Mueller muelle...@insightbb.com wrote: Normally I start X by startx which may be followed by an initialization file, so I don't get the default spartan default twm all the time. In Linux and FreeBSD, I generally use X as nonroot. Which is the normal and correct way, IMHO. So I don't really know how to start a program such as xterm as another user or how to have both root and nonroot windows in X. Is there any reason why you don't make use of su(1) or sudo (/usr/ports/security/sudo)? That way you can just launch a xterm as your normal user, and become root when you want / need. HTH -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 9.1-beta1: amdtemp.ko and AMD Fusion chips
Hello, I recently upgraded a AMD Fusion machine[1], to FreeBSD 9.1-beta1. I was a bit surprised to see that the amdtemp.ko module didn't work for this machine, as I thought PR kern/156358[2] had fixed that. Perhaps it didn't get in in time for 9.1? Anyway, I installed latest sources, used the patch found in the forums[3] and built a new kernel, and now amdtemp.ko works: tingo@kg-f4$ uname -a FreeBSD kg-f4.kg4.no 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #1: Sun Aug 5 18:43:08 CEST 2012 r...@kg-f4.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 tingo@kg-f4$ kldstat Id Refs AddressSize Name 13 0x8020 1320ec0 kernel 21 0x81521000 3048 amdtemp.ko tingo@kg-f4$ dmesg | grep amdtemp amdtemp0: AMD CPU On-Die Thermal Sensors on hostb4 tingo@kg-f4$ sysctl dev.amdtemp dev.amdtemp.0.%desc: AMD CPU On-Die Thermal Sensors dev.amdtemp.0.%driver: amdtemp dev.amdtemp.0.%parent: hostb4 dev.amdtemp.0.sensor0.core0: 54.0C Perhaps someone could MFC a patch? References: 1) http://sites.google.com/site/tingox/asrock_e350m1 2) http://www.freebsd.org/cgi/query-pr.cgi?pr=156358cat=kern 3) http://forums.freebsd.org/showpost.php?p=155483postcount=4 -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.0 - GPT boot problems?
On Fri, 03 Aug 2012 22:58:52 -0700 Kevin Oberman kob6...@gmail.com wrote: It's not clear from your message, but did you use the gpart bootcode command to write the protective MBR and the gptboot code as documented in the gpart(8) man page? Yes (this is why I wrote this message as a followup to the thread), all that was done in my first attempt, the problem is that the brain-dead firmware in this machine sees a GPT-partitioned disk and decides for itself that GPT = (U)EFI, and thus looks only for the EFI system partition, it does not try to boot from the gptboot in the freebsd-boot partition. If I use a MBR-partitoned drive, it boots ok. And yes, the BIOS (sorry, UEFI firmware) is the latest that Acer has provided for this machine. Just trying to make haeds and tails out of this UEFI thing, to see if it is a workable solution. -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.0 - GPT boot problems?
On Sat, 04 Aug 2012 03:10:52 -0400 Thomas Mueller muelle...@insightbb.com wrote: On Fri, Aug 3, 2012 at 3:09 PM, Torfinn Ingolfsen torfinn.ingolf...@getmail.no wrote: Just a short update on this machine (Acer Aspire X1470) and the GPT / UEFI situation. Today I set up another partition, EFI system partition. The partyitions now looks like this: root@kg-vm2# gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 119537664 2 freebsd-ufs (57G) 1195378268388608 3 freebsd-swap (4.0G) 127926434 121634816 4 freebsd-ufs (58G) 249561250 204800 5 efi (100M) 249766050 303597- free - (148M) I formatted the partition like this: root@kg-vm2# newfs_msdos -F32 /dev/ada0p5 newfs_msdos: trim 50 sectors to adjust to a multiple of 63 /dev/ada0p5: 204512 sectors in 12782 FAT32 clusters (8192 bytes/cluster) BytesPerSec=512 SecPerClust=16 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=63 Heads=16 HiddenSecs=0 HugeSectors=204750 FATsecs=100 RootCluster=2 FSInfo=1 +Backup=2 I have tried putting an EFI shell on it (I got the idea from this[1] page, I have tried both the 1.0 and 2.0 x64 shell), like this: root@kg-vm2# mount -t msdosfs /dev/ada0p5 /mnt root@kg-vm2# ls -l /mnt total 848 drwxr-xr-x 1 root wheel8192 Aug 3 14:30 EFI drwxr-xr-x 1 root wheel8192 Aug 3 16:21 boot -rwxr-xr-x 1 root wheel 847232 Aug 3 14:56 shellx64.efi root@kg-vm2# ls -l /mnt/boot total 760 -rwxr-xr-x 1 root wheel 771072 Aug 3 16:23 bootx64.efi root@kg-vm2# ls -l /mnt/EFI total 16 drwxr-xr-x 1 root wheel 8192 Aug 3 14:30 FreeBSD drwxr-xr-x 1 root wheel 8192 Aug 3 15:06 boot root@kg-vm2# ls -l /mnt/EFI/boot total 760 -rwxr-xr-x 1 root wheel 771072 Aug 3 15:29 bootx64.efi but no dice - it is not working, it still prints ERROR: No boot disk has been detected or the disk has failed. when I try to boot from this disk. How do I figure out where this UEFI firmware that Acer has put in this machine is getting it's boot manager and or boot loader from? I tried running 'strings -f' on the BIOS file (sorry, UEFI firmware), that got me all the EFI error messages, but nothing useful. Googling didn't help either. References: 1) https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface It's not clear from your message, but did you use the gpart bootcode command to write the protective MBR and the gptboot code as documented in the gpart(8) man page? -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com The gpart bootcode command is quite apart from and unrelated to (as far as I can tell) the EFI partition. Yes, this is what I have found out too. I think the EFI partition is supposed to be the first partition on a GPT-partitioned disk. This is not required by the specification as far as I can tell, but there are writings on the net saying that some implementations requires this (MS Win7 for example). I have installed FreeBSD to a USB stick, GPT-partitioned with three partitions: boot, root and swap. FWIW, I also use GPT-partitoned disks on many of my other machines; they work fine. It is (so far) only this machine which has this problem. EFI partition is to allow sharing a hard drive with multiple OS installations. The EFI system partition is also the place where (U)EFI firmwae will look for boot loaders, in order to load operating systems. YMMV. -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.0 - GPT boot problems?
Just a short update on this machine (Acer Aspire X1470) and the GPT / UEFI situation. Today I set up another partition, EFI system partition. The partyitions now looks like this: root@kg-vm2# gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 119537664 2 freebsd-ufs (57G) 1195378268388608 3 freebsd-swap (4.0G) 127926434 121634816 4 freebsd-ufs (58G) 249561250 204800 5 efi (100M) 249766050 303597- free - (148M) I formatted the partition like this: root@kg-vm2# newfs_msdos -F32 /dev/ada0p5 newfs_msdos: trim 50 sectors to adjust to a multiple of 63 /dev/ada0p5: 204512 sectors in 12782 FAT32 clusters (8192 bytes/cluster) BytesPerSec=512 SecPerClust=16 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=63 Heads=16 HiddenSecs=0 HugeSectors=204750 FATsecs=100 RootCluster=2 FSInfo=1 Backup=2 I have tried putting an EFI shell on it (I got the idea from this[1] page, I have tried both the 1.0 and 2.0 x64 shell), like this: root@kg-vm2# mount -t msdosfs /dev/ada0p5 /mnt root@kg-vm2# ls -l /mnt total 848 drwxr-xr-x 1 root wheel8192 Aug 3 14:30 EFI drwxr-xr-x 1 root wheel8192 Aug 3 16:21 boot -rwxr-xr-x 1 root wheel 847232 Aug 3 14:56 shellx64.efi root@kg-vm2# ls -l /mnt/boot total 760 -rwxr-xr-x 1 root wheel 771072 Aug 3 16:23 bootx64.efi root@kg-vm2# ls -l /mnt/EFI total 16 drwxr-xr-x 1 root wheel 8192 Aug 3 14:30 FreeBSD drwxr-xr-x 1 root wheel 8192 Aug 3 15:06 boot root@kg-vm2# ls -l /mnt/EFI/boot total 760 -rwxr-xr-x 1 root wheel 771072 Aug 3 15:29 bootx64.efi but no dice - it is not working, it still prints ERROR: No boot disk has been detected or the disk has failed. when I try to boot from this disk. How do I figure out where this UEFI firmware that Acer has put in this machine is getting it's boot manager and or boot loader from? I tried running 'strings -f' on the BIOS file (sorry, UEFI firmware), that got me all the EFI error messages, but nothing useful. Googling didn't help either. References: 1) https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: VirtualBox, AIO and zvol's - a cautionary tale
On Wed, 23 May 2012 14:11:48 +0100 Pete French petefre...@ingresso.co.uk wrote: Solution is simple - disable AIO. All then goes back to being nice and stable again. But it did take a while to find. Hope someone else finds the info usefull! Useful - thanks! -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Restricting users from certain privileges
On Sat, 28 Apr 2012 09:50:30 +0200 Zenny garbytr...@gmail.com wrote: Thanks Daniel, but sudo gives all (not selective) root privileges to the user (admin in my case). So this is not what I am trying to achieve in my original post. FWIW, sudo can be configured to allow only some commands. HTH -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.0 - GPT boot problems?
On Sat, 24 Mar 2012 17:26:03 +0100 Torfinn Ingolfsen torfinn.ingolf...@getmail.no wrote: Hi, I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire X1470). I installed from a usb memory stick (the default amd64 image), which I booted by pressing F12 and selecting it from the boot menu on the machine. I installed on a SSD (which replaced the hard drive originally in the machine), using the default scheme for 9.0 (GPT). The installation was painless (many thanks to all who made it that way), but when I try to boot the machine from the SSD afterwards, I just get this message from the BIOS: ERROR: No boot disk has been detected or the disk has failed. I tried selecting the SSD from the boot menu (via F12) instead (it shows up as EFI: M4-CT128M4SSD2), but got the same message. I upgraded the BIOS from version P01-A3 to version P01-A4 (the newest available), still no dice. Just an update: today I connected another disk to the machine (I used a sata-to-usb adapter, but I think that doesn't matter), this disk is MBR-partitioned, and the machine boots from this with no problems using the boot menu (via F12). root@kg-vm2# gpart show -p da1 = 63 117210177da1 MBR (55G) 63 29350692 da1s1 freebsd (14G) 29350755 29360079 da1s2 freebsd [active] (14G) 58710834 58499406 - free - (27G) The non-working disk looks like this: root@kg-vm2# gpart show -p ada0 = 34 250069613ada0 GPT (119G) 34128 ada0p1 freebsd-boot (64k) 162 119537664 ada0p2 freebsd-ufs (57G) 1195378268388608 ada0p3 freebsd-swap (4.0G) 127926434 121634816 ada0p4 freebsd-ufs (58G) 249561250 508397 - free - (248M) -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 9.0 - GPT boot problems?
Hi, I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire X1470). I installed from a usb memory stick (the default amd64 image), which I booted by pressing F12 and selecting it from the boot menu on the machine. I installed on a SSD (which replaced the hard drive originally in the machine), using the default scheme for 9.0 (GPT). The installation was painless (many thanks to all who made it that way), but when I try to boot the machine from the SSD afterwards, I just get this message from the BIOS: ERROR: No boot disk has been detected or the disk has failed. I tried selecting the SSD from the boot menu (via F12) instead (it shows up as EFI: M4-CT128M4SSD2), but got the same message. I upgraded the BIOS from version P01-A3 to version P01-A4 (the newest available), still no dice. If I use the usb stick I installed from, I can select the boot device, and actually boot from it, so there doesn't seem to be anything wrong with the SSD. I tried: kg-vm2# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 bootcode written to ada0 in case there was something wrong with the bootcode, but I still get the message ERROR: No boot disk has been detected or the disk has failed. gpart shows this: root@kg-vm2# gpart show ada0 = 34 250069613 ada0 GPT (119G) 34128 1 freebsd-boot (64k) 162 119537664 2 freebsd-ufs (57G) 1195378268388608 3 freebsd-swap (4.0G) 127926434 121634816 4 freebsd-ufs (58G) 249561250 508397- free - (248M) and root is on ada0p2, with swap on ada0p3: root@kg-vm2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ada0p2 56G2.3G 49G 4%/ devfs 1.0k1.0k 0B 100%/dev root@kg-vm2# swapinfo -h Device 1K-blocks UsedAvail Capacity /dev/ada0p3 4194304 0B 4.0G 0% Has anyone seen anything like this before? Any hints on what I can do? References: 1) http://sites.google.com/site/tingox/aspire_x1470_fbsd -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.0 - GPT boot problems?
On Sat, 24 Mar 2012 18:50:13 +0100 Christian Laursen x...@borderworlds.dk wrote: It sounds a bit like the BIOS thinks that since the disk uses GPT you want to EFI boot. That could very well be the case. As far as I know the default bootcode in the PMBR is meant for old style BIOS booting. Hmm, I was hoping that the pmbr / gptboot would work both ways. Is it possible to disable EFI in your BIOS? If that is the case, that's probably the easiest solution. No, I haven't found any place to do that. Before I installed FreeBSD on this SSD (before it was partitioned with gpart) it showed up in the BIOS under hard drive. (Other choices are removable drive Now it shows up under EFI device, and doesn't show up under hard drive. I'm unsure of the current state of EFI boot in FreeBSD but a little bit of searching did not look promising. Yes, after a bit of searching I agree with you. If anyone knows of a EFI capable boot loader for FreeBSD, I'm willing to try it. Rather that, than having to deal with grub, elilo or the other stuff. -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD9 and the sheer number of problem reports
On Thu, 23 Feb 2012 19:25:01 +0100 Damien Fleuriot m...@my.gd wrote: In the current state of things, I have *absolutely* no wish to run it in production :( Nobody forces you to jump onto the 9.0-release bandwagon. You can choose to skip it. If you skip 9.0 - will you be better prepared and less fearful when 9.1-release comes? You decide. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8.2-stable: devd fails to restart
On Tue, 07 Feb 2012 12:16:15 -0700 (MST) Warren Block wbl...@wonkity.com wrote: It's devd, IMO. Hey, come to think of it, I did enter a PR, the one above. If this is still a problem in 9 (which I can test in a bit), posting to -current might get some needed attention on it. PR updated. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8.2-stable: devd fails to restart
On Mon, 06 Feb 2012 00:08:55 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Sat, 4 Feb 2012, Torfinn Ingolfsen wrote: On Sat, 04 Feb 2012 10:34:19 -0700 (MST) Warren Block wbl...@wonkity.com wrote: Possibly relevant: http://www.freebsd.org/cgi/query-pr.cgi?pr=140462cat= (Using DHCP from /etc/rc.conf leaves a lock on devd.pid. SYNCDHCP does not.) And the thread: http://lists.freebsd.org/pipermail/freebsd-current/2009-October/012749.html Yes, it seems to be that problem. Tested on my other machine, which hasn't changed since the problem was discovered: root@kg-v7# service devd status devd is not running. root@kg-v7# ll /var/run/devd.pid -rw--- 1 root wheel 3 Jan 12 20:40 /var/run/devd.pid root@kg-v7# lsof /var/run/devd.pid COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dhclient 1075 root5w VREG 0,703 918547 /var/run/devd.pid dhclient 1091 _dhcp5w VREG 0,703 918547 /var/run/devd.pid root@kg-v7# So, if this was worked on back in 2009, why isn't fixed yet? I switched to using SYNCDHCP which avoids the problem, didn't enter a PR, and quickly forgot about it. It would be nice to have it fixed. I'm all for getting it fixed, even if I don't know how yet. Should a PR be against devd, dhclient, or ... something else? -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8.2-stable: devd fails to restart
On Fri, 03 Feb 2012 23:37:56 -0500 Jason Hellenthal jh...@dataix.net wrote: Just because of what I read already is pretty terse I am top-posting for a reason. $ su - # /etc/rc.d/devd stop # pgrep -l devd (This should show nothing if so kill the results) Done: root@kg-v2# /etc/rc.d/devd stop devd not running? root@kg-v2# pgrep -l devd root@kg-v2# # /sbin/devd -D -d(Paste the results) The first output was longer than my scrollback buffer, so I tried it one more time. Now it just hangs here: root@kg-v2# /sbin/devd -D -d Parsing /etc/devd.conf setting scsi-controller-regex=(aac|adv|adw|aha|ahb|ahc|ahd|aic|amd|amr|asr|bt|ciss|ct|dpt|esp|ida|iir|ips|isp|mlx|mly|mpt|ncr|ncv|nsp|stg|sym|trm|wds)[0-9]+ Parsing files in /etc/devd Parsing /etc/devd/asus.conf Parsing /etc/devd/uath.conf Parsing /etc/devd/usb.conf Parsing files in /usr/local/etc/devd Parsing /usr/local/etc/devd/webcamd.conf Strange. I tried deinstalling webcamd (yes, a shot in the dark, I know), but it didn't help: root@kg-v2# pkg_deinstall webcamd-3.2.0.2 --- Deinstalling 'webcamd-3.2.0.2' == You should manually remove the webcamd user. [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 954 packages found (-1 +0) (...) done] root@kg-v2# pgrep -l devd root@kg-v2# /sbin/devd -D -d Parsing /etc/devd.conf setting scsi-controller-regex=(aac|adv|adw|aha|ahb|ahc|ahd|aic|amd|amr|asr|bt|ciss|ct|dpt|esp|ida|iir|ips|isp|mlx|mly|mpt|ncr|ncv|nsp|stg|sym|trm|wds)[0-9]+ Parsing files in /etc/devd Parsing /etc/devd/asus.conf Parsing /etc/devd/uath.conf Parsing /etc/devd/usb.conf Parsing files in /usr/local/etc/devd -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8.2-stable: devd fails to restart
More data: root@kg-v2# service devd status devd is not running. root@kg-v2# service devd start Starting devd. devd: devd already running, pid: 808 /etc/rc.d/devd: WARNING: failed to start devd root@kg-v2# rm /var/run/devd.pid root@kg-v2# service devd start Starting devd. root@kg-v2# service devd status devd is running as pid 30165. root@kg-v2# service devd stop Stopping devd. root@kg-v2# service devd status devd is not running. root@kg-v2# ll /var/run/devd.pid -rw--- 1 root wheel 5 Feb 4 16:45 /var/run/devd.pid root@kg-v2# service devd start Starting devd. root@kg-v2# service devd status devd is running as pid 30206. Let me try to install the webcamd port again... done. Now testing again: root@kg-v2# service devd status devd is running as pid 30206. root@kg-v2# service devd stop Stopping devd. root@kg-v2# ll /var/run/devd.pid -rw--- 1 root wheel 5 Feb 4 16:48 /var/run/devd.pid root@kg-v2# service devd status devd is not running. root@kg-v2# service devd start Starting devd. root@kg-v2# service devd status devd is running as pid 35551. Not really sure what's going on here. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8.2-stable: devd fails to restart
On Sat, 04 Feb 2012 10:34:19 -0700 (MST) Warren Block wbl...@wonkity.com wrote: Possibly relevant: http://www.freebsd.org/cgi/query-pr.cgi?pr=140462cat= (Using DHCP from /etc/rc.conf leaves a lock on devd.pid. SYNCDHCP does not.) And the thread: http://lists.freebsd.org/pipermail/freebsd-current/2009-October/012749.html Yes, it seems to be that problem. Tested on my other machine, which hasn't changed since the problem was discovered: root@kg-v7# service devd status devd is not running. root@kg-v7# ll /var/run/devd.pid -rw--- 1 root wheel 3 Jan 12 20:40 /var/run/devd.pid root@kg-v7# lsof /var/run/devd.pid COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME dhclient 1075 root5w VREG 0,703 918547 /var/run/devd.pid dhclient 1091 _dhcp5w VREG 0,703 918547 /var/run/devd.pid root@kg-v7# So, if this was worked on back in 2009, why isn't fixed yet? -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8.2-stable: devd fails to restart
On Thu, 02 Feb 2012 21:45:26 -0800 Doug Barton do...@freebsd.org wrote: Actually all the OP needs to do is to make sure the src tree is up to date and run mergemaster. I MFC'ed the relevant changes to rc.d/devd last April. Strange, my machine was rebuilt later than that (yes, I always run mergemaster as part of the the make world): root@kg-v7# uname -a FreeBSD kg-v7.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #7: Sat Jul 9 23:00:31 CEST 2011 r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 root@kg-v7# root@kg-v7# head -3 /etc/rc.subr # $NetBSD: rc.subr,v 1.67 2006/10/07 11:25:15 elad Exp $ # $FreeBSD: src/etc/rc.subr,v 1.88.2.16 2011/04/29 20:31:52 dougb Exp $ # root@kg-v7# head -3 /etc/rc.d/devd #!/bin/sh # # $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $ Another machine which also has the same problem: root@kg-v2# uname -a FreeBSD kg-v2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Jul 16 02:07:14 CEST 2011 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 root@kg-v2# head -3 /etc/rc.subr # $NetBSD: rc.subr,v 1.67 2006/10/07 11:25:15 elad Exp $ # $FreeBSD: src/etc/rc.subr,v 1.88.2.17 2011/07/03 16:32:03 jilles Exp $ # root@kg-v2# head -3 /etc/rc.d/devd #!/bin/sh # # $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $ Is that the versions you are referring to? I have a machine with world built in December, it seems to have the same versions of the files: (note: i have not tried restarting devd on that machine) root@kg-vm# uname -a FreeBSD kg-vm.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Dec 17 17:47:43 CET 2011 r...@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 root@kg-vm# head -3 /etc/rc.subr # $NetBSD: rc.subr,v 1.67 2006/10/07 11:25:15 elad Exp $ # $FreeBSD: src/etc/rc.subr,v 1.88.2.17 2011/07/03 16:32:03 jilles Exp $ # root@kg-vm# head -3 /etc/rc.d/devd #!/bin/sh # # $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $ -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 8.2-stable: devd fails to restart
On Fri, 03 Feb 2012 08:34:10 +0300
Sergey Kandaurov pluk...@gmail.com wrote:
Please apply this patch and report how it goes for you.
http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/devd.diff?r1=1.12;r2=1.13
This is not in 8-STABLE yet.
It looks like it (or almost the same) is here already:
root@kg-v2# more /etc/rc.d/devd
#!/bin/sh
#
# $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $
#
# PROVIDE: devd
# REQUIRE: netif network_ipv6
# BEFORE: NETWORKING mountcritremote
# KEYWORD: nojail shutdown
. /etc/rc.subr
name=devd
rcvar=`set_rcvar`
command=/sbin/${name}
start_precmd=${name}_prestart
stop_precmd=find_pidfile
find_pidfile()
{
if get_pidfile_from_conf pid-file /etc/devd.conf; then
pidfile=$_pidfile_from_conf
else
pidfile=/var/run/${name}.pid
fi
}
devd_prestart ()
{
find_pidfile
# If devd is disabled, turn it off in the kernel to avoid memory leaks.
if ! checkyesno ${rcvar}; then
$SYSCTL hw.bus.devctl_disable=1
fi
}
load_rc_config $name
run_rc_command $1
HTH
--
Torfinn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 8.2-stable: devd fails to restart
Hi, I thought this bug was fixed back in 2009? root@kg-v7# uname -a FreeBSD kg-v7.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #7: Sat Jul 9 23:00:31 CEST 2011 r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 root@kg-v7# root@kg-v7# service devd status devd is running as pid 555. root@kg-v7# service devd restart Stopping devd. Starting devd. devd: devd already running, pid: 555 /etc/rc.d/devd: WARNING: failed to start devd root@kg-v7# service devd status devd is not running. What gives? -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: booting 8.2 on Gigabyte GA-790XTA-UD4
On Tue, 18 Oct 2011 21:17:58 +0200 Václav Zeman v.hais...@sh.cvut.cz wrote: I am having problems booting the FreeBSD 8.2 CD image on GA-790XTA-UD4(rev. 1.0). The last thing that I can see is BIOS drive A: is disk0. Is this completely not supported? Can I do anything to install FreeBSD on such box? Have you done the usual stuff? - if not running the latest BIOS, try to update - try to fiddle with relevant settings in BIOS - Try another release of FreeBSD (older or newer), or a new snapshot - Google name of board + FreeBSD HTH -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kern/143370: splash_txt ASCII splash screen module
On Wed, 29 Jun 2011 22:50:15 +1000 Antony Mawer li...@mawer.org wrote: Hi all, Not sure if this is the right place to post it -- about 6 years ago I put together a module which displays an ASCII splash screen on boot (rather than the graphical splash_pcx and splash_bmp modules). We have been running it in production since that time without issue. So, the difference between this and loader.conf's loader_logo construct is that a) this is a proper splash screen module b) you can / must design your splash screen with a separate program (compared to write / modify Forth code) Is my understanding correct? -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Fileserver panic - FreeBSD 8.1-stable and zfs
Update: On Thu, 02 Jun 2011 16:09:21 -0700 Jeremy Chadwick free...@jdc.parodius.com wrote: Anyway, your system has 4GB of RAM installed in it, so on 8.1-STABLE I'd recommend you try these settings: vm.kmem_size=3584M vm.kmem_size_max=3584M vfs.zfs.arc_max=2048M Now, these are all chosen by me off the top of my head with absolutely ZERO knowledge of what the memory usage on this system is like **without** ZFS in the picture. I'm making a lot of assumptions, and I'm assuming worst-case scenarios. For example, if this machine also runs mysqld and its tuned to take up a lot of memory, I would advocate dropping vfs.zfs.arc_max to 1536M or 1024M. Please don't drop it too much; ZFS performs best when it has lots of ARC. Since you mentioned going to 8.2-STABLE, all you need to tune on that version is one single tunable: vfs.zfs.arc_max The machine now runs 8.2-stable: root@kg-f2# uname -a FreeBSD kg-f2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #5: Fri Jun 3 17:20:39 CEST 2011 r...@kg-f2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 And I have added the following to /boot/loader.conf: vfs.zfs.arc_max=2048M Hopefully, this will keep the machine rock solid (unitil something else happens, at least). Oh, and thanks for your advice - really helpful. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Fileserver panic - FreeBSD 8.1-stable and zfs
FYI, in case it is interesting my zfs fileserver[1] just had a panic: (transcribed from screen) panic: kmem_malloc(131072): kmem_map too small: 1324613632 total allocated cpuid = 1 KDB: stack backtrace: #0 0x805df92e at kdb_backtrace+0x5e #1 0x805ada77 at panic+0x187 #2 0x80800190 at kmem_alloc+0 #3 0x807f7e0a at uma_large_malloc+0x4a #4 0x8059aee7 at malloc+0xd7 #5 0x80ed6763 at vdev_queue_io_to_issue+0x1c3 #6 0x80ed68e9 at vdev_queue_io_done+0x99 #7 0x80ee6c9f at zio_vdev_io_done+0x7f #8 0x80ee7237 at zio_execute+0x77 #9 0x80e872f3 at taskq_run_safe+0x13 #10 0x805ea984 at taskqueue_run+0xa4 #11 0x805eabf6 at taskqueue_thread_loop+0x46 #12 0x80584278 at fork_exit+0x118 #13 0x8087f2fe at fork_trampoline+0xe Uptime: 109d19h47m1s Cannot dump. Device not defined or unavailable. Automatic reboot in 15 seconds - press a key on the console to abort And the machine hung here, no response from keyboard. The machine runs: root@kg-f2# uname -a FreeBSD kg-f2.kg4.no 8.1-STABLE FreeBSD 8.1-STABLE #4: Fri Oct 29 12:11:48 CEST 2010 r...@kg-f2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 FWIW; i had started a scrub of one of the pools (zpool scrub storage) some time before this, I do not know how far it was before this happened (a scrub of this pool normally takes about 3 hours). Since the machine was totally unresponsive, I rebooted it. after reboot, I found out that the scrub was not finished: root@kg-f2# zpool status storage pool: storage state: ONLINE scrub: scrub in progress for 307445734561825858h22m, 2.76% done, 307445734561825792h47m to go config: NAMESTATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10ONLINE 0 0 0 ad12ONLINE 0 0 0 ad14ONLINE 0 0 0 ada0ONLINE 0 0 0 errors: No known data errors HTH References: 1) http://sites.google.com/site/tingox/ga-ma74gm-s2h_freebsd -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Fileserver panic - FreeBSD 8.1-stable and zfs
On Thu, 02 Jun 2011 12:50:26 -0700 Jeremy Chadwick free...@jdc.parodius.com wrote: This is a well-known thing with ZFS on FreeBSD. Because you're running 8.1-STABLE, this makes figuring out all the tunables and so on a lot more difficult than if you were running 8.2-STABLE. FWIW, the machine has been quite stable for me for a long time. Please provide: 1) Contents of /boot/loader.conf root@kg-f2# more /boot/loader.conf zfs_load=YES vfs.root.mountfrom=zfs:zroot siis_load=YES amdtemp_load=YES # testing without MSI hw.pci.enable_msix=0 hw.pci.enable_msi=0 2) Output from: sysctl hw.physmem hw.usermem hw.realmem (your hardware page says 4GB, but I can't be bothered to sift through multi-pages of wiki documents and links to find the answers) root@kg-f2# sysctl hw.physmem hw.usermem hw.realmem hw.physmem: 4141920256 hw.usermem: 3721527296 hw.realmem: 4966055936 3) Output from: sysctl vfs.zfs.zio.use_uma root@kg-f2# sysctl vfs.zfs.zio.use_uma vfs.zfs.zio.use_uma: 0 The scrub itself was not ultimately responsible for this problem (meaning the bug is not in scrub). The problem is that your kernel effectively wanted more memory for ZFS operations than was available. Understood. I didn't mean to imply it was; I just tried to provide data about activity on the server that might have contributed to the failure. FWIW, the scrub finished fine: root@kg-f2# zpool status storage pool: storage state: ONLINE scrub: scrub completed after 307445734561825860h15m with 0 errors on Thu Jun 2 23:23:44 2011 config: NAMESTATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10ONLINE 0 0 0 ad12ONLINE 0 0 0 ad14ONLINE 0 0 0 ada0ONLINE 0 0 0 errors: No known data errors The trick is to tune /boot/loader.conf until you can gain stability. Well, the server has been reasonably stable for me for about a year now (I had to replace a failing hard drive, but I count that as wear not instability). Again, because you're running 8.1-STABLE, the tuning parameters here will behave different than on 8.2-STABLE. We can go over those in a follow-up thread. I have no trouble with upgrading the server to 8.2-stable, if now is a good time to do it. (I haven't watched closely for any zfs related problems on the mailing list lately.) I've gotten to the point where I literally cannot remember all of the different situations/conditions/tunings for each FreeBSD kernel build, release, date, type, etc., so I tend to focus on the most recent RELENG_8 build. Then someone comes along with an older build. Hehe. :-) I know what you mean. Keeping up with all this stuff is getting harder every year. :) -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Fileserver panic - FreeBSD 8.1-stable and zfs
On Thu, 02 Jun 2011 12:44:49 -0700 Artem Belevich a...@freebsd.org wrote: It's probably one of the most frequently reported issues with ZFS. While things got quite a bit better lately, you still need to bump up kernel VM size with vm.kmem_size tunable. I typically set vm.kmem_size tunable to ~2x physical memory size. Mine is currently untuned: root@kg-f2# sysctl vm.kmem_size vm.kmem_size: 1331953664 I guess I have been lucky; the server has been stable for a long time now. In general you may want to update to the latest -stable. There were a lot of ZFS fixes committed. Yes, perhaps now is a good time to do so. I have held back on updates on this machine, to find out if zfs was stable. And I think it has been, for me at least. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mountlate not late enough for nfe0 with dhcp
On Fri, 27 May 2011 12:36:27 +0300 nickolas...@gmail.com wrote: 2011/5/27 Jeremy Chadwick free...@jdc.parodius.com: This has been discussed at length in the past, causing me to write an rc.d script to work around the problem. You can drop this script into /usr/local/etc/rc.d, chmod 755 it, and make use of it appropriately. The comments in the script should help you understand it. http://jdc.parodius.com/freebsd/netwait Example entries in rc.conf: netwait_enable=yes netwait_ip=4.2.2.1 4.2.2.2 netwait_if=em0 Maybe it's time to add this script to -STABLE? Problem touch many people, who need it (IMHO) Or, if the FAQ at freebsd.org isn't updated already, simply write about this script there? HTH -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: System extremely slow under light load
On Mon, 25 Apr 2011 16:23:37 +0200 Bartosz Fabianowski free...@chillt.de wrote: Try Knoppix, or Ubuntu LiveCD. I tend to use the former for rescue situations: Thanks. I am aware of both - but neither boots from USB (and I have no CD-Rs at hand). I am running UNetbootin under Windows XP in VirtualBox right now to try and get Xubuntu 10.04 onto a USB key. It is really sad that almost all Linux distributions require this detour via a proprietary operating system. Have you tried just using dd to copy the iso image of a Ubuntu / Linux LiveCD to a suitably sized USB memory stick? It has worked for me in the past. YMMV. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
panic in FreeBSD 8.2-stable.
In case this is useful. One of my machines just had a panic (transcribed by me): panic: bad pte cpuid = 0 KDB: stack backtrace: #0 0x80603f6e at kdb_backtrace+0x5e #1 0x805d1ae7 at panic+0x187 #2 0x808b5c08 at pmap_remove_pages+0x408 #3 0x805a3435 at exec_new_vmspace+0x285 #4 0x80589d20 at exec_elf64_imgact+0x3f0 #5 0x805a3813 at kern_execve+0x3b3 #6 0x805a4bed at execve+0x3d #7 0x8060ff55 at syscallenter+0x1e5 #8 0x808bce6b at syscall+0x4b #9 0x808a5642 at Xfast_syscall+0xe2 Uptime: 1d0h10m39s The machine is running FreeBSD 8.2-stable: root@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #0: Sun Apr 3 19:49:05 CEST 2011 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 Hardware info here: http://sites.google.com/site/tingox/rs480m2 HTH -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Constant rebooting after power loss
On Sun, 03 Apr 2011 13:04:54 +0100 Bruce Cran br...@cran.org.uk wrote: On 01/04/2011 16:47, Stefan `Sec` Zehl wrote: If you want to get rid of the reboot loop, set: background_fsck=NO Then it will either come up, or ask for help if anything fails. I realise that people like having systems that come up quickly after a crash, but is it worth reconsidering disabling background fsck by default since it can cause issues like this? Based _only_ on my own experience, and personal preference, I would say NO. The reason? It works nicely the way it is now, and any problems will be noticed, and can be fixed with a bit of effort, even for a person with little experience in running FreeBSD machines. One of the reasons that I like FreeBSD is that it gives me tools I need, but it doesn't try to automate or abstract away my responsiblites as a system administrator. I think the FreeBSD project has managed something impressive; being a platform for bringing in new ideas / tools, and at the same time staying conservative (POLA, and well thought out changes). I like that. -- Regards, Torfinn Ingolfsen FreeBSD user FreeBSD sysadmin on the personal / hobby level, for many, many years ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS pool on FreeBSD 8.2-STABLE broken?
On Wed, 30 Mar 2011 14:53:16 -0400 J. Hellenthal jh...@dataix.net wrote: He specifically does not need -9 to get v28 code for this recovery operation. Martin Matuska does a pretty swell job of keeping these [1] up-to-date so in-case something does go wrong it can be fixed fairly quickly without having to go through and rebuild this and that. 1. http://mfsbsd.vx.sk/ Ah... very useful tools. Thanks for mentioning. And thanks to Martin Matuska for doing this. Have a nice day, everyone. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Best way to switch from Linux to BSD
On Tue, 29 Mar 2011 01:32:23 -0400 Jason Hsu jhsu802...@jasonhsu.com wrote: I've been trying to switch from Linux to BSD for my everyday computing (email, word processing, spreadsheets, etc.), but I couldn't get things to work properly. I've been so spoiled by the quickness and user-friendliness of antiX/Swift Linux and Puppy Linux for so long. I have a backlog of stuff to do, so I'm sticking to Linux for now as my main OS. However, I might try BSD in VirtualBox and on my laptop. IMO; get a second machine (laptop or workstation / desktop) and install FreeBSD on that. After you get it working the way you want, you can dump your Linux machine. Are there any good tutorials for using BSD on the desktop? I'm having much more difficulty finding good information on BSD than was the case for Linux. In retrospect, this shouldn't be a surprise given that Linux is relatively mainstream while BSD is very obscure. I really don't understand this question. If you really are asking about *using* BSD on the desktop, there are very few, if any, differences compared to Linux. The basic GUI is the same (Xorg), the DE's are the same (the big ones being KDE, Gnome and Xfce), and almost all user programs are the same. What is the difference your perceive? Myself, I have kept one laptop running Linux (Xubuntu), because of two things: a) it is very hard (in Norway at least) to find and buy a laptop that will work almost 100% with FreeBSD, unless I want to double (or more) the price I can get a good laptop for. Somehow, Linux manages to adjust to most of the fails to meet specifications problems of laptop vendors today. b) Often, I need (or want) to check out a new service or program that only runs on Linux (for the time being). My main workstation is a desktop, running FreeBSD. All my test machines (most of them have desktops installed) run FreeBSD. Granted, many of them are triple-boot and run Linux and other BSDs as well, for testing purposes. My servers run FreeBSD. HTH -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: system crash during make installworld
On Mon, 21 Feb 2011 18:56:36 +0200 Andriy Gapon a...@freebsd.org wrote: on 21/02/2011 10:04 David J Brooks said the following: As the subject suggests, my laptop crashed during make installworld. The new kernel boots, but the ELF interpreter is not found and I cannot get to a single user prompt. What is the least painful way to proceed? My take would be an alternative bootable media: live CD or install CD or etc. Or, if the hard drive is easy to get at, and he has the a (S)ATA-to-usb dongle / dock; connect the hard drive to another FreeBSD machine and copy required files off that one. But first things first: does the old kernel still boot? (depending on how far in the process make installworld came, it might) HTH -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: The FreeBSD 7.4-BETA1 CD wont boot properly on this machine
On Sun, 19 Dec 2010 21:30:59 + Chris Rees utis...@gmail.com wrote: Did you try installing using a different computer onto that hard drive? Nope, not yet. Looking for easier alternatives first. Is the hardware supported by 7.x (http://www.freebsd.org/releases/7.3R/hardware.html for pointers) Well, AFAICT, it should work. Nothing odd or non-standard. Again, AFAICT. Is there a reason you want 7.4 rather than 8.1? The machine already runs 8.1 (see [1]). Sorry for not making that clear. (in my defence, the information is available on the page I referenced in my post, but obviously nobody bothered to check that. Oh well.) Now I want to install 7.4 on another partition, so I can test that release as well. I always try to install as many different releases on a machine as I can / have space for; it has proven useful in the past, and it is my small way to help FreeBSD developers by testing as much (many releases / branches) as I can, on as much hardware as I can. References: 1) http://sites.google.com/site/tingox/asus_v7-p7h55e_freebsd -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: The FreeBSD 7.4-BETA1 CD wont boot properly on this machine
On Sun, 19 Dec 2010 16:30:08 -0800 Jeremy Chadwick free...@jdc.parodius.com wrote: This has, historically, been caused by problems with certain firewire chipsets. The workaround has been to disable firewire in the BIOS. Aha! That's a great clue. I haven't seen that particular problem before. I've experienced this on a Shuttle system, and others have on different motherboards as well: http://old.nabble.com/run_interrupt_driven_hooks:-still-waiting-after-300-seconds-for-xpt_config-td23492390.html http://old.nabble.com/-Fwd%3A-run_interrupt_driven_hooks%3A-still-waiting...-for-xpt_config--td23641548.html http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009079.html However, that motherboard doesn't seem to support firewire (but Asus has been known to forget mentioning features on their site before). It has firewire. From /var/log/messages under FreeBSD 8.1-stable: fwohci0: 1394 Open Host Controller Interface mem 0xfbdff800-0xfbdf,0xfbdff400-0xfbdff47f,0xfbdff000-0xfbdff07f,0xfbdfec00-0xfbdfec7f irq 19 at device 0.0 on pci1 fwohci0: [ITHREAD] fwohci0: OHCI version 1.10 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:1e:8c:00:00:2c:b8:9a fwohci0: Phy 1394a available S400, 2 ports. So a quick tour into the bios to disable the firewire, then back to boot from the 7.4-BETA1 cd. Yes, it works now, and while I have been wrinting this message, it has just finished installing. Great advice. Thanks! Otherwise, run 8.x. I do already, see my other posting in this thread. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: The FreeBSD 7.4-BETA1 CD wont boot properly on this machine
On Mon, 20 Dec 2010 20:18:06 +0100 Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: So a quick tour into the bios to disable the firewire, then back to boot from the 7.4-BETA1 cd. Yes, it works now, and while I have been wrinting this message, it has just finished installing. For completeness, I tried enabling the firewire in the bios after I had installed FreeBSD7.4-BETA1. But it didn't work (I didn't think it would), the machine just printed the same error messages as the install CD did. Anyway, dmesg output and other info is available here: http://sites.google.com/site/tingox/asus_v7-p7h55e_freebsd -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
The FreeBSD 7.4-BETA1 CD wont boot properly on this machine
Hi, I am trying to install FreeBSD 7.4-BETA1 / amd64 on this[1] machine. The machine doesn't have a CD drive built-in, so I am using a Plextor PX-608CU external DVD writer which connects via usb as the CD drive to install from. I use the FreeBSD-7.4-BETA1-amd64-disc1.iso, which is burned to a CD. After powering on the machine, I press F8, get a nice little bootmenu, select the Plextor drive, and off we go. The kernel boots, and everything is great. But, after detecting the hard drive (ad4, ok it's really a SSD) and the cd drive, it just spits out messages like these: run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config and after spitting out one more message (the one for 300 seconds), it just sits there. Booting with verbose doesn't give men any more messages related to this. I've tried the -bootonly CD too - it has the same problem. Yes, the sha256 checksums on the files verifies a-ok, the CD's can be mounted in FreeBSD, etc. I even mad a usb memory stick image of the -disc1 and booted the machine from that, and it has the same problem (the run_interrupt... messages). Kicker: the machine boots nicely from a FreeBSD 8.1-release (amd64) CD. Also tried with a OpenBSD 4.8 (amd64) install CD, yep - it also boots nicely. So, any hints on how to get FreeBSD 7.4-BETA1 onto this machine? References: 1) http://sites.google.com/site/tingox/asus_v7-p7h55e -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: how to access the SOL (Serial over Lan) port in FreeBSD ?
On Tue, 14 Dec 2010 20:35:50 +0100 Luigi Rizzo ri...@iet.unipi.it wrote: i recently bought two motherboards with Intel AMT support, a remote management tool which among other things implements Serial Over Lan (SOL) -- which seems to be accessible via TCP port 16994 I have enabled the feature in the bios and built a client And configured it? See http://linux.die.net/man/7/amt-howto I know nothing about AMT (yet), but it looks interesting. HTH -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Reproducible Kernel Panic on 8.1-STABLE [SEC=UNCLASSIFIED]
On Fri, 15 Oct 2010 16:27:51 +0200 Ivan Voras ivo...@freebsd.org wrote: How stable is fuse sshfs lately? It looks like every time in the past I tried it I soon ended up panicking the system. Well, I use sshfs routinely to copy data between my machines, and have done so for about a year. Mostly small files (like; oh I must get the documentation files / whatever for this from my main workstation), but I have also used it for backup of several terabytes of data. I connect and disconnect with sshfs all the time. Most machines run FreeBSD 7 / 8, mostly amd64 and a couple run Linux (Ubuntu). So far, very stable, and almost no problems. I think the bug mentioned in this thread hit me, but just once so far. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problem with security log
On Wed, 13 Oct 2010 01:17:58 -0700 Jeremy Chadwick free...@jdc.parodius.com wrote: There isn't a 100% reliable way to get rid of this problem. I've been harping about this for years (sorry to sound like a jerk, but this really is a major problem that keeps coming up and annoys users/admins to no end. Or the problem might not be so major, it only shows up on the mailing lists about every six months. So maybe those who have the problem learns how to live with it. If it was a major problem, the mailing lists would be flooded. Just my 0.02 eurocents. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problem with security log
On Thu, 14 Oct 2010 05:07:48 -0700 Jeremy Chadwick free...@jdc.parodius.com wrote: But I classify this problem as high/severe because it makes a mess of things at the worst time possible -- situations where you absolutely need reliable output due to the nature of the problem you're dealing with (debugging a kernel, figuring out how/why something broke in the kernel, devices complaining about issues, disks reporting problems, etc.). And that I can agree on; the problem is severe, and should be fixed. Hopefully that will happen someday. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: VirtualBox OpenSolaris guest
On Sun, 10 Oct 2010 16:41:39 +0200 Emil Smolenski am...@raisa.eu.org wrote: opera-10.61.6430 opera-linuxplugins-10.61.6430 linux-f10-flashplugin-10.1r85 Aha, I was missing opera-linuxplugins. Installed now, seems to be working fine. Very useful. Thanks! Have a nice sunday, everyone! -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ISDN4BSD removal (was: FreeBSD 6.4 and 8.0 EoLs coming soon)
This is straying a bit, but I think it is important: the only good measure of when a technology is too old, is when people (who use FreeBSD in this case) stop using it. On Fri, 08 Oct 2010 11:12:32 +0200 Oliver Brandmueller o...@e-gitt.net wrote: Maybe you don't really want to hear this, but... ISDN is a dying technology. Any time soon you won't get ISDN termination by your telecom provider anymore. If at all, theyll deliver S0 in your home while doing VoIP from that little box on your wall. I don't know how it works in other countries, but here (in Norway) it works like this: yes - ISDN technology is dying. However, like all other technologies that major telcos have invested a lot in, its death is very slow. Extremely slow in fact. It could very well be that ISDN will live five or ten years still here, simply because it doesn't cost too much to maintain, and there is no new technology to push the dying ISDN over the edge off the cliff. Why is this? Well, telcos here are investing in mobile technologies for phones. They are _not_ interested in (and do not invest significant money in) things like VoIP. In fact, major telcos here doesn't invest significant money in fibre cables. They only put as much money into it as they need to keep the competition at bay. So who is investing in VoIP and fibre cables here? Answer: the ISP's that doesn't have any large investments in traditional telco cables. Another thing about VoIP calls: have they solved the emergency call needs a location problem? Here (again: in Norway) they are still working out how to solve this: if you call emergency services (police, fire department, etc.) from yout VoIP number; how do the emergency center locate you? I mean; how do they know that you are at home, and not at say, a cabin half across the country? With old landlines, there is no problem; it is always installed at an address. Just my point of view. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ISDN4BSD removal
On Fri, 08 Oct 2010 18:22:40 +0200 Dimitry Andric d...@freebsd.org wrote: On 2010-10-08 18:12, Torfinn Ingolfsen wrote: Another thing about VoIP calls: have they solved the emergency call needs a location problem? Here (again: in Norway) they are still working out how to solve this: if you call emergency services (police, fire department, etc.) from yout VoIP number; how do the emergency center locate you? Ehm, you tell them? You have them on the phone. :) If you are in a state to tell them, yes of course you do. However, the situtation might mean that you aren't very coherent at all. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: How dhcp client can set its hostname properly on lease time
On Thu, 07 Oct 2010 21:37:52 +0900 Mamoru Iwaki 1wk...@gmail.com wrote: Are there good way for dhcp client to set its hostname properly on lease time? Well, you *can* have the dhcp client on FreeBSD send an identifier, and with that identifier the dhcp server can assign the client a static ip lease. If that static ip is registered in your local dns, you're all set. Doesn't work well if you use the client on another network who doesn't offer static ip's. YMMV. The following will be a possble workaround, but I'm wondering there can be a smart answer in FreeBSD itself. It is possible to resolve the hostname corresponding to a dhcp-delivered ip-address with a local name server. So, (1) resolve the corresponding hostname from the local name server, (2) set it as hostname, and (3) call them every time when dhcp lease is updated Isn't the proper way with dns to configure dynamic DNS updates, and allow the client to do that? HTH -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: wifi issues under -stable
On Wed, 22 Sep 2010 16:46:43 -0500 Jim Bryant kc5vdj.free...@gmail.com wrote: One (this one) has an intel pro wireless 3945ABG installed, which returns: wpi0: Intel(R) PRO/Wireless 3945ABG irq 18 at device 0.0 on pci6 wpi0: Driver Revision 20071127 wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0x). wpi0: could not allocate memory resource device_attach: wpi0 attach returned 6 and the broadcom used in the other does the exact same thing. I'm thinking that this isn't really a problem with the wifi, but may be a mini-pci-e issue. More likelely, it is ACPI-related. Simply put: many laptops have broken ACPI implementations. Other OS'es might have a workaround for them, but FreeBSD does not. Since almost none of todays' laptops work correctly with ACPI disabled, this is a major pain. (Some laptops overheat when ACPI is disbled, because of disabled thermal management). You can try to figure out if the problem is acpi-related with the following hint in /boot/loader.conf (but beware of thermal problems; don't run the laptop too long with acpi disabled): hint.acpi.0.disabled=1 does anyone know how to solve this problem? Well, if you can identify exactly where the problem is, you might be able to work around it. However, the task isn't easy. Sometimes, forcing IRQ routing might help (but at least in 7.x this only works with acpi disabled). Using other OS'es (Linux) to identify if they do something different with the resources (irq, memeory etc. for devices) migh help pointing out wherer the problem might be. However, you will be speninding some time comparing outputs from a FreeBSD verbose boot with the same information from Linux. (This thread reminds me that I should test FreeBSD 8.1 on my old Acer laptop, which have acpi problems, and haven't worked with 6.0 - 8.0.) -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ROOT MOUNT ERROR when booting from zfs
On Thu, 19 Aug 2010 14:33:11 +0200 Heinrich Rebehn reb...@ant.uni-bremen.de wrote: Hi all, i am getting the error message in $subject when trying to boot from zfs. I followed the instructions found in: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror Before posting all config details and asking what i might have done wrong: Is there any possibility to get a more detailed error message than just ROOT MOUNT ERROR? e.g. zpool not found | zpool could not be imported | illegal mount options | etc You have tried verbose boot? If not, try it and see if you get more information. -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.x grudges
On Wed, 07 Jul 2010 14:22:22 -0400 Mikhail T. mi+t...@aldan.algebra.com wrote: 9. The k8temp utility (installed by sysutils/k8temp http://www.freshports.org/sysutils/k8temp), which worked fine on both of my AMD-machines, no longer works on the Athlon one (still works on the Opteron-based server). In case you are not aware of it: amdtemp(4) performs the same function (more or less) as k8temp. HTH -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.x grudges
On Wed, 07 Jul 2010 12:34:55 -0700 Kevin Oberman ober...@es.net wrote: k8temp is for older AMD system running K8 cores. It has been mostly replaced with amdtemp which works on newer cores. I'm not sure if amdtemp will work on K8 cores, though. It does (amdtemp works on K8s): r...@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 7.3-STABLE FreeBSD 7.3-STABLE #8: Mon Apr 5 21:10:07 CEST 2010 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 r...@kg-quiet# sysctl hw.machine hw.machine: amd64 r...@kg-quiet# sysctl dev.amdtemp dev.amdtemp.0.%desc: AMD K8 Thermal Sensors dev.amdtemp.0.%driver: amdtemp dev.amdtemp.0.%parent: hostb4 dev.amdtemp.0.sensor0.core0: 45.0C dev.amdtemp.0.sensor0.core1: 46.0C dev.amdtemp.0.sensor1.core0: 46.0C dev.amdtemp.0.sensor1.core1: 46.0C HTH -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.x grudges
On Thu, 08 Jul 2010 00:20:56 +0200 Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: On Wed, 07 Jul 2010 12:34:55 -0700 Kevin Oberman ober...@es.net wrote: k8temp is for older AMD system running K8 cores. It has been mostly replaced with amdtemp which works on newer cores. I'm not sure if amdtemp will work on K8 cores, though. It does (amdtemp works on K8s): r...@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 7.3-STABLE FreeBSD 7.3-STABLE #8: Mon Apr 5 21:10:07 CEST 2010 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 r...@kg-quiet# sysctl hw.machine hw.machine: amd64 r...@kg-quiet# sysctl dev.amdtemp dev.amdtemp.0.%desc: AMD K8 Thermal Sensors dev.amdtemp.0.%driver: amdtemp dev.amdtemp.0.%parent: hostb4 dev.amdtemp.0.sensor0.core0: 45.0C dev.amdtemp.0.sensor0.core1: 46.0C dev.amdtemp.0.sensor1.core0: 46.0C dev.amdtemp.0.sensor1.core1: 46.0C I forgot a part: r...@kg-quiet# sysctl hw.model hw.model: AMD Athlon(tm) 64 Processor 3000+ -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD eats 169.254.x.x addressed packets
On Tue, 08 Jun 2010 14:30:49 -0400 Stephen Clark sclar...@earthlink.net wrote: Hmmm... how is not responding to pings associated with forwarding? See http://en.wikipedia.org/wiki/169.254 Link Local addresses are special. HTH -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: [8-STABLE] USB printer disconnecting when trying to print
On Fri, 21 May 2010 10:29:04 +0200 Thomas Gellekum thomas.gelle...@gmx.de wrote: echo hallo /dev/ulpt0 [...] Any ideas on how to debug this are welcome. Most of todays printers do NOT understand plain text, usually you need a driver which transforms whatever you want to print into the language the printer understands. See http://www.openprinting.org/printer/Brother/Brother-HL-1250 for more info. HTH -- Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Powerd and est / eist functionality
On Wed, 24 Mar 2010 18:04:51 -0700 John Long fb...@sstec.com wrote: I want to thank you very much for all the info you have provided. It has clued me into a much better understanding and I see that it is a big un-standard thing to monitor these functions. It seems that things are FYI: for (some) Asus boards thererb is als acpi_aiboost(4). -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Exchange ActiveSync account
On Thu, 25 Mar 2010 14:11:00 +0100 Jack Raats j...@jarasoft.net wrote: I have an Exchange ActiveSync account and I would like to get this mail on my freebsd 7.3-stable server. I donn't haven an imap or pop account, only the information of the activesync account. Can anyone give me a clue how to achieve this? From http://en.wikipedia.org/wiki/Activesync Activesync uses ActiveSync Exchange, a proprietary protocol, requiring other vendors to license the protocol to achieve compatibility. In other words; it might not be possible. HTH -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64
Update: Perhaps the problems I have with this machine[1] are related to the MB-455SPF[1] hard drive cage I am using. It has three power connectors, which distributes power to all five drives. The documentation doesn't say more about which ports gives power to which drives, but since it is always drive 2 and 3 in the cage (ata5 and 6) that I've had problems with, I rearranged power connections to the cage. We will see if that makes any difference. References: 1) http://sites.google.com/site/tingox/ga-ma74gm-s2h 2) http://www.icydock.com/product/mb455spf.html -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64
On Sat, 13 Mar 2010 08:38:48 -0800 Jeremy Chadwick free...@jdc.parodius.com wrote: That enclosure also doesn't state if it has a SAF-TE or SES-2 chip on it. It's impossible to tell from the photos since the metallic enclosure cover up the backplane. Unfortunately, the manual is very brief and lacks such technical details / specs. This is a very simple enclosure; I don't think it even has any sensors except for the fan and temperature sensors, which are available at the signal out connector on the backplane. If it does, such chips can/will yank devices off the bus when the chip considers the drive faulty. At least in the SCSI world with SES-2, Well, the manual states that this is a host function: quote 2.2 HDD FAIL system 2.2.1 This product can not provide the signal, unless the HOST supports this function. 2.2.2 If the Host can provide HDD fail signal, connect the cable to the HOST and to the backplane HDD FAIL 1 - 2 - 3 - 4 - 5. 2.2.3 When the HDD is damaged, the light will show in red. /quote There is a separate connector for HDD fail input signals on the backplane. There are also output signals for power, access for each drive. The only thing I have connected the backplane is power (3 connectors) and sata (5 connectors). Since each drive has its own sata connector there really shouldn't be any reason to disconnect drives, but I guess it is possible. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64
On Sat, 13 Mar 2010 09:47:22 -0800 Jeremy Chadwick free...@jdc.parodius.com wrote: How do you tune the thresholds for the temperature or fan? If they're DIP switches, then chances are SAF-TE or SES-2 aren't involved and it's probably just some cheap/generic logic chip that does the work. There is a switch for the temp. The fan can't be adjusted. Luckily it is quite quiet. Is it a 4-pin connector? If so, what the manual is (horribly) trying to document is probably an SGPIO connector. Nope, eight pin. I've scanned the manual and put it up at the page for the machine[1], in case anyone have a need for it. SGPIO is a 4-pin connector which connects a SATA/SAS enclosure to a SATA/SAS HBA (controller) so that the two have a direct way to signal that a disk has physically failed -- otherwise, the controller has to make guesses about the state of things, and timeouts can take a while. SGPIO can also be used to provide other things; it's a generic communication interface with an official specification. This one seems much more simple; one signal (two pins) per drive. References: 1) http://sites.google.com/site/tingox/ga-ma74gm-s2h -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64
On Sat, 06 Mar 2010 14:19:44 +0100 Torfinn Ingolfsen torf...@broadpark.no wrote: However, the storage pool is not: r...@kg-f2# zpool status storage pool: storage state: UNAVAIL status: One or more devices are faulted in response to IO failures. action: Make sure the affected devices are connected, then run 'zpool clear'. see: http://www.sun.com/msg/ZFS-8000-HC scrub: scrub completed after 0h0m with 0 errors on Fri Mar 5 18:36:17 2010 config: NAMESTATE READ WRITE CKSUM storage UNAVAIL 0 3 0 insufficient replicas raidz1UNAVAIL 0 0 0 insufficient replicas ad8 ONLINE 0 0 0 ad10REMOVED 0 0 0 ad12REMOVED 0 0 0 ad14ONLINE 0 0 0 ada0ONLINE 0 0 0 errors: 2 data errors, use '-v' for a list After a reboot, things look like this: r...@kg-f2# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 2: Master: ad4 SAMSUNG HD252HJ/1AC01118 SATA revision 2.x Slave: no device present ATA channel 3: Master: ad6 SAMSUNG HD252HJ/1AC01118 SATA revision 2.x Slave: no device present ATA channel 4: Master: ad8 SAMSUNG HD103SJ/1AJ100E4 SATA revision 2.x Slave: no device present ATA channel 5: Master: ad10 SAMSUNG HD103SJ/1AJ100E4 SATA revision 2.x Slave: no device present ATA channel 6: Master: ad12 SAMSUNG HD103SJ/1AJ100E4 SATA revision 2.x Slave: no device present ATA channel 7: Master: ad14 SAMSUNG HD103SJ/1AJ100E4 SATA revision 2.x Slave: no device present r...@kg-f2# zpool status storage pool: storage state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10ONLINE 0 0 0 ad12ONLINE 0 0 0 ad14ONLINE 0 0 0 ada0ONLINE 0 0 0 errors: No known data errors and after a scrub: r...@kg-f2# zpool scrub storage r...@kg-f2# zpool status storage pool: storage state: ONLINE scrub: scrub completed after 0h0m with 0 errors on Sun Mar 7 12:28:31 2010 config: NAMESTATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10ONLINE 0 0 0 ad12ONLINE 0 0 0 ad14ONLINE 0 0 0 ada0ONLINE 0 0 0 errors: No known data errors -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64
Ok, a new development in this story. Note that as of yet, I haven't change SATA cables or done anything else with the hardware. However, I did upgrade to latest FreeBSD 8.0-stable / amd64 yesterday. The machine is still up (it iahsn't crashed yet), and today I found this in /var/log/messages: Mar 6 06:25:34 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Mar 6 06:25:34 kg-f2 kernel: ata5: hardware reset timeout Mar 6 06:25:45 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Mar 6 06:25:45 kg-f2 kernel: ata6: hardware reset timeout Mar 6 06:25:45 kg-f2 root: ZFS: vdev failure, zpool=storage type=vdev.no_replicas Mar 6 06:25:56 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 0080 Mar 6 06:25:56 kg-f2 kernel: ata5: hardware reset timeout Mar 6 06:26:06 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Mar 6 06:26:06 kg-f2 kernel: ata6: hardware reset timeout Mar 6 06:26:08 kg-f2 root: ZFS: zpool I/O failure, zpool=storage error=28 Mar 6 06:26:08 kg-f2 last message repeated 2 times Mar 6 06:26:08 kg-f2 root: ZFS: vdev I/O failure, zpool=storage path= offset= size= error= Mar 6 06:26:16 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Mar 6 06:26:16 kg-f2 kernel: ata5: hardware reset timeout Mar 6 06:26:27 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Mar 6 06:26:27 kg-f2 kernel: ata6: hardware reset timeout Mar 6 06:26:37 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 0080 Mar 6 06:26:37 kg-f2 kernel: ata5: hardware reset timeout Mar 6 06:26:47 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Mar 6 06:26:47 kg-f2 kernel: ata6: hardware reset timeout Mar 6 06:26:58 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Mar 6 06:26:58 kg-f2 kernel: ata5: hardware reset timeout Mar 6 06:27:08 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 0080 Mar 6 06:27:08 kg-f2 kernel: ata6: hardware reset timeout Before the upgrade, messages such as these would (AFAICT) nresult on a panic and reboot. Uptime: r...@kg-f2# uptime 2:11PM up 19:38, 3 users, load averages: 0.00, 0.00, 0.00 The boot / root mirror pool is okay: r...@kg-f2# zpool status zroot pool: zroot state: ONLINE scrub: scrub completed after 0h8m with 0 errors on Fri Mar 5 18:45:24 2010 config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 errors: No known data errors However, the storage pool is not: r...@kg-f2# zpool status storage pool: storage state: UNAVAIL status: One or more devices are faulted in response to IO failures. action: Make sure the affected devices are connected, then run 'zpool clear'. see: http://www.sun.com/msg/ZFS-8000-HC scrub: scrub completed after 0h0m with 0 errors on Fri Mar 5 18:36:17 2010 config: NAMESTATE READ WRITE CKSUM storage UNAVAIL 0 3 0 insufficient replicas raidz1UNAVAIL 0 0 0 insufficient replicas ad8 ONLINE 0 0 0 ad10REMOVED 0 0 0 ad12REMOVED 0 0 0 ad14ONLINE 0 0 0 ada0ONLINE 0 0 0 errors: 2 data errors, use '-v' for a list Currently, this pool isn't in use, so I am not concerned about data loss (luckily). Note that before this upgrade, with all panics and reboots, both zfs pools have always been clean and trouble-free after a reboot. atacontrol confirms that ad10 and ad12 are gone (ie. disconnected: r...@kg-f2# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 2: Master: ad4 SAMSUNG HD252HJ/1AC01118 SATA revision 2.x Slave: no device present ATA channel 3: Master: ad6 SAMSUNG HD252HJ/1AC01118 SATA revision 2.x Slave: no device present ATA channel 4: Master: ad8 SAMSUNG HD103SJ/1AJ100E4 SATA revision 2.x Slave: no device present ATA channel 5: Master: no device present Slave: no device present ATA channel 6: Master: no device present Slave: no device present ATA channel 7: Master: ad14 SAMSUNG HD103SJ/1AJ100E4 SATA revision 2.x Slave: no device present What happens if I just rebot the server now? (I think that ad10 and ad12 will be detected and connected), but what will zfs do with the 'storage' pool? As always, more info (including verbose dmesgs etc.) on the FreeBSD page[1] for this machine. References: 1) FreeBSd on this machine: http://sites.google.com/site/tingox/ga-ma74gm-s2h_freebsd -- Torfinn ___ freebsd-stable@freebsd.org
Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64
On Sat, 20 Feb 2010 15:35:46 -0800 Jeremy Chadwick free...@jdc.parodius.com wrote: After five days - a new crash. From /var/log/messages: Feb 26 00:57:39 kg-f2 ntpd[55453]: kernel time sync status change 6001 Feb 26 01:39:40 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 26 01:39:40 kg-f2 kernel: ata5: hardware reset timeout Feb 26 10:44:54 kg-f2 syslogd: kernel boot file is /boot/kernel/kernel Let's backtrack a bit. I've gone back and read through all of your previous posts on this matter, and so far all the problems are happening on ata5 and ata6. No timeouts or anomalies have appeared on any other ports -- just those two. It seems you are right. The kernel error messages indicate that commands submit to the controller took longer than 10 seconds to get a response, so the OS does a force-reset of the ports in attempt to get things working again. We can safely rule out the Silicon Image controller (otherwise ataX wouldn't be involved), which leaves the AMD SB700 SATA controller and the AMD SB700 PATA controller. And there is nothing connected to the pata controller. What exact disks (e.g. adX) are attached to ata5 and ata6? r...@kg-f2# dmesg | grep ata5 ata5: ATA channel 3 on atapci0 ata5: [ITHREAD] ad10: 953869MB SAMSUNG HD103SJ 1AJ100E4 at ata5-master UDMA100 SATA 3Gb/s r...@kg-f2# dmesg | grep ata6 ata6: ATA channel 4 on atapci0 ata6: [ITHREAD] ad12: 953869MB SAMSUNG HD103SJ 1AJ100E4 at ata6-master UDMA100 SATA 3Gb/s You haven't provided dmesg output in any of your posts, No, I didn't. I did state that full dmesg's and more info was available on the freebsd web page[1] for the machine in one of my first posts. and atacontrol/pciconf is not sufficient (I should really improve atacontrol by printing this information. I'll work on that in a few minutes). Cool, I would really like that feature. Some Linux users have reported AHCI-related issues with the SB600 southbridge, but the core of the problem turned out to be MSI on certain AMD northbridges (specifically RS480, RS400, and RS200). By disabling MSI entirely they were able to achieve stability. The FreeBSD equivalent would be to set the following in loader.conf and reboot: hw.pci.enable_msix=0 hw.pci.enable_msi=0 I will try that now. It might take five days or more to get an answer. The Linux quirk fix for this: http://git.kernel.org/?p=linux/kernel/git/stable/stable-queue.git;a=blob_plain;f=queue-2.6.21/pci-quirks-disable-msi-on-rs400-200-and-rs480.patch;hb=05ab505f2909acf3a614d3e6a32271c4c1f8a69d Your board has an AMD 740G northbridge, but it might be worth trying the MSI disable trick anyway. If it doesn't fix the problem then definitely re-enable MSI. Isn't hardware fun? ;-) Always. ;^) References: 1) http://sites.google.com/site/tingox/ga-ma74gm-s2h_freebsd -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64
On Fri, 26 Feb 2010 11:03:37 +0100 Torfinn Ingolfsen torf...@broadpark.no wrote: I will try that now. It might take five days or more to get an answer. Or not. Another panic. Output from /var/log/messages: Feb 26 11:10:33 kg-f2 ntpd[942]: kernel time sync status change 2001 Feb 26 11:44:19 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 0080 Feb 26 11:44:19 kg-f2 kernel: ata5: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 26 11:47:05 kg-f2 kernel: ata6: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 26 11:47:05 kg-f2 kernel: ata5: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 26 11:47:05 kg-f2 kernel: ata6: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 26 11:47:05 kg-f2 kernel: ata5: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 0080 Feb 26 11:47:05 kg-f2 kernel: ata6: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 26 11:47:05 kg-f2 kernel: ata5: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 26 11:47:05 kg-f2 kernel: ata6: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 26 11:47:05 kg-f2 kernel: ata5: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 0080 Feb 26 11:47:05 kg-f2 kernel: ata6: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ad4: TIMEOUT - FLUSHCACHE48 retrying (1 retry left) Feb 26 11:47:05 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 26 11:47:05 kg-f2 kernel: ata5: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 26 11:47:05 kg-f2 kernel: ata6: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 0080 Feb 26 11:47:05 kg-f2 kernel: ata5: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 0080 Feb 26 11:47:05 kg-f2 kernel: ata6: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 0080 Feb 26 11:47:05 kg-f2 kernel: ata5: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 26 11:47:05 kg-f2 kernel: ata6: hardware reset timeout Feb 26 11:47:05 kg-f2 kernel: ad6: TIMEOUT - FLUSHCACHE48 retrying (1 retry left) Feb 26 11:47:05 kg-f2 kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=31471070 Feb 26 12:23:38 kg-f2 syslogd: kernel boot file is /boot/kernel/kernel -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ntpd struggling to keep up - how to fix?
On Mon, 22 Feb 2010 07:17:42 +1100 Peter Jeremy peterjer...@acm.org wrote: On 2010-Feb-21 17:36:19 +0100, Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: Over time (probably a couple of days from scratch), the poll rate should increase to 1024. If it doesn't, it may indicate that your Like so: r...@kg-f2# ntpq -p remote refid st t when poll reach delay offset jitter == *kg-omni1.kg4.no 192.121.13.583 u 564 1024 3770.1633.018 3.196 -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ntpd struggling to keep up - how to fix?
On Sun, 21 Feb 2010 16:08:23 +1100 Peter Jeremy peterjer...@acm.org wrote: That's definitely not good - though it's marginally better than before. I have checked on a local machine and the timecounter frequency definitely needs to be adjusted in the opposite direction to the ntpd drift. I think I see the problem: I suggested 3579545Hz - 2500ppm, which gives an ACPI frequency of 3570596Hz. There was some miscommunication and you have set an ACPI frequency of 3577045Hz which is 2500Hz (or 698ppm) lower. The drift reported by the time resets has gone from +1930ppm (14.5s in 2:05:17) to +1233ppm (8.4s in 2:20:06) - which is 697ppm - fairly close to the change you made. (The PLL is running at +500ppm so the actual clock offset is 500ppm more than the time reset reports suggest. Very good info, it helps me understand more. Thanks! Having re-checked my maths, using both your time reset results, can you please try: sysctl machdep.acpi_timer_freq=3570847 Ok, trying that now: r...@kg-f2# sysctl machdep.acpi_timer_freq=3570847 machdep.acpi_timer_freq: 3577045 - 3570847 r...@kg-f2# /etc/rc.d/ntpd stop Stopping ntpd. r...@kg-f2# rm /var/db/ntpd.drift r...@kg-f2# /etc/rc.d/ntpd start Starting ntpd. That should result in a drift of close to zero (well within NTP's lock range of +/- 300ppm). Good. No. Once ntpd decides to continuously step, something is broken. Aha, very good to know. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ntpd struggling to keep up - how to fix?
On Sun, 21 Feb 2010 16:08:23 +1100 Peter Jeremy peterjer...@acm.org wrote: Having re-checked my maths, using both your time reset results, can you please try: sysctl machdep.acpi_timer_freq=3570847 That should result in a drift of close to zero (well within NTP's lock range of +/- 300ppm). And a few hours later: from /var/log/messages: Feb 21 09:54:50 kg-f2 ntpd[55452]: ntpd 4.2.4p5-a (1) Feb 21 09:59:10 kg-f2 ntpd[55453]: kernel time sync status change 2001 More info: r...@kg-f2# ntpq -p remote refid st t when poll reach delay offset jitter == *kg-omni1.kg4.no 78.157.115.4 3 u 31 64 3770.174 -10.253 0.160 r...@kg-f2# ntpdc -c loopi -c sysi offset: -0.010253 s frequency:6.744 ppm poll adjust: -30 watchdog timer: 47 s system peer: kg-omni1.kg4.no system peer mode: client leap indicator: 00 stratum: 4 precision:-18 root distance:0.02956 s root dispersion: 0.06795 s reference ID: [10.1.10.1] reference time: cf2bdf36.f8820aef Sun, Feb 21 2010 17:35:02.970 system flags: auth monitor ntp kernel stats jitter: 0.000153 s stability:0.000 ppm broadcastdelay: 0.003998 s authdelay:0.00 s Problem solved. Thanks a lot. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ntpd struggling to keep up - how to fix?
On Sat, 20 Feb 2010 12:53:51 +1100 Peter Jeremy peterjer...@acm.org wrote: Looks reasonable. Let us know the results. I'd be interested in the output from ntpdc -c loopi -c sysi. Ok, here we go (the server panic'ed again last night): r...@kg-f2# uptime 10:28PM up 2:26, 3 users, load averages: 0.00, 0.00, 0.00 r...@kg-f2# sysctl machdep.acpi_timer_freq machdep.acpi_timer_freq: 3577045 r...@kg-f2# tvlm Feb 20 20:06:41 kg-f2 ntpd[942]: kernel time sync status change 2001 Feb 20 20:21:49 kg-f2 ntpd[942]: time reset +1.118880 s Feb 20 20:37:53 kg-f2 ntpd[942]: time reset +1.188538 s Feb 20 20:53:03 kg-f2 ntpd[942]: time reset +1.121903 s Feb 20 21:09:00 kg-f2 ntpd[942]: time reset +1.179924 s Feb 20 21:24:57 kg-f2 ntpd[942]: time reset +1.178490 s Feb 20 21:39:58 kg-f2 ntpd[942]: time reset +1.110647 s Feb 20 21:55:53 kg-f2 ntpd[942]: time reset +1.177292 s Feb 20 22:11:44 kg-f2 ntpd[942]: time reset +1.172358 s Feb 20 22:26:48 kg-f2 ntpd[942]: time reset +1.114350 s r...@kg-f2# ntpq -p remote refid st t when poll reach delay offset jitter == kg-omni1.kg4.no 129.240.64.3 3 u8 6470.176 133.306 77.731 r...@kg-f2# ntpdc -c loopi -c sysi offset: 0.00 s frequency:500.000 ppm poll adjust: 4 watchdog timer: 194 s system peer: 0.0.0.0 system peer mode: unspec leap indicator: 11 stratum: 16 precision:-18 root distance:0.0 s root dispersion: 0.00290 s reference ID: [83.84.69.80] reference time: . Thu, Feb 7 2036 7:28:16.000 system flags: auth monitor ntp kernel stats jitter: 0.358109 s stability:0.000 ppm broadcastdelay: 0.003998 s authdelay:0.00 s Not synced at all. Not good. :-/ Perhaps I should give it more time? -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64
On Sat, 20 Feb 2010 11:37:18 -0800 Jeremy Chadwick free...@jdc.parodius.com wrote: Can you re-run smartctl -a instead of -H? Some of the SMART attributes may help determine what's going on, or there may be related errors in the SMART error log. smartctl -a output attached. Test sequence: ad4 - ad12, ada0. Otherwise I'd say what's happening is a SATA controller lock-up of some sort, since it happens on any of your channels. Could be a quirk of some kind in the SATA-CAM stuff (unless it also happens when using pure ata(4)). I am running a quite recent 8.0-stable: r...@kg-f2# uname -a FreeBSD kg-f2.kg4.no 8.0-STABLE FreeBSD 8.0-STABLE #2: Sun Jan 31 18:39:17 CET 2010 r...@kg-f2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 Perhaps I should upgrade. What controller are these disks hooked to again? Six of the disks (ad4, ad6, ad8, ad10, ad12) are connected to the SATA ports on the motherboard: r...@kg-f2# pciconf -lv | grep ata -A 4 atap...@pci0:0:17:0:class=0x010601 card=0xb0021458 chip=0x43911002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'SB700 SATA Controller [AHCI mode]' class = mass storage subclass = SATA -- atap...@pci0:0:20:1:class=0x01018a card=0x50021458 chip=0x439c1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'PATA 133 Controller (SB7xx)' class = mass storage subclass = ATA (There is nothing connected to the PATA ports). The last disk (ada0) is connected to a PCI card: o...@kg-f2# pciconf -lv | grep siis -A 3 si...@pci0:2:0:0: class=0x018000 card=0x35311095 chip=0x35311095 rev=0x01 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'SiI 3531 SATA Controller' class = mass storage Hardware info about the machine here: http://sites.google.com/site/tingox/ga-ma74gm-s2h HTH -- Torfinn smartctl 5.39 2009-12-09 r2995 [FreeBSD 8.0-STABLE amd64] (local build) Copyright (C) 2002-9 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint F1 DT series Device Model: SAMSUNG HD252HJ Serial Number:S17HJ9BSA04283 Firmware Version: 1AC01118 User Capacity:250,059,350,016 bytes Device is:In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is:Sat Feb 20 22:44:11 2010 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (3651) seconds. Offline data collection capabilities:(0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 62) minutes. Conveyance self-test routine recommended polling time:( 8) minutes. SCT capabilities: (0x003f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 051Pre-fail Always - 0 3 Spin_Up_Time0x0007 092 092 011Pre-fail Always - 3260 4 Start_Stop_Count0x0032 100
Re: ntpd struggling to keep up - how to fix?
On Sat, 20 Feb 2010 22:32:01 +0100 Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: This output looks ... wrong ... somehow to my eyes: r...@kg-f2# date Sat Feb 20 22:51:24 CET 2010 r...@kg-f2# ntpq -p remote refid st t when poll reach delay offset jitter == *kg-omni1.kg4.no 129.240.64.3 3 u 62 64 3770.244 597.314 360.123 r...@kg-f2# ntpdc -c loopi -c sysi offset: 0.00 s frequency:500.000 ppm poll adjust: 4 watchdog timer: 549 s system peer: kg-omni1.kg4.no system peer mode: client leap indicator: 11 stratum: 16 precision:-18 root distance:0.0 s root dispersion: 0.00822 s reference ID: [10.1.10.1] reference time: . Thu, Feb 7 2036 7:28:16.000 system flags: auth monitor ntp kernel stats jitter: 0.360107 s stability:0.000 ppm broadcastdelay: 0.003998 s authdelay:0.00 s Shouldn't ntpq and ntpdc be in agreement? -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ntpd struggling to keep up - how to fix?
On Fri, 19 Feb 2010 07:54:58 +1100 Peter Jeremy peterjer...@acm.org wrote: On 2010-Feb-17 20:03:22 +0100, Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: Did you delete /etc/ntp.drift between timecounter changes? I sure did, I used the instructions given. There's ntptime(8) but it doesn't have a self-calibrate mode. Ok, good to know. Based on the messages log you gave, and assuming the ntpd PLL is sane, your acpi-safe clock is about 2500ppm slow (the steps reflect about 2000ppm and the ntpd PLL should be compensating for a further 500ppm) - this is really bad, even for consumer-grade stuff. Are you running non-standard clock speeds or multipliers? No, everything at default values here (ie. I haven't changed anything in either BIOS or FreeBSD), except from changing timer from HPET to ACPI-safe. If there's nothing obvious, I'd follow John Hay's suggesion and force set either your TSC or ACPI frequency in sysctl.conf (you can't override the HPET frequency). Take either the TSC or ACPI frequency reported by sysctl machdep, reduce it by 2500ppm and set that in /etc/sysctl.conf. Assuming a standard (3.58MHz) ACPI, the latter would look like: machdep.acpi_timer_freq=3570596 This one is r...@kg-f2# sysctl machdep.acpi_timer_freq machdep.acpi_timer_freq: 3579545 So I should change that to 3577045, right? Like so: r...@kg-f2# sysctl machdep.acpi_timer_freq=3579545 machdep.acpi_timer_freq: 3579545 - 3579545 and I put it into /etc/sysctl.conf as well (in case the machine reboots again). kern.timecounter.hardware=ACPI-safe Yes, this is already in /etc/sysctl.conf The stop ntpd, delete /var/db/ntp.drift and either reboot or manually set the above sysctl's and restart ntpd. Done. We'll see if it works or not. [I think I've got the adjustment direction correct in the above, if I've stuffed up, you need to adjust in the other direction] Ok. Thanks to all for helping out. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ntpd struggling to keep up - how to fix?
On Thu, 18 Feb 2010 23:12:23 +0100 Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: So I should change that to 3577045, right? Like so: r...@kg-f2# sysctl machdep.acpi_timer_freq=3579545 machdep.acpi_timer_freq: 3579545 - 3579545 Eh... I just realized that I did it wrong. well, that's what cut and paste will do to you, if you don't pay attention. ;) Ok, I will try to do it right now: r...@kg-f2# sysctl machdep.acpi_timer_freq=3577045 machdep.acpi_timer_freq: 3579545 - 3577045 r...@kg-f2# /etc/rc.d/ntpd stop Stopping ntpd. r...@kg-f2# ll /var/db/ntp* -rw-r--r-- 1 root wheel 8 Feb 13 20:27 /var/db/ntpd.drift r...@kg-f2# rm /var/db/ntpd.drift r...@kg-f2# ll /var/db/ntp* ls: /var/db/ntp*: No such file or directory r...@kg-f2# /etc/rc.d/ntpd start Starting ntpd. and fixing it in /etc/sysctl.conf too. Done. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64
Another crash last night. In /var/log/messages: Feb 16 23:13:22 kg-f2 ntpd[2826]: time reset +1.780863 s Feb 16 23:16:42 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:16:42 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 0080 Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=65614674 Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 0080 Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 0080 Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=65614674 Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 007f Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 0080 Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ad6: WARNING - WRITE_DMA requeued due to channel reset LBA=65614674 Feb 16 23:20:39 kg-f2 kernel: ata3: FAILURE - already active DMA on this device Feb 16 23:20:39 kg-f2 kernel: ata3: setting up DMA failed Feb 16 23:20:39 kg-f2 kernel: ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=8389026 Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 0080 Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout Feb 16 23:20:39 kg-f2 kernel: ad4: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=65614674 Feb 16 23:20:39 kg-f2 kernel: ad6: TIMEOUT - READ_DMA retrying (0 retries left) LBA=8389026 Feb 16 23:20:39 kg-f2 root: ZFS: vdev I/O failure, zpool=zroot path=/dev/gpt/disk1 offset=29299662848 size=4096 error=5 Feb 17 09:09:40 kg-f2 syslogd: kernel boot file is /boot/kernel/kernel But ad4 and ad6 are the two disk mirrir (zfs) that I have built my root filesystem on. Hmm. -- Torfinn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
