recent current panic: ic: bio_offset 0 wrong, should be 16844800
Recent i386 CURRENT panic at boot diskless PC: Mounting root from nfs: NFS ROOT: 1.1.1.1:/i386/netboot Interface fxp0 IP-Address 1.1.1.2 Broadcast 1.1.1.255 Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point. Starting file system checks: cp: utmp: Read-only file system /etc/rc.d/cleanvar: cannot create /var/run/clean_var: Read-only file system +++ mount_md of /var +++ populate /var using /etc/mtree/BSD.var.dist +++ create log files based on the contents of /etc/newsyslog.conf +++ create lastlog ic: bio_offset 0 wrong, should be 16844800 Debugger(panic) Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 db tr Debugger(c083a924,c08fc1c0,c084129f,d628b774,100) at Debugger+0x54 panic(c084129f,0,0,1010800,0) at panic+0xd5 dev_strategy(c79f59e0,0,8100,d628b7b0,c0614d68) at dev_strategy+0xb8 spec_freeblks(d628b808,d628b834,c0751488,d628b808,0) at spec_freeblks+0xb2 spec_vnoperate(d628b808,0,1008,0,2b3) at spec_vnoperate+0x18 ffs_blkfree(c2c46000,c2d9d618,2021,0,800) at ffs_blkfree+0x1e8 handle_workitem_freeblocks(c2d7a400,0,0,d628b918,0) at handle_workitem_freeblock s+0x328 softdep_setup_freeblocks(c2dd4230,0,0,800,c79f59e0) at softdep_setup_freeblocks+ 0x8a3 ffs_truncate(c2dfee38,0,0,0,c1672d00) at ffs_truncate+0x6ff handle_workitem_remove(c2ca7ee0,0,c2dd4230,1,d628bb8c) at handle_workitem_remove +0x1ab softdep_setup_remove(c79f4388,c2dd4ec4,c2dd4230,1,d628bbb4) at softdep_setup_rem ove+0xcc ufs_dirremove(c2de0e38,c2dd4230,800c,1,d628bbc0) at ufs_dirremove+0x16d ufs_rmdir(d628bc20,d628bccc,c06b4424,d628bc20,d628bc1c) at ufs_rmdir+0xef ufs_vnoperate(d628bc20,d628bc1c,2,c2ca6400,c08d2400) at ufs_vnoperate+0x18 kern_rmdir(c2c8ba00,bfbfef56,0,d628bd40,c07d0bb0) at kern_rmdir+0x1b4 rmdir(c2c8ba00,d628bd10,c0855704,3ee,1) at rmdir+0x22 syscall(2f,2f,2f,0,0) at syscall+0x2c0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (137, FreeBSD ELF32, rmdir), eip = 0x280bd1af, esp = 0xbfbfee7c, ebp = 0xbfbfee98 --- db Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Who needs these silly statfs changes...
On Wed, Nov 12, 2003 at 06:04:00PM -0800, Kris Kennaway wrote: ...my sparc machine reports that my i386 nfs server has 15 exabytes of free space! enigma# df -k Filesystem 1K-blocks Used Avail Capacity Mounted on rot13:/mnt2 56595176 54032286 18014398507517260 0%/rot13/mnt2 18014398507517260 = 2^54 - 1964724. and 2^54KB == 2^64 bytes. Is it possible that rot13:/mnt2 has negative free space? (ie it's into the 8-10% reserved area). Kris Now accepting payment for data hosting Kennaway Have you tried writing a couple of GB to the NFS filesystem? Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
new kernel and old programs - bad system call
Hi, Is it ok to run a new kernel (after the statfs changes) and older programs? I thought so from what i gathered out of the commit messages, but my test box doesn't like it at all... Well except if something else broke stuff: ## ... Mounting root from ufs:/dev/da0s1a pid 50 (sh), uid 0: exited on signal 12 Enter full pathname of shell or RETURN for /bin/sh: # ls pid 56 (ls), uid 0: exited on signal 12 Bad system call # ## I thought that there might have been some leftover in my kernel compile directory to spoil things, so I did a make clean in the kernel directory and tried again, but it still does the same. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Who needs these silly statfs changes...
On Thu, Nov 13, 2003 at 06:44:25PM +1100, Peter Jeremy wrote: On Wed, Nov 12, 2003 at 06:04:00PM -0800, Kris Kennaway wrote: ...my sparc machine reports that my i386 nfs server has 15 exabytes of free space! enigma# df -k Filesystem 1K-blocks Used Avail Capacity Mounted on rot13:/mnt2 56595176 54032286 18014398507517260 0%/rot13/mnt2 18014398507517260 = 2^54 - 1964724. and 2^54KB == 2^64 bytes. Is it possible that rot13:/mnt2 has negative free space? (ie it's into the 8-10% reserved area). Yes, that's precisely what it is..the bug is either in df or the kernel (I suspect the latter, i.e. something in the nfs code). Kris pgp0.pgp Description: PGP signature
Vinum doesn't work anymore
Hello, I'm having major problems with the latest kernel sources and vinum. I don't really know where to begin the debug. For now, I'll have to run older sources just to have vinum working. Vinum isn't able to detect my volume, even though it worked fine before the install and reboot. Here's some info. Script started on Thu Nov 13 02:14:17 2003 # kldunload vinum.ko # ls -la /boot/kernel/vinum.ko -r-xr-xr-x 1 root wheel 97304 Nov 13 02:10 /boot/kernel/vinum.ko # ls -la /sbin/vinum -r-xr-xr-x 1 root wheel 752300 Nov 13 01:58 /sbin/vinum # kldload /boot/kernel/vinum.ko # /sbin/vinum vinum - start ** no drives found: No such file or directory vinum - dumpconfig Drive a:Device /dev/ad1s1e Created on at Sat Jul 19 03:10:25 2003 Config last updated Thu Nov 13 01:45:34 2003 Size: 200047002624 bytes (190779 MB) volume raid5 state up plex name raid5.p0 state up org raid5 1020s vol raid5 sd name raid5.p0.s0 drive a len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 0s sd name raid5.p0.s1 drive b len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 1020s sd name raid5.p0.s2 drive c len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 2040s sd name raid5.p0.s3 drive d len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 3060s sd name raid5.p0.s4 drive e len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 4080s sd name raid5.p0.s5 drive f len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 5100s [... etc for all the drives ...] vinum - read /dev/ad1 ** no drives found: No such file or directory Can't save Vinum config: No child processes vinum - quit # exit Script done on Thu Nov 13 02:15:17 2003 Also, when I tried fixing this problem by trying to compile vinum into the kernel (maybe would help, probably wouldn't), I got a compile error. The kernel is just the GENERIC kernel with device vinum added at the end of it. Here is the error: cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/vinum/vinum.c /usr/src/sys/dev/vinum/vinum.c: In function `vinumattach': /usr/src/sys/dev/vinum/vinum.c:136: error: structure has no member named `p_intr_nesting_level' /usr/src/sys/dev/vinum/vinum.c:143: error: structure has no member named `p_intr_nesting_level' /usr/src/sys/dev/vinum/vinum.c:150: error: structure has no member named `p_intr_nesting_level' /usr/src/sys/dev/vinum/vinum.c:162: error: structure has no member named `p_intr_nesting_level' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC_WITH_VINUM. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. The sources are freshly cvsuped from Nov 12, 2003. Cosmin Stroe. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recent current panic: ic: bio_offset 0 wrong, should be 16844800
This should be fixed now. In message [EMAIL PROTECTED], Alex Deiter writes: Recent i386 CURRENT panic at boot diskless PC: Mounting root from nfs: NFS ROOT: 1.1.1.1:/i386/netboot Interface fxp0 IP-Address 1.1.1.2 Broadcast 1.1.1.255 Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point. Starting file system checks: cp: utmp: Read-only file system /etc/rc.d/cleanvar: cannot create /var/run/clean_var: Read-only file system +++ mount_md of /var +++ populate /var using /etc/mtree/BSD.var.dist +++ create log files based on the contents of /etc/newsyslog.conf +++ create lastlog ic: bio_offset 0 wrong, should be 16844800 Debugger(panic) Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 db tr Debugger(c083a924,c08fc1c0,c084129f,d628b774,100) at Debugger+0x54 panic(c084129f,0,0,1010800,0) at panic+0xd5 dev_strategy(c79f59e0,0,8100,d628b7b0,c0614d68) at dev_strategy+0xb8 spec_freeblks(d628b808,d628b834,c0751488,d628b808,0) at spec_freeblks+0xb2 spec_vnoperate(d628b808,0,1008,0,2b3) at spec_vnoperate+0x18 ffs_blkfree(c2c46000,c2d9d618,2021,0,800) at ffs_blkfree+0x1e8 handle_workitem_freeblocks(c2d7a400,0,0,d628b918,0) at handle_workitem_freeblock s+0x328 softdep_setup_freeblocks(c2dd4230,0,0,800,c79f59e0) at softdep_setup_freeblocks+ 0x8a3 ffs_truncate(c2dfee38,0,0,0,c1672d00) at ffs_truncate+0x6ff handle_workitem_remove(c2ca7ee0,0,c2dd4230,1,d628bb8c) at handle_workitem_remove +0x1ab softdep_setup_remove(c79f4388,c2dd4ec4,c2dd4230,1,d628bbb4) at softdep_setup_rem ove+0xcc ufs_dirremove(c2de0e38,c2dd4230,800c,1,d628bbc0) at ufs_dirremove+0x16d ufs_rmdir(d628bc20,d628bccc,c06b4424,d628bc20,d628bc1c) at ufs_rmdir+0xef ufs_vnoperate(d628bc20,d628bc1c,2,c2ca6400,c08d2400) at ufs_vnoperate+0x18 kern_rmdir(c2c8ba00,bfbfef56,0,d628bd40,c07d0bb0) at kern_rmdir+0x1b4 rmdir(c2c8ba00,d628bd10,c0855704,3ee,1) at rmdir+0x22 syscall(2f,2f,2f,0,0) at syscall+0x2c0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (137, FreeBSD ELF32, rmdir), eip = 0x280bd1af, esp = 0xbfbfee7c, ebp = 0xbfbfee98 --- db Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Synaptics PS/2 TouchPad
Has anybody managed to get a Synaptics touchpad working on -current with ACPI? I have a Compaq Presario 2143 and the touchpad is not detected with ACPI enabled. With ACPI disabled it appears and works perfectly. A short time ago somebody suggested adding hints.psm.0.flags=0x64000 but that did nothing. I really need ACPI as without it not much else works, and it the only thing on the laptop that does not work. SuSE Linux finds it straight off, but -current is far and away the best at supporting the cardbus controller which locks SuSE regularly. -- David Smith Data Manager Omnicom Engineering Ltd ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sound patch for pop crackles
On Wed, 12 Nov 2003 13:36:31 -0500 Mathew Kanner [EMAIL PROTECTED] wrote: Hello All, Could people experiencing pops and crackles try the attached patch and set hw.snd.fragps=128. This patch also fixes select on vchans. more details in http://www.freebsd.org/cgi/query-pr.cgi?pr=59208 Thanks, --Mat I applied the patch to /usr/src/sys/dev/sound/pcm/channel.c but am not sure how to set hw.snd.fragsps=128. In my confusion I put it in /boot/loader.conf and rebooted. However, sysctl hw.snd.fragsps gives me sysctl: unknown oid 'hw.snd.fragsps'. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: floppy install troubles
At Wed, 12 Nov 2003 03:48:01 + (UTC), Peter Schultz wrote: I'm having trouble installing with the 5.1-CURRENT-20031110-JPSNAP floppies I got off snapshots.jp.freebsd.org. First off, I tried to create a new slice and it wants to use /dev/ad0p1. I don't believe the p is correct. I tried again without changing the slices at all, and when newfs ran the install stopped with this error: newfs: Cannot retrieve operator gid. I saw p slice too. Is your disk is fresh one (no write after buying), or already used one? -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Alpha too.. (was: Re: buildworld failure on sparc64?
On Wed, Nov 12, 2003 at 11:37:18PM +0100, Wilko Bulte wrote: And on Alpha as well: === lib/libpam/modules/pam_radius^M cc -O -pipe -mcpu=ev6 -mieee -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/inc lude -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers -Werror -Wall -Wno-format -y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-st rings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_radius/pa m_radius.c^M /usr/src/lib/libpam/modules/pam_radius/pam_radius.c: In function `build_access_request':^M /usr/src/lib/libpam/modules/pam_radius/pam_radius.c:114: warning: cast increases required alignment o f target type^M *** Error code 1^M ^M Stop in /usr/src/lib/libpam/modules/pam_radius.^M *** Error code 1^M ^M Stop in /usr/src/lib/libpam/modules.^M *** Error code 1^M ^M Stop in /usr/src/lib/libpam.^M *** Error code 1^M === lib/libpam/modules/pam_radius cc -O -pipe -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_radius/pam_radius.c /usr/src/lib/libpam/modules/pam_radius/pam_radius.c: In function `build_access_request': /usr/src/lib/libpam/modules/pam_radius/pam_radius.c:114: warning: cast increases required alignment of target type *** Error code 1 Stop in /usr/src/lib/libpam/modules/pam_radius. *** Error code 1 Stop in /usr/src/lib/libpam/modules. *** Error code 1 ? -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ---end of quoted text--- -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Synaptics PS/2 TouchPad
On 2003-11-13 09:12:54 (+), Dave Smith [EMAIL PROTECTED] wrote: Has anybody managed to get a Synaptics touchpad working on -current with ACPI? It works just fine on my Asus L3500H, with or without ACPI. I've recently started work on getting psm to support Synaptics TouchPads more fully: virtual scrollbars, up/down buttons, multiple finger detection, etc. I have the basics working, but my brain has been too fried lately to deal with the maths of translating absolute coordinates to sensibly accelerated motions. I have a Compaq Presario 2143 and the touchpad is not detected with ACPI enabled. With ACPI disabled it appears and works perfectly. Which Synaptics TouchPad do you have? Does psm say anything useful when you tell it to be verbose? - Philip -- Philip Paeps Please don't CC me, I am subscribed to the list. A man should be greater than some of his parts. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xscreensaver bug?
[EMAIL PROTECTED] wrote: I'm new in FreeBSD. I found that after I lock screen with xscreensaver, I can unlock it with the root's password as well as my normal user's password. I don't think it is a good thing. Is it a bug? It is intentional, although you can eliminate it with a recompile of the xscreensaver code, with the right options set. The intent is to allow the most priviledged user on the system, who could conceivably log in remotely and access all your data anyway, to kick off students or other people, perhaps in a large campus common xterminal lab, so that scarce shared resources are not tied up running a screen saver when there are people waiting to use them. Since the root user could always pull the power plug on the machine, reboot it, and get rid of the console user that way (after a lngthy delay to check the disks), then log in as root and access your data that way (again), the only thing you would be protecting is your session state. Note that a root user could still log on remotely, and, for things like IRC and other things with active I/O, still load a kernel module and take over your socket connections, etc. (in fact, this is an excellent way to create borgs for Netrek on Linux machines: just make a kernel module that can watch the traffic and knows how to fly the ship, fire torpedos, and strip bork commands out of the input stream for your blessed client). About the only thing you prevent them from getting at are your screen contents, and those are available through kernel modules, as well. Absolutely worst case, the root user could log in remotely, gdb your screen saver, type foobar as the password, and then hack the authentication function return value to say yes, that's the correct password for [EMAIL PROTECTED], and get in without needing to have xscreensaver accept the root password. In other words, the default UNIX security model is inadequate to protect things like compartmentalized data that the user jqdkf has access to, but that the user root is not supposed to have access to. If it really bothers you, then recompile xscreensaver; but then realize that if it really bothers root, they will just work around your laughable attempts to keep them out. Personally, if I were running a public lab, and there was a box with xscreensaver running on it that I wanted to log out, I'd use the root password to stop it, and just log the user out. Short of seeing kiddie porn as the background, I'd probably ignore the screen contents to the point of not remembering them 5 minutes later. On the other hand, if there was a box with xscreensaver running on it that I wanted to log out, and I tried to use the root password to stop it, and doing so failed, I would get intensely curious as to why it was apparently broken, and do my best to perform a root cause failure analysis for the xscreensaver program. This would probably make me remember a lot more, particularly the user who was logged in at the time, and the applicaions they were running, which could have interfered with keyboard input processing, etc.. If this is a public lab, and you are trying to avoid scrutiny (a difficult thing in a public lab, under any circumstances), then you painting a big red target on your back is probably not the best way to avoid unwanted attention (IMO). If you plan on leaving a machine unattended long enough for this to be an issue for you, there's a 100% reliable way to avoid the problem: log out before you walk away. 8-) 8-). -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Synaptics PS/2 TouchPad
On Thu, 13 Nov 2003 13:24:32 +0100 Philip Paeps [EMAIL PROTECTED] wrote: On 2003-11-13 09:12:54 (+), Dave Smith [EMAIL PROTECTED] wrote: Has anybody managed to get a Synaptics touchpad working on -current with ACPI? It works just fine on my Asus L3500H, with or without ACPI. I've recently started work on getting psm to support Synaptics TouchPads more fully: virtual scrollbars, up/down buttons, multiple finger detection, etc. I have the basics working, but my brain has been too fried lately to deal with the maths of translating absolute coordinates to sensibly accelerated motions. Can you post your work on the Synaptics TouchPads so we can test it. I have a Compaq Presario 2143 and the touchpad is not detected with ACPI enabled. With ACPI disabled it appears and works perfectly. Which Synaptics TouchPad do you have? Does psm say anything useful when you tell it to be verbose? - Philip -- Philip Paeps Please don't CC me, I am subscribed to the list. A man should be greater than some of his parts. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- I have a dream that one day this nation will rise up and live out the true meaning of its creed.. (Martin Luther King) /* FingerPrint: 0D42 F870 F650 6B86 CA9E E199 A57D 3824 F8AA A934 */ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Who needs these silly statfs changes...
On Thu, Nov 13, 2003 at 12:54:18AM -0800, Kris Kennaway wrote: On Thu, Nov 13, 2003 at 06:44:25PM +1100, Peter Jeremy wrote: On Wed, Nov 12, 2003 at 06:04:00PM -0800, Kris Kennaway wrote: ...my sparc machine reports that my i386 nfs server has 15 exabytes of free space! enigma# df -k Filesystem 1K-blocks Used Avail Capacity Mounted on rot13:/mnt2 56595176 54032286 18014398507517260 0%/rot13/mnt2 18014398507517260 = 2^54 - 1964724. and 2^54KB == 2^64 bytes. Is it possible that rot13:/mnt2 has negative free space? (ie it's into the 8-10% reserved area). Yes, that's precisely what it is..the bug is either in df or the kernel (I suspect the latter, i.e. something in the nfs code). And it's nothing new - I'm seeing this since several years now. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xscreensaver bug?
Absolutely worst case, the root user could log in remotely, gdb your screen saver, type foobar as the password, and then hack the authentication function return value to say yes, that's the correct password for [EMAIL PROTECTED], and get in without needing to have xscreensaver accept the root password. Or, even easier, log in remotely as root and simply killall -9 xscreensaver. I've had to do that a few times myself when I first tried out pam_krb5 and learned the hard way that xscreensaver doesn't like it very much (and my user account has * in the local password field). Craig ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atheron driver and netgear WG511T
hi, i get this when inserting my Netgear WG511T card into my laptop: ath0: Atheros 5212 mem 0x8801-0x8801 irq 11 at device 0.0 on cardbus0 ath0: unable to attach hardware; HAL status 13 device_probe_and_attach: ath0 attach returned 6 the ath manpage says that this chip should be supported... any ideas? Do you have the: device ath_hal line in your kernel config? Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
signal 12's everywhere on Current with update this morning.
I installed an older current snap, Oct 26, on a brandnew dell power edge with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great. I installed everything except the kitchen sink. Then I decided it was time to update, I've got serveral other machines weathering the storms. Bad idea. It doesn't hang or anything that I can get my teeth into but it just give signal 12 core dumps on many if not most applications. I caught this before finishing an install on another box, yesterday morning. One of the apps that generates signal 12 is ls so I tried pulling ls from the other box and it no longer has a problem. I am at a lost. Any suggestions for where to start would be appreciated. Thanks in advance, ed - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote: I installed an older current snap, Oct 26, on a brandnew dell power edge with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great. I installed everything except the kitchen sink. Then I decided it was time to update, I've got serveral other machines weathering the storms. Bad idea. It doesn't hang or anything that I can get my teeth into but it just give signal 12 core dumps on many if not most applications. I caught this before finishing an install on another box, yesterday morning. One of the apps that generates signal 12 is ls so I tried pulling ls from the other box and it no longer has a problem. I am at a lost. Any suggestions for where to start would be appreciated. Read /usr/src/UPDATING. Ceri -- pgp0.pgp Description: PGP signature
Re: signal 12's everywhere on Current with update this morning.
Mensaje citado por Ceri Davies [EMAIL PROTECTED]: | On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote: | I installed an older current snap, Oct 26, on a brandnew dell power edge | with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great. | I installed everything except the kitchen sink. Then I decided it was | time to update, I've got serveral other machines weathering the storms. | Bad idea. It doesn't hang or anything that I can get my teeth into but | it just give signal 12 core dumps on many if not most applications. I | caught this before finishing an install on another box, yesterday morning. | One of the apps that generates signal 12 is ls so I tried pulling ls | from the other box and it no longer has a problem. I am at a lost. | Any suggestions for where to start would be appreciated. | | Read /usr/src/UPDATING. | Thanks, I missed that. :( Sorry for the noise. ed - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
Mensaje citado por [EMAIL PROTECTED]: | Mensaje citado por Ceri Davies [EMAIL PROTECTED]: | | | On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote: | | I installed an older current snap, Oct 26, on a brandnew dell power edge | | with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great. | | I installed everything except the kitchen sink. Then I decided it was | | time to update, I've got serveral other machines weathering the storms. | | Bad idea. It doesn't hang or anything that I can get my teeth into but | | it just give signal 12 core dumps on many if not most applications. I | | caught this before finishing an install on another box, yesterday | morning. | | One of the apps that generates signal 12 is ls so I tried pulling ls | | from the other box and it no longer has a problem. I am at a lost. | | Any suggestions for where to start would be appreciated. | | | | Read /usr/src/UPDATING. | | | Thanks, I missed that. :( Sorry for the noise. | | ed I'm building new kernels as I write this. My next question is: One of the machines I'm building on is remote and was last rebuilt just before the change. What would be be better sequence for making the change after a fresh cvsup ? 1. Build and Install a new kernel 2. build a new world 3. Run mergemaster 4. ReBoot (I'm not sure it will come up multiuser with a new kernel and a 4 day old userland.) 5. Installworld and assess possible problems :-) or 1. Build and Install a new kernel 2. make buildworld 3. Run mergemaster 4. make installworld; shutdown -r now # and pray :-) Or is there a better option? Has anyone else already done this? Thanks, ed - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
[EMAIL PROTECTED] schrieb: Thanks, I missed that. :( Sorry for the noise. You're not the only one who missed that. We killed 2 machines yesterday evening (~11pm CET) this way. I think I did read UPDATING and I can't remember any warning entries?! It's there now, of course so we were just running cvsup a few hours too early I guess. ;) Anyway, things like this can happen if you decide to run -CURRENT. :-) cu, Uwe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Recent -CURRENT panic (New interrupt code related?); backtrace included
Yes I have device apic enabled, and after setting options NO_MIXED_MODE, the problem persists. However, fortunatelly, the spurious.patch seemed to solved the problem, and the system has been up for 9 hours without panic'ing as I described before. Do you need me to test atpic.patch as well? -Original Message- From: John Baldwin [mailto:[EMAIL PROTECTED] Sent: Thursday, November 13, 2003 12:29 AM To: Xin LI/ Cc: [EMAIL PROTECTED] Subject: RE: Recent -CURRENT panic (New interrupt code related?); backtrace included Do you have 'device apic' enabled? If so, can you try using 'options NO_MIXED_MODE'. Barring that, can you try http://www.FreeBSD.org/~jhb/patches/spurious.patch and if that doesn't work http://www.FreeBSD.org/~jhb/patches/atpic.patch? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Recent -CURRENT panic (New interrupt code related?); backtrace included
On 13-Nov-2003 Xin LI/ÀîöÎ wrote: Yes I have device apic enabled, and after setting options NO_MIXED_MODE, the problem persists. However, fortunatelly, the spurious.patch seemed to solved the problem, and the system has been up for 9 hours without panic'ing as I described before. Do you need me to test atpic.patch as well? No, that is fine, thanks. I will have a better patch later today that should hopefully work both with and without mixed mode. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Recent -current hangs on Tyan S2460 before finishing boot
On 13-Nov-2003 Benjamin Lewis wrote: Hello, I'm having trouble getting recent (post- device apic, pre- turnstile) kernels to boot on my Tyan S2460 (Tiger MP) system with dual AMD Athlons. What happens is that the machine seems to get stuck soon after the Waiting for SCSI devices to settle message is printed -- it appears to be willing to wait forever rather than the SCSI_DELAY time. Disabling ACPI in the BIOS has no apparent effect on the hang. Using SCHED_4BSD or SCHED_ULE likewise makes no difference. I've been following the current@ list hoping to see someone else report a problem similar to mine but haven't seen anything yet. I do have a serial console attached to the machine and DDB enabled so I'm able to provide some information and get more if needed. I'm including a copy of the boot messages from my last attempt to boot FreeBSD 5.1-CURRENT #2: Tue Nov 11 17:35:40 EST 2003 which was cvsup'ed shortly prior to the build date. Included in the messages are the output of ps and trace once I broke into ddb. I'm also including output from acpidump -t and mptable -verbose since I've seen that information requested in the past. Some details about the system that may be pertinent: 1. It has two 1Ghz Athlon Thunderbird (Not MP) processors. That hasn't been a problem so far. 2. The BIOS is version 1.04 (latest is 1.05). The last time I tried updating to 1.05 (some time ago) I saw lots of error messagess complaining about undefined ACPI stuff so I reverted. 3. There is a Tekram 390F (I think that's the model -- it uses the sym driver) and an Adaptec 3944 SCSI controller. A single internal SCSI drive is connected to the Tekram and 10 external drives are connected to the two ports on the 3944. The external drives are configured as a Vinum Raid10 array. There's also a single IDE drive connected to one of the built-in IDE controllers. Please let me know if there is anything more you want to know. Thanks, Can you do a 'show intrcnt' from the ddb prompt? It sounds like you may be getting an interrupt storm due to a mis-routed PCI interrupt. Actually, I think the problem is in the ata driver. Well, there are possibly bugs in the interrupt code in that interrupts that don't exist in the mptable (IRQ's 11 and 15) still get created, but, the fact that the mptable has no IRQ 15 to me means that there is no IRQ 15 and thus there should not be an ata1. Note that in your dmesg, ata1 does say that it doesn't do DMA because it has been disabled. Perhaps the ata driver needs to disable ata1 altogether on that chipset if it sees that condition. My guess is that the ata driver is waiting forever for an interrupt from ata1 which is never going to arrive, hence the hang. Do you have a boot -v dmesg from a working kernel? -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Alpha too..
This was fixed yesterday. My alpha successfully built world last night. Scott Wilko Bulte wrote: On Wed, Nov 12, 2003 at 11:37:18PM +0100, Wilko Bulte wrote: And on Alpha as well: === lib/libpam/modules/pam_radius^M cc -O -pipe -mcpu=ev6 -mieee -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/inc lude -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers -Werror -Wall -Wno-format -y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-st rings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_radius/pa m_radius.c^M /usr/src/lib/libpam/modules/pam_radius/pam_radius.c: In function `build_access_request':^M /usr/src/lib/libpam/modules/pam_radius/pam_radius.c:114: warning: cast increases required alignment o f target type^M *** Error code 1^M ^M Stop in /usr/src/lib/libpam/modules/pam_radius.^M *** Error code 1^M ^M Stop in /usr/src/lib/libpam/modules.^M *** Error code 1^M ^M Stop in /usr/src/lib/libpam.^M *** Error code 1^M === lib/libpam/modules/pam_radius cc -O -pipe -I/usr/src/lib/libpam/modules/pam_radius/../../../../contrib/openpam/include -I/usr/src/lib/libpam/modules/pam_radius/../../libpam -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/lib/libpam/modules/pam_radius/pam_radius.c /usr/src/lib/libpam/modules/pam_radius/pam_radius.c: In function `build_access_request': /usr/src/lib/libpam/modules/pam_radius/pam_radius.c:114: warning: cast increases required alignment of target type *** Error code 1 Stop in /usr/src/lib/libpam/modules/pam_radius. *** Error code 1 Stop in /usr/src/lib/libpam/modules. *** Error code 1 ? -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ---end of quoted text--- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
Mensaje citado por Uwe Laverenz [EMAIL PROTECTED]: | [EMAIL PROTECTED] schrieb: | | Thanks, I missed that. :( Sorry for the noise. | | You're not the only one who missed that. We killed 2 machines yesterday | evening (~11pm CET) this way. I think I did read UPDATING and I can't | remember any warning entries?! It's there now, of course so we were just | running cvsup a few hours too early I guess. ;) | | Anyway, things like this can happen if you decide to run -CURRENT. :-) Uwe, do you have any remote machines? I'm wondering what the correct sequence would be to update and reboot them. Thanks, ed - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xscreensaver bug?
Terry Lambert wrote: [EMAIL PROTECTED] wrote: I'm new in FreeBSD. I found that after I lock screen with xscreensaver, I can unlock it with the root's password as well as my normal user's password. I don't think it is a good thing. Is it a bug? It is intentional, although you can eliminate it with a recompile of the xscreensaver code, with the right options set. Wouldn't this lead to another security hazard, if a user compile his own hacked xscreensaver which captures and stashes the password into a file then runs it and leaves the terminal intentionally, `baiting' root? :o Although I can see the merit of this `feature', I think sysadmins should stay away from using it in general. `su -m thatuser -c killall xscreensaver' seems to be far safer. Eugene ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent -current hangs on Tyan S2460 before finishing boot
On November 13 2003, John Baldwin wrote: On 13-Nov-2003 Benjamin Lewis wrote: [trouble booting -current on Tyan Tiger MP] Can you do a 'show intrcnt' from the ddb prompt? It sounds like you may be getting an interrupt storm due to a mis-routed PCI interrupt. I didn't see any unexpectedly large numbers, but IRQ 15 isn't in the list: [...] GEOM: create disk ad0 dp=0xc2e19370 ad0: 57241MB WDC WD600AB-00BVA0 [116301/16/63] at ata0-master UDMA100 Waiting 10 seconds for SCSI devices to settle [halt - sent] Stopped at siointr1+0xec: jmp siointr1+0x220 db show intrcnt irq4: sio0 2 irq8: rtc 1725 irq13: npx0 1 stray irq13 1 irq14: ata0 17 irq19: ohci0 ahc0 1 irq0: clk 1 db cont [halt - sent] Stopped at siointr1+0xec: jmp siointr1+0x220 db show intrcnt irq4: sio0 4 irq8: rtc 3407 irq13: npx0 1 stray irq13 1 irq14: ata0 17 irq19: ohci0 ahc0 1 irq0: clk 1 db cont [halt - sent] Stopped at siointr1+0xec: jmp siointr1+0x220 db show intrcnt irq4: sio0 6 irq8: rtc 7418 irq13: npx0 1 stray irq13 1 irq14: ata0 17 irq19: ohci0 ahc0 1 irq0: clk 1 db Actually, I think the problem is in the ata driver. Well, there are possibly bugs in the interrupt code in that interrupts that don't exist in the mptable (IRQ's 11 and 15) still get created, but, the fact that the mptable has no IRQ 15 to me means that there is no IRQ 15 and thus there should not be an ata1. Note that in your dmesg, ata1 does say that it doesn't do DMA because it has been disabled. Perhaps the ata driver needs to disable ata1 altogether on that chipset if it sees that condition. My guess is that the ata driver is waiting forever for an interrupt from ata1 which is never going to arrive, hence the hang. Do you have a boot -v dmesg from a working kernel? Unfortunately, I'll have to wait until I get home to try enabling the ata1 controller in the BIOS. dmesg output from a boot -v with my working kernel is below. Thanks for looking at this! -Ben Copyright (c) 1992-2003 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 5.1-CURRENT #1: Sat Oct 18 13:47:46 EST 2003 [EMAIL PROTECTED]:/export/obj/usr/src-all/current/src/sys/AKIRA Preloaded elf kernel /boot/kernel.ok/kernel at 0xc086. Preloaded elf module /boot/kernel.ok/snd_pcm.ko at 0xc0860254. Preloaded elf module /boot/kernel.ok/snd_es137x.ko at 0xc0860304. Preloaded elf module /boot/kernel.ok/usb.ko at 0xc08603b8. Preloaded elf module /boot/kernel.ok/ums.ko at 0xc0860464. Preloaded elf module /boot/kernel.ok/agp.ko at 0xc0860510. Preloaded elf module /boot/kernel.ok/random.ko at 0xc08605bc. Preloaded elf module /boot/kernel.ok/acpi.ko at 0xc086066c. Calibrating clock(s) ... i8254 clock: 1192965 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 138815 Hz CPU: AMD Athlon(tm) Processor (1000.04-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x642 Stepping = 2 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044RSVD,AMIE,DSP,3DNow! Data TLB: 24 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 268369920 (255 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c29000 - 0x0fb3dfff, 250695680 bytes (61205 pages) avail memory = 251080704 (239 MB) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040010, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 bios32: Found BIOS32 Service Directory header at 0xc00f7480 bios32: Entry = 0xfd6c0 (c00fd6c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd6c0+0x120 pnpbios: Found PnP BIOS data at 0xc00f74d0 pnpbios: Entry = f:9ece Rev = 1.0 Other BIOS signatures found: null: null device, zero device mem: memory I/O Pentium Pro MTRR support enabled random: entropy source SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard pci_open(1):mode
Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
On Thu, Nov 13, 2003 at 07:39:15AM -0800, [EMAIL PROTECTED] wrote: Mensaje citado por [EMAIL PROTECTED]: | Mensaje citado por Ceri Davies [EMAIL PROTECTED]: | | | On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote: | | I installed an older current snap, Oct 26, on a brandnew dell power edge | | with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great. | | I installed everything except the kitchen sink. Then I decided it was | | time to update, I've got serveral other machines weathering the storms. | | Bad idea. It doesn't hang or anything that I can get my teeth into but | | it just give signal 12 core dumps on many if not most applications. I | | caught this before finishing an install on another box, yesterday | morning. | | One of the apps that generates signal 12 is ls so I tried pulling ls | | from the other box and it no longer has a problem. I am at a lost. | | Any suggestions for where to start would be appreciated. | | | | Read /usr/src/UPDATING. | | | Thanks, I missed that. :( Sorry for the noise. | | ed I'm building new kernels as I write this. My next question is: One of the machines I'm building on is remote and was last rebuilt just before the change. What would be be better sequence for making the change after a fresh cvsup ? 1. Build and Install a new kernel 2. build a new world 3. Run mergemaster 4. ReBoot (I'm not sure it will come up multiuser with a new kernel and a 4 day old userland.) 5. Installworld and assess possible problems :-) I upgraded a ancient -current last night, I did 1) cvsup 2) build and install new kernel 3) reboot 4) build and isntall new world 5) mergemaster 6) reboot /Jesper ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: APIC-UP related panic
On Wed, 12 Nov 2003, Dag-Erling [iso-8859-1] Smørgrav wrote: Matthew D. Fuller [EMAIL PROTECTED] writes: However, if NO_MIXED_MODE works, that is actually the more desirable way to run your system. How common is the need for this? Does turning of mixed mode when it's not needed give any real advantages higher up? NO_MIXED_MODE disables a hack which allow FreeBSD to work with mother- boards that lie about how APIC pins are wired. In general, you always want to use NO_MIXED_MODE *except* on hardware that has the bug that makes the mixed-mode hack necessary. Any way we can make this a tunable? :) -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
[EMAIL PROTECTED] schrieb: Uwe, do you have any remote machines? I'm wondering what the correct sequence would be to update and reboot them. I would suggest to do it this way: 1. make buildworld 2. make kernel KERNCONF=YOURCONF 3. *reboot* (with new kernel and old userland) 4. make installworld 5. mergemaster 6. *reboot* cu, Uwe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent -current hangs on Tyan S2460 before finishing boot
On 13-Nov-2003 Benjamin Lewis wrote: On November 13 2003, John Baldwin wrote: On 13-Nov-2003 Benjamin Lewis wrote: [trouble booting -current on Tyan Tiger MP] Can you do a 'show intrcnt' from the ddb prompt? It sounds like you may be getting an interrupt storm due to a mis-routed PCI interrupt. I didn't see any unexpectedly large numbers, but IRQ 15 isn't in the list: [...] GEOM: create disk ad0 dp=0xc2e19370 ad0: 57241MB WDC WD600AB-00BVA0 [116301/16/63] at ata0-master UDMA100 Waiting 10 seconds for SCSI devices to settle [halt - sent] Stopped at siointr1+0xec: jmp siointr1+0x220 db show intrcnt irq4: sio0 2 irq8: rtc 1725 irq13: npx0 1 stray irq13 1 irq14: ata0 17 irq19: ohci0 ahc0 1 irq0: clk 1 db cont [halt - sent] Stopped at siointr1+0xec: jmp siointr1+0x220 db show intrcnt irq4: sio0 4 irq8: rtc 3407 irq13: npx0 1 stray irq13 1 irq14: ata0 17 irq19: ohci0 ahc0 1 irq0: clk 1 db cont [halt - sent] Stopped at siointr1+0xec: jmp siointr1+0x220 db show intrcnt irq4: sio0 6 irq8: rtc 7418 irq13: npx0 1 stray irq13 1 irq14: ata0 17 irq19: ohci0 ahc0 1 irq0: clk 1 db You aren't getting any clock interrupts it seems. Very weird. Can you try using NO_MIXED_MODE instead? I still think the ata1 is bogus, but I don't think that is causing your hang now. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot0 and fdisk / disklabel misbehaviour
Rudolf Cejka wrote (2003/11/11): And almost at the same time, I'm looking at the last change to boot0.s 1.26, if there is forgotten TBL1SZ update, or not :o))) Just for record: I have submitted patch solving problems with bad information about partitions as kern/59256 right now. -- Rudolf Cejka cejkar at fit.vutbr.cz http://www.fit.vutbr.cz/~cejkar Brno University of Technology, Faculty of Information Technology Bozetechova 2, 612 66 Brno, Czech Republic ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: APIC-UP related panic
On 13-Nov-2003 Doug White wrote: On Wed, 12 Nov 2003, Dag-Erling [iso-8859-1] Smørgrav wrote: Matthew D. Fuller [EMAIL PROTECTED] writes: However, if NO_MIXED_MODE works, that is actually the more desirable way to run your system. How common is the need for this? Does turning of mixed mode when it's not needed give any real advantages higher up? NO_MIXED_MODE disables a hack which allow FreeBSD to work with mother- boards that lie about how APIC pins are wired. In general, you always want to use NO_MIXED_MODE *except* on hardware that has the bug that makes the mixed-mode hack necessary. Any way we can make this a tunable? :) I need to make it a runtime check again actually at some point. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tcp hostcache and ip fastforward for review
Andre Oppermann wrote: Makes sense. Can we ever have a packet that has a source address with INADDR_BROADCAST or IN_MULTICAST? I can't think of such a case. Can we ever have a packet with destination address INADDR_ANY? Maybe for BOOTP? But then the source address would be 0.0.0.0 too? IIRC, in case you have an IP-less interface and you want to subscribe it to some multicast address, the outgoing packet source address is 0.0.0.0. -- Daniel C. Sobral Gerência de Operações Divisão de Comunicação de Dados Coordenação de Segurança VIVO Centro Oeste Norte Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: floppy install troubles
On Thu, Nov 13, 2003 at 08:10:34PM +0900, Jun Kuriyama wrote: At Wed, 12 Nov 2003 03:48:01 + (UTC), Peter Schultz wrote: I'm having trouble installing with the 5.1-CURRENT-20031110-JPSNAP floppies I got off snapshots.jp.freebsd.org. First off, I tried to create a new slice and it wants to use /dev/ad0p1. I don't believe the p is correct. I tried again without changing the slices at all, and when newfs ran the install stopped with this error: newfs: Cannot retrieve operator gid. I saw p slice too. Is your disk is fresh one (no write after buying), or already used one? Mine was totally fresh. I had just created a HW RAID 0+1 setup. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Hang on boot after SETFEATURES recovered from missing interrupt message
Hi, I'm having trouble booting today's current. The kernel hangs after various messages such as: ad0: WARNING - SETFEATURES recovered from missing interrupt ad0: WARNING - READ_MUL recovered from missing interrupt ad0: WARNING - SET_MULTI recovered from missing interrupt I've tried disabling acpi and ata_dma with no effect. I can still break into the debugger, but as it is not a panic I don't know what help that is. Last running kernel is from Fri Oct 3 00:28:37 CEST 2003 which I think is post atang, but I'm not sure. Any tips are welcome. Full log of boot -v follows. -CJ Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS 639kB/228288kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Wed Jun 25 00:18:04 CEST 2003) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x4c0898 data=0x79fec+0x64c10 syms=[0x4+0x5a4f0+0x4 +0x6eb3a] /boot/kernel/vesa.ko text=0x39d8 data=0x2a0+0x27c syms=[0x4+0x850+0x4+0x709] /boot/kernel/snd_pcm.ko text=0x14cb8 data=0x2288+0x10c4 syms=[0x4+0x2bc0+0x4 +0x30f0] /boot/kernel/snd_emu10k1.ko text=0x4ffc data=0x61c+0x4 syms=[0x4+0xbe0+0x4 +0xc12] Loading /boot/defaults/loader.conf Hit [Enter] to boot immediately, or any other key for command prompt. Type '?' for a list of commands, 'help' for more detailed help. OK boot -v SMAP type=01 base= len=0009fc00 SMAP type=02 base=0009fc00 len=0400 SMAP type=02 base=000f len=0001 SMAP type=02 base= len=0001 SMAP type=01 base=0010 len=0def SMAP type=03 base=0dff3000 len=d000 SMAP type=04 base=0dff len=3000 Copyright (c) 1992-2003 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 5.1-CURRENT #0: Thu Nov 13 17:03:39 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BEEBELBROX Preloaded elf kernel /boot/kernel/kernel at 0xc0a97000. Preloaded elf module /boot/kernel/vesa.ko at 0xc0a97200. Preloaded elf module /boot/kernel/snd_pcm.ko at 0xc0a972ac. Preloaded elf module /boot/kernel/snd_emu10k1.ko at 0xc0a97358. Calibrating clock(s) ... i8254 clock: 1193256 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 499781229 Hz CPU: Pentium II/Pentium II Xeon/Celeron (499.78-MHz 686-class CPU) Origin = GenuineIntel Id = 0x665 Stepping = 5 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 234815488 (223 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c29000 - 0x0dbd9fff, 217780224 bytes (53169 pages) avail memory = 218529792 (208 MB) bios32: Found BIOS32 Service Directory header at 0xc00fafb0 bios32: Entry = 0xfb430 (c00fb430) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xb460 pnpbios: Found PnP BIOS data at 0xc00fc000 pnpbios: Entry = f:c028 Rev = 1.0 Other BIOS signatures found: wlan: 802.11 Link Layer null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 00 01 40 00 05 02 07 01 00 01 0e 01 00 01 17 01 00 01 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0a 01 0b 01 0c 01 0e 01 0f 01 VESA: 33 mode(s) found VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc0a6ece2 (122) VESA: NVidia VESA: NVidia Riva TNT B1 acpi0: AWARD AWRDACPI on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x80005810 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) pcibios: BIOS version 2.10 Using $PIR table, 7 entries at 0xc00fdf00 PCI-Only Interrupts: 5 9 10 11 Location Bus Device Pin Link IRQs slot 1 0 15A 0x60 3 4 5 7 9 10 11 12 14 15 slot 1 0 15B 0x61 3 4 5 7 9 10 11 12 14 15 slot 1 0 15C 0x62 3 4 5 7 9 10 11 12 14 15 slot 1 0 15D 0x63 3 4 5 7 9 10 11 12 14 15 slot 2 0 13A 0x61 3 4 5 7 9 10 11 12 14 15 slot 2 0 13B 0x62 3 4 5 7 9 10 11 12 14 15 slot 2 0 13C 0x63 3 4 5 7 9 10 11 12 14 15 slot 2 0 13D 0x60 3 4 5 7 9 10 11 12 14 15 slot 3 0 11A 0x62 3 4 5 7 9 10 11 12 14 15 slot 3 0 11B 0x63 3 4 5 7 9 10 11 12 14 15 slot 3 0 11C 0x60 3 4 5 7 9 10 11 12 14 15 slot 3 0 11D 0x61 3 4 5 7 9 10 11 12 14 15 slot 4 09A 0x63 3 4 5 7 9 10 11 12 14 15 slot 4 09B 0x60 3 4 5 7 9 10 11 12 14 15 slot 4 09C 0x61 3 4 5 7 9 10 11 12 14 15 slot 4 09D 0x62
Re: new kernel and old programs - bad system call
On Thu, 13 Nov 2003, John Hay wrote: Is it ok to run a new kernel (after the statfs changes) and older programs? I thought so from what i gathered out of the commit messages, but my test box doesn't like it at all... Well except if something else broke stuff: I have no problems with a current kernel and an old world. ## ... Mounting root from ufs:/dev/da0s1a pid 50 (sh), uid 0: exited on signal 12 Enter full pathname of shell or RETURN for /bin/sh: # ls pid 56 (ls), uid 0: exited on signal 12 Bad system call # ## Maybe you don't have old programs. Unfortunately, even /bin/sh is affected by the changes (it has a reference to fstatfs). I often boot old kernels (back to RELENG_4) with current utilities and will have to do something about this. Everying except things like ps works with only the following changes: - don't use the new eaccess() syscall in test(1). - change SYS_sigaction and SYS_sigreturn to their old (RELENG_4) values so that the newest signal handling is not used. This works almost perfectly because there are no significant changes to the data structures (only some semantic changes that most utilities don't care about). Larger changes in signal handling are the main thing that prevents current utilities running under RELENG_3. The statfs changes affect data structures, so they can't be avoided by simply changing the syscall numbers. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
Mensaje citado por Jesper Skriver [EMAIL PROTECTED]: | On Thu, Nov 13, 2003 at 07:39:15AM -0800, [EMAIL PROTECTED] wrote: CUT | I'm building new kernels as I write this. My next question is: | One of the machines I'm building on is remote and was last rebuilt | just before the change. What would be be better sequence for making | the change after a fresh cvsup ? | |1. Build and Install a new kernel |2. build a new world |3. Run mergemaster |4. ReBoot (I'm not sure it will come up multiuser with a new | kernel and a 4 day old userland.) |5. Installworld and assess possible problems :-) | | I upgraded a ancient -current last night, I did | | 1) cvsup | 2) build and install new kernel | 3) reboot | 4) build and isntall new world | 5) mergemaster | 6) reboot Jesper, Thanks. I'm already finishing a buildworld but I'm going to reboot after before installworld, I've already installed the kernel. I was afraid it would't go multiuser so I could finish with a ssh. Thanks for confirming that it will, or should :-) ed | | /Jesper | - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Vinum doesn't work anymore
Hello, On 13.11.2003 at 16:33 cosmin wrote: Hello, I'm having major problems with the latest kernel sources and vinum. I don't really know where to begin the debug. For now, I'll have to run older sources just to have vinum working. Vinum isn't able to detect my volume, even though it worked fine before the install and reboot. Here's some info. Script started on Thu Nov 13 02:14:17 2003 # kldunload vinum.ko # ls -la /boot/kernel/vinum.ko -r-xr-xr-x 1 root wheel 97304 Nov 13 02:10 /boot/kernel/vinum.ko # ls -la /sbin/vinum -r-xr-xr-x 1 root wheel 752300 Nov 13 01:58 /sbin/vinum # kldload /boot/kernel/vinum.ko # /sbin/vinum vinum - start ** no drives found: No such file or directory vinum - dumpconfig Drive a: Device /dev/ad1s1e Created on at Sat Jul 19 03:10:25 2003 Config last updated Thu Nov 13 01:45:34 2003 Size: 200047002624 bytes (190779 MB) volume raid5 state up plex name raid5.p0 state up org raid5 1020s vol raid5 sd name raid5.p0.s0 drive a len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 0s sd name raid5.p0.s1 drive b len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 1020s sd name raid5.p0.s2 drive c len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 2040s sd name raid5.p0.s3 drive d len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 3060s sd name raid5.p0.s4 drive e len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 4080s sd name raid5.p0.s5 drive f len 390715080s driveoffset 265s state up plex raid5.p0 plexoffset 5100s [... etc for all the drives ...] vinum - read /dev/ad1 ** no drives found: No such file or directory Can't save Vinum config: No child processes vinum - quit # exit Script done on Thu Nov 13 02:15:17 2003 Also, when I tried fixing this problem by trying to compile vinum into the kernel (maybe would help, probably wouldn't), I got a compile error. The kernel is just the GENERIC kernel with device vinum added at the end of it. Here is the error: cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/vinum/vinum.c /usr/src/sys/dev/vinum/vinum.c: In function `vinumattach': /usr/src/sys/dev/vinum/vinum.c:136: error: structure has no member named `p_intr_nesting_level' /usr/src/sys/dev/vinum/vinum.c:143: error: structure has no member named `p_intr_nesting_level' /usr/src/sys/dev/vinum/vinum.c:150: error: structure has no member named `p_intr_nesting_level' /usr/src/sys/dev/vinum/vinum.c:162: error: structure has no member named `p_intr_nesting_level' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC_WITH_VINUM. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. The sources are freshly cvsuped from Nov 12, 2003. I can confirm this, I've run truss on 'vinum ls' and get the following wich let me guess it might have todo with the recent statfs changes. modfind(0x80b8e74) = 178 (0xb2) stat(/var/log/vinum_history,0xbfbfea30)= 0 (0x0) open(/var/log/vinum_history,0x20a,0666)= 3 (0x3) lseek(3,0x0,2) = 2622 (0xa3e) gettimeofday(0xbfbfe998,0x0) = 0 (0x0) access(/etc/localtime,4) = 0 (0x0) open(/etc/localtime,0x0,00)= 4 (0x4) fstat(4,0xbfbfe8fc) = 0 (0x0) read(0x4,0xbfbfc5dc,0x1f08) = 837 (0x345) close(4) = 0 (0x0) fstat(3,0xbfbfe6bc) = 0 (0x0) readlink(/etc/malloc.conf,0xbfbfe6a0,63) ERR#2 'No such file or directory' issetugid() = 0 (0x0) issetugid() = 0 (0x0) getuid() = 0 (0x0) mmap(0x0,4096,0x3,0x1002,-1,0x0) = 671944704 (0x280d1000) break(0x80e7000) = 0 (0x0) break(0x80eb000) = 0 (0x0) write(3,0x80e7000,50)= 50 (0x32) __sysctl(0xbfbfe9c4,0x2,0xbfbfe9cc,0xbfbfe9c0,0x80b6da8,0x14) = 0 (0x0) __sysctl(0xbfbfe9cc,0x3,0x0,0x0,0x0,0x0) = 0 (0x0) open(/dev/vinum/control,0x2,00)= 4 (0x4) ioctl(4,0x40404641,0x80e4620)= 0 (0x0) fork() = 1208 (0x4b8) SIGNAL 20 ^ break(0x80ec000)
Re: floppy install troubles
David O'Brien wrote: On Thu, Nov 13, 2003 at 08:10:34PM +0900, Jun Kuriyama wrote: At Wed, 12 Nov 2003 03:48:01 + (UTC), Peter Schultz wrote: I'm having trouble installing with the 5.1-CURRENT-20031110-JPSNAP floppies I got off snapshots.jp.freebsd.org. First off, I tried to create a new slice and it wants to use /dev/ad0p1. I don't believe the p is correct. I tried again without changing the slices at all, and when newfs ran the install stopped with this error: newfs: Cannot retrieve operator gid. I saw p slice too. Is your disk is fresh one (no write after buying), or already used one? Mine was totally fresh. I had just created a HW RAID 0+1 setup. Mine is totally old and suffers from the same exact problems with today's JPSNAP. I was thinking the p problem would be fixed with src/lib/libdisk/create_chunk.c 1.83. Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel 865 probs
On Wednesday 12 November 2003 8:47 pm, Peter Risdon wrote: Jaco, Thanks for this. Jaco H. van Tonder wrote: For what its worth, I had a lot of problems on the I865P board, and It boiled down to memory corruption. The machine had lots of random crashes, meanng that they were not occuring when I do something specific. The machine startted to panic as soon as the load got high. I took out the memory, and placed it into another slot and the machine is cruising along happily now. I played with the memory slots as soon as the problems started, and found memtest would sometimes throw up huge numbers of errors, and sometimes none at all. FWIW slot 1 was the worst. But I suspect, no more than that, some other problem as well. I've seen this behavior from memtest. Using the menu to restart usually fixes. The bogus errors are easy to spot. The other questions is what is the date of the -CURRENT tree that is giving this problems? I can recall quite a few problems, which were fixed, that could cause this problem. Nov 10. I ran cvsup at about 9:00am GMT. Peter Risdon. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- ian j hart http://ars.userfriendly.org/cartoons/?id=20031016 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Currentwith update this morning.
I'm not having any luck - I'm started to feel like I'm missing something here :) I cvsup'd yesterday afternoon, and did my usual make buildworld, kernel, install kernel, single user mode, then make installworld - except it bombed on the installworld. I ignored the message moved on. So, this morning, I cvsup'ed again, and started over. Here's what I get when doing a make buildworld: -- stage 1.1: legacy release compatibility shims -- snip === tools/build /usr/obj/usr/src/i386/usr/src/tools/build created for /usr/src/tools/build cd /usr/src/tools/build; make buildincludes; make installincludes rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/legacy/usr/include /usr/src/tools/build/dummy.c cc -O -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/tools/build/dummy.c building static egacy library ranlib libegacy.a sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libegacy.a /usr/obj/usr/src/i386/legacy/usr/lib *** Signal 11 Stop in /usr/src/tools/build. *** Error code 1 Stop in /usr/src. *** Error code 1 I've tried rm'ing the /usr/obj subdirs, and even moving /usr/src out of the way and re cvsuping the whole tree, still no luck.. How am I being stupid here? Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Currentwith update this morning.
Mensaje citado por Eric Anderson [EMAIL PROTECTED]: | I'm not having any luck - I'm started to feel like I'm missing something | here :) You're getting signal 11's. That could indicate memory problems. I get signal 12's with the changes to the statfs structure. I assume that you rebooted after the bombed installworld, didn't you? If not that just might be the solution, if you did the problem could be else where. ed | | I cvsup'd yesterday afternoon, and did my usual make buildworld, kernel, | install kernel, single user mode, then make installworld - except it | bombed on the installworld. I ignored the message moved on. So, this | morning, I cvsup'ed again, and started over. | | Here's what I get when doing a make buildworld: | -- | stage 1.1: legacy release compatibility shims | -- | snip | === tools/build | /usr/obj/usr/src/i386/usr/src/tools/build created for /usr/src/tools/build | cd /usr/src/tools/build; make buildincludes; make installincludes | rm -f .depend | mkdep -f .depend -a-I/usr/obj/usr/src/i386/legacy/usr/include | /usr/src/tools/build/dummy.c | cc -O -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c | /usr/src/tools/build/dummy.c | building static egacy library | ranlib libegacy.a | sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libegacy.a | /usr/obj/usr/src/i386/legacy/usr/lib | *** Signal 11 | | Stop in /usr/src/tools/build. | *** Error code 1 | | Stop in /usr/src. | *** Error code 1 | | I've tried rm'ing the /usr/obj subdirs, and even moving /usr/src out of | the way and re cvsuping the whole tree, still no luck.. | | How am I being stupid here? | | Eric | | | | -- | -- | Eric AndersonSystems Administrator Centaur Technology | All generalizations are false, including this one. | -- | | | ___ | [EMAIL PROTECTED] mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-current | To unsubscribe, send any mail to [EMAIL PROTECTED] | - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
making a release
I'm trying to build a set of release floppies, but my setting for CHROOTDIR seems to be ignored and the release gets dumped in my root file system under /R. Shouldn't /R be installed under whatever I set CHROOTDIR to? Thanks, Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: making a release
I use the following all of the time: cd /usr/src/release ; make release BUILDNAME=5.1-CURRENT CHROOTDIR=/usr/release CVSROOT=/usr/ncvs Scott On Thu, 13 Nov 2003, Peter Schultz wrote: I'm trying to build a set of release floppies, but my setting for CHROOTDIR seems to be ignored and the release gets dumped in my root file system under /R. Shouldn't /R be installed under whatever I set CHROOTDIR to? Thanks, Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new kernel and old programs - bad system call
On Fri, Nov 14, 2003 at 06:38:28AM +1100, Bruce Evans wrote: On Thu, 13 Nov 2003, John Hay wrote: Is it ok to run a new kernel (after the statfs changes) and older programs? I thought so from what i gathered out of the commit messages, but my test box doesn't like it at all... Well except if something else broke stuff: I have no problems with a current kernel and an old world. ## ... Mounting root from ufs:/dev/da0s1a pid 50 (sh), uid 0: exited on signal 12 Enter full pathname of shell or RETURN for /bin/sh: # ls pid 56 (ls), uid 0: exited on signal 12 Bad system call # ## Maybe you don't have old programs. Unfortunately, even /bin/sh is affected by the changes (it has a reference to fstatfs). I'm pretty sure it is old binaries because they work with my old kernel: beast# ls -l /bin/*sh* /boot/kernel.work/kernel /boot/kernel/kernel -r-xr-xr-x 2 root wheel 879252 Nov 11 14:52 /bin/csh -r-xr-xr-x 1 root wheel 751752 Nov 11 14:52 /bin/sh -r-xr-xr-x 2 root wheel 879252 Nov 11 14:52 /bin/tcsh -r-xr-xr-x 1 root wheel 2673454 Nov 3 09:17 /boot/kernel.work/kernel -r-xr-xr-x 1 root wheel 2758305 Nov 13 09:01 /boot/kernel/kernel The binaries work just fine with kernel.work but not with kernel. Maybe I should try a few other things, like a UP kernel. Luckily the old reboot still works on the new kernel. :-) John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: making a release
Scott Long wrote:
I use the following all of the time:
cd /usr/src/release ; make release BUILDNAME=5.1-CURRENT
CHROOTDIR=/usr/release CVSROOT=/usr/ncvs
Quick question: is it ok to do make -jn release ?
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Currentwith update this morning.
[EMAIL PROTECTED] wrote: Mensaje citado por Eric Anderson [EMAIL PROTECTED]: | I'm not having any luck - I'm started to feel like I'm missing something | here :) You're getting signal 11's. That could indicate memory problems. I get signal 12's with the changes to the statfs structure. I assume that you rebooted after the bombed installworld, didn't you? If not that just might be the solution, if you did the problem could be else where. Thanks ed, but it isn't a memory problem.. After the bombed installworld, I rebooted, and it came up (running the kernel I built with the src that bombed), and now I'm in a corner - however Andy Farkas gave me a hint to put in an older kernel (maybe the one from 5.1-RELEASE?) and reboot using that kernel, then rebuild world and install world.. I think my world is older than my kernel.. Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: making a release
On Fri, 14 Nov 2003, Andy Farkas wrote: Scott Long wrote: I use the following all of the time: cd /usr/src/release ; make release BUILDNAME=5.1-CURRENT CHROOTDIR=/usr/release CVSROOT=/usr/ncvs Quick question: is it ok to do make -jn release ? -- I wouldn't trust invoking -jX directly. There are three variables in the release makefile that can do that for the different stages, just edit the makefile as appropriate. Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ULE and very bad responsiveness
On Thu, 13 Nov 2003, Harald Schmalzbauer wrote: On Thursday 13 November 2003 07:17, Harald Schmalzbauer wrote: Hi, from comp.unix.bsd.freebsd.misc: Kris Kennaway wrote: On 2003-11-13, Harald Schmalzbauer [EMAIL PROTECTED] wrote: Well, I don't have any measurements but in my case it's not neccessary at all. I built a UP kernel with ULE like Kris advised me. Are you running an up-to-date 5.1-CURRENT? ULE was broken with these characteristics until very recently. If you're up-to-date and still see these problems, you need to post to the current mailing list. Kris Yes, I am running current as of 13. Nov. Find attached my first problem description. This time I also attached my dmesg and kernel conf Try running seti with nice +20 rather than 15. Do you experience bad interactivity without seti running? Thanks, Jeff Thanks, -Harry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Currentwith update this morning.
On Nov 13, 2003, at 1:02 PM, Eric Anderson wrote: snip === tools/build /usr/obj/usr/src/i386/usr/src/tools/build created for /usr/src/tools/build cd /usr/src/tools/build; make buildincludes; make installincludes rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/legacy/usr/include /usr/src/tools/build/dummy.c cc -O -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/tools/build/dummy.c building static egacy library ranlib libegacy.a sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libegacy.a /usr/obj/usr/src/i386/legacy/usr/lib *** Signal 11 I ran into this yesterday, after building before UPDATING was updated. You can get around this by manually re-compiling and installing (by copying, not by doing a make install) /usr/bin/install. After doing this, your buildworld (or buildkernel) will succeed. Brent -- J. Brent Jones PGP Key ID: 0xC50A0BC0 Director of Computing Santa Fe Institute (505) 984-8800 ext. 2716 http://www.santafe.edu ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recent -current hangs on Tyan S2460 before finishing boot
On November 13 2003, John Baldwin wrote: On 13-Nov-2003 Benjamin Lewis wrote: [trouble booting -current on Tyan Tiger MP] Can you do a 'show intrcnt' from the ddb prompt? It sounds like you may be getting an interrupt storm due to a mis-routed PCI interrupt. db show intrcnt [...] irq0: clk 1 You aren't getting any clock interrupts it seems. Very weird. Can you try using NO_MIXED_MODE instead? I still think the ata1 is bogus, but I don't think that is causing your hang now. NO_MIXED_MODE did the trick -- an otherwise identical kernel to the one that was hanging now boots to multiuser successfully. Thank you so much for your help! -Ben -- Benjamin Lewis [EMAIL PROTECTED] Database Analyst/Programmer IT Security and Policy - Identity and Access Management Purdue University ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: making a release
Scott Long wrote: I use the following all of the time: cd /usr/src/release ; make release BUILDNAME=5.1-CURRENT CHROOTDIR=/usr/release CVSROOT=/usr/ncvs I have NODOC=YES NOPORTS=YES and thought I'd be able to get by with EXTSRCDIR=/usr/src in place of CVSROOT=/usr/ncvs. Looks like EXTCRCDIR is not widely used, but would be convenient for a local user. Pete... Scott On Thu, 13 Nov 2003, Peter Schultz wrote: I'm trying to build a set of release floppies, but my setting for CHROOTDIR seems to be ignored and the release gets dumped in my root file system under /R. Shouldn't /R be installed under whatever I set CHROOTDIR to? Thanks, Pete... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning.
[EMAIL PROTECTED] writes: I'm building new kernels as I write this. My next question is: One of the machines I'm building on is remote and was last rebuilt just before the change. What would be be better sequence for making the change after a fresh cvsup ? RTFM. make buildworld make buildkernel make installkernel reboot make installworld mergemaster reboot DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: drm, irqs, etc.
On Wed, Nov 12, 2003 at 06:42:39PM -0800 I heard the voice of Kevin Oberman, and lo! it spake thus: In reality, 5.0 and 5.1 are neither, but questions have to go somewhere and it was announced some time ago that until a V5 version was declared 'STABLE', that questions should go to CURRENT and not STABLE. Well, if you wanna be pedantic about it, no -RELEASE's are -STABLE either. It's just a question of which branch the releases are branched (and/or snapshot'd) from. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atheron driver and netgear WG511T
On Thursday 13 November 2003 06:19 am, Eric Anderson wrote: hi, i get this when inserting my Netgear WG511T card into my laptop: ath0: Atheros 5212 mem 0x8801-0x8801 irq 11 at device 0.0 on cardbus0 ath0: unable to attach hardware; HAL status 13 device_probe_and_attach: ath0 attach returned 6 the ath manpage says that this chip should be supported... any ideas? Do you have the: device ath_hal line in your kernel config? Bernhard and I worked out that his card has a new 2112 radio that's not yet supported by the HAL. I hope to have something to try next week. Sam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: undelete for FreeBSD current?
Thanks Robert, The strings method worked very well in this instance. -Original Message- From: Robert Watson [mailto:[EMAIL PROTECTED] Sent: Thursday, 13 November 2003 1:59 PM To: Barney Wolff Cc: Thyer, Matthew; '[EMAIL PROTECTED]' Subject: Re: undelete for FreeBSD current? On Wed, 12 Nov 2003, Barney Wolff wrote: On Thu, Nov 13, 2003 at 11:30:51AM +1030, Thyer, Matthew wrote: I've done a bad thing and need to recover a single file in /usr/local/etc/rc.d/ after a rm -rf of /usr/local I've kept the file system relatively quiet since then. TCT may help. http://www.porcupine.org/forensics/tct.html but I don't think it's been tested with current/ufs2. Also, don't expect to build it on the system and then find a deleted file. But if you have a clue of what you're looking for, just grepping /dev/dan or /dev/adn might work. (grep -a -A100 -B100) Assuming that the file system had a fair amount of free space, and therefore wasn't fragmented, I've always found the strings command quite helpful in recovering text files after loss or deletion. It can also be nicely applied to /dev/mem if you accidentally close that pesky editor window without save... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ULE and very bad responsiveness
On Thursday 13 November 2003 22:25, Jeff Roberson wrote: On Thu, 13 Nov 2003, Harald Schmalzbauer wrote: On Thursday 13 November 2003 07:17, Harald Schmalzbauer wrote: Hi, from comp.unix.bsd.freebsd.misc: Kris Kennaway wrote: On 2003-11-13, Harald Schmalzbauer [EMAIL PROTECTED] wrote: Well, I don't have any measurements but in my case it's not neccessary at all. I built a UP kernel with ULE like Kris advised me. Are you running an up-to-date 5.1-CURRENT? ULE was broken with these characteristics until very recently. If you're up-to-date and still see these problems, you need to post to the current mailing list. Kris Yes, I am running current as of 13. Nov. Find attached my first problem description. This time I also attached my dmesg and kernel conf Try running seti with nice +20 rather than 15. Do you experience bad interactivity without seti running? On a related note, when will SCHED_ULE become the default? It looks like it's ready now (I just played Quake 3 while compiling a new X server :)). This should speed up the finding of any bugs in SCHED_ULE. Best regards, Arjan pgp0.pgp Description: signature
Re: ULE and very bad responsiveness
On Thursday 13 November 2003 22:25, Jeff Roberson wrote: On Thu, 13 Nov 2003, Harald Schmalzbauer wrote: On Thursday 13 November 2003 07:17, Harald Schmalzbauer wrote: Hi, from comp.unix.bsd.freebsd.misc: Kris Kennaway wrote: On 2003-11-13, Harald Schmalzbauer [EMAIL PROTECTED] wrote: Well, I don't have any measurements but in my case it's not neccessary at all. I built a UP kernel with ULE like Kris advised me. Are you running an up-to-date 5.1-CURRENT? ULE was broken with these characteristics until very recently. If you're up-to-date and still see these problems, you need to post to the current mailing list. Kris Yes, I am running current as of 13. Nov. Find attached my first problem description. This time I also attached my dmesg and kernel conf Try running seti with nice +20 rather than 15. Do you experience bad interactivity without seti running? No, without seti everythin seems to be fine except that I cannot watch two movies at the same time which is no problem with the old scheduler. I already switched back from ULE to the old because at the moment ULE makes working exhausting. I also could play quake(2) and have something compiling in the background but I see every new object file in form of a picture freeze. Also every other disk access seems to block the whole machine for a moment. I'll try again if somebody has an idea what's wrong. Then I can try running seti wtih nice 20 but that's not really a solution. It's working perfectly with nice 15 and the old scheduler. Thanks, -Harry Thanks, Jeff Thanks, -Harry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] pgp0.pgp Description: signature
Re: Synaptics PS/2 TouchPad
On Thursday 13 November 2003 22:54, Philip Paeps wrote: I've recently started work on getting psm to support Synaptics TouchPads more fully: virtual scrollbars, up/down buttons, multiple finger detection, etc. I have the basics working, but my brain has been too fried lately to deal with the maths of translating absolute coordinates to sensibly accelerated motions. Ooh nice :) Can you put it up somewhere so I can have a look? There is an XFree86 Synaptics driver which you could probably glean some ideas from.. http://w1.894.telia.com/~u89404340/touchpad/ -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[lists-vmailmgr@biaix.org: issues compiling on FreeBSD-5.1]
Hi, I can't compile vmailmgr on FreeBSD 5.1-RELEASE-p10, find the initial details in the attached message (which can't make it to [EMAIL PROTECTED]). What follows is copy'n'pasted compiler output of my attempts at 'fixing' the issue. However, the error messages don't give me more hints, and I have no further clue (why shouldn't configure find strlen or uid_t?, why shouldn't gcc know about constructors?) I've tried adding #include string.h to config.h, and then it fails at: g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I..-g -O2 -fno-rtti -fno-exceptions -Wall -W -c datum.cc In file included from ../fdbuf/fdbuf.h:78, from datum.h:4, from datum.cc:17: ../fdbuf/fdobuf.h:52: `uid_t' was not declared in this scope ../fdbuf/fdobuf.h:52: `gid_t' was not declared in this scope ../fdbuf/fdobuf.h:52: invalid data member initialization ../fdbuf/fdobuf.h:52: (use `=' to initialize static data members) gmake[3]: *** [datum.o] Error 1 gmake[3]: Leaving directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9/lib/cdb++' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9/lib' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9' gmake: *** [all-recursive-am] Error 2 [EMAIL PROTECTED]:~/packages/vmailmgr-0.96.9]0$ If I then add #include sys/types.h to config.h I get: gmake[3]: Entering directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9/lib/mystring' g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I..-g -O2 -fno-rtti -fno-exceptions -Wall -W -c append.cc append.cc: In member function `void mystring::append(const char*)': append.cc:17: `strlen' undeclared (first use this function) append.cc:17: (Each undeclared identifier is reported only once for each function it appears in.) gmake[3]: *** [append.o] Error 1 gmake[3]: Leaving directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9/lib/mystring' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9/lib' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9' gmake: *** [all-recursive-am] Error 2 [EMAIL PROTECTED]:~/packages/vmailmgr-0.96.9]0$ Adding #include string.h to lib/mystring/append.cc gets me to: gmake[2]: Entering directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9/authenticate' gcc -g -O2 -fno-rtti -fno-exceptions -Wall -W -o authvmailmgr authvmailmgr.o authvlib.o ../lib/libvmailmgr.a -L../lib/courier-authlib -lauthmod -lcrypt authvlib.o: In function `set_user(pwentry const*)': /home/joan/packages/vmailmgr-0.96.9/authenticate/authvlib.cc:63: undefined reference to `operator new(unsigned)' authvlib.o: In function `check': /home/joan/packages/vmailmgr-0.96.9/authenticate/authvlib.cc:81: undefined reference to `operator new(unsigned)' /home/joan/packages/vmailmgr-0.96.9/authenticate/authvlib.cc:93: undefined reference to `operator new(unsigned)' [about 50 more lines of undefined linking references] ../lib/libvmailmgr.a(list_table.o): In function `hash_tablebool, hash_nodebool, crc_hash::realloc(unsigned)': ../misc/hash_table.h:91: undefined reference to `operator new[](unsigned)' ../lib/libvmailmgr.a(cdb_get.o): In function `cdb_reader::get(mystring const)': ../mystring/mystring.h:111: undefined reference to `operator new(unsigned)' ../lib/libvmailmgr.a(read_uns.o): In function `configuration::read_uns(mystring const, unsigned, config_cacheunsigned) const': /home/joan/packages/vmailmgr-0.96.9/lib/config/read_uns.cc:42: undefined reference to `operator new(unsigned)' gmake[2]: *** [authvmailmgr] Error 1 gmake[2]: Leaving directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9/authenticate' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9' gmake: *** [all-recursive-am] Error 2 [EMAIL PROTECTED]:~/packages/vmailmgr-0.96.9]0$ And here I have to give up. Obviously configure it's not doing it's job, but I have no idea how to solve this. Any workarounds? tks -- pica ---BeginMessage--- [please Honour Mail-Followup-To:, not subscribed] vmailmgr-0.96.9 does not compile on FreeBSD-5.1p10: [EMAIL PROTECTED]:~/packages]0$rm -rf vmailmgr-0.96.9; \ tar xzf vmailmgr-0.96.9.tar.gz ; cd vmailmgr-0.96.9; \ ./configure --prefix=/package/host/peque.upc.es/vamilmgr-0 .96.9; gmake creating cache ./config.cache checking for a BSD compatible install... /usr/bin/install -c [...] creating config.h gmake all-recursive [...] Making all in misc gmake[3]: Entering directory `/fs/home/mount/home/joan/packages/vmailmgr-0.96.9/lib/misc' c++ -DHAVE_CONFIG_H -I. -I. -I../.. -I..-g -O2 -fno-rtti -fno-exceptions -Wall -W -c exec.cc exec.cc: In function `int presetenv(const char*, const mystring)': exec.cc:29: `strlen' undeclared (first use this function) exec.cc:29: (Each undeclared identifier
Re: HEADS-UP new statfs structure
Just for a short note: cfsd (ports/security/cfs) should be recompiled as well after those statfs changes. -- Mit freundlichen Gruessen, Marco Wertejuk - mwcis.com Consulting Internet Solutions ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: signal 12's everywhere on Current with update this morning.
In message: [EMAIL PROTECTED] Uwe Laverenz [EMAIL PROTECTED] writes: : [EMAIL PROTECTED] schrieb: : : Uwe, do you have any remote machines? I'm wondering what the correct : sequence would be to update and reboot them. : : I would suggest to do it this way: : : 1. make buildworld : 2. make kernel KERNCONF=YOURCONF : 3. *reboot* (with new kernel and old userland) Into single user... : 4. make installworld : 5. mergemaster : 6. *reboot* This is the order that's recommended in UPDATING since 3.something. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
