Re: Updated to 13-STABLE in VirtualBox; on shutdown stuck after uhub[01] being detached
(Changed my email address to the one I used to subscribe to the mailing list.) On Wed, Apr 28, 2021 at 10:05 AM Guido Falsi wrote: Hi, On 28/04/21 00:12, parv wrote: > > I had updated FreeBSD, in VirtualBox 5.22 on Windows with EFI, from > > 12-STABLE > > to 13-STABLE; upgraded the ZFS pools & the EFI boot loader. Currently > > testing with 13 GENERIC kernel. > > You mean you enabled EFI inside virtualbox? Why do you need that? For testing if FreeBSD can boot with EFI (with ZFS-on-root) ... one day I may just install the thing directly on a disk, outside of a virtual machine ... one day! > EFI > support in VirtualBox is experimental and is available for OSes unable > to boot without EFI. FreeBSD is perfectly able to boot in virtualbox > without EFI so no need for it. > I am aware. > > Now on shutdown, "shutdown -p now" (in single user mode, after manually > > unmounting > > ZFS datasets [...] the shutting down process gets stuck, > > and CPU use jumps to 80% > ... > > In the end I chose "Power Off" from VirutalBox menu. "Reset" reboots the > > machine. > > None of these have any effect ... > >- Send the shutdown signal > >- ACPI Shutdown > > > > Help please. > Solved the issue via ... % sysctl hw.efi.poweroff=0 ... after that shudown went on as expected. Got that from ... https://forums.freebsd.org/threads/freebsd-13-does-not-shut-down-my-laptop.79853/ NOt sure even which further information to ask about this, but to be > sure I understand correctly, FreeBSD is the guest here, correct? Yes, FreeBSD is the guest on Windows 10 host. - parv ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Updated to 13-STABLE in VirtualBox; on shutdown stuck after uhub[01] being detached
Hi there, I had updated FreeBSD, in VirtualBox 5.22 on Windows with EFI, from 12-STABLE to 13-STABLE; upgraded the ZFS pools & the EFI boot loader. Currently testing with 13 GENERIC kernel. Now on shutdown, "shutdown -p now" (in single user mode, after manually unmounting ZFS datasets via "zfs unmount -a"), the shutting down process gets stuck, and CPU use jumps to 80% (Intel i5 6300U, 3 CPUs given to VM, of Thinkpad X260). Last few lines are ... ... All buffers synced. Uptime: uhub0: detached uhub1: detached In the end I chose "Power Off" from VirutalBox menu. "Reset" reboots the machine. None of these have any effect ... - Send the shutdown signal - ACPI Shutdown Help please. - parv ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ZFS (in virtual machine): $HOME being a dataset causes xauth to timeout- access delays?
Hi there, I have FreeBSD 12-STABLE in VirtualBox 5.2.44 on Windows 10. All the "disks" are file-backed virtual disks. I noticed that after making $HOME a ZFS dataset, there were delays ... - generally in start of Xorg; - exhibited by xauth (after using "startx") error messages about timeout with authority files. After reverting back $HOME not being a dataset on its own as before, there are no delays in start of Xorg; nor are any timeout message from xauth as before. Has anybody else noticed that? - parv Before making $HOME (/aux/home/parv) a dataset ... aux0 mounted at /aux aux0/home at /aux/home Conversion of $HOME to a dataset .. % zfs create aux0/home/parv2 % mv /aux/home/parv/* /aux/home/parv2/ % mv /aux/home/parv/.* /aux/home/parv2/ % rm -rf /aux/home/parv % zfs rename aux0/home/parv2 aux0/home/parv ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS (in virtual machine): $HOME being a dataset causes xauth to timeout- access delays?
On Thu, Apr 1, 2021 at 3:38 PM parv/freebsd wrote: I am wondering if $SRC_BASE, $MAKEOBJDIRPREFIX, & $WRKDIRPREFIX being ZFS datasets now would increase compile time. I will found that out in few weeks (in case of buildworld & kernel) as earlier I had both $SRC_BASE & $MAKEOBJDIRPREFIX as plain directories & took ~5--6 hours. I have FreeBSD 12-STABLE in VirtualBox 5.2.44 on Windows 10. All the "disks" > are file-backed virtual disks. > > I noticed that after making $HOME a ZFS dataset, there were delays ... > - generally in start of Xorg; > - exhibited by xauth (after using "startx") error messages about timeout > with authority files. > > After reverting back $HOME not being a dataset on its own as before, there > are > no delays in start of Xorg; nor are any timeout message from xauth as > before. > > Has anybody else noticed that? > ... - parv ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ZFS (in virtual machine): $HOME being a dataset causes xauth to timeout- access delays?
Hi there, I have FreeBSD 12-STABLE in VirtualBox 5.2.44 on Windows 10. All the "disks" are file-backed virtual disks. I noticed that after making $HOME a ZFS dataset, there were delays ... - generally in start of Xorg; - exhibited by xauth (after using "startx") error messages about timeout with authority files. After reverting back $HOME not being a dataset on its own as before, there are no delays in start of Xorg; nor are any timeout message from xauth as before. Has anybody else noticed that? - parv Before making $HOME (/aux/home/parv) a dataset ... aux0 mounted at /aux aux0/home at /aux/home Conversion of $HOME to a dataset .. % zfs create aux0/home/parv2 % mv /aux/home/parv/* /aux/home/parv2/ % mv /aux/home/parv/.* /aux/home/parv2/ % rm -rf /aux/home/parv % zfs rename aux0/home/parv2 aux0/home/parv ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Fwd: Re: Weird loader behavior
Forwarding to the list from the address I have actually subscribed to (in "basic HTML mode" Google Mail uses the actual account address not the alias already set up) ... -- Forwarded message - Date: Sun, Jan 31, 2021 at 2:37 PM Subject: Re: Weird loader behavior To: Juraj Lutter Cc: Juraj L wrote on Jan 31, 2021 at 12:15 PM ... > > Reading loader env vars from /efi/freebsd/loader.env > Setting currdev to disk0p1: ... >Command line arguments: loader.efi >EFI version: 2.40 >EFI Firmware: BHYVE (rev 1.00) >Console: efi (0x20001000) >Load Path: \EFI\BOOT\BOOTX64.EFI >Load Device: PciRoot(0x0)/Pci(0x3,0x0)/HD(1 ,GPT,A7A0422F-6F85-11EA-8A55-00A09858FAF5,0x28,0x64000) ... > Setting currdev to zfs:zroot/ROOT/default: > ZFS: i/o error - all block copies unavailable > ZFS: i/o error - all block copies unavailable > ERROR: /boot/lua/loader.lua:1: unexpected symbol near '`'. ... > - problematic version is stable/12-c243335-ge817c8f77fe Could you show your /boot/loader/loader.conf if you have one? Do you mean yo can boot with git commit 31c234974, one earlier than e817c8f77fe? If not, are you able to boot with even earlier commit of c48240fa6f8? > - Booting off 12.2-STABLE snapshot ISO 20210128-r369150 and using -a flag to ask > for a root mount and specifying zfs:zroot/ROOT/default makes the system run > normally (apropriate modules have to be loaded from within the loadet, ofc). > - using in-tree zfs > - zpool scrub did not show any anomalies > - gpart bootcode has already been run (after first unsusccessful boot). > - Another bhyve guest (13.0-ALPHA3) on the same host works OK What is git commit hash for 13.0-ALPHA3? - parv -- ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 12.2-RELEASE buildworld fail at cddl/zfs / libuutil.so
On Wed, Jan 27, 2021 at 6:10 AM Tomasz CEDRO wrote: Hi Tomasz, On 27.01.2021 12:52, parv/freebsd wrote: > ... > > # /usr/bin/time -h make buildkernel buildworld NO_CLEAN=1 > > . ^ ^ ^ ^ ^ ^ > > Perhaps try with cleaning out first buildworld, then kernel? > > Well I did remove all from /usr/obj, build failed, then checked out > /usr/src from svn, build failed, then checked out /usr/src from git, and > it failed. > > Just to make sure this is not a local environment problem I have > switched to stable/12 branch (that is 12-STABLE) and it builds fine!! > Thanks for the clue ... # git log --pretty=fuller --grep libuutil release/12.2.0..stable/12 commit 30ec3f368d Author: Eugene Grosbein AuthorDate: Dec.2020.1206-1622 + Commit: Eugene Grosbein CommitDate: Dec.2020.1206-1622 + MFC r364027 by arichardson: Fix linker error in libuutil with recent LLVM This also fixes nanobsd-style build (cross-compiling). Original commit log: Not marking the function as static can result in a linker error: undefined reference to __assfail [--no-allow-shlib-undefined] I noticed this error after updating our CHERI LLVM to the latest upstream LLVM HEAD revision. This change effectively reverts r329984 and marks dmu_buf_init_user as static (which keeps the GCC build happy). ... above seems to (as I haven't bisected) be the fix in 12-STABLE which allows the build to finish with success. - parv > # git branch >main >releng/12.2 > * stable/12 > ... > # /usr/bin/time -h make buildkernel buildworld release -j12 > ... > --- kernel.full --- > linking kernel.full > ctfmerge -L VERSION -g -o kernel.full ... >text data bssdec hex filename >23861318 1836970 3798784 29497072 0x1c216f0 kernel.full > --- kernel.debug --- > objcopy --only-keep-debug kernel.full kernel.debug > --- kernel --- > objcopy --strip-debug --add-gnu-debuglink=kernel.debug kernel.full kernel > -- > >>> Kernel build for GENERIC completed on Wed Jan 27 08:03:22 CET 2021 > -- > `release' is up to date. > 1h16m12.69s real5h45m44.19s user > 28m53.59s sys > > > Did anyone manage to build 12.2-RELEASE from repo? :-) > -- ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 12.2-RELEASE buildworld fail at cddl/zfs / libuutil.so
On Tue, Jan 26, 2021 at 7:45 PM Tomasz CEDRO wrote: > I cannot buildworld for 12.2-RELEASE. Using /usr/src as svn or git no > matter (its set to releng/12.2). Did clean /usr/obj. Any hints welcome :-) > > # uname -a > FreeBSD hexagon 12.2-RELEASE-p1 FreeBSD 12.2-RELEASE-p1 GENERIC amd64 > What is the git commit hash (for others)? I had recently compiled 12-STABLE (c243308-ge82353584c58) without issues; running as guest in VirtualBox on MS Windows 10. > # /usr/bin/time -h make buildkernel buildworld NO_CLEAN=1 > . ^ ^ ^ ^ ^ ^ Perhaps try with cleaning out first buildworld, then kernel? - parv (..) > ===> bin/tests (all) > ===> cddl (all) > ===> cddl/lib (all) > ===> cddl/lib/drti (all) > ===> cddl/lib/libavl (all) > ===> cddl/lib/libctf (all) > ===> cddl/lib/libdtrace (all) > ===> cddl/lib/libnvpair (all) > ===> cddl/lib/libumem (all) > ===> cddl/lib/libuutil (all) > ===> cddl/lib/libzfs_core (all) > ===> cddl/lib/libzfs (all) > ===> cddl/lib/libzpool (all) > ===> cddl/lib/tests (all) > ===> cddl/sbin (all) > ===> cddl/sbin/zfs (all) > cc -target x86_64-unknown-freebsd12.2 > --sysroot=/usr/obj/usr/src/amd64.amd64/tmp > -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -fno-common > -I/usr/src/cddl/contrib/opensolaris/lib/libzpool/common > -I/usr/src/cddl/compat/opensolaris/include > -I/usr/src/cddl/compat/opensolaris/lib/libumem > -I/usr/src/sys/cddl/compat/opensolaris > -I/usr/src/cddl/contrib/opensolaris/head > -I/usr/src/cddl/contrib/opensolaris/lib/libuutil/common > -I/usr/src/cddl/contrib/opensolaris/lib/libzfs/common > -I/usr/src/cddl/contrib/opensolaris/lib/libzfs_core/common > -I/usr/src/cddl/contrib/opensolaris/lib/libumem/common > -I/usr/src/cddl/contrib/opensolaris/lib/libnvpair > -I/usr/src/sys/cddl/contrib/opensolaris/uts/common > -I/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs > -I/usr/src/sys/cddl/contrib/opensolaris/common/zfs > -DNEED_SOLARIS_BOOLEAN -g -O0 -std=gnu99 -fstack-protector-strong > -Wno-pointer-sign -Wno-unknown-pragmas -Wno-empty-body > -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef > -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum > -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -o > zfs.full zfs_main.o zfs_iter.o -ljail -lnvpair -luutil -lzfs_core > -lzfs > ld: error: /usr/obj/usr/src/amd64.amd64/tmp/usr/lib/libuutil.so: > undefined reference to __assfail > cc: error: linker command failed with exit code 1 (use -v to see > invocation) > *** Error code 1 > > Stop. > make[5]: stopped in /usr/src/cddl/sbin/zfs > *** Error code 1 > (..) > -- ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8-stable crashing recently in ufsdirhash
On August 5, 2015 4:10:14 AM HST, Ian wrote: On Tue, 2015-08-04 at 23:54 -1000, parv wrote: Please CC me as I cannot properly use my laptop, Thinkpad X200 (i386). 8-stable has been crashing a lot since source update of Jul 2015[0]. After building debug kernel, kgdb shows lock reversal order in ufsdirhash. File systems (/, var, misc) are all UFS, with var misc having soft updates enabled. Crash had happened just after boot (during mktemp); when I tried to delete a directory (/misc/obj); when I tried to edit (vi /etc/fstab) so that / would be mounted readonly. Most recent crash ... http://imagebin.ca/v/2B50NARvIHs ... [0] crash also happened while svn was trying to update source of 8. Now svn log wants to connect to the remote repo instead of showing the current revision. When you say you built a debug kernel, does that include option WITNESS_KDB? Yes; other things wrt debug kernel ... options DDB options GDB options KDB options KDB_TRACE #options KDB_UNATTENDED options INVARIANT options INVARIANT_SUPPORT options WITNESS #options WITNESS_KDB options WITNESS_SKIPSPIN If so, remove that so you can find the real error. Above is the current state (of kernel configuration). LORs related to ufs_dirhash have been reported for years, and nobody with the appropriate skills seems to be interested in fixing them; they just get declared to be harmless. Aye. After installing kernel with W*KDB option missing, FreeBSD 8 now runs meaningfully long enough before crash-reboot. Thanks Ian. I will now do binary search which is causing seemingly random crashes. Crashes seem to coincide with network traffic on wlan device (ath). Between Jun 2015 Jul 23 2015, only changes relevant are apparently related to TCP openssh. (IMO the spewage related to this makes witness essentially useless.) Is there any point then in keeping even plain WITNESS option? -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8-stable crashing recently in ufsdirhash
On August 5, 2015 12:20:15 PM HST, Kevin O wrote: On Wed, Aug 5, 2015 at 1:15 PM, Chris H wrote: On Wed, 05 Aug 2015 09:30:28 -1000 parv wrote On August 5, 2015 4:10:14 AM HST, Ian L wrote: On Tue, 2015-08-04 at 23:54 -1000, parv wrote: Please CC me as I cannot properly use my laptop, Thinkpad X200 (i386). 8-stable has been crashing a lot since source update of Jul 2015[0]. After building debug kernel, kgdb shows lock reversal order in ufsdirhash. File systems (/, var, misc) are all UFS, with var misc having soft updates enabled. ... Most recent crash ... http://imagebin.ca/v/2B50NARvIHsH ... When you say you built a debug kernel, does that include option WITNESS_KDB? If so, remove that so you can find the real error. LORs related to ufs_dirhash have been reported for years, and nobody with the appropriate skills seems to be interested in fixing them; they just get declared to be harmless. ... I will try that as soon as I can. Currently after every little fs operation, I am thrown in debugger-reboot-fsck cycle. As such I cannot do anything. ... I tried booting /boot/kernel.old/kernel from boot prompt but that presented debugger soon after boot. BTW is it possible to set kernel.old to boot next time at boot prompt? ... It might be somewhat easier to boot from the boot-only/install CD/DVD, and then choose rescue mode. After you've gotten there. Simply mount / in read/write, them open it's /boot/loader.conf, and add the following: kernel=kernel.old boot_single=YES and save it. You can then remove the CD/DVD, and reboot which will land you in single-user mode, from your kernel.old/kernel. Assuming it booted to that kernel OK, you can run fsck -f ... Chris, after spending my mail I was thinking on the same lines. But I delayed due to laziness, till ... You're working too hard. You can drop into the loader prompt and enter boot kernel.old. This will reload both the kernel and modules from /boot/kernel.old. Thanks Kevin. It was the loader prompt, not the boot prompt, that I should have tried. After booting old kernel from loader prompt, functionality was restored (to some workable state). Also handy and virtually unknown is that you can build test kernels and not blow away the old, working kernel by using make reinstallkernel instead of installkernel. This will keep the existing kernel.old and just replace the currently running kernel. Thanks again. N.B. There is a bug that will cause a failure to re-install PORTS_MODULES. ... At this point I am not worried about kernel modules built from ports. I just want a working version that won't seemingly randomly crash, leaving no core dump or any other relevant messages. The only thing pointing to a crash are entries in wtmp, which lastlog reports as crash. Nothing. Else. -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8-stable crashing recently in ufsdirhash
Please CC me as I cannot properly use my laptop, Thinkpad X200 (i386). 8-stable has been crashing a lot since source update of Jul 2015[0]. After building debug kernel, kgdb shows lock reversal order in ufsdirhash. File systems (/, var, misc) are all UFS, with var misc having soft updates enabled. Crash had happened just after boot (during mktemp); when I tried to delete a directory (/misc/obj); when I tried to edit (vi /etc/fstab) so that / would be mounted readonly. Most recent crash ... http://imagebin.ca/v/2B50NARvIHsH Any clue would be appreciated. - parv [0] crash also happened while svn was trying to update source of 8. Now svn log wants to connect to the remote repo instead of showing the current revision. -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8-stable crashing recently in ufsdirhash
On August 4, 2015 11:54:16 PM HST, parv wrote: Please CC me as I cannot properly use my laptop, Thinkpad X200 (i386). 8-stable has been crashing a lot since source update of Jul 2015[0]. ... Another crash on umount ... http://imagebin.ca/v/2B5CKNCOojPW -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8-stable crashing recently in ufsdirhash
On August 5, 2015 12:55:28 AM HST, Ian wrote: On Wed, 5 Aug 2015 00:33:16 -1000, parv wrote: On August 4, 2015 11:54:16 PM HST, parv wrote: Please CC me as I cannot properly use my laptop, Thinkpad X200 (i386). 8-stable has been crashing a lot since source update of Jul 2015[0]. ... Another crash on umount ... http://imagebin.ca/v/2B5CKNCOojPW My X200 runs really nicely on 9.3 amd64, and 10.x almost certainly. Just sayin' .. I wouldn't bother chasing an expired branch, or i386, when you can run amd64 with - frankly - more enthusiastic support. Well, I don't see a way to upgrade while FreeBSD 8 is crashing on file system operations (mktemp, rm, umount, mount after boot, vi, ed, etc). As for amd64 version, my 'puter is really i386. -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8-stable crashing recently in ufsdirhash
On August 5, 2015 4:10:14 AM HST, Ian L wrote: On Tue, 2015-08-04 at 23:54 -1000, parv wrote: Please CC me as I cannot properly use my laptop, Thinkpad X200 (i386). 8-stable has been crashing a lot since source update of Jul 2015[0]. After building debug kernel, kgdb shows lock reversal order in ufsdirhash. File systems (/, var, misc) are all UFS, with var misc having soft updates enabled. Crash had happened just after boot (during mktemp); when I tried to delete a directory (/misc/obj); when I tried to edit (vi /etc/fstab) so that / would be mounted readonly. Most recent crash ... http://imagebin.ca/v/2B50NARvIHsH Any clue would be appreciated. ... When you say you built a debug kernel, does that include option WITNESS_KDB? If so, remove that so you can find the real error. LORs related to ufs_dirhash have been reported for years, and nobody with the appropriate skills seems to be interested in fixing them; they just get declared to be harmless. I will try that as soon as I can. Currently after every little fs operation, I am thrown in debugger-reboot-fsck cycle. As such I cannot do anything. This is my own damn fault because the non-debug kernel would run for some random but meaningful amount of time before crash reboot. I tried booting /boot/kernel.old/kernel from boot prompt but that presented debugger soon after boot. BTW is it possible to set kernel.old to boot next time at boot prompt? -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Intel 82574 issue reported on Slashdot
in message a18965a6-8d17-4919-9947-fe43d2503...@gsoft.com.au, wrote Daniel O'Connor thusly... On 09/02/2013, at 4:46, Jack Vogel jfvo...@gmail.com wrote: recommends contacting your motherboard manufacturer if you have continued concerns or questions whether your products are impacted. Here is the link: http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-gigabit-ethernet-controller-statement Any questions or concerns may be sent to me. In all honesty.. The blog post (and your email) are basically information free, they don't name names and provide no script or downloadable code that will allow end users to check if they are affected. Contact your motherboard manufacturer is much more time consuming than Run sysctl... | grep foo | awk ... to see if your system is affected. Gift^WStraight from horse's mouth ... http://blog.krisk.org/2013/02/packets-of-death.html http://www.kriskinc.com/intel-pod - parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7-STABLE - ath, Atheros 5212 - crash on network activity
in message 20090807155141.ga1...@holstein.holy.cow, wrote p...@pair.com thusly... I am in the process of upgrading from 6-STABLE to 7-STABLE, but have been stymied due to FreeBSD/i386 7 crashing on network activity. Machine is Thinkpad T61 with Atheros 5212 (IBM 802.11 [abg]) card. ... GNU gdb 6.1.1 [FreeBSD] ... This GDB was configured as i386-marcel-freebsd... ... Unread portion of the kernel message buffer: panic: operating mode 1 cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper(c0c260f0,e8fbc8fc,c0852763,c0c5338d,1,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0c5338d,1,c0c3326f,e8fbc908,1,...) at kdb_backtrace+0x29 panic(c0c3326f,1,4,c0c21ab3,ce,...) at panic+0x114 ieee80211_set_tim(c7aac000,1,c0c345ca,c7,0,c7aad510,c670d22c) at ieee80211_set_tim+0x2d ieee80211_pwrsave(c7aac000,c7b1ab00,c0be15cd,62c,c0c30884,...) at ieee80211_pwrsave+0x1f3 ath_start(c6709000,c6709108,e8fbca08,c08ed81f,c6709000,...) at ath_start+0x4e3 if_start(c6709000,0,c0c30884,195,2,...) at if_start+0x4f ether_output_frame(c6709000,c7b1ab00,6,0,e8fbca2a,...) at ether_output_frame+0x1ce ether_output(c6709000,c7b1ab00,e8fbcac0,c6b45e0c,0,...) at ether_output+0x48d ieee80211_output(c6709000,c7b1ab00,e8fbcac0,c6b45e0c,c6b402d0,...) at ieee80211_output+0x38 ip_output(c7b1ab00,0,e8fbcabc,0,0,...) at ip_output+0xa10 udp_send(c6b051a0,0,c7b1ab00,0,0,...) at udp_send+0x89b sosend_dgram(c6b051a0,0,e8fbcbe0,c7b1ab00,0,...) at sosend_dgram+0x359 sosend(c6b051a0,0,e8fbcbe0,0,0,...) at sosend+0x3f kern_sendit(c6b49b40,4,e8fbcc5c,0,0,...) at kern_sendit+0x107 sendit(0,7844401d,0,0,0,...) at sendit+0xad sendto(c6b49b40,e8fbccfc,18,c0c3ea41,c,...) at sendto+0x48 syscall(e8fbcd38) at syscall+0x2a1 Xint0x80_syscall() at Xint0x80_syscall+0x20 ... Could anybody please clue me in about what I can do to solve the problem of ath (Atheros 5212) crashing? I had also filed the bug, not much activity on it yet ... http://www.freebsd.org/cgi/query-pr.cgi?pr=137592 - parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 7-STABLE - ath, Atheros 5212 - crash on network activity
Hi, I am in the process of upgrading from 6-STABLE to 7-STABLE, but have been stymied due to FreeBSD/i386 7 crashing on network activity. Machine is Thinkpad T61 with Atheros 5212 (IBM 802.11 [abg]) card. Machine information (under FreeBSD 6.X) can be obtained from ... http://www103.pair.com/parv/comp//unix/freebsd/thinkpad-t61-8897-cto/sys/dmesg http://www103.pair.com/parv/comp//unix/freebsd/thinkpad-t61-8897-cto/sys/pciconf-lcv ... until I do the disk replacement dance again ( get the 7-STABLE specific dmesg pciconf data). I had updated the 7-STABLE sources around Aug 7, 2pm UTC from cvsup5 before I bothered with getting a crash dump. A backtrace of FreeBSD/i386 7-STABLE follows ... - Parv GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Unread portion of the kernel message buffer: panic: operating mode 1 cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper(c0c260f0,e8fbc8fc,c0852763,c0c5338d,1,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0c5338d,1,c0c3326f,e8fbc908,1,...) at kdb_backtrace+0x29 panic(c0c3326f,1,4,c0c21ab3,ce,...) at panic+0x114 ieee80211_set_tim(c7aac000,1,c0c345ca,c7,0,c7aad510,c670d22c) at ieee80211_set_tim+0x2d ieee80211_pwrsave(c7aac000,c7b1ab00,c0be15cd,62c,c0c30884,...) at ieee80211_pwrsave+0x1f3 ath_start(c6709000,c6709108,e8fbca08,c08ed81f,c6709000,...) at ath_start+0x4e3 if_start(c6709000,0,c0c30884,195,2,...) at if_start+0x4f ether_output_frame(c6709000,c7b1ab00,6,0,e8fbca2a,...) at ether_output_frame+0x1ce ether_output(c6709000,c7b1ab00,e8fbcac0,c6b45e0c,0,...) at ether_output+0x48d ieee80211_output(c6709000,c7b1ab00,e8fbcac0,c6b45e0c,c6b402d0,...) at ieee80211_output+0x38 ip_output(c7b1ab00,0,e8fbcabc,0,0,...) at ip_output+0xa10 udp_send(c6b051a0,0,c7b1ab00,0,0,...) at udp_send+0x89b sosend_dgram(c6b051a0,0,e8fbcbe0,c7b1ab00,0,...) at sosend_dgram+0x359 sosend(c6b051a0,0,e8fbcbe0,0,0,...) at sosend+0x3f kern_sendit(c6b49b40,4,e8fbcc5c,0,0,...) at kern_sendit+0x107 sendit(0,7844401d,0,0,0,...) at sendit+0xad sendto(c6b49b40,e8fbccfc,18,c0c3ea41,c,...) at sendto+0x48 syscall(e8fbcd38) at syscall+0x2a1 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (133, FreeBSD ELF32, sendto), eip = 0x782d2e83, esp = 0xbfbfccdc, ebp = 0xbfbfcd08 --- KDB: enter: panic Physical memory: 3034 MB Dumping 156 MB: 141 125 109 93 77 61 45 29 13 Reading symbols from /boot/kernel/speaker.ko...Reading symbols from /boot/kernel/speaker.ko.symbols...done. done. Loaded symbols for /boot/kernel/speaker.ko Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko #0 doadump () at pcpu.h:196 196 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc04db4eb in db_fncall (dummy1=1, dummy2=0, dummy3=-1059146496, dummy4=0xe8fbc6e0 ) at /usr/src7/sys/ddb/db_command.c:516 #2 0xc04dba4c in db_command (last_cmdp=0xc0d3b014, cmd_table=0x0, dopager=1) at /usr/src7/sys/ddb/db_command.c:413 #3 0xc04dbb4d in db_command_loop () at /usr/src7/sys/ddb/db_command.c:466 #4 0xc04dd20f in db_trap (type=3, code=0) at /usr/src7/sys/ddb/db_main.c:228 #5 0xc087e4fe in kdb_trap (type=3, code=0, tf=0xe8fbc888) at /usr/src7/sys/kern/subr_kdb.c:524 #6 0xc0b5976b in trap (frame=0xe8fbc888) at /usr/src7/sys/i386/i386/trap.c:687 #7 0xc0b3f73b in calltrap () at /usr/src7/sys/i386/i386/exception.s:166 #8 0xc087e65f in kdb_enter_why (why=0xc0c2320a panic, msg=0xc0c2320a panic) at cpufunc.h:60 #9 0xc0852780 in panic (fmt=0xc0c3326f operating mode %u) at /usr/src7/sys/kern/kern_shutdown.c:557 #10 0xc09226e6 in ieee80211_set_tim (ni=0xc0c2320a, set=1) at /usr/src7/sys/net80211/ieee80211_power.c:140 #11 0xc0922401 in ieee80211_pwrsave (ni=0xc7aac000, m=0xc7b1ab00) at /usr/src7/sys/net80211/ieee80211_power.c:206 #12 0xc0583a45 in ath_start (ifp=0xc6709000) at /usr/src7/sys/dev/ath/if_ath.c:1618 #13 0xc08e75fb in if_start (ifp=0xc6709000) at /usr/src7/sys/net/if.c:2837 #14 0xc08ed81f in ether_output_frame (ifp=0xc6709000, m=0xc7b1ab00) ---Type return to continue, or q return to quit--- at /usr/src7/sys/net/if_ethersubr.c:405 #15 0xc08edde1 in ether_output (ifp=0xc6709000, m=0xc7b1ab00, dst=0xe8fbcac0, rt0=0xc6b45e0c) at /usr/src7/sys/net/if_ethersubr.c:374 #16 0xc0920299 in ieee80211_output (ifp=0xc6709000, m=0xc7b1ab00, dst=0xe8fbcac0, rt0=0xc6b45e0c) at /usr/src7/sys/net80211/ieee80211_output.c:261 #17 0xc093969c in ip_output (m=0xc7b1ab00, opt=0x0, ro=0xe8fbcabc, flags=Variable flags is not available. ) at /usr/src7/sys/netinet/ip_output.c:554 #18 0xc09a734a
pkg_delete dumps core while deinstalling old libgtkhtml
Hi, While deinstalling libgtkhtml-2.11.1, pkg_delete (FreeBSD 6-STABLE/i386) dies due to segfault ... gdb /usr/sbin/pkg_delete -c /var/db/package/libgtkhtml-2.11.1/pkg_delete.core GNU gdb 6.1.1 [FreeBSD] ... This GDB was configured as i386-marcel-freebsd...(no debugging symbols found)... Core was generated by `pkg_delete'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libmd.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libmd.so.3 Reading symbols from /lib/libutil.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libutil.so.5 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x78152f52 in strcmp () from /lib/libc.so.6 (gdb) bt #0 0x78152f52 in strcmp () from /lib/libc.so.6 #1 0x0804b3e3 in ?? () #2 0x08052060 in ?? () #3 0x in ?? () #4 0x in ?? () #5 0x in ?? () #6 0x in ?? () #7 0x in ?? () #8 0x in ?? () #9 0x in ?? () #10 0x08052040 in ?? () #11 0x08056b60 in ?? () #12 0xbfbfda08 in ?? () #13 0x0804ad65 in ?? () #14 0x in ?? () #15 0x000c in ?? () #16 0xbfbfd870 in ?? () #17 0x78168518 in __sfvwrite () from /lib/libc.so.6 ... if anybody needs missing symbols, could you please tell me what I would need to do? I could (write a program) myself (to) handle the file deletion, unless there is already an existing program besides pkg_delete itself. Is there one? - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: HDD USB still on after computer shutdown
in message [EMAIL PROTECTED], wrote Dominique Goncalves thusly... I use FreeBSD 6.3-STABLE and an HDD USB (Maxtor, external PSU, 500GB). When I shutdown my computer (shutdown -p now ) the HDD USB is still on. In Windows XP it works, the HDD USB is off. Is there a way to resolve this issue? %dmesg ... I have a Thinkpad T61 laptop which has a section in BIOS configuration titled USB something-or-other. When a particular subsection is activated, the help text mentions along the lines that enabling the option would continue to power USB ports for connected devices after shutdown. So do poke around in BIOS, unless of course somebody else could offer a solution to be executed within FreeBSD. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X.org: Fatal server error [Solved]
in message [EMAIL PROTECTED], wrote Harald Weis
thusly...
2. The `pkg_info -L' check does not certify that the file is
actually in its place
To actually verify the existence of the files, stat(2) them somehow
(will work at least in bourne like shells) ...
pkg_info -L port-name \
| awk '!/^(Info|Files:|$)/ { print $0 }' \
| xargs ls -l /dev/null
... above will only show the error messages for missing files of a
port|package.
- Parv
--
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI MSI (was Re: What current Dell Systems are supported/work)
in message [EMAIL PROTECTED], wrote John Baldwin thusly... On Friday 18 January 2008 08:50:31 am John Baldwin wrote: On Friday 18 January 2008 05:30:06 am Parv wrote: There was no page fault or trap 12 message when the panic happened. After some of messages are printed (as in dmesg), kdb is entered ... ioapic0: Assigning PCI IRQ 23 to local APIC 1 msi: Assigning MSI IRQ 256 to local APIC 0 panic: blockabke sleep block (sleep mutex) msi @ /misc/src-6/sys/i386/i386/msi.c:381 cpuid: 0 kdb: stack backtrace kbd_backtrace( c0adc531,0,c0abaafd,c1020c34,c0bab700,...) at ... \ [I skipped from here to the db prompt] ... Tomorrow, rather later today, I will type up the trace output. Please let me know if you would like to see any other output that I could possibly provide. This is good enough for me to see the bug, I'll work on fixing it. There are some locking changes in the x86 interrupt code I need to MFC. Try this patch: ... Thanks much John. Your patch allowed my computer to resume normal operation without disabling MSI via hw.pci.enable_msi*. Lest I forget, mahalo for saving me from typing up the trace output. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI MSI (was Re: What current Dell Systems are supported/work)
(Dropped Vivek K from recipient list; edited the URLs in my previous message.) in message [EMAIL PROTECTED], wrote John Baldwin thusly... On Thursday 17 January 2008 06:05:17 am Parv wrote: ... Speaking of MSI being on by default in recent 6-STABLE ... well, that caused my ThinkPad T61 (8859-CTO) ... dmesg: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/dmesg kernel (combined for easy perusal): http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/cf/kern/combined/T61-SMP.debug--combined /boot/device.hints: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/cf/boot/device.hints ... to go in panic[0] ... [0] I could not save the dump for neither do I have access to serial console, nor could the file system be mounted. Missing also here is a digital camera. If anybody is interested, I could write screen down, and repeat to them. For starters, can you get the output of 'pciconf -lc'? Hi John, You can find pciconf -lc at ... http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/pciconf-lc and pciconf -lv, just in case ... http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8897-cto/sys/pciconf-lv Secondly, I really will need the kernel panic message. If it is a page fault (trap 12) then write down the faulting virtual address and the faulting IP. If you can scribble down any of the stack trace from DDB that would be helpful as well. There was no page fault or trap 12 message when the panic happened. After some of messages are printed (as in dmesg), kdb is entered ... ioapic0: Assigning PCI IRQ 23 to local APIC 1 msi: Assigning MSI IRQ 256 to local APIC 0 panic: blockabke sleep block (sleep mutex) msi @ /misc/src-6/sys/i386/i386/msi.c:381 cpuid: 0 kdb: stack backtrace kbd_backtrace( c0adc531,0,c0abaafd,c1020c34,c0bab700,...) at ... \ [I skipped from here to the db prompt] . . . Tomorrow, rather later today, I will type up the trace output. Please let me know if you would like to see any other output that I could possibly provide. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
PCI MSI (was Re: What current Dell Systems are supported/work)
in message [EMAIL PROTECTED], wrote Vivek Khera thusly... On Jan 10, 2008, at 11:09 AM, John Baldwin wrote: *: This is the default behavior for 7.0, I have not encountered the problem mentioned above on any 1950/2950 boxes so far I have tested. I will enable MSI by default on 6.x now (so will take affect for 6.4). We've also enabled it by default on 6.x at work. Where can one go to read up on what MSI is and how it helps us? Is enabling it just setting a sysctl? Does that have to be done in loader.conf or can it happen later? Speaking of MSI being on by default in recent 6-STABLE ... well, that caused my ThinkPad T61 (8859-CTO) ... dmesg: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8859-cto/sys/dmesg kernel (combined for easy perusal): http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8859-cto/cf/kern/combined/T61-SMP.debug--combined /boot/device.hints: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t61-8859-cto/cf/boot/device.hints ... to go in panic[0]. So, for now I have added ... # Since MSI turned on by default on 2008.01.10.21.17.12 UTC, # causes panic so disable MSI. hw.pci.enable_msix=0 hw.pci.enable_msi=0 ... to /boot/loader.conf. [0] I could not save the dump for neither do I have access to serial console, nor could the file system be mounted. Missing also here is a digital camera. If anybody is interested, I could write screen down, and repeat to them. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /boot size in 7.0 beta3
in message [EMAIL PROTECTED], wrote Matthew D. Fuller thusly... On Thu, Dec 06, 2007 at 05:32:41PM -0800 I heard the voice of Doug Hardie, and lo! it spake thus: Between 6.2 and 7 /boot has grown from 45 MB to 114 MB. That poses a significant issue for those of us who have been running production systems for many years. I have the root partition set to 200 MB which has been more than enough. Well, 200 meg has been pretty tight and rather small for a couple versions now. My 194 meg / partition set up in 3-CURRENT days is pretty tight these days 8-} On not too old RELENG_6 with a debug kernel (nothing much in /root, /tmp is a symlinked to elsewhere) ... df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s3a 193M 71M107M40%/ /dev/ufs/t61var 387M104M253M29%/var /dev/ufs/t61usr 678M155M468M25%/usr /dev/ufs/t61home 24G6.3G 16G28%/home /dev/ufs/t61misc 13G6.8G5.4G56%/misc devfs 1.0K1.0K 0B 100%/dev So, just what have you been stuffing in /? Now if /var is really in /, then 200M is indeed close to the usage (175M) for comfort. - Parv rm'ing away all the .symbols files from the kernel dir did the trick for me, though (I did have to do it in another terminal while `installkernel` was running to get it to complete... there's probably a flag I can pass to make): Filesystem SizeUsed Avail Capacity Mounted on /dev/da0s1a 194M 65M113M36%/ -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: local/rc.d/* executed twice
in message [EMAIL PROTECTED],
wrote Stefan Hauser thusly...
after upgrading 3 machines, i noticed that /usr/local/etc/rc.d/*
scipts get exectued twice. does anyone have a fix for it ?
This had been discussed/mentioned on ports@ mailing list, and
possibly on questions@ too; search for Doug Barton's messages during
the last month.
In short term, set local_startup possibly local_periodic to the
actual directories ...
http://groups.google.com/group/mailing.freebsd.ports/msg/2604cd508c3ca533
You see $local_startup currently, at least on 6-STABLE, is set to
/usr/{X11R6,local}. And after the X11 Windows System update to xorg
7.x, /usr/X11R6 would be a symbolic link to /usr/local (if you had
followed the official|supported directions), which leads to double
runs of /usr/local/etc/rc.d. See ...
http://groups.google.com/group/mailing.freebsd.ports/msg/dd286acc00ef71d4
The proper, and long term, solution is to fix /etc/rc.subr, for
local start ups, so that symbolic links do not cause multiple runs of
the same script. A initial patch had been submitted to rc@ list by
yours truly based on initial work by Doug ...
http://groups.google.com/group/mailing.freebsd.ports/msg/653b2a0f3cfdb76f
http://groups.google.com/group/mailing.freebsd.ports/msg/1d0f640cc8bb6433
http://groups.google.com/group/lucky.freebsd.rc/browse_thread/thread/cd21685e1b8c35cd/
... for some reason the patch had been stripped in message to @rc,
which I had initially sent to [EMAIL PROTECTED] Note that above patch does
not deal with periodic scripts running twice (noticed wrt PostgreSQL
port).
- Parv
--
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 induced panic additional info
in message [EMAIL PROTECTED], wrote Steve Kargl thusly... By increasing the kernel message buffer, I was able to get the previous Unread portion im my last email. Unread portion of the kernel message buffer: lock order reversal: (sleepable after non-sleepable) 1st 0xc34caec0 ath0 (ath0) @ /usr/src/sys/dev/ath/if_ath.c:5210 2nd 0xc32cbe24 user map (user map) @ /usr/src/sys/vm/vm_map.c:3074 ... Oh yes, I got the problem with ath interface on mode 11g (along with WPA DHCP set in /etc/rc.conf); see LOR - ath (similar to LOR #42) on FreeBSD 6-STABLE, [EMAIL PROTECTED]. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
LOR - ath (similar to LOR #42) on FreeBSD 6-STABLE 2007.04.08.19.20.49
(Before Apr 8 update, I built the world+kernel as of 2007.03.29.21.58.25 UTC.) I am running FreeBSD 6-STABLE as of 2007.04.08.19.20.49 UTC, with ath0 driver for Belkin My Essentials Wireless G card, which I had been using without problems until now. Some of current configuration is ... device.hints: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/boot.device.hints loader.conf: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/boot.loader.conf kernel (debug): http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/kernel.cleaned-up dmesg (does not show ath0 attachment): http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/dmesg dmesg (earlier, w/ ath0): http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/dmesg I had not set up dumpdev large enough dumpdir at the time of above crap-shoot. I will update when I LOR happens again. Yesterday, while in X having problem connecting to places, namely hosted by pair.com, computer shut itself down. I rebooted with a debug kernel complete with WITNESS* options; just after attaching the ath0 interface, I was greeted by (sorry, I do/did not have a serial console setup; I do have some images) ... http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/00-crash/ ... of importance ... start of LOR message: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/00-crash/witness-01-lor-sleep-after-nonsleep.png backtrace: http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/00-crash/witness-02-backtrace.png ... there are 4 other images which may be inconsequential (ath0 attachment messages; output of command 'bt' which seemed to produced the same output as above; output of 'ps' 'x'). Above appears to be, to my untrained eye, similar to ... http://sources.zabbadoz.net/freebsd/lor/042.html http://lists.freebsd.org/pipermail/freebsd-current/2005-November/058007.html http://lists.freebsd.org/pipermail/freebsd-current/2005-December/059168.html Is there anything I could do to generate other|more data? Is there a solution for my above LOR? - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LOR - ath (similar to LOR #42) on FreeBSD 6-STABLE 2007.04.08.19.20.49
in message [EMAIL PROTECTED],
wrote Parv thusly...
(Before Apr 8 update, I built the world+kernel as of
2007.03.29.21.58.25 UTC.) I am running FreeBSD 6-STABLE as of
2007.04.08.19.20.49 UTC, with ath0 driver for Belkin My
Essentials Wireless G card, which I had been using without
problems until now.
...
I had not set up dumpdev large enough dumpdir at the time of
above crap-shoot. I will update when I LOR happens again.
Ok, now that dumpd{ev,ir} have been set up, vmcore is available if
somebody serious wants to look; backtraces (in text form) are
available (I did not know what else to look for) ...
First debug trace (happens to contain dmesg too):
http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/00-crash/kern-debug.log
Trace generated after ifconfig ath0 mode 11g:
http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/00-crash/kern-debug.ath-ifconfig-mode11g
... seems almost the same, those two, save for dmesg in one.
Please let me know if you would like to see anything not already
presented.
While fiddling, I found that ath0 driver has been giving trouble
since yesterday evening if try to set mode 11g either in
/etc/rc.conf or manually via ifconfig.
Just what the hell could have changed suddenly -- most likely on
Linksys WRT54g v4 wireless AP/switch/router as I do not remember
changing anything (world|kernel wise) on this FreeBSD Thinkpad T-42?
(Yes, the internet connection from Comcast, at home, to sites on
pair.com was terrible.)
http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/00-crash/
... of importance ...
start of LOR message:
http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/00-crash/witness-01-lor-sleep-after-nonsleep.png
backtrace:
http://www103.pair.com/parv/comp/unix/freebsd/thinkpad-t42-2373-5tu/err/2007-04-19.ath-lor/00-crash/witness-02-backtrace.png
- Parv
--
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Thread Hijacking (was Re: Is SATA II supported in 6.2-stable?)
in message [EMAIL PROTECTED], wrote Artem Kuchin thusly... (something about SATA in IPMI thread, and previously, something about IPMI in USB thread) Artem, Could you please stop hijacking threads? If you need to start a new thread, then please do not reply to a message of unrelated topic; start a whole new message. Or, at the very least, delete In-reply-to: and References: headers, with subject line changed of course. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Practically missing cpio(1L) man page since Oct 22 2006
A few minutes ago I was extracting information about mass copying with pax(1) cpio(1L) on 6.2-PRERELEASE. I got information from pax(1) man page, but i found cpio(1L) man page to be rather lacking. (Yeah, I saw the pointer to info.) Is it possible to have a genuine cpio(1L) 2.6 man page available? I got curious when I tried my luck with FreeBSD man page index ... http://www.freebsd.org/cgi/man.cgi ... and got a genuine man page, (had FreeBSD 6.1-RELEASE selected per default). I found nothing in PR database about neutering the cpio man page; so went to cvsweb ... http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/cpio/doc/cpio.1 ... which was missing the substantial version in there. I did a second trip to man.cgi selected FreeBSD 6.1-STABLE, which showed the rather empty man page. Just to confirm that I turned to cvs- mailing list stored locally, and here I found ... delphij 2006-10-23 03:33:27 UTC ... 1.3.38.2 +0 -328src/contrib/cpio/cpio.1 (dead) ... 1.1.1.1.40.1 +0 -558src/contrib/cpio/cpio.texi (dead) ... 1.2.2.1 +41 -0 src/contrib/cpio/doc/cpio.1 (new) 1.2.2.1 +563 -0src/contrib/cpio/doc/cpio.texi (new) ... no wonder (NOW!) that cvsweb did not 330-some line version of man page as the path had been changed, and I did not happen to misplace my mind during world build install, along with some combination of entry in /etc/make.conf (yup, checked there too;). GNU, drown thyself with info! - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sound device reported but no devices created
in message [EMAIL PROTECTED], wrote Freddie Cash thusly... # kldload snd_driver # cat /dev/sndstat read the text to see what driver(s) it loaded # echo 'snd_driver_load=YES' /boot/loader.conf snd_driver will load every single sound driver available in FreeBSD, all at once, and the kernel will attempt to detect every sound chipset supported by those drivers. Neat. Thanks much Freddie. (No, i don't have any sound driver problems, but your method seems much easier|lazier than to explicitly search for the sound hardware related FreeBSD bits.) - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-BETA4-i386-disc2.iso - only usr/share/doc, no usr/src?
in message [EMAIL PROTECTED], wrote Scot Hetzel thusly... On 3/27/06, Parv [EMAIL PROTECTED] wrote: Does the 6.1-BETA4-i386-disc2.iso contain only usr/share/doc, or for some reason i am unable to see anything else? I was looking for usr/src (and for a odd chance to have usr/ports); i suppose those two trees would be available somewhere on some disc for RELENG_6_1. Have you checked if they are on the disc1 ISO? Oh, yes both (src ports) were there on disc1 under 6.1-BETA* directory. For some reason, that directory just did not register. Sorry for the noise. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1-BETA4-i386-disc2.iso - only usr/share/doc, no usr/src?
Does the 6.1-BETA4-i386-disc2.iso contain only usr/share/doc, or for some reason i am unable to see anything else? I was looking for usr/src (and for a odd chance to have usr/ports); i suppose those two trees would be available somewhere on some disc for RELENG_6_1. I mounted the image as ... mdconfig -a -t vnode -f /path/to/6.1-BETA4-i386-disc2.iso -u 0 mount -t cd9660 /dev/md0 /mnt ... then looked around as usual (cd, ls). - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ndis0 does not associate since update to RELENG_6
in message [EMAIL PROTECTED], wrote Fabian Keil thusly... Fabian Keil [EMAIL PROTECTED] wrote: I fail to get the following device working since my update from RELENG_5 to RELENG_6 a few days ago: [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class= network I found a work around. It still works with /usr/ports/net/iwi-firmware/: I also found the same about ndis driver. I was not even able to assign a ssid, mode, or a channel to a ndis0 interface. At least net/iwi-firmware works w/ WPA (even if the interface causes freeze after waking up from long sleep on IBM Thinkpad T42; or after some time of good/stable connectivity, ping to Linksys WRT54G (router, running as a AP/switch) goes unanswered). BTW, when i read that you found a work around, i was expecting a work around to make ndis work. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ndis0 does not associate since update to RELENG_6
in message [EMAIL PROTECTED], wrote Fabian Keil thusly... Parv [EMAIL PROTECTED] wrote: in message [EMAIL PROTECTED], wrote Fabian Keil thusly... Fabian Keil [EMAIL PROTECTED] wrote: I fail to get the following device working since my update from RELENG_5 to RELENG_6 a few days ago: [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class= network I found a work around. It still works with /usr/ports/net/iwi-firmware/: I also found the same about ndis driver. I was not even able to assign a ssid, mode, or a channel to a ndis0 interface. At least net/iwi-firmware works w/ WPA (even if the interface causes freeze after waking up from long sleep on IBM Thinkpad T42; Did you try to load and unload if_iwi.ko in /etc/rc.resume and /etc/rc.suspend? No, i hadn't; currently i am doing it manually when i am not sure about the length of the sleep state. I should look in to it, hunh.? BTW, when i read that you found a work around, i was expecting a work around to make ndis work. I'm sorry for my misleading wording then. Of course it's just a work around to get the PRO/Wireless 2200BG working at all. No problem. Actually, i myself am happy as long as there is some way to have a secure (semi-)stable wireless connection, on FreeBSD, w/ not-too-expensive hardware. It's just that I had forgotten about the existence of iwi. The last days I was using em0 to connect my Laptop to the network. Getting if_iwi to work after my initial posting was a relief. Same here, almost. I had not looked particularly hard in iwi or ndis -- but was aware of both -- until my sister's nagging broke me to buy a wireless AP/router. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Laptop choices
in message [EMAIL PROTECTED], wrote Gary Kline thusly... I'm looking for a newer laptop (a newer, faster ThinkPad, probably). There are ' some seriously cheap laptops on-sale, but they would probably be a bad choice because they have those touch/scratch mouse-pad things that I can't use. So:: does anybody know of a ThinkPad clone? Or, can the touch pads be disabled in the bios? Yes, yes the touch pad can be disabled in BIOS, at least on IBM ThinkPad T41 (my sister dislikes touchpad) T42 (i noticed the option in BIOS to disable touchpad) . I do not know of a ThinkPad clone; if/when you do, i would like to hear about them too. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
sh(1) man page needs to be updated for \[hHWw$] usage
A PR (bin/89410) about the handing of \[uW] in sh(1) on 6.0 caused me to look for its introduction. I found that '\[hHWw$]' escape sequences had been introduced in 5.4, mention of which so far has been lacking from sh.1. Could somebody please update the man page? Should i file a PR? - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Page fault, GEOM problem??
in message [EMAIL PROTECTED], wrote Michal Mertl thusly... Johan Ström wrote: On 18 nov 2005, at 18.43, Xin LI wrote: ... So, it seems it does run savecore after running dumpon and mounting disks etc... Is that wrong? No, this is normal. When you run savecore you need to have mounted filesystems. In order to mount the filesystems they may have to be checked. The fsck program requires big amount of memory to check larger filesystems so the swap has to be enabled. Core dumps are written to the dump device (swap) from the end whereas the swap is normally used from the beginning (or the other way around). Therefore there's quite a big chance that, even when the swap has to be used for fsck, the core dump is intact and usable. Is there any formula to calculate the size of swap to account for fsck core dump while assigning swap size (short of having two swap partitions)? If the usage of the swap file by fsck corrupts the core dump you may start after next crash in single user mode and run the commands manually (without enabling swap). Is that after kernel (re)boots? And would the commands to be executed be savecore followed by swapon? - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bzegrep behaviour not consistent with egrep?
in message [EMAIL PROTECTED], wrote James Long thusly... Should these two commands produce identical output? $ bzegrep 38436|41640 /var/log/maillog.0.bz2 | wc -l 0 $ bzcat /var/log/maillog.0.bz2 | egrep 38436|41640 | wc -l 121 And more fun, try also egrep -J| wc, which is similar to the 2d case above. Seems like the first e in bzegrep is erroneous. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bzegrep behaviour not consistent with egrep?
in message [EMAIL PROTECTED], wrote Jung-uk Kim thusly... On Thursday 20 October 2005 04:57 pm, Parv wrote: in message [EMAIL PROTECTED], wrote James Long thusly... ... $ bzegrep 38436|41640 /var/log/maillog.0.bz2 | wc -l 0 $ bzcat /var/log/maillog.0.bz2 | egrep 38436|41640 | wc -l 121 ... And more fun, try also egrep -J| wc, which is similar to the 2d case above. Can you elaborate the fun, please? In short: will you take bad choice of words as an explanation? In somewhat long form: i had read once, twice, or more times in past (most likely in comp.unix.*) that egrep was exactly not same as grep -E, and/or fgrep not exactly as grep -F. The OP's finding reminded me of that even if behaviour difference that was due to an actual bug. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, mergemaster dying due to problem w/ mtree -eU ...
in message [EMAIL PROTECTED], wrote Parv thusly... in message [EMAIL PROTECTED], wrote Scot Hetzel thusly... On 10/5/05, Parv [EMAIL PROTECTED] wrote: ... mtree -eU -f /misc/src-5/etc/mtree/BSD.root.dist -p /var/tmp/temproot/ mtree:No such file or directory *** Error code 1 Stop in /misc/src-5/etc. *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the temproot environment I have /usr/src symlinked ... lrwxr-xr-x 1 root wheel 9 Dec 21 2004 /usr/src@ - /misc/src lrwxr-xr-x 1 root wheel 5 Oct 5 00:04 /misc/src@ - src-5 drwxr-xr-x 21 root wheel 1024 Oct 5 03:49 /misc/src-5/ Not sure if I had run accros this problem when I move my source directory from /usr/src to /usr/src/5x. But I added: SOURCEDIR='/usr/src/5x/etc' to /etc/mergemaster.rc. I will try your suggestion, and report back. I tried again (w/ SOURCEDIR=/misc/src-5/etc) after installing 5-stable-2005.10.04.18.00.43; mergemaster still dies w/ the above error message in single user mode. There must be something that is missing in that mode (compared to multi user mode) for mergemaster not to work. Come to think of it, it seems to be a PATH problem as /usr/sbin is not included in PATH in single user mode here. I will update PATH try again (at some point). - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.x, mergemaster dying due to problem w/ mtree -eU ...
I am having problem using mergemaster in 5-stable () and had the same problem when i updated from 5.3 to 5.4. Following is the complete session after installworld of 5-stable ... # /usr/sbin/mergemaster -i *** The directory specified for the temporary root environment, /var/tmp/temproot, exists.This can be a security risk if untrusted users have access to the system. Use 'd' to delete the old /var/tmp/temproot and continue Use 't' to select a new temporary root directory Use 'e' to exit mergemaster Default is to use /var/tmp/temproot as is How should I deal with this? [Use the existing /var/tmp/temproot] d *** Deleting the old /var/tmp/temproot *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot mtree -eU -f /misc/src-5/etc/mtree/BSD.root.dist -p /var/tmp/temproot/ mtree:No such file or directory *** Error code 1 Stop in /misc/src-5/etc. *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the temproot environment I have /usr/src symlinked ... lrwxr-xr-x 1 root wheel 9 Dec 21 2004 /usr/src@ - /misc/src lrwxr-xr-x 1 root wheel 5 Oct 5 00:04 /misc/src@ - src-5 drwxr-xr-x 21 root wheel 1024 Oct 5 03:49 /misc/src-5/ So what is wrong on my end that mergemaster dies during mtree process? - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, mergemaster dying due to problem w/ mtree -eU ...
in message [EMAIL PROTECTED], wrote Parv thusly... I am having problem using mergemaster in 5-stable () Forgot to note the vintage of 5-stable, which is 2005.10.04.18.00.43. -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, mergemaster dying due to problem w/ mtree -eU ...
in message [EMAIL PROTECTED], wrote Scot Hetzel thusly... On 10/5/05, Parv [EMAIL PROTECTED] wrote: ... mtree -eU -f /misc/src-5/etc/mtree/BSD.root.dist -p /var/tmp/temproot/ mtree:No such file or directory *** Error code 1 Stop in /misc/src-5/etc. *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the temproot environment I have /usr/src symlinked ... lrwxr-xr-x 1 root wheel 9 Dec 21 2004 /usr/src@ - /misc/src lrwxr-xr-x 1 root wheel 5 Oct 5 00:04 /misc/src@ - src-5 drwxr-xr-x 21 root wheel 1024 Oct 5 03:49 /misc/src-5/ Not sure if I had run accros this problem when I move my source directory from /usr/src to /usr/src/5x. But I added: SOURCEDIR='/usr/src/5x/etc' to /etc/mergemaster.rc. I did not have above problem in 4.x branches w/ mergemaster wrt moving /usr/src to elsewhere. I will try your suggestion, and report back. Thank you. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, mergemaster dying due to problem w/ mtree -eU ...
in message [EMAIL PROTECTED], wrote Parv thusly... in message [EMAIL PROTECTED], wrote Scot Hetzel thusly... On 10/5/05, Parv [EMAIL PROTECTED] wrote: ... mtree -eU -f /misc/src-5/etc/mtree/BSD.root.dist -p /var/tmp/temproot/ mtree:No such file or directory *** Error code 1 [ OP notes that /usr/src is symlinked to elsewhere ] Not sure if I had run accros this problem when I move my source directory from /usr/src to /usr/src/5x. But I added: SOURCEDIR='/usr/src/5x/etc' to /etc/mergemaster.rc. I will try your suggestion, and report back. I tried it in *multiuser* mode. Regardless of /etc/mergemaster.rc, mergemaster worked w/o any problems. I will try using /etc/mergemaster.rc in single user mode when i will get the opportunity. I doubt that mergemaster will get past the mtree error there. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [HEADS UP] perl symlinks in /usr/bin will be gone
in message [EMAIL PROTECTED], wrote Jack L. Stone thusly... At 06:46 PM 1.30.2005 -0500, Parv wrote: in message [EMAIL PROTECTED], wrote Anton Berezin thusly... Unless I hear too many cries don't do that (with justification), I plan to not create any perl symlinks in /usr/bin in the forthcoming upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This will ONLY be true for FreeBSD 5.X and FreeBSD CURRENT I am for it. Please do do that. Thanks. Please don't do it If this were a mere vote of the respondents, the NAYs have it by far. Don't worry Anton has already stated, at least once, that the link(s) will live (and even more may be added) before i could have influenced him (fat chance given a large number of negative responses reached him before my sole positive reply). - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [HEADS UP] perl symlinks in /usr/bin will be gone
in message [EMAIL PROTECTED], wrote Anton Berezin thusly... Unless I hear too many cries don't do that (with justification), I plan to not create any perl symlinks in /usr/bin in the forthcoming upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This will ONLY be true for FreeBSD 5.X and FreeBSD CURRENT I am for it. Please do do that. Thanks. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sometimes 5.3-RELEASE-p5 is stuck at the last steps of shutdown
in message [EMAIL PROTECTED], wrote Rostislav Krasny thusly... I use FreeBSD 5.3-RELEASE-p5 on i386. Sometimes my system is stuck at the last steps of shutdown. Following quoting is what I saw yesterday when my system was stuck again (the last lines): init: some processes would not die; ps axl advised I did not have seen or notice this message. Waiting (max 60 seconds) for system process `vnlru' to stop... done Waiting (max 60 seconds) for system process `bufdaemon' to stop... done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining... 2 1 0 0 0 done No buffers busy after final sync I am using the same version as above on IBM ThinkPad T42 (2373-5TU). Before i removed the, well, removable CD/DVD drive, system would either turn off the power or bring up System halted ... Press a key to reboot or turn off power like message, depending upon the command issued (apm or acpi). After removing the CD/DVD drive (while the computer was turned off), system refused to shutdown (or bring up the message System halted ...), or to respond to Ctrl-Alt-Esc or Ctrl-Alt-Del keys. It just stuck at the above mentioned message, No buffers busy I tried 2-3 times, w/ acpi only, both in console and X. (I did not see anything interesting in the logs later.) (Yes, after reinserting the drive, system halts/shuts down as expected.) - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
4.9.x to 4.10: Stuck on reboot
Hi Generally Beautiful and Possibly Helpful People, Since version 4.9 and currently running version 4.10-RELEASE-p2, both i386, reboot causes only a hang up after system has been up for few hours. I did not have stuck-on-reboot problem somewhere between 4.6 4.8. Boot sequence hangs after following lines have been printed... lpt0: Printer on ppbus0 lpt0: Interrupt-driven port isa_probe_children: probing PnP devices Some relevant information... - Current dmesg (attached also) ... http://parv.holy.cow/parv/comp/unix/err/dmesg/dmesg-4.10-p2-2004.06.30.17.33.59 - Current kernel configuration ... http://parv.holy.cow/parv/comp/unix/cf/FreeBSD/KERNCONF - General overview of Dell Inspiron 5000e (laptop)... http://parv.holy.cow/parv/comp/unix/FreeBSD/delli5000e.xhtmls Is there any solution for the situation of stuck on reboot? - Parv -- Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.10-RELEASE-p2 #7: Sat Aug 28 12:06:36 EDT 2004 [EMAIL PROTECTED]:/misc/src-4.10/sys/BOVINE Calibrating clock(s) ... TSC clock: 696963716 Hz, i8254 clock: 1193170 Hz Timecounter i8254 frequency 1193170 Hz CPU: Intel Pentium III (696.96-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 402587648 (393152K bytes) Physical memory chunk(s): 0x01000 - 0x9efff, 647168 bytes (158 pages) 0x000422000 - 0x017fe7fff, 398221312 bytes (97222 pages) avail memory = 387149824 (378076K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f7210 bios32: Entry = 0xfd890 (c00fd890) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x11e pnpbios: Found PnP BIOS data at 0xc00f7240 pnpbios: Entry = f:a600 Rev = 1.0 pnpbios: Event flag at 4b4 Other BIOS signatures found: ACPI: 000f71d0 Preloaded elf kernel kernel at 0xc03fb000. Pentium Pro MTRR support enabled Creating DISK md0 md0: Malloc disk pci_open(1):mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) Using $PIR table, 7 entries at 0xc00fdf50 apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard found- vendor=0x8086, dev=0x7190, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 1, range 32, base e000, size 26 found- vendor=0x8086, dev=0x7191, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1secondarybus=1 found- vendor=0x104c, dev=0xac1c, revid=0x01 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=255 found- vendor=0x104c, dev=0xac1c, revid=0x01 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=255 found- vendor=0x8086, dev=0x7110, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found- vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[20]: type 1, range 32, base 1050, size 4 found- vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=5 map[20]: type 1, range 32, base 1060, size 5 found- vendor=0x8086, dev=0x7113, revid=0x03 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[90]: type 1, range 32, base 1040, size 4 found- vendor=0x125d, dev=0x1978, revid=0x10 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=5 map[10]: type 1, range 32, base 1400, size 8 pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 found- vendor=0x1002, dev=0x4c46, revid=0x02 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f800, size 26 map[14]: type 1, range 32, base 2000, size 8 map[18]: type 1, range 32, base f400, size 14 pci1: PCI bus on pcib1 pci1: ATI model 4c46 graphics accelerator (vendor=0x1002, dev=0x4c46) at 0.0 irq 11 pci_cfgintr_linked: linked (60) to hard-routed irq 11 pci_cfgintr: 0:4 INTA routed to irq 11 pcic0: TI PCI-1225 PCI-CardBus Bridge irq 11 at device 4.0 on pci0 pcic0: PCI Memory allocated: 0x8800 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr save][FUNC pci
Re: 4.9.x to 4.10: Stuck on reboot
in message [EMAIL PROTECTED], wrote Parv thusly... Sorry about the inaccessible URLs in previous message. Here they are again... - Current dmesg (attached also) ... http://www103.pair.com/parv/comp/unix/err/dmesg/dmesg-4.10-p2-2004.06.30.17.33.59 - Current kernel configuration ... http://www103.pair.com/parv/comp/unix/cf/freebsd/KERNCONF - General overview of Dell Inspiron 5000e (laptop)... http://www103.pair.com/parv/comp/unix/freebsd/delli5000e.xhtmls - Parv -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.9-STABLE -- 4.8-RELEASE downgrade. Pitfalls?
wrote Chuck Swiger thusly... Parv wrote: [ ... ] Port making will fail if you keep ports trees updated at least due to use of new make(1) syntax introduced, in 4.9, in a port's Makefile. The problem i noticed was related to use of parenthesis in .if ... .endif structure. Thanks for the response, Parv, but ugh! I cringe at the notion that continually tweaking make and the port Makefiles causes problems with backwards compatibility to a still-supported FreeBSD release. That looks like the message that i sent to one of the FreeBSD lists. After searching PR database, it seems somebody else found the exact reason... http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/60288 I think life w/ NetBSD would not be so bad via its FreeBSD ports equivalent pkgsrc. One other known benefit, via pkgviews, is that multiple versions of a particular an be simultaneously installed/used at the cost of use of many symbolic links. Here are some things on pkgsrc ... http://www.NetBSD.org/~jlam/pkgsrcCon/presentations.html http://www.NetBSD.org/Documentation/pkgsrc/ http://www.NetBSD.org/Documentation/software/packages.html http://www.NetBSD.org/Documentation/software/pkgviews.pdf The last time i read papers/slides listed on pkgsrcCon, ugly symbolic links would have been the only problem for me after the problem of potentially missing ported software that i currently use on FreeBSD. (No, i have not checked the pkgsrc list). Mind you that i have no experience of NetBSD or pkgsrc, so both may have their own problems currently unknown to me. - Parv -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.7-release-2002.11.14.02.05.57 - spontaneous reboot possibly related to modem/pccard/ppp
in message [EMAIL PROTECTED], wrote Julian Stacey thusly... parv wrote: in message [EMAIL PROTECTED], wrote parv thusly... so far i had experienced 2 spontaneous reboots on freebsd 4.7-release-2002.11.14.02.05.57 (on dell inspiron 5000e). curses! this time, computer locked up just after PPP connection went out. :( laptop wasn't connected to AC-mains. i couldn't find anything in the logs. last file that was updated was ppp log showing normal activity only. ... Weak batteries maybe ? I had a tower a few years back, where FreeBSD would guarantee to crash each `mount /cdrom`. i thought about but that doesn't seem likely. when the last lockup happened, one battery was consumed 20%, another battery had yet to be consumed. i verified that by apm (just before the lock), and by pressing a button on the batteries themselves. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
4.7-release-2002.11.14.02.05.57 - spontaneous reboot possibly related to modem/pccard/ppp
so far i had experienced 2 spontaneous reboots on freebsd 4.7-release-2002.11.14.02.05.57 (on dell inspiron 5000e). after being connected to internet (user ppp) via linksys pcmlm56 modem (on sio1) for say 2-3 minutes, card removed message comes (despite that it's still connected); messages follow indicating that the card has been found (even though card remain untouched through out the process)... moo /kernel: Nov 28 21:32:48 moo pccardd[60]: sio1: Linksys (EtherFast 10100 + 56K PC Card (PCMLM56)) removed. moo /kernel: Nov 28 21:32:54 moo pccardd[60]: Card Linksys(EtherFast 10100 + 56K PC Card (PCMLM56)) [(null)] [( Linksys (EtherFast 10100 + 56K PC Card (PCMLM56)) [(null)] [(null)] moo /kernel: Nov 28 21:32:54 moo pccardd[60]: Found existing driver (sio) for Linksys moo /kernel: Nov 28 21:32:54 moo pccardd[60]: Using I/O addr 0x2f8, size 8 moo /kernel: Nov 28 21:32:54 moo pccardd[60]: Using I/O addr 0x300, size 32 moo /kernel: Nov 28 21:32:54 moo pccardd[60]: Setting config reg at offs 0xffe0 to 0x43, Reset time = 900 ms moo /kernel: Nov 28 21:33:00 moo pccardd[60]: Assigning I/O window 0, start 0x2f8, size 0x8 flags 0x7 moo /kernel: Nov 28 21:33:00 moo pccardd[60]: Assigning I/O window 1, start 0x300, size 0x20 flags 0x7 moo /kernel: Nov 28 21:33:00 moo pccardd[60]: Assign sio1, io 0x2f8-0x2ff, mem 0x0, 0 bytes, irq 11, flags 0 moo /kernel: Nov 28 21:33:00 moo pccardd[60]: sio1: Linksys (EtherFast 10100 + 56K PC Card (PCMLM56)) inserted. ...then machine hangs, preparing for reboot (/tmp is mounted on mfs)... Nov 28 21:38:13 moo /kernel: swapon: adding /dev/ad0s2b as swap device Nov 28 21:38:13 moo /kernel: Automatic boot in progress... Nov 28 21:38:13 moo /kernel: Warning: Block size and bytes per inode restrict cylinders per group to 92. Nov 28 21:38:13 moo /kernel: Warning: inode blocks/cyl group (125) = data blocks (37) in last Nov 28 21:38:13 moo /kernel: cylinder group. This implies 1200 sector(s) cannot be allocated. ...any ideas? i don't know how significant this is, but this type of spontaneous reboot has had happened only when working on 2 batteries. below are possibly relevant files... kernel: http://parv.holy.cow/parv/comp/unix/cf/freebsd/KERNCONF dmesg (2002.10.22.03.43.30, will update asap): http://parv.holy.cow/parv/comp/unix/err/dmesg/delli5000e-dmesg /etc/pccard.conf: http://parv.holy.cow/parv/comp/unix/cf/network/pccard.pcmlm56 - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.7-release-2002.11.14.02.05.57 - spontaneous reboot possibly related to modem/pccard/ppp
in message [EMAIL PROTECTED], wrote parv thusly... so far i had experienced 2 spontaneous reboots on freebsd 4.7-release-2002.11.14.02.05.57 (on dell inspiron 5000e). after being connected to internet (user ppp) via linksys pcmlm56 modem (on sio1) for say 2-3 minutes, card removed message comes (despite that it's still connected); messages follow indicating that the card has been found (even though card remain untouched through out the process)... ... http://parv.holy.cow/parv/comp/unix/cf/freebsd/KERNCONF http://parv.holy.cow/parv/comp/unix/err/dmesg/delli5000e-dmesg http://parv.holy.cow/parv/comp/unix/cf/network/pccard.pcmlm56 sorry, i didn't realise that holy.cow domain exists only in the mind of my machine. below are the correct ones, for sure i promise... kernel: http://www103.pair.com/parv/comp/unix/cf/freebsd/KERNCONF dmesg: http://www103.pair.com/parv/comp/unix/err/dmesg/delli5000e-dmesg /etc/pccard.conf: http://www103.pair.com/parv/comp/unix/cf/network/pccard.pcmlm56 - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: after cvsup'd to RELENG_4_7 source, Could not find bsd.init.mk bsd.links.mk error
in message [EMAIL PROTECTED], wrote parv thusly... first i did make cleandir; make clean in /usr/src w/o problems. then when i tried make modules-cleandir make modules-cleandepend in /usr/src/sys/complile/KERNCONF, i get the following error... cd ../../modules ; env MAKEOBJDIRPREFIX=/cdrw/src/sys/compile/BOVINE/modules DEBUG=-g DEBUG_FLAGS=-g MACHINE=i386 make cleandir === accf_data /cdrw/src/sys/modules/accf_data/../../conf/kmod.mk, line 63: Could not find bsd.init.mk /cdrw/src/sys/modules/accf_data/../../conf/kmod.mk, line 190: Could not find bsd.links.mk make: fatal errors encountered -- cannot continue *** Error code 1 for the sake of closure... i removed the /sys/compile/BOVINE directory, followed by (cvsup to RELENG_4_7 for the sake of my sanity, followed by) another cleaning. that didn't produce the problem. after another install of world/kernel, reissuing the above modules-clean* commands didn't produce any errors either. thankfully! so, above problem is not a problem any more. not for me. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Periodic: support for non-sendmail MTAs
in message [EMAIL PROTECTED], wrote Gregory Neil Shapiro thusly... Set: daily_submit_queuerun=NO in /etc/periodic.conf. ah, i was wondering about that that setting it in /etc/rc.conf doesn't do much. thanks. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
boot process stuck at start_init: trying /sbin/init
installed freebsd source is/are dated around the hours of aug 10, 11
2002.
well, everything was going great... until i ran MAKEDEV thru
mergemaster. after running MAKEDEV, i saw errors flying by about
missing wheel operator groups... to which i didn't pay much
attention (as i was thinking that's just silly! wheel group has to
be in /etc/{passwd,groups}.)
since then after rebooting, i/boot process cannot go past...
start_init: trying /sbin/init
...un/loading new/old kernel doesn't further the boot in any way.
various devices -- cd-rw, floppy, hard drives, etc. -- are
identified correctly.
if it helps, kernel configuration is...
http://www103.pair.com/parv/comp/unix/cf/freebsd/KERNCONF
...and not-so-old (4.6-stable jun 26-27 2002) boot log...
http://www103.pair.com/parv/comp/unix/err/dmesg/delli5000e-dmesg
...what can i do now?
thanks in advance.
kindly cc me ([EMAIL PROTECTED]) as i can't access freebsd list
proper.
- desperate freebsd user
__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: 4.6 kernel build failure
in message [EMAIL PROTECTED], wrote Roelof Osinga thusly... cc -O -pipe -march=pentiumpro -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -c linux_sysent.c In file included from linux_sysent.c:14: linux_proto.h:57: syntax error before `linux_time_t' linux_proto.h:57: `linux_time_t' undeclared here (not in a function) hi roelof, i just couldn't take your suffering anymore was mightly hoping that you just might search google out of sheer desparation. i also had the problem; followed the UPDATING comment about it which didn't work, so i sent it to the -stable list in jan 2002. here is another thing to try... http://spitfire.velocet.net/pipermail/freebsd-stable/2002-January/025084.html -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: makeworld worked - my first attempt at this revisited
in message [EMAIL PROTECTED], wrote Chip Wiegand thusly... In a nutshell, these are the steps I followed - # less /usr/src/UPDATING # cd /usr/obj/ # chflags -R noschg * # rm -rf usr (this didn't exist to begin with) # ls -la (it was empty before I even started) # cd /usr/src # make cleandir make cleandir # make buildworld # make buildkernel KERNCONF=GENERIC # make installkernel KERNCONF=GENERIC # reboot # boot -s # fsck -p # mount -t ufs -a you do understand that there is no need to mount all the ufs's, only filesystems need to installworld? if you have only the required partitions as ufs's, then, of course, there is no difference. # swapon -a say, why would one want to do fsck and/or swapon? just to be safe? # cd /usr/src # make installworld # mergemaster -v you may also want to look into -i option (to install uninstalled files w/o being asked). - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
double man entries
after upgrading to 4-stable-2002.05.17.16.15.01 (4.6-rc) -- from 4-stable-2002.05.02.08.43.44 (4.6-prerelease) -- i see double entries for the same section of a man page, as now there exist compressed (old) uncompressed (new) versions -r--r--r-- 2 root wheel 999 May 19 12:13 /usr/share/man/man1/apropos.1 -r--r--r-- 1 root wheel 605 Jan 20 2001 /usr/share/man/man1/apropos.1.gz -r--r--r-- 1 root wheel 30586 May 19 12:12 /usr/share/man/man1/ar.1 -r--r--r-- 1 root wheel 10137 Aug 15 2001 /usr/share/man/man1/ar.1.gz -r--r--r-- 1 root wheel8458 May 19 12:18 /usr/share/man/man1/asn1parse.1 -r--r--r-- 1 root wheel3657 May 3 17:32 /usr/share/man/man1/asn1parse.1.gz -r--r--r-- 4 root wheel5650 May 19 12:15 /usr/share/man/man1/at.1 -r--r--r-- 1 root wheel2368 Mar 17 01:36 /usr/share/man/man1/at.1.gz -r--r--r-- 2 root wheel3188 May 19 12:15 /usr/share/man/man1/basename.1 -r--r--r-- 1 root wheel1582 Sep 20 2001 /usr/share/man/man1/basename.1.gz -r--r--r-- 1 root wheel 34468 May 19 12:12 /usr/share/man/man1/bc.1 -r--r--r-- 1 root wheel 11774 Mar 8 2001 /usr/share/man/man1/bc.1.gz ...there are total of 4298 entries like above. i didn't encounter any doublets w/ 4.6-prerelease during regular use of man, only now in 4.6-rc. man -a -w ar gives... /usr/share/man/cat1/ar.1.gz (source: /usr/share/man/man1/ar.1) /usr/share/man/cat1/ar.1.gz (source: /usr/share/man/man1/ar.1.gz) /usr/share/man/man1aout/ar.1aout /usr/share/man/man1aout/ar.1aout.gz /usr/share/man/cat4/i386/ar.4.gz (source: /usr/share/man/man4/i386/ar.4) /usr/share/man/cat4/i386/ar.4.gz (source: /usr/share/man/man4/i386/ar.4.gz) /usr/share/man/man4/ar.4.gz /usr/share/man/man5/ar.5 /usr/share/man/man5/ar.5.gz ...man 4 ar (yes, that is w/o -a option) produces ar(4) page twice. below is part of /etc/make.conf which may be of some siginificance... INSTALL=install -C NOMANCOMPRESS= false ...any ideas what went wrong and/or how to avoid it in future? - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: wordperfect
(changed followups to -questions, from -stable, where it belongs) in message [EMAIL PROTECTED], wrote Eric thusly... ... Can someone who has successfully installed WordPerfect 8 (or 9?) to FBSD please let me know 1. Does the performance meet production standards, 2. Any tips for installation, and ... consider the following to be a tip. or, a rant. your choice. xwp can be a PITA when invoked from xterm (as compared to when invoked from root menu of a window manager). consider i am in /usr/home/parv; i create a subdirectory ./tmp. i invoke xwp in /usr/home/parv from xterm. now, if i try to save a file in ./tmp, xwp complains about missing files. if i happen to be in /usr/home/parv when the first i started xwp, registration key is saved there. if i, by misfortune, happen to be in /usr/home/parv/tmp start xwp from there, i will be asked for the registration key .wprc directory will be created in /usr/home/parv/tmp. so far, wherever i saved a file, a .wprc directory was created. talk about the sheep droppings[0]! now, i consciously try to avoid starting xwp from the command line and use root menu (in fvwm2) to launch xwp. oh, if i happened not to be in /usr/home/parv when i started[1] X, too bad... [0] in case you don't know, sheep droppings are in small black round balls; generally aligned in a line as sheep walks poops. [1] the working directory is inherited in X (from console) if not properly taken care of, say in xinitrc. if you start X from /tmp, you will see be in that directory when you start xterm, for example. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
cvsup usable UTC date for tracking -stable
i know how to track a tree via cvsup w/ tag and date. my question is where/how do i find the freeze date to sync my tree? for example, i want to sync src to 4.5-rc2 but not current -stable. what date will it be, then, for 4.5-rc2? i read RELNOTES and README at... ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.5-RC2/ ...couldn't find anything (or, i missed). - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: cvsup usable UTC date for tracking -stable
in message [EMAIL PROTECTED], wrote Christopher Schulte thusly... At 12:42 AM 1/20/2002 -0800, Jim Mock wrote: On Sun, 20 Jan 2002 at 03:21:00 -0500, parv wrote: i know how to track a tree via cvsup w/ tag and date. my question is where/how do i find the freeze date to sync my tree? ... I'm not sure what you're talking about here. The current -STABLE branch *is* 4.5-RC2. jim, i know. but after release of the -rc2 iso image, -stable is more than just -rc2. I think the original poster was asking how to use cvsup to sync source tree to the exact cut of a rcX.iso. aka how to reproduce exactly the source that was used to generate an official RC. yes, that is exactly what i am seeking: how to find the date of sources from which the iso image is built. It's going to be something like src-all date=2002.01.xx.xx.xx.xx in the supfile. That'll allow testing to happen, without needing to pull an entire .iso file. Of course, 'cvsup - make world' is not the same as 'insert cd, install from scratch' i guess, it's not. then again, i am doing it for my own peace of mind, not necessarily actively testing the -rc2. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: how to tell if 'make buildworld' finished?
in message [EMAIL PROTECTED],
wrote Christopher Schulte thusly...
At 10:37 PM 1/6/2002 +0100, you wrote:
Hi,
I usually run a shell command like this ('#' is the prompt):
# (date; make buildworld; date) | tee /var/tmp/buildworld.log
You can also look at the `script` command. When executed, a new shell will
begin and all output to terminal is stored in a file which can be checked
after the fact.
christopher, i know about the command script. i avoid it whenever
i can for two reasons: (1) sometimes it's impossible to send SIGTSTP
(STOP signal from keyboard) and (2) control characters at the end of
line.
i use following syntax as appropriate...
# command log
# command log 21
# command | tee [-a] log
thanks anyway.
- parv
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: how to tell if 'make buildworld' finished?
in message [EMAIL PROTECTED],
wrote Oliver Fromme thusly...
Hi,
hi there.
I usually run a shell command like this ('#' is the prompt):
# (date; make buildworld; date) | tee /var/tmp/buildworld.log
So you have a datestamp output at the very beginning and at
the very end.
thanks oliver. somebody, off the list, contacted me w/ similar
clue. he preferred to use this syntax...
# date command date
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: building kernel problem w/ linux_proto.h
in message [EMAIL PROTECTED], wrote Brian T. Schellenberger thusly... On Sunday 06 January 2002 10:28 am, parv wrote: hi, i cvsup'd old sources (4-stable oct 13 2001) to current (4-stable 2002.01.05.15.45.19). at this point i am stuck at errors w/ linux_proto.h ... first i ran make cleandir in /usr/src, removed /usr/obj/*, and tried to build kernel. after first snag, i searched the internet which indicated to read src/UPDATING. well, first i did make modules-clean in src/sys/compile/$KERNCONF as i do not have MODULES_WITH_WORLD=yes in /etc/make.conf. after that when i tried again, it failed. so i tried again after running make cleandir in src/sys/modules/linux w/o any success. This is probably a more subtle fix than this, but the following is what finally worked for me: rm -r /usr/obj rm -r /usr/src cvsup /root/sup/conf ln -s /root/BTS /usr/src/sys/i386/conf ... CAUTION2: Without a broadband, this would be tiresome--it causes the entire source to be re-downloaded from the net. you know what, that's exactly what i am doing right now... it started at 2.43p edt, and currently cvsup is downloading src/contrib/ncurses; time now is 6.23p. a long way to go on dial up connection. NOTE: There is almost certainly a more subtle solution. But if you have a fast connection, just doing the above is probably a lot easier less frustrating than tracking it down. i would sure hope that somebody else will track it down, as doing fresh cvsup of src tree needs patience, at least on dial up connection. thanks brian. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
kernel config fails if src/sys/compile directory doesn't exit. bug?
i upgraded recently to 4.4-release (releng_4_4 cvsup tag) from -prerelease. i noticed that kernel config fails (in /usr/src/sys/i386/conf) if /usr/src/sys/compile directory doesn't exist. tried these variations... # [/usr/sbin/]config [-r] BOVINE ...error message was... config: ../../compile/BOVINE: No such file or directory ...after creating the ../../compile directory, config ran and kernel was installed w/o problems. questions: - shouldn't config create the src/sys/compile? - is this a software (known) bug? - if config isn't supposed to create the compile directory and kernel config/build fails, shouldn't it be documented? by the way, config(8) talks only about the destination directory creation (in this case, BOVINE) but not any intermediary... ... config should be run from the conf subdirectory of the system source (usually /sys/ARCH/conf), where ARCH represents one of the architectures supported by FreeBSD. config creates the directory ../../compile/SYSTEM_NAME or the one given with the -d option as neces- sary and places all output files there. If the output directory already exists and the -r flag was specified, it will be removed first. ... -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: of shell, find, and (g)xargs (Re: mass uninstall all ports?)
i forgot to include this message in my last reply, so bear w/ me...
on Jul 16 11:29, i got this from Andreas...
On Thu, Jul 12, 2001 at 07:10:17PM -0400, parv wrote:
...in the end both will do the same thing: remove/delete all the
installed software as listed in /var/db/pkg. if you go the 'pkg_info'
route, you should add '-f' and or '-d' flag.
if pkg_delete/xargs/shell complain that 'pipe broken', 'too many
arguments', or some such, then you can try this...
# find /var/db/pkg -type d -execdir pkg_delete -fd {} \;
This forks a pkg_delete command for every port found, thats expensive.
Why not use find/xargs combination in this case as well ?
( cd /var/db/pkg; find . -type d | xargs pkg_delete )
Andreas ///
to give everybody else the right context, my last message was a reply
to abe, omitted from the above andreas' quoted message...
on Jul 12 18:48, i got this from abram...
I have updated the ports using cvsup. So, this:
cd /var/db/pkg pkg_delete -fd *
will remove all the packages and ports that are
installed?
I really want to understand what I'm doing here ;-)
Another person suggested I do:
pkg_info | cut -d\ -f1 | xargs pkg_delete
what is the difference between what these two commands
will do?
Abe
andreas, your 'find+xargs' script is basically same as
'pkg_info+cut+xargs', as quoted by abe above, as far as 'xargs'
is concerned. so the 'too many arguments' problem is still exists.
thus was the reason of using 'find ... -execdir ...'; i suppose i
should have noted the expense instead of intentionally omitting it.
--
so, do you like word games or scrabble?
- parv
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
problem w/ make buildworld sha1-586.so
(i am using 4.2-stable on intel pentium iii 600/700 MHz) after sources are corrected for errors related to stty and successfully building world once (around 5a), i cvusp'd the sources (around 6-8 a) again tried building the world, but the following error occured this time... (haven't seen any messages yet on this either on this list or on cvs-all, or on freebsd-questions) - parv error log ... cc -O -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/lib crypto -DNO_IDEA -DL_ENDIAN -DSHA1_ASM -DBN_ASM -DMD5_ASM -DRMD160_ASM -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sec ure/lib/libcrypto/../../../crypto/openssl/crypto/sha/sha_dgst.c -o sha_dgst.o cc -fpic -DPIC -O -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/se cure/lib/libcrypto -DNO_IDEA -DL_ENDIAN -DSHA1_ASM -DBN_ASM -DMD5_ASM -DRMD160_ASM -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/sha/sha_dgst.c -o sha_dgst.So cc -O -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/lib crypto -DNO_IDEA -DL_ENDIAN -DSHA1_ASM -DBN_ASM -DMD5_ASM -DRMD160_ASM -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sec ure/lib/libcrypto/../../../crypto/openssl/crypto/sha/sha_one.c -o sha_one.o cc -fpic -DPIC -O -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/se cure/lib/libcrypto -DNO_IDEA -DL_ENDIAN -DSHA1_ASM -DBN_ASM -DMD5_ASM -DRMD160_ASM -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/sha/sha_one.c -o sha_one.So cc -O -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/lib crypto -DNO_IDEA -DL_ENDIAN -DSHA1_ASM -DBN_ASM -DMD5_ASM -DRMD160_ASM -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sec ure/lib/libcrypto/../../../crypto/openssl/crypto/sha/sha1_one.c -o sha1_one.o cc -fpic -DPIC -O -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/se cure/lib/libcrypto -DNO_IDEA -DL_ENDIAN -DSHA1_ASM -DBN_ASM -DMD5_ASM -DRMD160_ASM -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/sha/sha1_one.c -o sha1_one.So cc -O -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/lib crypto -DNO_IDEA -DL_ENDIAN -DSHA1_ASM -DBN_ASM -DMD5_ASM -DRMD160_ASM -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sec ure/lib/libcrypto/../../../crypto/openssl/crypto/sha/sha1dgst.c -o sha1dgst.o cc -fpic -DPIC -O -pipe -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/se cure/lib/libcrypto -DNO_IDEA -DL_ENDIAN -DSHA1_ASM -DBN_ASM -DMD5_ASM -DRMD160_ASM -DNO_IDEA -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/sha/sha1dgst.c -o sha1dgst.So perl -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/des/asm:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/cr ypto/perlasm /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/sha/asm/sha1-586.pl elf 386 sha1-586.pl.s ; as sha1-586 .pl.s -o sha1-586.o perl -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/des/asm:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/cr ypto/perlasm /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/sha/asm/sha1-586.pl elf 386 sha1-586.pl.s ; as sha1-586 .pl.s -o sha1-586.So sha1-586.pl.s: Assembler messages: sha1-586.pl.s:1: Error: Rest of line ignored. First ignored character is `%'. *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
