FreeBSD stuck during the boot process.
Hi there!! When I try to boot FreeBSD from a USB stick, it stuck during the boot process. But if I boot it in safe mode, it succeeds to boot. How can I figure out what's wrong with the standard boot process? I can't even log the boot messages since the computer stuck and not respond. Thanks in advance!! Atar. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD stuck during the boot process.
On Tue, 17 Sep 2013 12:15:58 +0300, Atar wrote: When I try to boot FreeBSD from a USB stick, it stuck during the boot process. But if I boot it in safe mode, it succeeds to boot. How can I figure out what's wrong with the standard boot process? I can't even log the boot messages since the computer stuck and not respond. You could try a verbose boot (equivalent: boot -v) and see _when_ the system stops resonding. It would help to post the error message (last lines of console output) to the list to get a better impression about what's happening. If I remember correctly, safe mode refers to the mode with ACPI disabled, right? In this case, it _could_ be an ACPI problem (a really wild guess, as you have provided no information about the system you are trying to boot FreeBSD on). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD stuck during the boot process.
On Tue, Sep 17, 2013 at 9:47 AM, atar atar.yo...@gmail.com wrote: Polytropon free...@edvax.de wrote: On Tue, 17 Sep 2013 12:15:58 +0300, Atar wrote: When I try to boot FreeBSD from a USB stick, it stuck during the boot process. But if I boot it in safe mode, it succeeds to boot. Yes, you remember correctly, safe mode disable the ACPI support automatically. The problem may also be that USB devices take a long time to settle. I suggest these in your /boot/loader.conf hint.acpi.0.disabled=1 kern.cam.boot_delay=1 kern.cam.scsi_delay=2000 The CAM boot delay is needed for USB booting on some of my machines, esp. Soekris boxes. 10 seconds is safe. - M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD stuck during the boot process.
Polytropon free...@edvax.de wrote: On Tue, 17 Sep 2013 12:15:58 +0300, Atar wrote: When I try to boot FreeBSD from a USB stick, it stuck during the boot process. But if I boot it in safe mode, it succeeds to boot. How can I figure out what's wrong with the standard boot process? I can't even log the boot messages since the computer stuck and not respond. You could try a verbose boot (equivalent: boot -v) and see _when_ the system stops resonding. It would help to post the error message (last lines of console output) to the list to get a better impression about what's happening. If I remember correctly, safe mode refers to the mode with ACPI disabled, right? In this case, it _could_ be an ACPI problem (a really wild guess, as you have provided no information about the system you are trying to boot FreeBSD on). Thanks for replying!! Yes, you remember correctly, safe mode disable the ACPI support automatically. I think it's a problem in the ACPI system because when I disable ACPI, it boot successfully even without choosing safe mode. But what that is strange here, is that Microsoft Windows and Linux (Debian) are able to boot with ACPI enabled. furthermore, some days ago FreeBSD itself succeeded to boot also with ACPI support enabled. As for the error messages, there's not a particular error message. it simply stuck during the initialization of the PCI bus. Here are the last eight lines: pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pcib2: domain 0 pcib2: secondary bus2 pcib2: subordinate bus 2 pcib2: no prefetched decode pcib2 Subtractively decoded bridge. pcib2: ACPI PCI bus on pcib2 pcib2: domain=0, physical bus=2 Regards, atar. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
poudriere: Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers.
Hi, I having trouble using poudriere since updating it to 3.0.4 on FreeBSD 9.1-p4. Trying poudriere-devel throws the same error. Here is the complete output of trying to compile shells/bash: # poudriere bulk -p hostportstree -f /usr/local/etc/poudriere.d/91amd64-buildlist.conf -j 91amd64 -J 1 -vv Creating the reference jail... done Mounting system devices for 91amd64-hostportstree Mounting ports/packages/distfiles Mounting packages from: /mnt/system/DATEN/poudriere/basefs/data/packages/91amd64-hostportstree Mounting /var/db/ports from: /usr/local/etc/poudriere.d/options Logs: /mnt/system/DATEN/poudriere/basefs/data/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s WWW: http://pkg.cbt-l.de/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s Appending to make.conf: /usr/local/etc/poudriere.d/make.conf /etc/resolv.conf - /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/etc/resolv.conf Starting jail 91amd64-hostportstree Calculating ports order and dependencies Computing deps for shells/bash DEBUG: shells/bash depends on ports-mgmt/pkg Computing deps for ports-mgmt/pkg DEBUG: shells/bash depends on devel/bison Computing deps for devel/bison DEBUG: devel/bison depends on ports-mgmt/pkg DEBUG: devel/bison depends on devel/m4 Computing deps for devel/m4 DEBUG: devel/m4 depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 Computing deps for lang/perl5.14 DEBUG: lang/perl5.14 depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 DEBUG: devel/bison depends on devel/gettext Computing deps for devel/gettext DEBUG: devel/gettext depends on ports-mgmt/pkg DEBUG: devel/gettext depends on converters/libiconv Computing deps for converters/libiconv DEBUG: converters/libiconv depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 DEBUG: devel/bison depends on devel/m4 DEBUG: shells/bash depends on devel/gettext DEBUG: shells/bash depends on converters/libiconv pkg package missing, skipping sanity Cleaning the build queue Building 7 packages using 1 builders Starting/Cloning builders mount: linprocfs: File name too long Hit CTRL+t at any time to see build progress and stats [01] Starting build of ports-mgmt/pkg make: chdir /usr/ports/ports-mgmt/pkg: No such file or directory Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers. /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/building /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/9 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/8 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/7 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/6 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/5 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/4 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/3 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/2 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/0 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/unbalanced /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/pkg-1.1.4_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/bison-2.7.1,1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/gettext-0.18.3 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/libiconv-1.14_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1/pkg-1.1.4_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1/m4-1.4.16_1,1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1/perl-5.14.4 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1/gettext-0.18.3 /mnt/system/DATEN/poudriere/basefs/data/build
Re: poudriere: Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers.
On 7/23/2013 8:36 AM, Wolfgang Riegler wrote: Hi, I having trouble using poudriere since updating it to 3.0.4 on FreeBSD 9.1-p4. Trying poudriere-devel throws the same error. Here is the complete output of trying to compile shells/bash: # poudriere bulk -p hostportstree -f /usr/local/etc/poudriere.d/91amd64-buildlist.conf -j 91amd64 -J 1 -vv Creating the reference jail... done Mounting system devices for 91amd64-hostportstree Mounting ports/packages/distfiles Mounting packages from: /mnt/system/DATEN/poudriere/basefs/data/packages/91amd64-hostportstree Mounting /var/db/ports from: /usr/local/etc/poudriere.d/options Logs: /mnt/system/DATEN/poudriere/basefs/data/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s WWW: http://pkg.cbt-l.de/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s Appending to make.conf: /usr/local/etc/poudriere.d/make.conf /etc/resolv.conf - /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/etc/resolv.conf Starting jail 91amd64-hostportstree Calculating ports order and dependencies Computing deps for shells/bash DEBUG: shells/bash depends on ports-mgmt/pkg Computing deps for ports-mgmt/pkg DEBUG: shells/bash depends on devel/bison Computing deps for devel/bison DEBUG: devel/bison depends on ports-mgmt/pkg DEBUG: devel/bison depends on devel/m4 Computing deps for devel/m4 DEBUG: devel/m4 depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 Computing deps for lang/perl5.14 DEBUG: lang/perl5.14 depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 DEBUG: devel/bison depends on devel/gettext Computing deps for devel/gettext DEBUG: devel/gettext depends on ports-mgmt/pkg DEBUG: devel/gettext depends on converters/libiconv Computing deps for converters/libiconv DEBUG: converters/libiconv depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 DEBUG: devel/bison depends on devel/m4 DEBUG: shells/bash depends on devel/gettext DEBUG: shells/bash depends on converters/libiconv pkg package missing, skipping sanity Cleaning the build queue Building 7 packages using 1 builders Starting/Cloning builders mount: linprocfs: File name too long Hit CTRL+t at any time to see build progress and stats [01] Starting build of ports-mgmt/pkg make: chdir /usr/ports/ports-mgmt/pkg: No such file or directory Does ports-mgmt/pkg exist in the ports tree you are using? Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers. /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/building /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/9 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/8 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/7 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/6 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/5 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/4 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/3 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/2 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/0 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/unbalanced /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/pkg-1.1.4_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/bison-2.7.1,1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/gettext-0.18.3 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/libiconv-1.14_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1/pkg-1.1.4_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1/m4-1.4.16_1,1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison
Re: poudriere: Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers.
yes, there is /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/usr/ports/ports-mgmt/pkg/ regards Wolfgang Am Dienstag, 23. Juli 2013, 08:48:38 schrieb Bryan Drewery: On 7/23/2013 8:36 AM, Wolfgang Riegler wrote: Hi, I having trouble using poudriere since updating it to 3.0.4 on FreeBSD 9.1-p4. Trying poudriere-devel throws the same error. Here is the complete output of trying to compile shells/bash: # poudriere bulk -p hostportstree -f /usr/local/etc/poudriere.d/91amd64-buildlist.conf -j 91amd64 -J 1 -vv Creating the reference jail... done Mounting system devices for 91amd64-hostportstree Mounting ports/packages/distfiles Mounting packages from: /mnt/system/DATEN/poudriere/basefs/data/packages/91amd64-hostportstree Mounting /var/db/ports from: /usr/local/etc/poudriere.d/options Logs: /mnt/system/DATEN/poudriere/basefs/data/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s WWW: http://pkg.cbt-l.de/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s Appending to make.conf: /usr/local/etc/poudriere.d/make.conf /etc/resolv.conf - /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/etc/resolv.conf Starting jail 91amd64-hostportstree Calculating ports order and dependencies Computing deps for shells/bash DEBUG: shells/bash depends on ports-mgmt/pkg Computing deps for ports-mgmt/pkg DEBUG: shells/bash depends on devel/bison Computing deps for devel/bison DEBUG: devel/bison depends on ports-mgmt/pkg DEBUG: devel/bison depends on devel/m4 Computing deps for devel/m4 DEBUG: devel/m4 depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 Computing deps for lang/perl5.14 DEBUG: lang/perl5.14 depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 DEBUG: devel/bison depends on devel/gettext Computing deps for devel/gettext DEBUG: devel/gettext depends on ports-mgmt/pkg DEBUG: devel/gettext depends on converters/libiconv Computing deps for converters/libiconv DEBUG: converters/libiconv depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 DEBUG: devel/bison depends on devel/m4 DEBUG: shells/bash depends on devel/gettext DEBUG: shells/bash depends on converters/libiconv pkg package missing, skipping sanity Cleaning the build queue Building 7 packages using 1 builders Starting/Cloning builders mount: linprocfs: File name too long Hit CTRL+t at any time to see build progress and stats [01] Starting build of ports-mgmt/pkg make: chdir /usr/ports/ports-mgmt/pkg: No such file or directory Does ports-mgmt/pkg exist in the ports tree you are using? Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers. /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/building /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/9 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/8 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/7 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/6 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/5 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/4 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/3 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/2 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/0 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/unbalanced /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/pkg-1.1.4_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/bison-2.7.1,1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/gettext-0.18.3 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/libiconv-1.14_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1 /mnt/system/DATEN/poudriere/basefs/data/build
Re: poudriere: Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers.
On 7/23/2013 9:00 AM, Wolfgang Riegler wrote: yes, there is /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/usr/ports/ports-mgmt/pkg/ Can you try with NOLINUX=yes in your poudriere.conf? regards Wolfgang Am Dienstag, 23. Juli 2013, 08:48:38 schrieb Bryan Drewery: On 7/23/2013 8:36 AM, Wolfgang Riegler wrote: Hi, I having trouble using poudriere since updating it to 3.0.4 on FreeBSD 9.1-p4. Trying poudriere-devel throws the same error. Here is the complete output of trying to compile shells/bash: # poudriere bulk -p hostportstree -f /usr/local/etc/poudriere.d/91amd64-buildlist.conf -j 91amd64 -J 1 -vv Creating the reference jail... done Mounting system devices for 91amd64-hostportstree Mounting ports/packages/distfiles Mounting packages from: /mnt/system/DATEN/poudriere/basefs/data/packages/91amd64-hostportstree Mounting /var/db/ports from: /usr/local/etc/poudriere.d/options Logs: /mnt/system/DATEN/poudriere/basefs/data/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s WWW: http://pkg.cbt-l.de/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s Appending to make.conf: /usr/local/etc/poudriere.d/make.conf /etc/resolv.conf - /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/etc/resolv.conf Starting jail 91amd64-hostportstree Calculating ports order and dependencies Computing deps for shells/bash DEBUG: shells/bash depends on ports-mgmt/pkg Computing deps for ports-mgmt/pkg DEBUG: shells/bash depends on devel/bison Computing deps for devel/bison DEBUG: devel/bison depends on ports-mgmt/pkg DEBUG: devel/bison depends on devel/m4 Computing deps for devel/m4 DEBUG: devel/m4 depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 Computing deps for lang/perl5.14 DEBUG: lang/perl5.14 depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 DEBUG: devel/bison depends on devel/gettext Computing deps for devel/gettext DEBUG: devel/gettext depends on ports-mgmt/pkg DEBUG: devel/gettext depends on converters/libiconv Computing deps for converters/libiconv DEBUG: converters/libiconv depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 DEBUG: devel/bison depends on devel/m4 DEBUG: shells/bash depends on devel/gettext DEBUG: shells/bash depends on converters/libiconv pkg package missing, skipping sanity Cleaning the build queue Building 7 packages using 1 builders Starting/Cloning builders mount: linprocfs: File name too long Hit CTRL+t at any time to see build progress and stats [01] Starting build of ports-mgmt/pkg make: chdir /usr/ports/ports-mgmt/pkg: No such file or directory Does ports-mgmt/pkg exist in the ports tree you are using? Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers. /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/building /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/9 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/8 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/7 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/6 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/5 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/4 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/3 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/2 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/0 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/unbalanced /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/pkg-1.1.4_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/bison-2.7.1,1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/gettext-0.18.3 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/libiconv-1.14_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bison-2.7.1,1 /mnt/system/DATEN
Re: poudriere: Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers.
Running poudriere with NO_LINUX=yes in poudriere.conf seems to work. Because I using FreeBSD as a desktop system as well. I need some linux ports. Any chance for it? thanks regards Wolfgang Am Dienstag, 23. Juli 2013, 09:12:13 schrieb Bryan Drewery: On 7/23/2013 9:00 AM, Wolfgang Riegler wrote: yes, there is /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/usr/ports/ports-mgmt/pkg/ Can you try with NOLINUX=yes in your poudriere.conf? regards Wolfgang Am Dienstag, 23. Juli 2013, 08:48:38 schrieb Bryan Drewery: On 7/23/2013 8:36 AM, Wolfgang Riegler wrote: Hi, I having trouble using poudriere since updating it to 3.0.4 on FreeBSD 9.1-p4. Trying poudriere-devel throws the same error. Here is the complete output of trying to compile shells/bash: # poudriere bulk -p hostportstree -f /usr/local/etc/poudriere.d/91amd64-buildlist.conf -j 91amd64 -J 1 -vv Creating the reference jail... done Mounting system devices for 91amd64-hostportstree Mounting ports/packages/distfiles Mounting packages from: /mnt/system/DATEN/poudriere/basefs/data/packages/91amd64-hostportstree Mounting /var/db/ports from: /usr/local/etc/poudriere.d/options Logs: /mnt/system/DATEN/poudriere/basefs/data/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s WWW: http://pkg.cbt-l.de/logs/bulk/91amd64-hostportstree/2013-07-23_14h06m33s Appending to make.conf: /usr/local/etc/poudriere.d/make.conf /etc/resolv.conf - /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/etc/resolv.conf Starting jail 91amd64-hostportstree Calculating ports order and dependencies Computing deps for shells/bash DEBUG: shells/bash depends on ports-mgmt/pkg Computing deps for ports-mgmt/pkg DEBUG: shells/bash depends on devel/bison Computing deps for devel/bison DEBUG: devel/bison depends on ports-mgmt/pkg DEBUG: devel/bison depends on devel/m4 Computing deps for devel/m4 DEBUG: devel/m4 depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 Computing deps for lang/perl5.14 DEBUG: lang/perl5.14 depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 DEBUG: devel/bison depends on devel/gettext Computing deps for devel/gettext DEBUG: devel/gettext depends on ports-mgmt/pkg DEBUG: devel/gettext depends on converters/libiconv Computing deps for converters/libiconv DEBUG: converters/libiconv depends on ports-mgmt/pkg DEBUG: devel/bison depends on lang/perl5.14 DEBUG: devel/bison depends on devel/m4 DEBUG: shells/bash depends on devel/gettext DEBUG: shells/bash depends on converters/libiconv pkg package missing, skipping sanity Cleaning the build queue Building 7 packages using 1 builders Starting/Cloning builders mount: linprocfs: File name too long Hit CTRL+t at any time to see build progress and stats [01] Starting build of ports-mgmt/pkg make: chdir /usr/ports/ports-mgmt/pkg: No such file or directory Does ports-mgmt/pkg exist in the ports tree you are using? Error: Unknown stuck queue bug detected. Please submit the entire build output to poudriere developers. /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/building /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/9 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/8 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/7 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/6 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/5 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/4 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/3 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/2 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/0 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/pool/unbalanced /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/pkg-1.1.4_1 /mnt/system/DATEN/poudriere/basefs/data/build/91amd64-hostportstree/ref/poudriere/deps/bash-4.2.45/bison-2.7.1,1 /mnt
Re: Xorg got stuck sometimes
On 20/11/2012 19:18, Hooman Oroojeni wrote: Try to rebuild Xorg with WITHOUT_NOUVEAU. That maybe helpfull. Cheers On Tue, Nov 20, 2012 at 5:38 PM, David Demelier demelier.da...@gmail.com mailto:demelier.da...@gmail.com wrote: Hi there, Sometimes, Xorg got stuck but I can't reproduce it always. When it appears, Xorg just stop being usable and mouse / keyboard can't be used also, switching to tty does not work at all and the screen is frozen. But I still can use ssh to connect the broken host and shutdown it normally, Xorg will use 100% of CPU when it breaks like this. I noticed this message when it appears : EQ overflowing. The server is probably stuck in an infinite loop. I'm using the nvidia nvidia-driver-304.64 on FreeBSD 9.1-RC3 Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailto:freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org mailto:freebsd-questions-unsubscr...@freebsd.org -- It appeared again, without doing much stuff but I can get these message from kernel when it appeared : NVRM: GPU at :01:00: GPU-a259b0bd-20f2-e5b9-681f-848cadfd1d79 NVRM: Xid (:01:00): 8, Channel 0001 I need to find a solution, if not I will need to remove FreeBSD and switch back to Linux, thing I don't want to. Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg got stuck sometimes
On 20/11/2012 20:11, David Demelier wrote: On 20/11/2012 19:18, Hooman Oroojeni wrote: Try to rebuild Xorg with WITHOUT_NOUVEAU. That maybe helpfull. Cheers On Tue, Nov 20, 2012 at 5:38 PM, David Demelier demelier.da...@gmail.com mailto:demelier.da...@gmail.com wrote: Hi there, Sometimes, Xorg got stuck but I can't reproduce it always. When it appears, Xorg just stop being usable and mouse / keyboard can't be used also, switching to tty does not work at all and the screen is frozen. But I still can use ssh to connect the broken host and shutdown it normally, Xorg will use 100% of CPU when it breaks like this. I noticed this message when it appears : EQ overflowing. The server is probably stuck in an infinite loop. I'm using the nvidia nvidia-driver-304.64 on FreeBSD 9.1-RC3 Cheers, -- David Demelier _ freebsd-questions@freebsd.org mailto:freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/__mailman/listinfo/freebsd-__questions http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-__unsubscr...@freebsd.org mailto:freebsd-questions-unsubscr...@freebsd.org -- WITHOUT_NOUVEAU is already in my make.conf.. Cheers, Let see if the 310.19 version will clear the problem, by the way why this version is not in the ports yet, because of the ports freeze? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg got stuck sometimes
On 20/11/2012 19:18, Hooman Oroojeni wrote: Try to rebuild Xorg with WITHOUT_NOUVEAU. That maybe helpfull. Cheers On Tue, Nov 20, 2012 at 5:38 PM, David Demelier demelier.da...@gmail.com mailto:demelier.da...@gmail.com wrote: Hi there, Sometimes, Xorg got stuck but I can't reproduce it always. When it appears, Xorg just stop being usable and mouse / keyboard can't be used also, switching to tty does not work at all and the screen is frozen. But I still can use ssh to connect the broken host and shutdown it normally, Xorg will use 100% of CPU when it breaks like this. I noticed this message when it appears : EQ overflowing. The server is probably stuck in an infinite loop. I'm using the nvidia nvidia-driver-304.64 on FreeBSD 9.1-RC3 Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailto:freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org mailto:freebsd-questions-unsubscr...@freebsd.org -- Finally, it seems to be flash player the problem, just removed from firefox plugin and no problem anymore. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bash pipe redirection gets stuck
long at rule.lv writes: Dear all, I stumbled upon a problem where multiple pipe redirection occasionally get stuck when trying to get sha256 sum of a stream. You can try to reproduce the problem if you have /usr/ports/shells/bash installed (output redirection used in this command is possible only in bash). Create temporary test file with command: dd if=/dev/urandom of=/tmp/file1 bs=1k count=10 And the command I'm using is: /usr/local/bin/bash -c 'cat /tmp/file1 | tee (/sbin/sha256 /tmp/file1.sha256) /tmp/file1.copy' ; echo $status I could reproduce it on FreeBSD 9.0-RELEASE-p3 on 3rd try, but after upgrade of bash-4.1.11 to bash-4.2.37 it works (tested 30 times). jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
bash pipe redirection gets stuck
Dear all, I stumbled upon a problem where multiple pipe redirection occasionally get stuck when trying to get sha256 sum of a stream. You can try to reproduce the problem if you have /usr/ports/shells/bash installed (output redirection used in this command is possible only in bash). Create temporary test file with command: dd if=/dev/urandom of=/tmp/file1 bs=1k count=10 And the command I'm using is: /usr/local/bin/bash -c 'cat /tmp/file1 | tee (/sbin/sha256 /tmp/file1.sha256) /tmp/file1.copy' ; echo $status Command gets stuck about once in 20 executions. top output when command gets stuck (irrelevant processes removed): PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 84073 HappyUser 1 520 17612K 2268K wait0 0:00 0.00% bash 84154 HappyUser 1 520 10084K 844K fifoow 1 0:00 0.00% tee And more strangely, I can reproduce this problem on 9.0-RELEASE and 7.4-RELEASE-p6, but couldn't reproduce on 8.2-RELEASE-p4. Thanks for any pointers/explanations, Normunds ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bash pipe redirection gets stuck
On Mon, 3 Dec 2012 16:35:15 +0200 (EET) l...@rule.lv articulated: Dear all, I stumbled upon a problem where multiple pipe redirection occasionally get stuck when trying to get sha256 sum of a stream. You can try to reproduce the problem if you have /usr/ports/shells/bash installed (output redirection used in this command is possible only in bash). Create temporary test file with command: dd if=/dev/urandom of=/tmp/file1 bs=1k count=10 And the command I'm using is: /usr/local/bin/bash -c 'cat /tmp/file1 | tee (/sbin/sha256 /tmp/file1.sha256) /tmp/file1.copy' ; echo $status Command gets stuck about once in 20 executions. top output when command gets stuck (irrelevant processes removed): PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 84073 HappyUser 1 520 17612K 2268K wait0 0:00 0.00% bash 84154 HappyUser 1 520 10084K 844K fifoow 1 0:00 0.00% tee And more strangely, I can reproduce this problem on 9.0-RELEASE and 7.4-RELEASE-p6, but couldn't reproduce on 8.2-RELEASE-p4. Thanks for any pointers/explanations, Normunds For starters, what version of Bash? FreeBSD is still a few patches behind the current patch level, so that is also a possibility. I would suggest you visit: https://lists.gnu.org/mailman/listinfo/bug-bash, subscribe to the list and then ask your question bug-b...@gnu.org. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Communicate! It can't make things any worse. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bash pipe redirection gets stuck
On 03.12.12 15:35, l...@rule.lv wrote: [...] I stumbled upon a problem where multiple pipe redirection occasionally get stuck when trying to get sha256 sum of a stream. You can try to reproduce the problem if you have /usr/ports/shells/bash installed (output redirection used in this command is possible only in bash). Create temporary test file with command: dd if=/dev/urandom of=/tmp/file1 bs=1k count=10 And the command I'm using is: /usr/local/bin/bash -c 'cat /tmp/file1 | tee (/sbin/sha256 /tmp/file1.sha256) /tmp/file1.copy' ; echo $status Command gets stuck about once in 20 executions. top output when command gets stuck (irrelevant processes removed): PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 84073 HappyUser 1 520 17612K 2268K wait0 0:00 0.00% bash 84154 HappyUser 1 520 10084K 844K fifoow 1 0:00 0.00% tee And more strangely, I can reproduce this problem on 9.0-RELEASE and 7.4-RELEASE-p6, but couldn't reproduce on 8.2-RELEASE-p4. It maybe couldn't gather more randomness from /dev/random? The random(4) manpage suggests that there's (theoretically) indeed a chance that it blocks - see the section about 'kern.random.sys.seeded'. So in fact - when you think the command gets stuck - it's probably not bash related at all. cheers, Frank Reppin -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bash pipe redirection gets stuck
long at rule.lv writes: Dear all, I stumbled upon a problem where multiple pipe redirection occasionally get stuck when trying to get sha256 sum of a stream. You can try to reproduce the problem if you have /usr/ports/shells/bash installed (output redirection used in this command is possible only in bash). Create temporary test file with command: dd if=/dev/urandom of=/tmp/file1 bs=1k count=10 And the command I'm using is: /usr/local/bin/bash -c 'cat /tmp/file1 | tee (/sbin/sha256 /tmp/file1.sha256) /tmp/file1.copy' ; echo $status ... Do you get stuck with this ? Does it make any difference ? /usr/local/bin/bash -c 'cat /tmp/file1 | tee /tmp/file1.copy | /sbin/sha256 \ /tmp/file1.sha256' ; echo $status jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bash pipe redirection gets stuck
jb jb.1234abcd at gmail.com writes: ... Do you get stuck with this ? Does it make any difference ? I missed a redirector - sorry about that; the entry should be: /usr/local/bin/bash -c 'cat /tmp/file1 | tee /tmp/file1.copy | /sbin/sha256 \ /tmp/file1.sha256' ; echo $status jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: bash pipe redirection gets stuck
On 03.12.12 15:35, l...@rule.lv wrote: [...] I stumbled upon a problem where multiple pipe redirection occasionally get stuck when trying to get sha256 sum of a stream. You can try to reproduce the problem if you have /usr/ports/shells/bash installed (output redirection used in this command is possible only in bash). Create temporary test file with command: dd if=/dev/urandom of=/tmp/file1 bs=1k count=10 And the command I'm using is: /usr/local/bin/bash -c 'cat /tmp/file1 | tee (/sbin/sha256 /tmp/file1.sha256) /tmp/file1.copy' ; echo $status Command gets stuck about once in 20 executions. top output when command gets stuck (irrelevant processes removed): PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 84073 HappyUser 1 520 17612K 2268K wait0 0:00 0.00% bash 84154 HappyUser 1 520 10084K 844K fifoow 1 0:00 0.00% tee And more strangely, I can reproduce this problem on 9.0-RELEASE and 7.4-RELEASE-p6, but couldn't reproduce on 8.2-RELEASE-p4. It maybe couldn't gather more randomness from /dev/random? The random(4) manpage suggests that there's (theoretically) indeed a chance that it blocks - see the section about 'kern.random.sys.seeded'. So in fact - when you think the command gets stuck - it's probably not bash related at all. cheers, Frank Reppin -- 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped Thanks for your answer, but randomly generated file is created fine (it is only for illustrative purpose). As far as I understand, thing that blocks is tee inside bash command or pipeline. Thanks and best regards, Normunds ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Xorg got stuck sometimes
Hi there, Sometimes, Xorg got stuck but I can't reproduce it always. When it appears, Xorg just stop being usable and mouse / keyboard can't be used also, switching to tty does not work at all and the screen is frozen. But I still can use ssh to connect the broken host and shutdown it normally, Xorg will use 100% of CPU when it breaks like this. I noticed this message when it appears : EQ overflowing. The server is probably stuck in an infinite loop. I'm using the nvidia nvidia-driver-304.64 on FreeBSD 9.1-RC3 Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg got stuck sometimes
Try to rebuild Xorg with WITHOUT_NOUVEAU. That maybe helpfull. Cheers On Tue, Nov 20, 2012 at 5:38 PM, David Demelier demelier.da...@gmail.comwrote: Hi there, Sometimes, Xorg got stuck but I can't reproduce it always. When it appears, Xorg just stop being usable and mouse / keyboard can't be used also, switching to tty does not work at all and the screen is frozen. But I still can use ssh to connect the broken host and shutdown it normally, Xorg will use 100% of CPU when it breaks like this. I noticed this message when it appears : EQ overflowing. The server is probably stuck in an infinite loop. I'm using the nvidia nvidia-driver-304.64 on FreeBSD 9.1-RC3 Cheers, -- David Demelier __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg got stuck sometimes
On 20/11/2012 19:18, Hooman Oroojeni wrote: Try to rebuild Xorg with WITHOUT_NOUVEAU. That maybe helpfull. Cheers On Tue, Nov 20, 2012 at 5:38 PM, David Demelier demelier.da...@gmail.com mailto:demelier.da...@gmail.com wrote: Hi there, Sometimes, Xorg got stuck but I can't reproduce it always. When it appears, Xorg just stop being usable and mouse / keyboard can't be used also, switching to tty does not work at all and the screen is frozen. But I still can use ssh to connect the broken host and shutdown it normally, Xorg will use 100% of CPU when it breaks like this. I noticed this message when it appears : EQ overflowing. The server is probably stuck in an infinite loop. I'm using the nvidia nvidia-driver-304.64 on FreeBSD 9.1-RC3 Cheers, -- David Demelier _ freebsd-questions@freebsd.org mailto:freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/__mailman/listinfo/freebsd-__questions http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-__unsubscr...@freebsd.org mailto:freebsd-questions-unsubscr...@freebsd.org -- WITHOUT_NOUVEAU is already in my make.conf.. Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Combining netcat with fifos results in stuck queues/sbwait
I was hoping to establish a simple processing server using nc(1). After finding numerous examples of combining netcat with fifos (named pipes) I am unable to establish a reliable setup. E.g. following the example of the canonical netcat server: server: #mkfifo backpipe #nc -l 4242 backpipe | tr -u [:lower:] [:upper:] backpipe client: #mkfifo frontpipe #nc localhost 4242 frontpipe testfile.out #cat testfile.in frontpipe For any non-trivially small testfile I inevitably end up with the processes at both ends stuck in sbwait. I have managed to avoid the stuck condition by setting the TCP buffer sizes at both ends: nc -I 2048 -O 1024 with a resulting throughput of ~40kB/s (and a supplementary problem of truncation). There are other oddities, such as not using the fifo on the client end: #nc -I 2048 -O 1024 localhost 4242 testfile.in testfile.out also results in stuck processes. So far I've tried on 8.2/8.3 i386 and amd64. The full implementation is planned to use fifos for input and output along with fd redirection but attempts using that have fared no better. Can anyone provide a secret-sauce recipe for netcat/fifo success? Thanks, Wayne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck between current and 9 release.
On 11/14/11 8:50 PM, eculp wrote: I was running current (before 10) last month, had a health emergency and when I could check the server current was 10. I ereased all sources and switched all my csup files to release and begin building a new world daily with no problems to be sure all was well. ( probably a mistake ). Port upgrades were building fine with portmaster so I just decided to reboot to see if all was well.( Dumb ) it wasn't, (Murphy's Law), the machine won't boot. Rather than a spinning slash (/) a single one and it hangs. I have been looking for an amd 64 version of a release snapshot and haven't found anything close. I have no idea why it doesn't even try to boot. I have tried all the loader options and get nowhere. I could use any suggestions especially since I don't even have a amd64 snapshot other than old ones to do a reinstall especially if there is a problem with the release. Thanks, ed P.S. If this should be on another list please let me know. If there is an AMD RELEASE 9 snap somewhere other than what is in the handbook. Anything would be great. 9 hasn't been released yet, but you can grab 9.0-RC2 from FTPs, for example: ftp://ftp.free.fr/mirrors/ftp.freebsd.org/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC2-amd64-dvd1.iso ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
msk0 NIC getting stuck
Greetings all, Has anyone seen similar problems as this... Nov 22 14:49:49 sleipnir kernel: msk0: watchdog timeout Nov 22 14:49:49 sleipnir kernel: msk0: prefetch unit stuck? Nov 22 14:49:49 sleipnir kernel: msk0: initialization failed: no memory for Rx b uffers The NIC freezes completely and will not return to sanity with ifconfig msk0 down and ifconfig msk0 up. The environment this happens on is FreeBSD sleipnir 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #0: Sun Nov 20 17:34:27 EET 2011 root@sleipnir:/usr/obj/usr/src/sys/Sleipnir amd64 The same thing happens with the GENERIC kernel as well as with my locally compiled kernel. The only difference in the kernels is that the locally compiled one supports 4 fibs. The hardware is a Supermicro H8DCL-6F motherboard with 2 AMD 4162EE CPUs and 16GB of memory. All of the file systems are mirrored on top of GUID partitions. Most of them are UFS2+SU on top of gmirror and one ZFS on top of zpool mirror. Cheers, // jau .--- ..- -.- -.- .-.- .-.-.-..- -.- -.- --- -. . -. /Jukka A. Ukkonen, Oxit Ltd, Finland /__ M.Sc. (sw-eng cs)(Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Oxit.Fi /Internet: jau(a)iki.fi v .--- .- ..- ...-.- .. -.- .. .-.-.- ..-. .. + + + + My opinions are mine and mine alone, not my employers. + + + + ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck between current and 9 release.
14.11.2011 23:50, eculp пишет: I have been looking for an amd 64 version of a release snapshot and haven't found anything close. Seems that you need this: ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/ -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck between current and 9 release.
Quoting Boris Samorodov b...@passap.ru: 14.11.2011 23:50, eculp пишет: I have been looking for an amd 64 version of a release snapshot and haven't found anything close. Seems that you need this: ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/ -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve Thanks Boris. You are a life saver. Hopefully the Handbook will be updated. The current one has the following: Acquire the Memory Stick Image just for information The memory stick image can be downloaded from the ISO-IMAGES/ directory from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/arch/arch/ISO-IMAGES/version/FreeBSD-9.0-RELEASE-arch-memstick.img. Replace arch and version with the architecture and the version number which you want to install, respectively. For example, the memory stick images for FreeBSD/i386 9.0-RELEASE are available from ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.0/FreeBSD-9.0-RELEASE-i386-memstick.img. /just for information Thanks again. ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Stuck between current and 9 release.
I was running current (before 10) last month, had a health emergency and when I could check the server current was 10. I ereased all sources and switched all my csup files to release and begin building a new world daily with no problems to be sure all was well. ( probably a mistake ). Port upgrades were building fine with portmaster so I just decided to reboot to see if all was well.( Dumb ) it wasn't, (Murphy's Law), the machine won't boot. Rather than a spinning slash (/) a single one and it hangs. I have been looking for an amd 64 version of a release snapshot and haven't found anything close. I have no idea why it doesn't even try to boot. I have tried all the loader options and get nowhere. I could use any suggestions especially since I don't even have a amd64 snapshot other than old ones to do a reinstall especially if there is a problem with the release. Thanks, ed P.S. If this should be on another list please let me know. If there is an AMD RELEASE 9 snap somewhere other than what is in the handbook. Anything would be great. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ot :stuck in GRUB
Hi all, A Friend of mine has some version of either *nux or bsd installed (he does not even know for sure), turns out he clicked yes for some updates to install and upon restarting he now winds up at GRUB , I told him to type boot and it reports kernel must loaded prior to booting I really have no time to get out there, so he shipped me his hard drive which I should be receiving today or tomorrow. It *seems* to me the update may have corrupted some type of conf file, am I on the right track here? Does anyone have any suggestion, since its an old friend I can't charge him, but nor do I want to spend a significant amount of time on it. TIA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ot :stuck in GRUB
Hi all, A Friend of mine has some version of either *nux or bsd installed (he does not even know for sure), turns out he clicked yes for some updates to install and upon restarting he now winds up at GRUB , I told him to type boot and it reports kernel must loaded prior to booting I really have no time to get out there, so he shipped me his hard drive which I should be receiving today or tomorrow. It *seems* to me the update may have corrupted some type of conf file, am I on the right track here? Does anyone have any suggestion, since its an old friend I can't charge him, but nor do I want to spend a significant amount of time on it. TIA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ot : stuck in GRUB
GRUB is the boot program for several versions of Linux, not for FreeBSD. For a useful answer, ask where Linux weenies hang out, not here. Or even better, just google for the text of the error message. R's, John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ot : stuck in GRUB
On Tue, 27 Sep 2011, John Levine wrote: GRUB is the boot program for several versions of Linux, not for FreeBSD. But many people also use it to boot FreeBSD in multi-boot situations. The pkg-message in sysutils/grub and sysutils/grub2 might help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
On Tue, 15 Feb 2011 12:47:42 -0800, Rem P Roberti remeg...@comcast.net wrote: NOTE: Slightly OT, but figured it was worth the post. As a side-note, the config-file will be cleaned up before being embedded into the kernel. Meaning config -x `sysctl -n kern.bootfile` will rarely ever match the config that was used to generate the kernel in the first place. Specifically, comments are removed, and if you've nested configs using the include statement, redundant and/or conflicting directives will be consolidated. If you instead wish to embed the kernel config AS-IS, comments and structure remaining in-tact, you should instead: cd /sys/ARCH/conf config -C -g CONFIG NOTE: `/sys' ought to be a symbolic link to `/usr/src/sys' NOTE: ARCH is to be replaced with something like i386, amd64, etc. NOTE: CONFIG is to be replaced with something like GENERIC, PAE, MYCUSTOMKERNELCONFIG, etc. Then one simply does the following to compile the kernel: cd ../../compile/CONFIG make depend make BUT... then again not everybody: a. compiles their own custom kernels b. uses a custom config c. needs to be able to extract the config verbatim from the compiled kernel YNMV (Your Needs May Vary). -- Devin Not off topic at all, and much appreciated. A lot of what has been offered as a result of my OP is a bit over my head at this stage of the game, but much isn't. I'm gaining on it! The procedure described above reminds me to how kernels have been built in the FreeBSD 4 era. Interesting to see that it is -a- still supported and -b- serves a specific purpose that may be intended sometimes. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
Where do I locate the kernel config file? Adding options INCLUDE_CONFIG_FILE to /sys/i386/conf/GENERIC or /sys/amd64/conf/ allows config -x /boot/kernel/kernel Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not quoted-printable, Not HTML, Not base 64. Reply below text sections not at top, to avoid breaking cumulative context. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
On Feb 15, 2011, at 4:25 AM, Julian H. Stacey wrote: Where do I locate the kernel config file? Adding options INCLUDE_CONFIG_FILE to /sys/i386/conf/GENERIC or /sys/amd64/conf/ allows config -x /boot/kernel/kernel NOTE: Slightly OT, but figured it was worth the post. As a side-note, the config-file will be cleaned up before being embedded into the kernel. Meaning config -x `sysctl -n kern.bootfile` will rarely ever match the config that was used to generate the kernel in the first place. Specifically, comments are removed, and if you've nested configs using the include statement, redundant and/or conflicting directives will be consolidated. If you instead wish to embed the kernel config AS-IS, comments and structure remaining in-tact, you should instead: cd /sys/ARCH/conf config -C -g CONFIG NOTE: `/sys' ought to be a symbolic link to `/usr/src/sys' NOTE: ARCH is to be replaced with something like i386, amd64, etc. NOTE: CONFIG is to be replaced with something like GENERIC, PAE, MYCUSTOMKERNELCONFIG, etc. Then one simply does the following to compile the kernel: cd ../../compile/CONFIG make depend make BUT... then again not everybody: a. compiles their own custom kernels b. uses a custom config c. needs to be able to extract the config verbatim from the compiled kernel YNMV (Your Needs May Vary). -- Devin Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not quoted-printable, Not HTML, Not base 64. Reply below text sections not at top, to avoid breaking cumulative context. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Cheers, Devin Teske - CONTACT INFORMATION - Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com - LEGAL DISCLAIMER - This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. - END TRANSMISSION - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
NOTE: Slightly OT, but figured it was worth the post. As a side-note, the config-file will be cleaned up before being embedded into the kernel. Meaning config -x `sysctl -n kern.bootfile` will rarely ever match the config that was used to generate the kernel in the first place. Specifically, comments are removed, and if you've nested configs using the include statement, redundant and/or conflicting directives will be consolidated. If you instead wish to embed the kernel config AS-IS, comments and structure remaining in-tact, you should instead: cd /sys/ARCH/conf config -C -g CONFIG NOTE: `/sys' ought to be a symbolic link to `/usr/src/sys' NOTE: ARCH is to be replaced with something like i386, amd64, etc. NOTE: CONFIG is to be replaced with something like GENERIC, PAE, MYCUSTOMKERNELCONFIG, etc. Then one simply does the following to compile the kernel: cd ../../compile/CONFIG make depend make BUT... then again not everybody: a. compiles their own custom kernels b. uses a custom config c. needs to be able to extract the config verbatim from the compiled kernel YNMV (Your Needs May Vary). -- Devin Not off topic at all, and much appreciated. A lot of what has been offered as a result of my OP is a bit over my head at this stage of the game, but much isn't. I'm gaining on it! Cheers... Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Stuck
This is a new one for me. I decided to do a manual update on my 8.1 box, starting with csup. Buildworld went fine, as did buildkernel. However, when I tried to install the new kernel installkernel choked with an error message telling me that it could not proceed because the root partition was full. What! I did a df and sure enough the root partition was overloaded. When I installed the system I used sysinstalls recommended sizes for the root partion, which is around 10G. Anyway, when I rebooted, the system rebooted into single user mode, and that is presently where I stand. I have no idea how to proceed at this point, and would appreciate any help in fixing this. Of course, I smell a newbie type error in all of this, but haven't quite figured out where I went wrong. Cheers... Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Stuck
Rem Roberti writes: This is a new one for me. I decided to do a manual update on my 8.1 box, starting with csup. Buildworld went fine, as did buildkernel. However, when I tried to install the new kernel installkernel choked with an error message telling me that it could not proceed because the root partition was full. What! I did a df and sure enough the root partition was overloaded. When I installed the system I used sysinstalls recommended sizes for the root partion, which is around 10G. Anyway, when I rebooted, the system rebooted into single user mode, and that is presently where I stand. I have no idea how to proceed at this point, and would appreciate any help in fixing this. Of course, I smell a newbie type error in all of this, but haven't quite figured out where I went wrong. Start with this: du -x / | sort -nr | head -n 30 This will give you the largest directories; if any of them don't look right - investigate further. (For comparison: the root directory on this machine is 2 gbytes, of which I use 1.1. 10 gbytes is a lot of space.) Respectfully, Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
On 13 February 2011 16:51, Rem Roberti remeg...@comcast.net wrote: This is a new one for me. I decided to do a manual update on my 8.1 box, starting with csup. Buildworld went fine, as did buildkernel. However, when I tried to install the new kernel installkernel choked with an error message telling me that it could not proceed because the root partition was full. What! I did a df and sure enough the root partition was overloaded. When I installed the system I used sysinstalls recommended sizes for the root partion, which is around 10G. Anyway, when I rebooted, the system rebooted into single user mode, and that is presently where I stand. I have no idea how to proceed at this point, and would appreciate any help in fixing this. Of course, I smell a newbie type error in all of this, but haven't quite figured out where I went wrong. To fix your booting, I suggest that you check that /boot/kernel.old exists: # [ -d /boot/kernel ] echo Yes! If this doesn't say Yes! then stop, and wait for someone to help you out a little more. If it does: # /bin/mv /boot/kernel /boot/kernel.faulty # /bin/mv /boot/kernel.old /boot/kernel # reboot That should get you back up until you can fix your other problems! Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
On Sun, 13 Feb 2011 08:51:12 -0800, Rem Roberti remeg...@comcast.net wrote: This is a new one for me. I decided to do a manual update on my 8.1 box, starting with csup. Buildworld went fine, as did buildkernel. However, when I tried to install the new kernel installkernel choked with an error message telling me that it could not proceed because the root partition was full. What! I did a df and sure enough the root partition was overloaded. When I installed the system I used sysinstalls recommended sizes for the root partion, which is around 10G. Where is it advised to make / 10 GB? Do you have any other functional parts that get their own partition traditionally (such as /tmp, /var, /usr) on the / partition? The installation process should not make the system bigger, as updating the system usually keeps nearly the same sizes. An exception is the kernel: Here, a backup of the previous kernel will be generated. On a partition / with 10 GB capacity and at least 1 GB free you should not run into problems. Kernel and modules should not grow bigger than that. Anyway, when I rebooted, the system rebooted into single user mode, and that is presently where I stand. I have no idea how to proceed at this point, and would appreciate any help in fixing this. You could try to mount the partitions via # mount -a # exit and bring up the system in multi-user mode, if possible. You can try to make sure there is sufficient space on the / partition to repeat the system and kernel installation procedure. Make sure you read the comment section of /usr/src/Makefile which gives a very good roadmap of how to properly perform an update. Of course, I smell a newbie type error in all of this, but haven't quite figured out where I went wrong. If you can provide command output. You can use the program script to make a copy of all terminal input/output to a file. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
On 02/13/11 09:01, Robert Huff wrote: Rem Roberti writes: This is a new one for me. I decided to do a manual update on my 8.1 box, starting with csup. Buildworld went fine, as did buildkernel. However, when I tried to install the new kernel installkernel choked with an error message telling me that it could not proceed because the root partition was full. What! I did a df and sure enough the root partition was overloaded. When I installed the system I used sysinstalls recommended sizes for the root partion, which is around 10G. Anyway, when I rebooted, the system rebooted into single user mode, and that is presently where I stand. I have no idea how to proceed at this point, and would appreciate any help in fixing this. Of course, I smell a newbie type error in all of this, but haven't quite figured out where I went wrong. Start with this: du -x / | sort -nr | head -n 30 This will give you the largest directories; if any of them don't look right - investigate further. (For comparison: the root directory on this machine is 2 gbytes, of which I use 1.1. 10 gbytes is a lot of space I completely misspoke, having confused the hard drive in question with another box. This drive is a 40G drive, of which 500MB was allotted for root. When I ran your command I noticed the /boot/kernel.old was very large, so I moved the whole thing over to my home directory, which finally allowed me to boot the computer normally. This was an intuitive move, and probably not that kosher, but it worked. But where do we go from here? Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
On 13 February 2011 13:53, Rem P Roberti remeg...@comcast.net wrote: On 02/13/11 09:01, Robert Huff wrote: Rem Roberti writes: This is a new one for me. I decided to do a manual update on my 8.1 box, starting with csup. Buildworld went fine, as did buildkernel. However, when I tried to install the new kernel installkernel choked with an error message telling me that it could not proceed because the root partition was full. What! I did a df and sure enough the root partition was overloaded. When I installed the system I used sysinstalls recommended sizes for the root partion, which is around 10G. Anyway, when I rebooted, the system rebooted into single user mode, and that is presently where I stand. I have no idea how to proceed at this point, and would appreciate any help in fixing this. Of course, I smell a newbie type error in all of this, but haven't quite figured out where I went wrong. Start with this: du -x / | sort -nr | head -n 30 This will give you the largest directories; if any of them don't look right - investigate further. (For comparison: the root directory on this machine is 2 gbytes, of which I use 1.1. 10 gbytes is a lot of space I completely misspoke, having confused the hard drive in question with another box. This drive is a 40G drive, of which 500MB was allotted for root. When I ran your command I noticed the /boot/kernel.old was very large, so I moved the whole thing over to my home directory, which finally allowed me to boot the computer normally. This was an intuitive move, and probably not that kosher, but it worked. But where do we go from here? Remove all the *.symbols files (if you're not going to be debugging). Build with makeoptions DEBUG=-g commented out of your kernel config. (my root filesystem has 70M used. On amd64, no less) -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
Rem Roberti writes: This is a new one for me. I decided to do a manual update on my 8.1 box, starting with csup. Buildworld went fine, as did buildkernel. However, when I tried to install the new kernel installkernel choked with an error message telling me that it could not proceed because the root partition was full. What! I did a df and sure enough the root partition was overloaded. When I installed the system I used sysinstalls recommended sizes for the root partion, which is around 10G. Anyway, when I rebooted, the system rebooted into single user mode, and that is presently where I stand. I have no idea how to proceed at this point, and would appreciate any help in fixing this. Of course, I smell a newbie type error in all of this, but haven't quite figured out where I went wrong. Start with this: du -x / | sort -nr | head -n 30 This will give you the largest directories; if any of them don't look right - investigate further. (For comparison: the root directory on this machine is 2 gbytes, of which I use 1.1. 10 gbytes is a lot of space I completely misspoke, having confused the hard drive in question with another box. This drive is a 40G drive, of which 500MB was allotted for root. When I ran your command I noticed the /boot/kernel.old was very large, so I moved the whole thing over to my home directory, which finally allowed me to boot the computer normally. This was an intuitive move, and probably not that kosher, but it worked. But where do we go from here? Remove all the *.symbols files (if you're not going to be debugging). Build with makeoptions DEBUG=-g commented out of your kernel config. (my root filesystem has 70M used. On amd64, no less) Getting rid of all those .symbols files made a big difference. Where do I locate the kernel config file? Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
Quoth ill...@gmail.com on Sunday, 13 February 2011: On 13 February 2011 13:53, Rem P Roberti remeg...@comcast.net wrote: On 02/13/11 09:01, Robert Huff wrote: Rem Roberti writes: This is a new one for me. I decided to do a manual update on my 8.1 box, starting with csup. Buildworld went fine, as did buildkernel. However, when I tried to install the new kernel installkernel choked with an error message telling me that it could not proceed because the root partition was full. What! I did a df and sure enough the root partition was overloaded. When I installed the system I used sysinstalls recommended sizes for the root partion, which is around 10G. Anyway, when I rebooted, the system rebooted into single user mode, and that is presently where I stand. I have no idea how to proceed at this point, and would appreciate any help in fixing this. Of course, I smell a newbie type error in all of this, but haven't quite figured out where I went wrong. Start with this: du -x / | sort -nr | head -n 30 This will give you the largest directories; if any of them don't look right - investigate further. (For comparison: the root directory on this machine is 2 gbytes, of which I use 1.1. 10 gbytes is a lot of space I completely misspoke, having confused the hard drive in question with another box. This drive is a 40G drive, of which 500MB was allotted for root. When I ran your command I noticed the /boot/kernel.old was very large, so I moved the whole thing over to my home directory, which finally allowed me to boot the computer normally. This was an intuitive move, and probably not that kosher, but it worked. But where do we go from here? Remove all the *.symbols files (if you're not going to be debugging). Build with makeoptions DEBUG=-g commented out of your kernel config. (my root filesystem has 70M used. On amd64, no less) I have INSTALL_NODEBUG=yes in my make.conf, which someone on this list advised. Apparently that still builds the symbols but doesn't install them in /boot/kernel, saving a ton of space. This will prevent you running into this same problem the next time you build. -- Sterling (Chip) Camden | sterl...@camdensoftware.com | 2048D/3A978E4F http://chipsquips.com | http://camdensoftware.com | http://chipstips.com pgprXJHgVes3X.pgp Description: PGP signature
Re: Stuck
Remove all the *.symbols files (if you're not going to be debugging). Build with makeoptions DEBUG=-g commented out of your kernel config. (my root filesystem has 70M used. On amd64, no less) I knew that I asked a dumb question when I asked where to find the kernel config. OK...I commented out the section in question, and we'll see how it goes. Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
On Sun, 13 Feb 2011 10:31:24 -0800, Rem P Roberti remeg...@comcast.net wrote: Getting rid of all those .symbols files made a big difference. Where do I locate the kernel config file? It is /usr/src/sys/i386/conf/NAME or /usr/src/sys/amd64/conf/NAME depending on your architecture; GENERIC is the name of the default kernel (which doesn't require KERNCONF=NAME in the make commands). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
On Sun, 13 Feb 2011 10:53:09 -0800, Rem P Roberti remeg...@comcast.net wrote: I completely misspoke, having confused the hard drive in question with another box. This drive is a 40G drive, of which 500MB was allotted for root. For a current FreeBSD system, this is a bit too small (although sufficient under certain circumstances). Making / 1G or 2G should be fully sufficient in all cases. When I ran your command I noticed the /boot/kernel.old was very large, so I moved the whole thing over to my home directory, which finally allowed me to boot the computer normally. The .old file is a backup of the previous kernel, this backup is created automatically when you make installkernel. This was an intuitive move, and probably not that kosher, but it worked. It simply removes the ability to boot the old kernel, which doesn't seem to be a problem here. But where do we go from here? Check your kernel configuration (remove symbols), maybe remove building of modules you don't need (see man src.conf for details), repeat the installation procedure outlined in /usr/src/Makefile (comment section at the beginning). You should then end up with a fully functional updated system. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
I'm back in business, and the update finished without any more problems. However...the output of df is now really strange: root@ /etc: df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/label/rootfs0 507630326732 140288 70% / devfs 1 1 0 100%/dev /dev/label/var0 1012974 173368 758570 19% /var /dev/label/usr0 33292236 9351168 21277690 31% /usr linprocfs 4 4 100%/usr/compat/linux/proc /dev/md0 789518 20 726338 0%/tmp What happened to the Filesystem labels? Rem ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stuck
On 02/13/11 10:44, Polytropon wrote: On Sun, 13 Feb 2011 10:31:24 -0800, Rem P Robertiremeg...@comcast.net wrote: Getting rid of all those .symbols files made a big difference. Where do I locate the kernel config file? It is /usr/src/sys/i386/conf/NAME or /usr/src/sys/amd64/conf/NAME depending on your architecture; GENERIC is the name of the default kernel (which doesn't require KERNCONF=NAME in the make commands). Yes...I realized that I had asked a rather dumb question. I made the changes and all worked fine. I still can't figure out why the output of df looks the way it does. Re, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: zpool won't mount as dataset stuck
Hi, On Sun, 28 Nov 2010 04:30:48 pm Geoff Roberts wrote: Long and short is I can see the tank zpool without a problem, but whenever I try to import it the disk light flashes every second and the datasets won't mount. I can run a history command on tank and that shows the following repeated every second (tgx keeps incrementing by one): 2010-11-28.15:08:33 [internal rollback txg:9645688] dataset = 222 [user root on systemname.com] 2010-11-28.15:08:34 [internal rollback txg:9645689] dataset = 222 [user root on systemname.com] Just for reference, I was able to use the steps below to recover the data of the zpool that was stuck. The steps below were done using virtual machines. The zpool history command was a great help as well. a) Created a FreeBSD 9.0 system and applied a ZFS v28 patch for a few features that looked useful for my problem. i) Ability to mount zpool in readonly ii) Ability to mount zpool with -N (do not mount datasets) iii) Ability to mount zpool with -T to specify a particular transaction set. In the end I didn't need this feature. b) Took an image of one of the mirror partitions housing the zpool using dd and transferred that to a file on a stand UFS2 file system. This was so I could work on a copy and transfer the data on an external hard disk to the FreeBSD 9.0 virtual machine. c) Used mdconfig to mount the file image on the FreeBSD 9.0 system. d) I was able to use zpool import -o readonly=on -N poolname The readonly option in particular seemed to stop the last transaction continually attempting to run in an endless loop. e) I could then see the datasets. From here I was able to mount them and recover all the data. Geoff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
zpool won't mount as dataset stuck
Hi, In a slight panic here as my main ZFS pool tank won't mount. I have two ZFS pools on two different drives - a system pool on a single disk called data and a mirrored pool on two disks called tank. The tank zpool contains all my jails and non-system boot type data. I was wanting to test FreeBSD 8.2-PRERELEASE and therefore took a snapshot of data and tank: zfs snapshot -r d...@pre82 zfs snapshot -r t...@pre82 tank seemed to hang on the above command for ages and I had to Ctrl-C. Long and short is I can see the tank zpool without a problem, but whenever I try to import it the disk light flashes every second and the datasets won't mount. I can run a history command on tank and that shows the following repeated every second (tgx keeps incrementing by one): 2010-11-28.15:08:33 [internal rollback txg:9645688] dataset = 222 [user root on systemname.com] 2010-11-28.15:08:34 [internal rollback txg:9645689] dataset = 222 [user root on systemname.com] The zpool seems to be stuck. What should I do from here? Is there a way to freeze dataset operations so I can at least mount them? Other thoughts and questions I had: a) What would be the best way to take a raw image of the zpool so I can work on a copy of the zpool rather than the original? b) Would it be worth trying to import the zpool on FreeBSD current or OpenSolaris? Any help greatly appreciated. Kind regards, Geoff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg 7.5 and OpenMotif: mouse stuck in box
Dear William, excellent! The patch you pointed me to works for me too. Thank you so much for your help, I am going to send an email to the port maintainers to see whether they can fix this in the ports tree. very best giuseppe On Mon, Oct 11, 2010 at 6:43 PM, William Bulley w...@umich.edu wrote: According to Giuseppe Pagnoni gpagn...@gmail.com on Mon, 10/11/10 at 10:57: thank you very much for your reply, it does seem to be the same type of bug. However, and I apologize for being dense here, it is not immediate to me how to proceed practically to apply the patch from within the ports framework. Also, I still wonder why the patch hasn't been incorporated in the tree given that the bug is known I am not able to answer your final question - that is left to the ports maintainers to address. I simply installed the latest (was it 1.7.5) xorg-server at that time and added those half dozen patches. If 1.7.7 solved the problem, then I'm not sure what issue(s) you have. If you want to have FreeBSD ports upgraded, I would contact the port's maintainers directly. I chose not to install xorg-server 1.7.7 since I was unsure if there were other dependencies or issues that might arise from doing so. I'm not used to patching a mature, released port, so for me even that was a leap of faith! :-) Just for clarity, I did not formally patch this port (xorg-server). I went into the directory tree beneath the work directory, found the dit/events.c file, and made those above mentioned (about six or so) small source code patches. I then re-made the port and re-installed the port. After it tested successfully, I reported my results to the -questions list in case it would help others. YMMV. And good luck! Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41125 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5336 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Xorg 7.5 and OpenMotif: mouse stuck in box
Dear all, I am resending this because it seems to me a really critical bug (prevents you from using OpenMotif or lesstif applications), but apparently nothing has been changed since last july. Upgrading xorg to 1.7.7 does fix the problem, but I wonder if this may cause dependency problems in the ports tree. Also, if this is the correct fix, is there a reason why it hasn't been integrated in the ports yet? thanks again giuseppe I am having a problem with xorg 1.7.5 and OpenMotif resulting in the mouse being stuck in certain areas of the Motif windows that are supposed to open dialog boxes when right-clicked. I noticed that somebody else reported the problem already in this list, and that it seems to have been fixed in xorg 1.7.7. However xorg 1.7.7 is not yet available in the ports tree, nor it looks like a patch is in for the current version (I tried to recompile xorg today after a port tree update). Is manually compiling Xorg the only solution right now? thanks in advance for any advice giuseppe -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41125 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5336 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg 7.5 and OpenMotif: mouse stuck in box
Giuseppe Pagnoni wrote: I am resending this because it seems to me a really critical bug (prevents you from using OpenMotif or lesstif applications), but apparently nothing has been changed since last july. Upgrading xorg to 1.7.7 does fix the problem, but I wonder if this may cause dependency problems in the ports tree. Also, if this is the correct fix, is there a reason why it hasn't been integrated in the ports yet? thanks again giuseppe I am having a problem with xorg 1.7.5 and OpenMotif resulting in the mouse being stuck in certain areas of the Motif windows that are supposed to open dialog boxes when right-clicked. I noticed that somebody else reported the problem already in this list, and that it seems to have been fixed in xorg 1.7.7. However xorg 1.7.7 is not yet available in the ports tree, nor it looks like a patch is in for the current version (I tried to recompile xorg today after a port tree update). Is manually compiling Xorg the only solution right now? thanks in advance for any advice giuseppe This is what I found recently. Hope this helps you. - Forwarded message from William Bulley w...@umich.edu - To: FreeBSD Questions freebsd-questions@freebsd.org From: William Bulley w...@umich.edu Date: Thu, 2 Sep 2010 11:31:15 -0400 Subject: SOLVED: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE Cc: x...@freebsd.org, st...@freebsd.org See below for details of solution. - Forwarded message from William Bulley w...@umich.edu - To: FreeBSD Questions freebsd-questions@freebsd.org From: William Bulley w...@umich.edu Date: Wed, 25 Aug 2010 07:38:34 -0400 Subject: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE For years I have run Open-Motif on FreeBSD without issue. I use a USB keyboard and a USB three button mouse attached to a Dell Optiplex 960. This combination has worked fine for the past year. This week I upgraded from 8.0-STABLE circa January 2010 to 8.1-STABLE. I do this by doing a buildworld/installworld sequence after csup-ing stable-supfile and rebooting. In this case I also pkg_deleted all of my ports and am rebuilding them from source. Building Xorg is one of the very first ports I attempt since I prefer to work in xterms not virtual terminals. This upgrade moved me from Xorg 7.3 to Xorg 7.5, but Open-Motif stayed the same - open-motif-2.2.3_6 - it hasn't changed in years. After building Xorg, as root, I ran the Xorg -configure command to generate my xorg.conf.new file. Since a working /etc/X11/xorg.conf file was still around after the upgrade from 8.0-STABLE/Xorg 7.3, I felt no need to change anything in that file (later file comparisons confirmed that nothing had changed). My only relevant additions to /etc/X11/xorg.conf are these: Section ServerFlags Option AutoAddDevices off Option DontZap false EndSection In my /etc/rc.conf file I have dbus and hald enabled, and that has not changed since the beginning of 2010 after the confusion abated. As a normal user, I start Xorg using /usr/local/bin/xinit as always. I have several xterms configured in my ~/.xinitrc file. All those came up in the correct location and state. I was able to open those that started in iconic mode. In an open/raised xterm I could enter carriage returns and see my shell prompt move down the window. But when I tried to close/minimize an open/raised xterm, things failed. I use the following keyboard/mouse combination (configured in my .mwmrc file) to close (minimize) an xterm (and other applications): Shift Btn3Click window f.minimize This is also unchanged for some years. This particular setting has no bearing on the problem I came across yesterday. I merely state it for the record. However, this configuration triggers the bug. The problem is as soon as I use that Shift/Btn3Click combination, my arrow cursor disappears, then I cannot move to or select other xterms - I am frozen, or locked, into the xterm I was trying to close/minimize. All I can do at this point is to kill(1) the /usr/local/bin/xinit command to return to the virtual terminal where I launched my Xorg session. I am now reluctantly using the good old /usr/local/bin/twm which is always built when Xorg is built from source. I am at a loss as to what to look for next. I suspect Xorg, or the keyboard and mouse driver, not the video driver, that came with. It might be a problem with hald(8), but again, I don't know how to debug this. Any help with this very odd bug would be greatly appreciated. - End forwarded message - This problem is known (and fixed) in newer versions of xorg-server. See this URL for details of the problem. http://cgit.freedesktop.org/xorg/xserver/commit/?id=1884db430a5680e37e94726dff46686e2218d525 I have also attached the changes I made to the dit/events.c file. After rebuilding xorg-server with those patches, the Open Motif (mwm) window manager now works with the above
Re: Xorg 7.5 and OpenMotif: mouse stuck in box
Dear William, thank you very much for your reply, it does seem to be the same type of bug. However, and I apologize for being dense here, it is not immediate to me how to proceed practically to apply the patch from within the ports framework. Also, I still wonder why the patch hasn't been incorporated in the tree given that the bug is known thanks again giuseppe On Mon, Oct 11, 2010 at 4:07 PM, William Bulley w...@umich.edu wrote: Giuseppe Pagnoni wrote: I am resending this because it seems to me a really critical bug (prevents you from using OpenMotif or lesstif applications), but apparently nothing has been changed since last july. Upgrading xorg to 1.7.7 does fix the problem, but I wonder if this may cause dependency problems in the ports tree. Also, if this is the correct fix, is there a reason why it hasn't been integrated in the ports yet? thanks again giuseppe I am having a problem with xorg 1.7.5 and OpenMotif resulting in the mouse being stuck in certain areas of the Motif windows that are supposed to open dialog boxes when right-clicked. I noticed that somebody else reported the problem already in this list, and that it seems to have been fixed in xorg 1.7.7. However xorg 1.7.7 is not yet available in the ports tree, nor it looks like a patch is in for the current version (I tried to recompile xorg today after a port tree update). Is manually compiling Xorg the only solution right now? thanks in advance for any advice giuseppe This is what I found recently. Hope this helps you. - Forwarded message from William Bulley w...@umich.edu - To: FreeBSD Questions freebsd-questions@freebsd.org From: William Bulley w...@umich.edu Date: Thu, 2 Sep 2010 11:31:15 -0400 Subject: SOLVED: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE Cc: x...@freebsd.org, st...@freebsd.org See below for details of solution. - Forwarded message from William Bulley w...@umich.edu - To: FreeBSD Questions freebsd-questions@freebsd.org From: William Bulley w...@umich.edu Date: Wed, 25 Aug 2010 07:38:34 -0400 Subject: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE For years I have run Open-Motif on FreeBSD without issue. I use a USB keyboard and a USB three button mouse attached to a Dell Optiplex 960. This combination has worked fine for the past year. This week I upgraded from 8.0-STABLE circa January 2010 to 8.1-STABLE. I do this by doing a buildworld/installworld sequence after csup-ing stable-supfile and rebooting. In this case I also pkg_deleted all of my ports and am rebuilding them from source. Building Xorg is one of the very first ports I attempt since I prefer to work in xterms not virtual terminals. This upgrade moved me from Xorg 7.3 to Xorg 7.5, but Open-Motif stayed the same - open-motif-2.2.3_6 - it hasn't changed in years. After building Xorg, as root, I ran the Xorg -configure command to generate my xorg.conf.new file. Since a working /etc/X11/xorg.conf file was still around after the upgrade from 8.0-STABLE/Xorg 7.3, I felt no need to change anything in that file (later file comparisons confirmed that nothing had changed). My only relevant additions to /etc/X11/xorg.conf are these: Section ServerFlags Option AutoAddDevices off Option DontZap false EndSection In my /etc/rc.conf file I have dbus and hald enabled, and that has not changed since the beginning of 2010 after the confusion abated. As a normal user, I start Xorg using /usr/local/bin/xinit as always. I have several xterms configured in my ~/.xinitrc file. All those came up in the correct location and state. I was able to open those that started in iconic mode. In an open/raised xterm I could enter carriage returns and see my shell prompt move down the window. But when I tried to close/minimize an open/raised xterm, things failed. I use the following keyboard/mouse combination (configured in my .mwmrc file) to close (minimize) an xterm (and other applications): Shift Btn3Click window f.minimize This is also unchanged for some years. This particular setting has no bearing on the problem I came across yesterday. I merely state it for the record. However, this configuration triggers the bug. The problem is as soon as I use that Shift/Btn3Click combination, my arrow cursor disappears, then I cannot move to or select other xterms - I am frozen, or locked, into the xterm I was trying to close/minimize. All I can do at this point is to kill(1) the /usr/local/bin/xinit command to return to the virtual terminal where I launched my Xorg session. I am now reluctantly using the good old /usr/local/bin/twm which is always built when Xorg is built from source. I am at a loss as to what to look for next. I suspect Xorg, or the keyboard and mouse driver, not the video driver, that came with. It might be a problem with hald(8), but again, I don't know how
Re: Xorg 7.5 and OpenMotif: mouse stuck in box
According to Giuseppe Pagnoni gpagn...@gmail.com on Mon, 10/11/10 at 10:57: thank you very much for your reply, it does seem to be the same type of bug. However, and I apologize for being dense here, it is not immediate to me how to proceed practically to apply the patch from within the ports framework. Also, I still wonder why the patch hasn't been incorporated in the tree given that the bug is known I am not able to answer your final question - that is left to the ports maintainers to address. I simply installed the latest (was it 1.7.5) xorg-server at that time and added those half dozen patches. If 1.7.7 solved the problem, then I'm not sure what issue(s) you have. If you want to have FreeBSD ports upgraded, I would contact the port's maintainers directly. I chose not to install xorg-server 1.7.7 since I was unsure if there were other dependencies or issues that might arise from doing so. I'm not used to patching a mature, released port, so for me even that was a leap of faith! :-) Just for clarity, I did not formally patch this port (xorg-server). I went into the directory tree beneath the work directory, found the dit/events.c file, and made those above mentioned (about six or so) small source code patches. I then re-made the port and re-installed the port. After it tested successfully, I reported my results to the -questions list in case it would help others. YMMV. And good luck! Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Laptop stuck at bios splash again :-( .(chunk 'ad1s4 ; ad1s2 ,ad1s3 does not start on a track boundary : install issue)
On Fri, 27 Aug 2010 10:13:22 +0530 Mubeesh ali mubeeshal...@gmail.com wrote: It seems like i am awfully unlucky :-( ,getting two bad HDDs in a row or iam doing something terribly wrong. With my new HDD ;installed ubuntu and this time installed PC bsd not freebsd ,in a separate partition. It booted up once into PC bsd,life was good and then from next reboot .it is stuck at bios splash. As Bruce from this list commented to an earlier mail(not booting after freebsd install) ,i am assuming my bios (INSYDE bios) doesn't like freebsd partitions or freebsd in combination with ubuntu ? It seems the INSYDE bios is rather poor: other people have had problems when trying to use TrueCrypt or PGP in Windows: http://social.answers.microsoft.com/Forums/en-US/w7hardware/thread/cc99bd9c-c65c-4ad1-a892-653be6102195 -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Laptop stuck at bios splash again :-( .(chunk 'ad1s4 ; ad1s2 ,ad1s3 does not start on a track boundary : install issue)
It seems like i am awfully unlucky :-( ,getting two bad HDDs in a row or iam doing something terribly wrong. With my new HDD ;installed ubuntu and this time installed PC bsd not freebsd ,in a separate partition. It booted up once into PC bsd,life was good and then from next reboot .it is stuck at bios splash. As Bruce from this list commented to an earlier mail(not booting after freebsd install) ,i am assuming my bios (INSYDE bios) doesn't like freebsd partitions or freebsd in combination with ubuntu ? On Thu, Aug 26, 2010 at 12:01 AM, Mubeesh ali mubeeshal...@gmail.com wrote: yes. there is an un allocated 50 gb space (deleted a partition using win 7 partition tools) and we created a feebsd slice in the unallocated space while running sysinstall However in the next screen; i guess where it should give us an option to partition the freebsd slice into root,home,swap etc ? it throws this error about the track boundary and it defaults to use the entire disk. sure i will double check the procedure in handbook. thanks, Mubeesh On Wed, Aug 25, 2010 at 11:49 PM, claudiu vasadi claudiu.vas...@gmail.com wrote: of course there is. if you have empty space, create a freebsd slice and your set. handbook - instalation section section 2.6 is EXACTLY what you need, but I strongly recommend reading the handbook (as much as possible) -- Best Regards, Mubeesh Ali.V.M -- Best Regards, Mubeesh Ali.V.M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sockets stuck in use
On Mon, Jul 19, 2010 at 11:04 PM, Adam Vande More amvandem...@gmail.com wrote: On Mon, Jul 19, 2010 at 3:12 AM, Jim stapleton...@gmail.com wrote: I was working on an application I've been developing, and I closed the last instance a bit over 12 hours ago, but some of the sockets are still stuck in use: [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED Is there any way to get rid of them without restarting the machine? I was playing with sockopt SO_KEEPALIVE and SO_LINGER when I caused this issue.. sockstat(1) will tell you process that has the socket open, can you kill it from there? -- Adam Vande More Thanks... That told me who to kill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
sockets stuck in use
I was working on an application I've been developing, and I closed the last instance a bit over 12 hours ago, but some of the sockets are still stuck in use: [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED Is there any way to get rid of them without restarting the machine? I was playing with sockopt SO_KEEPALIVE and SO_LINGER when I caused this issue.. Thanks, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sockets stuck in use
Jim stapleton...@gmail.com writes: I was working on an application I've been developing, and I closed the last instance a bit over 12 hours ago, but some of the sockets are still stuck in use: [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED Is there any way to get rid of them without restarting the machine? I was playing with sockopt SO_KEEPALIVE and SO_LINGER when I caused this issue.. Does tcpdrop(8) help? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sockets stuck in use
On Mon, Jul 19, 2010 at 10:20 AM, Anonymous swel...@gmail.com wrote: Jim stapleton...@gmail.com writes: I was working on an application I've been developing, and I closed the last instance a bit over 12 hours ago, but some of the sockets are still stuck in use: [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED Is there any way to get rid of them without restarting the machine? I was playing with sockopt SO_KEEPALIVE and SO_LINGER when I caused this issue.. Does tcpdrop(8) help? No, the result (The first command is what I figured would be correct, given the man page, the second was just to be paranoid - although this machine is both the host and destination, having glommed onto several ports. The .80 IPs are within the web server's jail. I cannot tcpdrop within the jail [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED [s...@elrond ~/dev/pipe/scripts]$ sudo tcpdrop 192.168.1.80 46116 192.168.1.2 9612 tcpdrop: 192.168.1.80 46116 192.168.1.2 9612: No such process [s...@elrond ~/dev/pipe/scripts]$ sudo tcpdrop 192.168.1.2 9612 192.168.1.80 46116 tcpdrop: 192.168.1.2 9612 192.168.1.80 46116: No such process [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED [s...@elrond ~/dev/pipe/scripts]$ cd /data/jail/ [s...@elrond /data/jail]$ sudo ./bilbo_web_shell [r...@bilbo_web /data/jail]# tcpdrop 192.168.1.80 46116 192.168.1.2 9612 tcpdrop: 192.168.1.80 46116 192.168.1.2 9612: Operation not permitted Thanks, -Jim Stapleton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sockets stuck in use
On Mon, Jul 19, 2010 at 3:12 AM, Jim stapleton...@gmail.com wrote: I was working on an application I've been developing, and I closed the last instance a bit over 12 hours ago, but some of the sockets are still stuck in use: [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612 tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_SENT tcp4 0 0 192.168.1.80.35742 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.46116 192.168.1.2.9612 CLOSED tcp4 0 0 192.168.1.80.36792 192.168.1.2.9612 CLOSED Is there any way to get rid of them without restarting the machine? I was playing with sockopt SO_KEEPALIVE and SO_LINGER when I caused this issue.. sockstat(1) will tell you process that has the socket open, can you kill it from there? -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Server cannot boot : mount root got stuck
Fellow FreeBSDians, I am experiencing a problem with my FreeBSD server box. I can't get the system up. when I boot the machine its boots asking for boot options, and going with the default boot option This is an old freeBSD server box with FreeBSD-6.1 then its reaching mount root after that nothing, its stuck on this prompt mount root mount root I didn't do anything, day before yesterday its working.. Yesterday when I tried to login from my desktop , it not allowing me to login through my ssh keys so I checked physically the server and connected a monitor, seeing the boot splash image is garbled with some alphabetic characters.. and tried to reboot, hardware reboot. But it reaching the boot splash image of FreeBSD with boot options displayed, but what ever boot option I select , it not going further, but reboots again to the boot splash image screen. Today morning I just took its hard disk and connected to another box having same specs Then I started the box, with the harddisk of my server ..., then it going after the boot, so I thought issues over... But my bad, this time it comes to a prompt mount root and stuck there.. No key board inputs works in mount root prompt Any hints to recover this issue, most appreciated, and this is a production server , and I want it up as early as possible. Thanks in Advance Dhanesh _ Bollywood This Decade http://entertainment.in.msn.com/bollywoodthisdecade/___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Server cannot boot : mount root got stuck
From: dhaneshk k dhanes...@hotmail.com To: freebsd-questions@freebsd.org Sent: Friday, July 2, 2010 12:26:34 AM Subject: Server cannot boot : mount root got stuck Fellow FreeBSDians, I am experiencing a problem with my FreeBSD server box. I can't get the system up. when I boot the machine its boots asking for boot options, and going with the default boot option This is an old freeBSD server box with FreeBSD-6.1 then its reaching mount root after that nothing, its stuck on this prompt mount root mount root I didn't do anything, day before yesterday its working.. Yesterday when I tried to login from my desktop , it not allowing me to login through my ssh keys so I checked physically the server and connected a monitor, seeing the boot splash image is garbled with some alphabetic characters.. and tried to reboot, hardware reboot. But it reaching the boot splash image of FreeBSD with boot options displayed, but what ever boot option I select , it not going further, but reboots again to the boot splash image screen. Today morning I just took its hard disk and connected to another box having same specs Then I started the box, with the harddisk of my server ..., then it going after the boot, so I thought issues over... But my bad, this time it comes to a prompt mount root and stuck there.. When you moved the disk to the other server, the device name probably was changed. When you get a working keyboard, you can use '?' at that prompt to see what devices GEOM knows about or determine it from the boot messages. No key board inputs works in mount root prompt Odd. Are you using a USB keyboard? Any hints to recover this issue, most appreciated, and this is a production server , and I want it up as early as possible. Thanks in Advance Dhanesh _ Bollywood This Decade http://entertainment.in.msn.com/bollywoodthisdecade/___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
gnome install: stuck
Laptop with Freebsd 8.0, with gnome installed and gdm_enable=YES gnome_enable=YES in /etc/rc.conf, no changes to /etc/ttys (that is: ttyv8 ... xdm off) After reboot, system starts in gnome, gives a greenish background, a taskbar at the bottom, with only date/time, a button for 'Universal access preferences' and an icon for the battery. In the desktop a grey window with 2 buttons labeled 'Restart' and 'Shutdown'. Clicking either of them makes them be blueish for the time the mouse button in pressed, but nothing happens. I am stuck in Gnome. Why and how to solve it ? (I can only do Ctrl-Alt-F1 to get to the command prompt, but even that I have to do twice: the first time it gives a flickering almost entirely black screen with at the top some half line of flickering ascii characters (can't read), doing a Ctrl-Alt-F9 (back to gnome) and again Ctrl-Alt-F1 gives me a stable login: prompt.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gnome install: stuck
On Mon, Mar 8, 2010 at 12:46 AM, n dhert ndhert...@gmail.com wrote: Laptop with Freebsd 8.0, with gnome installed and gdm_enable=YES gnome_enable=YES in /etc/rc.conf, no changes to /etc/ttys (that is: ttyv8 ... xdm off) After reboot, system starts in gnome, gives a greenish background, a taskbar at the bottom, with only date/time, a button for 'Universal access preferences' and an icon for the battery. In the desktop a grey window with 2 buttons labeled 'Restart' and 'Shutdown'. Clicking either of them makes them be blueish for the time the mouse button in pressed, but nothing happens. I am stuck in Gnome. Why and how to solve it ? (I can only do Ctrl-Alt-F1 to get to the command prompt, but even that I have to do twice: the first time it gives a flickering almost entirely black screen with at the top some half line of flickering ascii characters (can't read), doing a Ctrl-Alt-F9 (back to gnome) and again Ctrl-Alt-F1 gives me a stable login: prompt.) Sounds like you are in GDM, not gnome. There's probably a login button somewhere, you need to authenticate with the system then you'll be logged into the desktop. Also, it's just Alt-F9 to return to the graphical display, ctrl not needed there. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Making installworld got stuck on SunFire v20z (Freebsd 8.0)
Lucas Wang wrote: I tried to install Freebsd 8.0 on one of our lab machines, which is SunFire v20z. After successfully installing it from CD, I followed the following steps trying to update the kernel and world: cvsup make buildworld make buildkernel make installkernel reboot mergemaster -p make installworld Everything was fine until the `make installworld` process run for a while and then got stuck, after that it won't respond to Ctrl-C. When I tried to login from another tty, it doesn't respond either. I even tried installing the machine from scratch several times, and at different times it got stuck when installing different libraries. I would really appreciate any ideas about why this could happen or how to solve it. If you have an AMD CPU of a recent generation, Try adding vm.pmap.pg_ps_enabled=0 to /boot/loader.conf and rebooting. This disables Superpages - there is a CPU bug on some of those. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Making installworld got stuck on SunFire v20z (Freebsd 8.0)
Thanks for your reply. I'll give it a try. Lucas On Feb 20, 2010, at 5:00 PM, Ivan Voras wrote: Lucas Wang wrote: I tried to install Freebsd 8.0 on one of our lab machines, which is SunFire v20z. After successfully installing it from CD, I followed the following steps trying to update the kernel and world: cvsup make buildworld make buildkernel make installkernel reboot mergemaster -p make installworld Everything was fine until the `make installworld` process run for a while and then got stuck, after that it won't respond to Ctrl-C. When I tried to login from another tty, it doesn't respond either. I even tried installing the machine from scratch several times, and at different times it got stuck when installing different libraries. I would really appreciate any ideas about why this could happen or how to solve it. If you have an AMD CPU of a recent generation, Try adding vm.pmap.pg_ps_enabled=0 to /boot/loader.conf and rebooting. This disables Superpages - there is a CPU bug on some of those. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Making installworld got stuck on SunFire v20z (Freebsd 8.0)
On Thu, 18 Feb 2010, Lucas Wang spaketh thusly: -}I tried to install Freebsd 8.0 on one of our lab machines, which is -}SunFire v20z. After successfully installing it from CD, I followed the -}following steps trying to update the kernel and world: -} -}cvsup -}make buildworld -}make buildkernel -}make installkernel -}reboot -}mergemaster -p -}make installworld -} -}Everything was fine until the `make installworld` process run for a while and then got stuck, -}after that it won't respond to Ctrl-C. When I tried to login from another tty, it -}doesn't respond either. I even tried installing the machine from scratch -}several times, and at different times it got stuck when installing different libraries. Hard tellin'. When you tried to install from scratch, did you keep the same partitions and not force a newfs? When you rebooted, did you reboot into single-user? The steps that have never failed me are close to what you have: - csup - env -i make buildworld - env -i make buildkernel - env -i make installkernel - reboot into single user - mount -a - mergemaster -paU - make installworld - mergemaster -aU - reboot Perhaps try a re-install but fiddle a bit with the partition sizes and/or force a newfs of the partitions. Also, at the install step where you select the entire drive (assuming this is what you are doing), you can delete what's there and re-select use the entire drive. That also forces newfs'ing. YMMV -- Randy(schu...@earlham.edu) 765.983.1283 * Love with your heart, think with your head; not the other way around. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Making installworld got stuck on SunFire v20z (Freebsd 8.0)
I tried to install Freebsd 8.0 on one of our lab machines, which is SunFire v20z. After successfully installing it from CD, I followed the following steps trying to update the kernel and world: cvsup make buildworld make buildkernel make installkernel reboot mergemaster -p make installworld Everything was fine until the `make installworld` process run for a while and then got stuck, after that it won't respond to Ctrl-C. When I tried to login from another tty, it doesn't respond either. I even tried installing the machine from scratch several times, and at different times it got stuck when installing different libraries. I would really appreciate any ideas about why this could happen or how to solve it. Lucas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD AMD64 7.1 LAST_ACK stuck
Hello, I'm running FreeBSD AMD64 7.1-p4 After the server experienced a DoS attack, it ended up with many sockets stuck in LACK_ACK state as reported by netstat -na Is this a bug or something else is wrong, how would I troubleshoot this? Please CC me. Thank you very much! Simon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
IBM T43 - iwi0 firmware stuck issue
Hello List , I am new in this list , so if these is an old topic forgive me.I have successfully installed FreeBSD 7.2 to IBM T43 Laptop.I am using wireless network with WPA key.My Laptop has Intel Pro Wireless 2200.I installed iwi driver and firmware successfully. I am successfully connecting to my home and ofis wireless networks with wpa supplicant.However every 4 or 5 minutes my connection gets down and i got iwi0: firmware stuck in state 4 , resetting and then iwi0 device timeout errors.These drops my connection , after that it take 30 seconds to my connection come back up.Then after 5 minutes again same errors and these goes on. I search a little bit on Google however find nothing usefull. Is there anybody who faced with same problem? And is there any solutions or upgrades for that issue. Best Regards Siyan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2 system stuck trying at boot, trying to mount root device
On Wed, Jun 24, 2009 at 8:57 PM, Polytropon free...@edvax.de wrote: On Wed, 24 Jun 2009 14:13:41 -0400, Forrest Aldrich for...@gmail.com wrote: I also did a proper mount, fsck, and umount under the LiveFS shell, which made no difference. I hope I'm just reading it in the wrong order. The correct order is to 1st fsck, then mount, not vice versa. Never fsck a mounted file system. The other messages I see on the console include GEOM output: GEOM_LABEL: Label for provider ad4s1a is ufsid/blahblah then GEOM_LABEL: Label for ufsid/blahblah removed. This is completely normal today. As long as a file system is not mounted, the label is provided. When it gets mounted, this label is being removed. You see this on your console. Anyone know how I can rescue this? Does /var/log/messages show something strange looking? I experienced similar behaviour recently when i had built kernel+userland with -fomit-frame-pointer. I ended up doing a repair from an install CD, and rebuilding kernel+world without -fomit-frame-pointer afterwards. Your init is probably broken. regards, usleepless -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
7.2 system stuck trying at boot, trying to mount root device
I'm running a modest PC that has FreeBSD-7.2 installed (fairly current build from CVS). Today, I did a shutdown -r to reboot the system. When it returned, the console is reporting: Trying to mount root from ufs:/dev/ad4s1a I've gone through and restored the boot loader, this works fine (it's back to F1 or F2) -- it continues to do this. I also did a proper mount, fsck, and umount under the LiveFS shell, which made no difference. Then I tried a modest binary upgrade just in case. No luck. After Googling around, and not finding much more info than what I did, I figured I would ask here. If I have to, I can ship off the data to another system (after I rebuild) and try to bring all it's functions back (but it's a lot, cyrus, etc). The other messages I see on the console include GEOM output: GEOM_LABEL: Label for provider ad4s1a is ufsid/blahblah then GEOM_LABEL: Label for ufsid/blahblah removed. Anyone know how I can rescue this? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2 system stuck trying at boot, trying to mount root device
On Wed, 24 Jun 2009 14:13:41 -0400, Forrest Aldrich for...@gmail.com wrote: I also did a proper mount, fsck, and umount under the LiveFS shell, which made no difference. I hope I'm just reading it in the wrong order. The correct order is to 1st fsck, then mount, not vice versa. Never fsck a mounted file system. The other messages I see on the console include GEOM output: GEOM_LABEL: Label for provider ad4s1a is ufsid/blahblah then GEOM_LABEL: Label for ufsid/blahblah removed. This is completely normal today. As long as a file system is not mounted, the label is provided. When it gets mounted, this label is being removed. You see this on your console. Anyone know how I can rescue this? Does /var/log/messages show something strange looking? -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to reset a connection stuck in CLOSE_WAIT state
Hi, I am runnig FlexNet license manager on FreeBSD (6.4), this is alinux application, but it is running smoothly. The problem occurs sometime at stop time, it will not stop cleanly and leave a connection in CLOSE_WAIT state. As a result, the ports are not freed and the license managerserver cannot restart. Is there a simple way to force reset the hanging connection? Best regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to reset a connection stuck in CLOSE_WAIT state
On Wed, Jun 03, 2009 at 05:38:24PM +0700, Olivier Nicole wrote: Hi, I am runnig FlexNet license manager on FreeBSD (6.4), this is alinux application, but it is running smoothly. The problem occurs sometime at stop time, it will not stop cleanly and leave a connection in CLOSE_WAIT state. As a result, the ports are not freed and the license managerserver cannot restart. Is there a simple way to force reset the hanging connection? /usr/sbin/tcpdrop maybe? Not sure it would reset/kill the connection immediately though. You'll have to try it. Best regards, Olivier -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to reset a connection stuck in CLOSE_WAIT state
On Wed, Jun 03, 2009 at 05:38:24PM +0700, Olivier Nicole wrote: Hi, I am runnig FlexNet license manager on FreeBSD (6.4), this is alinux application, but it is running smoothly. The problem occurs sometime at stop time, it will not stop cleanly and leave a connection in CLOSE_WAIT state. As a result, the ports are not freed and the license managerserver cannot restart. Is there a simple way to force reset the hanging connection? Best regards, Olivier I think tcpdrop(8) can handle that. -- Best regards, Jeff | Nobody wants to say how this works. | | Maybe nobody knows ... | | Xorg.conf(5)| ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
firefox3 gets stuck/freezing for 30 seconds every 30 seconds
Since a week now my firefox3 got stuck and freezing for 30 seconds (approx.) every 30 seconds. I'm running a SMP box with FreeBSD 8.0-CURRENT/amd64, OS is most recent. I also recompiled firefox3, dbus, libX11 and xcb (maybe senseless since I do not know what causes the freezing/hungs), but without success. By the way, perl-5.10 is installed and every port has been recompiled depending on perl. So ... I'm floating like a dead man in the water. What can I do? Regards, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: firefox3 gets stuck/freezing for 30 seconds every 30 seconds
Since a week now my firefox3 got stuck and freezing for 30 seconds (approx.) every 30 seconds. I'm running a SMP box with FreeBSD 8.0-CURRENT/amd64, OS is most recent. I also recompiled firefox3, dbus, libX11 and xcb (maybe senseless since I do not know what causes the freezing/hungs), but without success. By the way, perl-5.10 is installed and every port has been recompiled depending on perl. So ... I'm floating like a dead man in the water. What can I do? Something like this happened to me. I have i386 CURRENT cvsup'ed yesterday. Do you have flash support with nspluginwrapper ? Do you have linux-f8 and compat.linux.osrelease=2.6.16 ? If both are true, please try compat.linux.osrelease=2.4.2 and switch back to f4. With these settings problems vanished in my case, may be they will work for you too. Looks like linux 2.6.16 emulation has problems with flash9. Can anyone confirm this ? Regards, Gus Regards, Oliver ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ultranav usb keyboard panics on bootup -- stuck
Hi All Anybody know how I work around the following panic ?? panic: ohci_add_done: addr 0x7fef1c30 not found cpuid = 0 Uptime: 1s I have just purchased a new Lenovo ultranav usb keyboard from . (My old ibm ps/2 one died) http://uk.insight.com/apps/productpresentation/index.php?product_id=LEN31P9304nbs_search=C%3D106%26S%3D1040%26lang%3Den-gb%26K%3D%26M%3DLEN The panic is definitely happening because of the usb keyboard (with integrated mouse), if I take it out and replace with a ps/2 counterpart the computer boots up normally. Regards Craig Butler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Ath vs Netgear wg311t stuck beacon error
I am having trouble getting a Netgear WG311t card to work, I had tried 7.1beta but kept getting irq interrupt storm no matter what slot or irq was set to the slot/card. Installed 6.3, stuck beacon error. I have tried a, b, and g mode. I have tested the card with other os's to see if was hardware. ifconfig ath0 up ifconfig ath0 inet 10.10.1.14 netmask 255.255.255.0 ssid myap media 11g mediaopt hostap from /var/log/messages Nov 17 21:21:07 wall kernel: ath0: stuck beacon; resetting (bmiss count 4) Nov 17 21:21:25 wall last message repeated 30 times Nov 17 21:21:25 wall syslogd: exiting on signal 15 Nov 17 21:22:18 wall syslogd: kernel boot file is /boot/kernel/kernel Nov 17 21:22:18 wall kernel: ath0: stuck beacon; resetting (bmiss count 4) Nov 17 21:22:18 wall last message repeated 2 times Nov 17 21:22:18 wall kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done Nov 17 21:22:18 wall kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...ath0: stuck beacon; resetting ( Nov 17 21:22:18 wall kernel: done Nov 17 21:22:18 wall kernel: Waiting (max 60 seconds) for system process `syncer' to stop...ath0: stuck beacon; resetting (bmi Nov 17 21:22:18 wall kernel: ath0: stuck beacon; resetting (bmiss count 4) Nov 17 21:22:18 wall kernel: Nov 17 21:22:18 wall kernel: Syncing disks, vnodes remaining...1 ath0: stuck beacon; resetting (bmiss count 4) Nov 17 21:22:18 wall kernel: 1 ath0: stuck beacon; resetting (bmiss count 4) Nov 17 21:22:18 wall kernel: ath0: stuck beacon; resetting (bmiss count 4) Nov 17 21:22:18 wall kernel: 0 ath0: stuck beacon; resetting (bmiss count 4) Nov 17 21:22:18 wall kernel: 0 ath0: stuck beacon; resetting (bmiss count 4) Nov 17 21:22:18 wall kernel: ath0: stuck beacon; resetting (bmiss count 4) wall# vmstat -i interrupt total rate irq1: atkbd0 94 0 irq15: ata1 47 0 irq17: ath0 228298 33 irq20: atapci0 4678 0 irq23: vr0 2338 0 cpu0: timer 13615967 1999 Total 13851422 2034 pciconf -lv [EMAIL PROTECTED]:0:0: class=0x06 card=0x1b451019 chip=0x02041106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8M400 CPU to PCI Bridge' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:1:class=0x06 card=0x chip=0x12041106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8M400 CPU to PCI Bridge' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:2:class=0x06 card=0x chip=0x22041106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8M400 CPU to PCI Bridge' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:3:class=0x06 card=0x chip=0x32041106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = '1394 i2c CPU to PCI Bridge' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:4:class=0x06 card=0x chip=0x42041106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8M400 CPU to PCI Bridge' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:7:class=0x06 card=0x chip=0x72041106 rev=0x00 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'K8M400 CPU to PCI Bridge' class = bridge subclass = HOST-PCI [EMAIL PROTECTED]:1:0: class=0x060400 card=0x chip=0xb1881106 rev=0x00 hdr=0x01 vendor = 'VIA Technologies Inc' device = 'VT8237 K8HTB CPU to AGP 2.0/3.0 Bridge' class = bridge subclass = PCI-PCI [EMAIL PROTECTED]:9:0: class=0x02 card=0x700c1799 chip=0x001a168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'Atheros AR5005G Atheros AR5005G 802.11abg NIC Chipset / TP-Link (TL-WN551G)' class = network subclass = ethernet [EMAIL PROTECTED]:10:0: class=0x02 card=0x05701317 chip=0x09851317 rev=0x11 hdr=0x00 vendor = 'ADMtek Inc' device = 'AN983 FastNIC PCI 10/100 Fast Ethernet Adapter' class = network subclass = ethernet [EMAIL PROTECTED]:15:0: class=0x01018f card=0x1b451019 chip=0x31491106 rev=0x80 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8237 VT6410 SATA RAID Controller' class = mass storage subclass = ATA [EMAIL PROTECTED]:15:1: class=0x01018a card=0x1b451019 chip=0x05711106 rev=0x06 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT82C586A/B/VT82C686/A/B/VT823x/A/C Bus Master IDE Controller' class = mass storage subclass = ATA [EMAIL PROTECTED]:16:0:class=0x0c0300 card=0x1b451019 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA
RE: Upgrade 6.2-Release to 7.0-Release - stuck!
Righty - now that I'm back from my wanderings I've managed to complete the upgrade from 6.3 to 7.0-RELEASE, but am still getting issues with named not starting. For reference, I pulled down a clean 7.0-R version of named.conf and dropped it in as /etc/named.conf /var/log/messages shows the following (lots): Jul 30 14:39:53 bigsis root: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/local/sbin/named Weird thing? Course it can't run /usr/local/sbin/named as it ain't there - it's at /usr/sbin/named, BUT, /etc/rc.d/named has the location correct so I'm not sure where anything is getting reference to /usr/local/sbin... Marc A Coyles ICT Support Team (ext 730) Mbl: 07850 518106 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade 6.2-Release to 7.0-Release - stuck!
Marc Coyles wrote: Righty - now that I'm back from my wanderings I've managed to complete the upgrade from 6.3 to 7.0-RELEASE, but am still getting issues with named not starting. For reference, I pulled down a clean 7.0-R version of named.conf and dropped it in as /etc/named.conf /var/log/messages shows the following (lots): Jul 30 14:39:53 bigsis root: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/local/sbin/named Weird thing? Course it can't run /usr/local/sbin/named as it ain't there - it's at /usr/sbin/named, BUT, /etc/rc.d/named has the location correct so I'm not sure where anything is getting reference to /usr/local/sbin... Have you changed named_program in either /etc/rc.conf or /etc/defaults/rc.conf ? as a quick check, for file in /etc/rc.conf /etc/defaults/rc.conf ; do grep -H named_program $file ; done should return /etc/defaults/rc.conf:named_program=/usr/sbin/named# path to named, if you want a different one. if you havent Vince Marc A Coyles ICT Support Team (ext 730) Mbl: 07850 518106 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrade 6.2-Release to 7.0-Release - stuck!
OK - further developments! Got to the first reboot stage after running sh freebsd-update.sh -f freebsd-update.conf install First point to note: If you don't want a sudden panic attack, remember to remove the non-bootable floppy disk from the drive. Other than that, all has gone to plan and is working fine, other than named which is failing - at a guess because I ended up with the original file rather than the new file. Can anyone point me to where I can get me grubby l'il mits on a clean named.conf from 7.0-RELEASE? Marc A Coyles ICT Support Team (ext 730) Mbl: 07850 518106 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade 6.2-Release to 7.0-Release - stuck!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marc Coyles wrote: | OK - further developments! Got to the first reboot stage after running sh | freebsd-update.sh -f freebsd-update.conf install | | First point to note: If you don't want a sudden panic attack, remember to | remove the non-bootable floppy disk from the drive. | | Other than that, all has gone to plan and is working fine, other than named | which is failing - at a guess because I ended up with the original file | rather than the new file. Can anyone point me to where I can get me grubby | l'il mits on a clean named.conf from 7.0-RELEASE? | | | Marc A Coyles | ICT Support Team (ext 730) | Mbl: 07850 518106 | Hi Marc, Very good - glad you got everything working! You can pull the named.conf directly from FreeBSD's CVSweb interface: http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/etc/namedb/named.conf?rev=1.26.4.1;content-type=text%2Fplain;only_with_tag=RELENG_7_0_0_RELEASE Best regards, Greg - -- Greg Larkin http://www.sourcehosting.net/ http://www.FreeBSD.org/ - The Power To Serve -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIiHcg0sRouByUApARAnPVAJ94RfT7eCqvVunOO6XluavGZaEuwACgufeA LU/116zUPixfBF0F30MWdco= =4jJc -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrade 6.2-Release to 7.0-Release - stuck!
Am running freebsd-update following instructions at
http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.htm
l
Its decided that it cant merge named.conf changes automagically and has
dropped me into vi with the file open
looking as below. What exactly is it
wanting me to do? Tisnt particularly clear, and this is the first time
Ive ever attempted an upgrade
current version
include /etc/namedb/rndc.key;
controls {
inet 127.0.0.1 allow { localhost; } keys { rndc-key; };
};
// $FreeBSD: src/etc/namedb/named.conf,v 1.21.2.1 2005/09/10 08:27:27 dougb
Exp
$
===
// $FreeBSD: src/etc/namedb/named.conf,v 1.26.4.1 2008/01/13 20:48:23 dougb
Exp
$
7.0-RELEASE
//
// Refer to the named.conf(5) and named(8) man pages, and the documentation
// in /usr/share/doc/bind9 for more details.
//
// If you are going to set up an authoritative server, make sure you
// understand the hairy details of how DNS works. Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.
options {
current version
pid-file /var/run/named/pid;
===
// Relative to the chroot directory, if any
7.0-RELEASE
directory /etc/namedb;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats;
// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
listen-on { 127.0.0.1; };
// If you have IPv6 enabled on this system, uncomment this option for
// use as a local resolver. To give access to the network, specify
// an IPv6 address, or the keyword any.
// listen-on-v6{ ::1; };
// These zones are already covered by the empty zones listed below.
// If you remove the related empty zones below, comment these lines out.
disable-empty-zone 255.255.255.255.IN-ADDR.ARPA;
disable-empty-zone
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.IP6.ARPA;
disable-empty-zone
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.IP6.ARPA;
// In addition to the forwarders clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
// forward only;
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
forwarders {
127.0.0.1;
};
*/
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND versions 8 and later
* use a pseudo-random unprivileged UDP port by default.
*/
// query-source address * port 53;
};
// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.
// The traditional root hints mechanism. Use this, OR the slave zones below.
zone . { type hint; file named.root; };
/* Slaving the following zones from the root name servers has some
significant advantages:
1. Faster local resolution for your users
2. No spurious traffic will be sent from your network to the roots
3. Greater resilience to any potential root server failure/DDoS
On the other hand, this method requires more monitoring than the
hints file to be sure that an unexpected failure mode has not
incapacitated your server. Name servers that are serving a lot
of clients will benefit more from this approach than individual
hosts. Use with caution.
To use this mechanism, uncomment the entries below, and comment
the hint zone above.
*/
/*
zone . {
current version
type hint;
file /etc/namedb/named.root;
===
type slave;
file slave/root.slave;
masters {
192.5.5.241;// F.ROOT-SERVERS.NET.
};
notify no;
7.0-RELEASE
};
current version
zone 0.0.127.IN-ADDR.ARPA {
type master;
file /etc/namedb/localhost.rev;
===
zone arpa {
type slave;
file slave/arpa.slave;
masters {
192.5.5.241;// F.ROOT-SERVERS.NET.
};
notify no;
7.0-RELEASE
};
current version
// RFC 3152
zone
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
{
type master;
file /etc/namedb/localhost-v6.rev;
===
zone in-addr.arpa {
type slave;
file slave/in-addr.arpa.slave;
masters {
Re: Upgrade 6.2-Release to 7.0-Release - stuck!
Marc Coyles wrote:
Am running freebsd-update following instructions at
http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.htm
l
I did similar recently, although I went from 6.2 to 6.3 then to 7
(almost certainly not necessary though.)
It’s decided that it can’t merge named.conf changes automagically and has
dropped me into vi with the file open… looking as below. What exactly is it
wanting me to do? T’isn’t particularly clear, and this is the first time
I’ve ever attempted an upgrade…
Basicly, its saying the current version contains whatever it lists up to
the
===
and the 7 release version has whatever is after the seperator, up to the
7.0-RELEASE
and you need to edit it to say what you want it to be. If you have never
modifed the file, just delete the current stuff and leave the
7.0-RELEASE stuff. I have a very customised named.conf so i just said
that whatever was fine and then restored it from backup after the
upgrade was finished.
Vince
current version
include /etc/namedb/rndc.key;
controls {
inet 127.0.0.1 allow { localhost; } keys { rndc-key; };
};
// $FreeBSD: src/etc/namedb/named.conf,v 1.21.2.1 2005/09/10 08:27:27 dougb
Exp
$
===
// $FreeBSD: src/etc/namedb/named.conf,v 1.26.4.1 2008/01/13 20:48:23 dougb
Exp
$
7.0-RELEASE
//
// Refer to the named.conf(5) and named(8) man pages, and the documentation
// in /usr/share/doc/bind9 for more details.
//
// If you are going to set up an authoritative server, make sure you
// understand the hairy details of how DNS works. Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.
options {
current version
pid-file /var/run/named/pid;
===
// Relative to the chroot directory, if any
7.0-RELEASE
directory /etc/namedb;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats;
// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
listen-on { 127.0.0.1; };
// If you have IPv6 enabled on this system, uncomment this option for
// use as a local resolver. To give access to the network, specify
// an IPv6 address, or the keyword any.
// listen-on-v6{ ::1; };
// These zones are already covered by the empty zones listed below.
// If you remove the related empty zones below, comment these lines out.
disable-empty-zone 255.255.255.255.IN-ADDR.ARPA;
disable-empty-zone
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.IP6.ARPA;
disable-empty-zone
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.IP6.ARPA;
// In addition to the forwarders clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
// forward only;
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
forwarders {
127.0.0.1;
};
*/
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND versions 8 and later
* use a pseudo-random unprivileged UDP port by default.
*/
// query-source address * port 53;
};
// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.
// The traditional root hints mechanism. Use this, OR the slave zones below.
zone . { type hint; file named.root; };
/* Slaving the following zones from the root name servers has some
significant advantages:
1. Faster local resolution for your users
2. No spurious traffic will be sent from your network to the roots
3. Greater resilience to any potential root server failure/DDoS
On the other hand, this method requires more monitoring than the
hints file to be sure that an unexpected failure mode has not
incapacitated your server. Name servers that are serving a lot
of clients will benefit more from this approach than individual
hosts. Use with caution.
To use this mechanism, uncomment the entries below, and comment
the hint zone above.
*/
/*
zone . {
current version
type hint;
file /etc/namedb/named.root;
===
type slave;
file slave/root.slave;
masters {
192.5.5.241;
Re: Upgrade 6.2-Release to 7.0-Release - stuck!
Marc Coyles wrote:
Am running freebsd-update following instructions at
http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html
It’s decided that it can’t merge named.conf changes automagically and has
dropped me into vi with the file open… looking as below. What exactly is it
wanting me to do? T’isn’t particularly clear, and this is the first time
I’ve ever attempted an upgrade…
It's [apparently] expecting you to use vi to create a named.conf
that will work, and showing you the contents of both the old
named.conf and the one found in 7.0-RELEASE. I'm not familiar
with freebsd-update (still using the old csup/buildworld routine)
but it sure look like mergemaster, more or less, except that
mergemaster not only allowed you to leave it until later and
do the merge by hand but also had a two-column diff with
a selector routine, so you could create a merged version
on-the-fly.
Is the box an important DNS server? What happens if you just
save the file as is and try and come back to it later? (YMMV,
standard disclaimer, and all that). if you've *never* edited
named.conf before, you'd probably be OK to just remove all the
current version stuff in favor of the 7.0-RELEASE stuff, *but*
generally all my boxen *have* been altered, so that wouldn't
work.
current version
include /etc/namedb/rndc.key;
controls {
inet 127.0.0.1 allow { localhost; } keys { rndc-key; };
};
// $FreeBSD: src/etc/namedb/named.conf,v 1.21.2.1 2005/09/10 08:27:27 dougb
Exp
$
===
// $FreeBSD: src/etc/namedb/named.conf,v 1.26.4.1 2008/01/13 20:48:23 dougb
Exp
$
7.0-RELEASE
//
// Refer to the named.conf(5) and named(8) man pages, and the documentation
// in /usr/share/doc/bind9 for more details.
//
// If you are going to set up an authoritative server, make sure you
// understand the hairy details of how DNS works. Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.
options {
current version
pid-file /var/run/named/pid;
===
// Relative to the chroot directory, if any
7.0-RELEASE
directory /etc/namedb;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats;
// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
listen-on { 127.0.0.1; };
// If you have IPv6 enabled on this system, uncomment this option for
// use as a local resolver. To give access to the network, specify
// an IPv6 address, or the keyword any.
// listen-on-v6{ ::1; };
// These zones are already covered by the empty zones listed below.
// If you remove the related empty zones below, comment these lines out.
disable-empty-zone 255.255.255.255.IN-ADDR.ARPA;
disable-empty-zone
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.IP6.ARPA;
disable-empty-zone
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.IP6.ARPA;
// In addition to the forwarders clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
// forward only;
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
forwarders {
127.0.0.1;
};
*/
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND versions 8 and later
* use a pseudo-random unprivileged UDP port by default.
*/
// query-source address * port 53;
};
// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.
// The traditional root hints mechanism. Use this, OR the slave zones below.
zone . { type hint; file named.root; };
/* Slaving the following zones from the root name servers has some
significant advantages:
1. Faster local resolution for your users
2. No spurious traffic will be sent from your network to the roots
3. Greater resilience to any potential root server failure/DDoS
On the other hand, this method requires more monitoring than the
hints file to be sure that an unexpected failure mode has not
incapacitated your server. Name servers that are serving a lot
of clients will benefit more from this approach than individual
hosts. Use with caution.
To use this mechanism, uncomment the entries
RE: Upgrade 6.2-Release to 7.0-Release - stuck!
Have left as is (for now). Finish the rest off tomorrow... The box runs WHM
/ cPanel... and just holds a few vhosts under single domain. DNS is handled
by ISP's servers...
If anything in original was modified, it was done by WHM/cPanel, not me...
Am at the freebsd-update install point now... so will have another look at
things in the morning with fresh eyes...
Ta fer the suggestions folks!
Marc A Coyles
ICT Support Team (ext 730)
Mbl: 07850 518106
-Original Message-
From: Kevin Kinsey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2008 4:16 PM
To: [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Subject: Re: Upgrade 6.2-Release to 7.0-Release - stuck!
Marc Coyles wrote:
Am running freebsd-update following instructions at
http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.htm
l
Its decided that it cant merge named.conf changes automagically and has
dropped me into vi with the file open
looking as below. What exactly is
it
wanting me to do? Tisnt particularly clear, and this is the first time
Ive ever attempted an upgrade
It's [apparently] expecting you to use vi to create a named.conf
that will work, and showing you the contents of both the old
named.conf and the one found in 7.0-RELEASE. I'm not familiar
with freebsd-update (still using the old csup/buildworld routine)
but it sure look like mergemaster, more or less, except that
mergemaster not only allowed you to leave it until later and
do the merge by hand but also had a two-column diff with
a selector routine, so you could create a merged version
on-the-fly.
Is the box an important DNS server? What happens if you just
save the file as is and try and come back to it later? (YMMV,
standard disclaimer, and all that). if you've *never* edited
named.conf before, you'd probably be OK to just remove all the
current version stuff in favor of the 7.0-RELEASE stuff, *but*
generally all my boxen *have* been altered, so that wouldn't
work.
current version
include /etc/namedb/rndc.key;
controls {
inet 127.0.0.1 allow { localhost; } keys { rndc-key; };
};
// $FreeBSD: src/etc/namedb/named.conf,v 1.21.2.1 2005/09/10 08:27:27
dougb
Exp
$
===
// $FreeBSD: src/etc/namedb/named.conf,v 1.26.4.1 2008/01/13 20:48:23
dougb
Exp
$
7.0-RELEASE
//
// Refer to the named.conf(5) and named(8) man pages, and the
documentation
// in /usr/share/doc/bind9 for more details.
//
// If you are going to set up an authoritative server, make sure you
// understand the hairy details of how DNS works. Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.
options {
current version
pid-file /var/run/named/pid;
===
// Relative to the chroot directory, if any
7.0-RELEASE
directory /etc/namedb;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats;
// If named is being used only as a local resolver, this is a safe
default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
listen-on { 127.0.0.1; };
// If you have IPv6 enabled on this system, uncomment this option for
// use as a local resolver. To give access to the network, specify
// an IPv6 address, or the keyword any.
// listen-on-v6{ ::1; };
// These zones are already covered by the empty zones listed below.
// If you remove the related empty zones below, comment these lines out.
disable-empty-zone 255.255.255.255.IN-ADDR.ARPA;
disable-empty-zone
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.IP6.ARPA;
disable-empty-zone
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.IP6.ARPA;
// In addition to the forwarders clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
// forward only;
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the
Internet.
/*
forwarders {
127.0.0.1;
};
*/
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND versions 8 and later
* use a pseudo-random unprivileged UDP port by default.
*/
// query-source address * port 53;
};
// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.
// The traditional root hints mechanism
Sockets stuck in CLOSED state...
Dear All, Recently i've been upgrading some of my machines from FreeBSD 6.x amd64 to FreeBSD 7.0 amd64. After upgrading I noticed a weird error/bug. It seems that after several thousand TCP connections some seem to hang in 'CLOSED' state. netstat -n gives: ... tcp4 0 0 1.2.3.4.* 4.5.6.7.42149 CLOSED tcp4 39 0 1.2.3.4.* 4.5.6.7.54103 CLOSED tcp4 35 0 1.2.3.4.* 4.5.6.7.41718 CLOSED tcp4 38 0 1.2.3.4.* 4.5.6.7.55618 CLOSED tcp4 41 0 1.2.3.4.* 4.5.6.7.44230 CLOSED tcp4 39 0 1.2.3.4.* 4.5.6.7.49439 CLOSED ... These never go away; they gradually increase and increase until the application starts giving errors (probably because some socket or filedescriptor limit is reached). When the application is killed these entries disappear. The application in question is a self written DNS server, multithreaded, and running fine for years without any troubles on both BSD 5.x as well as 6.x. Also 32bits as well as 64bits on 6.x. Ofcourse that doesn't mean that the application is error free, however, after doing extensive testing I really can not find anything wrong with the application itself, so I'm thinking maybe there's a change somewhere that causes this? I know that tcp/network has been completely redone... What basically happens in the application is this: - one main tcp thread runs an infinite while loop waiting for new connections to arrive - as soon as one arrives a new thread is spawned that handles the newly created stream - it reads some bytes, writes some bytes, then closes it - thread exits What appears to happen is this: after the new thread is spawned it tries to read 2 bytes (DNS tcp length information). It gets back 0 bytes (EOF) and therefore closes the sockets and calls pthread_exit. However in netstat that same stream oftenly appears to have bytes 'stuck' in the in queue... I really can't see how this can cause hanging sockets in 'CLOSED' state. Even if the incoming queue isnt read entirely a call to close should close it. Also I really can't find any documentation in netstat, or elsewhere, about the 'CLOSED' state... Any help would greatly be appreciated! Kind Regards, Ali Niknam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sockets stuck in CLOSED state...
... tcp4 0 0 1.2.3.4.* 4.5.6.7.42149 CLOSED tcp4 39 0 1.2.3.4.* 4.5.6.7.54103 CLOSED tcp4 35 0 1.2.3.4.* 4.5.6.7.41718 CLOSED tcp4 38 0 1.2.3.4.* 4.5.6.7.55618 CLOSED tcp4 41 0 1.2.3.4.* 4.5.6.7.44230 CLOSED tcp4 39 0 1.2.3.4.* 4.5.6.7.49439 CLOSED ... These never go away; they gradually increase and increase until the application starts giving errors (probably because some socket or filedescriptor limit is reached). When the application is killed these entries disappear. The application in question is a self written DNS server, multithreaded, and running fine for years without any troubles on both BSD 5.x as well as 6.x. Also 32bits as well as 64bits on 6.x. do stupid thing - in your source add #define socket TEST_SOCKET #define connect TEST_CONNECT #define bind TEST_BIND #define listen TEST_LISTEN all other network functions you use same way here! and write one .c program where all these TEST_* functions are defined, doing the same as original PLUS logging to file. after a while (when you see this closed/unclosed connections) stop it and look at logs. i'm almost sure you will notice where is a problem. possibly threads implementation changed... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sockets stuck in CLOSED state...
Wojciech Puchar wrote: #define socket TEST_SOCKET ... and write one .c program where all these TEST_* functions are defined, doing the same as original PLUS logging to file. after a while (when you see this closed/unclosed connections) stop it and look at logs. Thank you for the suggestions. I had considered that myself, however the server is doing about 300 DNS queries per second, so that's not easy to log. And even if it is logged you have sooo much information that it's nearly impossible to comprehend it. The thing is that the problem does not occur always; the same ip can connect and do queries for thousands of times before 1 connection gets stuck. To give you an idea: after about 24 hours (so that's about 26 million queries) I get about 10 stuck connections. i'm almost sure you will notice where is a problem. possibly threads implementation changed... I can imagine; still, as far as I know, it should not be possible to be stuck in CLOSED... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tried to symlink /etc to another disk, now stuck
Steve Bertrand wrote, On 6/12/2008 7:09 PM:
Steve Bertrand wrote:
Dan Nelson wrote:
I'm off to try it. I've got a system here with a da device. I'll fsck
up /etc/fstab, reboot, and report back with the appropriate mountroot
prompt entry...
# cat /etc/fstab
# DeviceMountpoint FStype Options Dump Pass#
/dev/da0a / ufs rw,noatime 1 1
md /tmpmfs rw,-s32M,nosuid,noatime
0 0
(..snip..)
..change /etc/fstab to mount root to /dev/ad15a, reboot:
mountroot
# mountrootufs:/dev/da0a {ENTER}
...machine boots up.
To the OP...if you know what your disk type is, you CAN get it to
continue to mount root at the mountroot prompt.
Furthering that, you can also fsck and mount your other disk mountpoints
in order to gain access to your editing binaries.
There is no need to use an external resource to boot the machine from if
you are already aware that the only thing that got fsck'd up is the
mountpoints in the fstab (or, like in this case, the file was
unavailable entirely). The disk structure is still the same, and the
system can see this with manual intervention.
OP: at the mountroot prompt, try this: ufs:/dev/ad0s1a
and see if you get anywhere.
Steve
Thanks to Steve, Dan and Andrew for offering suggestions for regaining
access to my box!
I was finally able to mount / from the mountroot prompt using
ufs:/dev/aacd0s1a (this is a Dell PowerEdge server with a SCSI RAID5
array.) Fortunately, there was an /etc.old directory left over from the
last patch level upgrade I did; that was enough to get the system
booting normally so that I could copy back the former /etc directory
that I had moved at the start of this whole fiasco.
I think I will start retaining electronic and hard-copy fstab files from
my FreeBSD boxes for future reference, as Steve suggested in a later
message.
--
Glenn Gillis
ELAW U.S. Information Technology Manager
Environmental Law Alliance Worldwide
http://www.elaw.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Tried to symlink /etc to another disk, now stuck
I think I did just about the worst thing I could do to my organization's FreeBSD-4.11 email server today: I was trying to free up space on the root disk and attempted to copy the /etc directory to another disk, /new/etc, then delete and symlink the old location to the new: $ sudo cp -Rp /etc /new/etc $ sudo rm -rd /etc/; sudo ln -s /new/etc /etc Of course, with the sudoers file in the original /etc directory, the first sudo command to remove the /etc directory disabled the second sudo command's ability to run. Now, I cannot log in as a privileged user to copy or move /new/etc back to /etc. (Because the password files were also in /etc.) I've tried booting into Single User mode with boot -s at the boot prompt, only to receive a mountroot prompt wanting to know where to find the root filesystem. I've also tried booting from my installation distribution, but can't get out of the installation without the machine rebooting. To make a long story shorter, is there any hope for getting a privileged user account on this machine to move /etc back to where it should be? -- Glenn Gillis ELAW U.S. Information Technology Manager Environmental Law Alliance Worldwide http://www.elaw.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tried to symlink /etc to another disk, now stuck
Glenn Gillis wrote: Now, I cannot log in as a privileged user to copy or move /new/etc back to /etc. (Because the password files were also in /etc.) I've tried booting into Single User mode with boot -s at the boot prompt, only to receive a mountroot prompt wanting to know where to find the root filesystem. What type of disk(s) do you have in the box? I can't remember the exact syntax of the mountroot prompt, but I'll break one of my machines here to 'remind' myself if you know what driver you use for your root partition. ad (IDE) ar (RAID) da (SCSI) ...etc. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tried to symlink /etc to another disk, now stuck
In the last episode (Jun 12), Glenn Gillis said: I think I did just about the worst thing I could do to my organization's FreeBSD-4.11 email server today: I was trying to free up space on the root disk and attempted to copy the /etc directory to another disk, /new/etc, then delete and symlink the old location to the new: $ sudo cp -Rp /etc /new/etc $ sudo rm -rd /etc/; sudo ln -s /new/etc /etc Of course, with the sudoers file in the original /etc directory, the first sudo command to remove the /etc directory disabled the second sudo command's ability to run. Now, I cannot log in as a privileged user to copy or move /new/etc back to /etc. (Because the password files were also in /etc.) I've tried booting into Single User mode with boot -s at the boot prompt, only to receive a mountroot prompt wanting to know where to find the root filesystem. I've also tried booting from my installation distribution, but can't get out of the installation without the machine rebooting. To make a long story shorter, is there any hope for getting a privileged user account on this machine to move /etc back to where it should be? It may be easiest to boot a live CD (FreeSBIE, or a FreeBSD-7 install disc 1 should work), mount both of your hard drives from it, and put /etc back where it belongs that way. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tried to symlink /etc to another disk, now stuck
Dan Nelson wrote: To make a long story shorter, is there any hope for getting a privileged user account on this machine to move /etc back to where it should be? It may be easiest to boot a live CD (FreeSBIE, or a FreeBSD-7 install disc 1 should work), mount both of your hard drives from it, and put /etc back where it belongs that way. This is a very good point, but in this case, if its only /etc that has been relocated, the system is at mountroot because fstab can't be found. If the disk type is known, it is as simple as typing the appropriate location of the root fs at that prompt and the system will come up. Under single user, the OP would have full access to everything to revert the changes (perhaps other disk areas with binaries may have to be mounted manually as well)... I'm off to try it. I've got a system here with a da device. I'll fsck up /etc/fstab, reboot, and report back with the appropriate mountroot prompt entry... Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tried to symlink /etc to another disk, now stuck
Steve Bertrand wrote:
Dan Nelson wrote:
I'm off to try it. I've got a system here with a da device. I'll fsck up
/etc/fstab, reboot, and report back with the appropriate mountroot
prompt entry...
# cat /etc/fstab
# DeviceMountpoint FStype Options Dump
Pass#
/dev/da0a / ufs rw,noatime 1 1
md /tmpmfs rw,-s32M,nosuid,noatime
0 0
(..snip..)
..change /etc/fstab to mount root to /dev/ad15a, reboot:
mountroot
# mountrootufs:/dev/da0a {ENTER}
...machine boots up.
To the OP...if you know what your disk type is, you CAN get it to
continue to mount root at the mountroot prompt.
Furthering that, you can also fsck and mount your other disk mountpoints
in order to gain access to your editing binaries.
There is no need to use an external resource to boot the machine from if
you are already aware that the only thing that got fsck'd up is the
mountpoints in the fstab (or, like in this case, the file was
unavailable entirely). The disk structure is still the same, and the
system can see this with manual intervention.
OP: at the mountroot prompt, try this: ufs:/dev/ad0s1a
and see if you get anywhere.
Steve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
