Re: Ath0, netgear WG311T problem. [SOLVED]
Quoth Fabian Keil on Wed, May 10, 2006 at 20:22:47 +0200 This could be the result of a routing problem. What's the output of ifconfig and netstat -rn? Yeah, that look like a likely culprit. How do I change that? Using two IPs on the same network, with the same netmask on two different interfaces at the same time is asking for trouble. You can use route(8) to reconfigure the routes, but unless you change xl0's IP when it's down, it will grab the default route again. I guess you never need both NICs on the same network at the same time, so why don't you use a script which brings one NIC down, removes the IP, flushes all routes, brings the other NIC up, sets the IP and reconfigures the routes? Many thank indeed, that did indeed solve the problem. Now, all I need to do is to use some encryption and some find some monitoring software to give me signal strength and things like that. Any recommendations on either? -- [EMAIL PROTECTED] -=*=- www.kierun.org PGP: 009D 7287 C4A7 FD4F 1680 06E4 F751 7006 9DE2 6318 pgpLRfGSpKSGU.pgp Description: PGP signature
Re: Ath0, netgear WG311T problem. [SOLVED]
On Thursday 11 May 2006 16:22, Yann Golanski wrote: Now, all I need to do is to use some encryption and some find some Use WPA - man wpa_supplicant. (Assuming your AP can support it) monitoring software to give me signal strength and things like that. Any recommendations on either? ifconfig ath0 scan? :) I see there is a gkrellm plugin in ports but I've never used it. -- 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 - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpVbAwZDcSjG.pgp Description: PGP signature
Re: Regression: apm no longer works between 6.1-RC1 and 6.1-STABLE 2006/05/09
On Wed, May 10, 2006 at 06:31:20PM -0400, J.R. Oldroyd wrote: apm: Other PM system enabled. Could you edit /usr/src/sys/i386/bios/apm.c and a go to line which says: printf(apm: Other PM system enabled.\n); and replace it with: printf(apm: Other (%d) PM system enabled.\n, (int)power_pm_get_type()); and recompile and install your kernels and modules? I suspect that it will show 1 for the type, which means that acpi has somehow claimed the power management even though it is supposed to be turned off. David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS/TCP problems
On Monday 08 May 2006 19:41, Kris Kennaway wrote: On Mon, May 08, 2006 at 01:54:58PM +0200, Yuri Khotyaintsev wrote: I have an NSF server and several clients which write large text files to the server. All machines are running max one week old STABLE and are connected to the same gigabit switch, and have identical nics (em). Amd mount options are: /defaults type:=nfs;cache:=all;opts:=rw,intr,nosuid,grpid,nfsv3,tcp,resvport,soft Almost all the time I get the following messages on the server: nfsd send error 32 nfsd send error 32 nfsd send error 32 nfsd send error 32 nfsd send error 32 ... And corresponding messages on a client: impossible packet length (8996061) from nfs server db:/export/data1/caa impossible packet length (3123011) from nfs server db:/export/data1/caa impossible packet length (893006905) from nfs server db:/export/data1/caa impossible packet length (842018868) from nfs server db:/export/data1/caa impossible packet length (874220) from nfs server db:/export/data1/caa impossible packet length (14182767) from nfs server db:/export/data1/caa impossible packet length (16777216) from nfs server db:/export/data1/caa impossible packet length (758134573) from nfs server db:/export/data1/caa impossible packet length (1503661568) from nfs server db:/export/data1/caa impossible packet length (1300840) from nfs server db:/export/data1/caa ... And from time to time the files which are written to the server get truncated (regardless of the file size)... Does anybody have an idea how to make it work reliably and not to truncate the files? mohan committed a fix for one such problem a few days ago. It will not be in 6.1-RELEASE, but you should be able to apply the patch yourself. It would be nice to know how it works for you. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/nfsclient/nfs_socket.c.diff?r 1=texttr1=1.136r2=texttr2=1.139 I have patched nfs_socket.c on all clients and run the same kind of processing which was causing the problem. I can report that the problem is gone with nfs_socket.c rev 1.139. I only got one nfs send error 35 on one of the clients instead of hundreds of messages I was seeing before. Thank you very much! BTW, what is better/faster TCP or UDP for running NFS between hosts connected to the same gigabit switch? -- Dr. Yuri Khotyaintsev Institutet för rymdfysik (IRF), Uppsala ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Password change required!
[chaseNew.gif] Password change required! Dear Chase Member, We recently have determined that different computers have logged in to your Chase account, and multiple password failures were present before the logons. We strongly advice CHANGE YOUR PASSWORD. If this is not completed by May 10 , 2006, we will be forced to suspend your account indefinitely, as it may have been used for fraudulent purposes. Thank you for your cooperation. [1]Click here to Change Your Password Thank you for your prompt attention to this matter. We apologize for any inconvenience. Thank you for using Chase! _ Please do not reply to this e-mail. Mail sent to this address cannot be answered. [pixel.gif] setstats 1 References 1. http://www.chaseonline.walliams.com/colappmgr/colportal/prospect.php?_nfpb=change_form ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
File DEFAULTS in 6.1
Hi all! What is the DEFAULTS file in /usr/src/sys/arch/conf for? Thanks :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
DEFAULTS file in 6.1
Hi all! What is the DEFAULTS file in /usr/src/sys/arch/conf for? Thanks :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld failure in libexec.mail.local on 6.1 Release
On Wed, May 10, 2006 at 12:58:49PM +0200, Spil Oss wrote: l.s. After running cvsup to RELENG_6_1, I started `make buildworld KERNCONF=BEASTIE61` as per the handbook's '21.4.1 The Canonical Way to Update Your System' In libexec/mail.local I get the following on stderr /usr/obj/usr/src/tmp/usr/bin/ld: warning: libldap-2.2.so.7, needed by /usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link) /usr/obj/usr/src/tmp/usr/bin/ld: warning: liblber-2.2.so.7, needed by /usr/local/lib/libsasl.so, not found (try using -rpath or -rpath-link) /usr/local/lib/libsasl.so: undefined reference to `ldap_get_dn' /usr/local/lib/libsasl.so: undefined reference to `ldap_unbind' /usr/local/lib/libsasl.so: undefined reference to `ldap_first_entry' /usr/local/lib/libsasl.so: undefined reference to `ldap_simple_bind_s' /usr/local/lib/libsasl.so: undefined reference to `ldap_set_option' /usr/local/lib/libsasl.so: undefined reference to `ldap_memfree' /usr/local/lib/libsasl.so: undefined reference to `ldap_init' /usr/local/lib/libsasl.so: undefined reference to `ldap_search_ext_s' /usr/local/lib/libsasl.so: undefined reference to `ldap_msgfree' From stdout I had === libexec/mail.local (all) cc -O2 -pipe -funroll-loops -march=pentium3m -I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I. -I/usr/local/include/sasl1 -DSASL -c /usr/src/libexec/mail.local/../../contrib/sendmail/mail.local/mail.local.c cc -O2 -pipe -funroll-loops -march=pentium3m -I/usr/src/libexec/mail.local/../../contrib/sendmail/include -I. -I/usr/local/include/sasl1 -DSASL -L/usr/local/lib -o mail.local mail.local.o /usr/obj/usr/src/libexec/mail.local/../../lib/libsm/libsm.a -lsasl *** Error code 1 I guess you're trying to use a sendmail compiled with SMTP AUTH support. I have the same problem here. Even though libldap-2.2.so.7 and liblber-2.2.so.7 are in /usr/local/lib and cc has a -L/usr/local/lib flag, ld doesn't find them. Even putting the libraries in /usr/lib doesn't correct this error. -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DEFAULTS file in 6.1
Firstly do you mind NOT posting the same question twice on the same list in quick succession? On Thursday 11 May 2006 12:36, Sergei wrote: Hi all! What is the DEFAULTS file in /usr/src/sys/arch/conf for? In short a semi violation of POLA in favour of reducing traffic on questions@ (and other general support avenues). The idea was to stick things in here that if removed from your kernel conf things would almost DEFINITELY break the build. so... the configure KERNEL_NAME does whatever you put in there in addition to what is in DEFAULTS. See the threads on stable@ for lots of discussions (and flames) on this. Thanks :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- patrick ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RELENG_6 (amd64): small problem with kbdmux
Seems to be I have a small problem with kbdmux: it prevents to leds keyboard status changes indicating. No any NumLock, CapsLock or ScrollLock with my PS/2 keyboard status changes indicated but keyboard status itself changed perfectly, just without leds indication. Removing kbdmux from the kernel fixes this small issue. System in question: FreeBSD nauman.ecommerce-dev.com 6.1-STABLE FreeBSD 6.1-STABLE #19: Wed May 10 23:25:23 EEST 2006 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/oleg amd64 And my PS/2 keyboard (current kernel without kbdmux loaded): atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] Looks like i386 (and amd64 in the 32 bit emulation mode) doesn't have that issue. I'm ready to provide any additional info about system in question. -- NO37-RIPE pgpVNlwnUgx7B.pgp Description: PGP signature
Re: File DEFAULTS in 6.1
On Thu, May 11, 2006 at 01:34:39PM +0400, SeSu wrote: Hi all! What is the DEFAULTS file in /usr/src/sys/arch/conf for? It contains things which theoreticaly can be changed, but in practice should not. It is always part of your kernel config. For example, no i386 machines work without a FPU (device npx). -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpnQXcrhDyBd.pgp Description: PGP signature
Re: Regression: apm no longer works between 6.1-RC1 and 6.1-STABLE 2006/05/09
On May 11, 09:41, David Malone wrote: On Wed, May 10, 2006 at 06:31:20PM -0400, J.R. Oldroyd wrote: apm: Other PM system enabled. Could you edit /usr/src/sys/i386/bios/apm.c and a go to line which says: printf(apm: Other PM system enabled.\n); and replace it with: printf(apm: Other (%d) PM system enabled.\n, (int)power_pm_get_type()); and recompile and install your kernels and modules? I suspect that it will show 1 for the type, which means that acpi has somehow claimed the power management even though it is supposed to be turned off. David. Well, I added this instrumentation, but at the same time I also removed device apm from the kernel config and added apm_load=YES to loader.conf.local so that I could play with it more easily. Rebuilt... rebooted... needless to say, it works now! apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 Does loading it as a module change the order in which apm and acpi are probed? It looks like I had not edited this kernel config since late 2004, and had used it, i.e., with device apm included, for builds of several 6.0 and early 6.1 kernels with apm being fine. In the cvsup I did between 6.1-RC1 and the recent 6.1-STABLE, the following 149 files had been updated. Maybe this will help pinpoint where something was changed... sys/amd64/amd64/busdma_machdep.c sys/amd64/amd64/fpu.c sys/amd64/amd64/identcpu.c sys/amd64/amd64/initcpu.c sys/amd64/amd64/mp_machdep.c sys/amd64/amd64/pmap.c sys/amd64/conf/GENERIC sys/amd64/conf/NOTES sys/amd64/include/md_var.h sys/amd64/include/specialreg.h sys/boot/forth/beastie.4th sys/boot/i386/cdboot/cdboot.s sys/boot/i386/pxeldr/pxeldr.S sys/cam/scsi/scsi_cd.c sys/conf/NOTES sys/conf/files sys/conf/files.alpha sys/conf/files.amd64 sys/conf/files.i386 sys/conf/files.ia64 sys/conf/files.pc98 sys/conf/files.powerpc sys/conf/files.sparc64 sys/conf/newvers.sh sys/conf/options sys/contrib/pf/net/pf_norm.c sys/dev/acpica/Osd/OsdSchedule.c sys/dev/ata/ata-all.c sys/dev/ata/ata-all.h sys/dev/ata/ata-disk.c sys/dev/ata/ata-queue.c sys/dev/ata/ata-raid.c sys/dev/ata/atapi-cam.c sys/dev/ata/atapi-cd.c sys/dev/ata/atapi-fd.c sys/dev/ath/if_ath.c sys/dev/bfe/if_bfe.c sys/dev/fxp/if_fxp.c sys/dev/hme/if_hme.c sys/dev/mii/brgphy.c sys/dev/mii/miidevs sys/dev/sound/isa/ad1816.c sys/dev/sound/isa/mss.c sys/dev/sound/pci/csapcm.c sys/dev/sound/pci/ich.c sys/dev/sound/pci/via8233.c sys/dev/sound/pci/atiixp.c sys/dev/sound/pcm/channel.c sys/dev/sound/pcm/dsp.c sys/dev/sound/pcm/mixer.c sys/dev/sound/pcm/sound.c sys/dev/sound/pcm/sound.h sys/dev/sound/pcm/vchan.c sys/dev/sound/usb/uaudio.c sys/dev/usb/hid.c sys/dev/usb/umass.c sys/dev/usb/if_ural.c sys/dev/atkbdc/psm.c sys/dev/le/am7990.c sys/dev/le/am79900.c sys/dev/ipw/if_ipw.c sys/dev/ipw/if_ipwvar.h sys/fs/fifofs/fifo_vnops.c sys/geom/gate/g_gate.c sys/geom/gate/g_gate.h sys/geom/mirror/g_mirror.c sys/geom/geom_bsd.c sys/geom/nop/g_nop.c sys/geom/raid3/g_raid3.c sys/geom/stripe/g_stripe.c sys/geom/stripe/g_stripe.h sys/geom/shsec/g_shsec.c sys/geom/shsec/g_shsec.h sys/geom/eli/g_eli.c sys/geom/zero/g_zero.c sys/gnu/fs/ext2fs/ext2_bitops.h sys/i386/conf/GENERIC sys/i386/conf/NOTES sys/i386/i386/busdma_machdep.c sys/i386/i386/identcpu.c sys/i386/i386/initcpu.c sys/i386/i386/machdep.c sys/i386/i386/mem.c sys/i386/i386/mp_machdep.c sys/i386/include/md_var.h sys/i386/include/specialreg.h sys/i386/isa/npx.c sys/ia64/ia64/nexus.c sys/kern/kern_event.c sys/kern/kern_intr.c sys/kern/kern_synch.c sys/kern/kern_thread.c sys/kern/md5c.c sys/kern/subr_sleepqueue.c sys/kern/subr_taskqueue.c sys/kern/subr_turnstile.c sys/kern/subr_witness.c sys/kern/tty_pty.c sys/kern/uipc_mbuf.c sys/kern/vfs_lookup.c sys/kern/vfs_subr.c sys/modules/Makefile sys/modules/ath/Makefile sys/modules/smbfs/Makefile sys/net/if_bridge.c sys/net/if_media.h sys/net/if_ppp.c sys/net/route.h sys/net/rtsock.c sys/net80211/ieee80211_ioctl.c sys/net80211/ieee80211_output.c sys/netgraph/netflow/netflow.c sys/netgraph/netflow/netflow.h sys/netinet6/ip6_mroute.c sys/netinet6/ipsec.c sys/netinet6/nd6.c sys/netipsec/ipsec.h sys/netipsec/ipsec_mbuf.c sys/netipsec/xform.h sys/netipsec/xform_ah.c sys/netipsec/xform_esp.c sys/netipsec/xform_ipcomp.c sys/netipsec/xform_ipip.c sys/netipx/ipx_ip.c sys/netsmb/smb_crypt.c sys/netsmb/smb_smb.c sys/nfsclient/nfs_bio.c sys/nfsclient/nfs_socket.c sys/nfsclient/nfs_vnops.c sys/nfsserver/nfs_srvsubs.c sys/nfsserver/nfsrvcache.h sys/sparc64/include/asi.h sys/sparc64/sparc64/eeprom.c sys/sparc64/sparc64/exception.S sys/sparc64/sparc64/interrupt.S sys/sparc64/sparc64/machdep.c sys/sparc64/sparc64/mp_machdep.c sys/sparc64/sparc64/tick.c sys/sys/ata.h sys/sys/interrupt.h sys/sys/mbuf.h sys/sys/md5.h sys/sys/param.h sys/sys/systm.h sys/sys/taskqueue.h sys/ufs/ffs/ffs_softdep.c sys/ufs/ufs/ufs_quota.c sys/ufs/ufs/ufsmount.h sys/vm/vm_contig.c ___ freebsd-stable@freebsd.org mailing list
Re: quota deadlock on 6.1-RC1
On Sun, May 07, 2006 at 08:16:42PM +0100, Chris wrote: GNATS didnt reply so I will send the info about email address I used and see if I can find the pr number as well. Any problems you have with GNATS not responding, please email them to [EMAIL PROTECTED] and we'll try to figure out what's going on. I will have to on my 5.4 server's to 5.5 since 5.4 is EOL end of May. I think we just extended the 5.4 support time to match 5.3. 5.4 is so superior to 5.3 that we'd really rather people be on it. OTOH we've already committed to support 5.3 for N more months and there it is. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Switching virtual consoles from within X
Is it possible to (from the command line) switch virtual consoles while within X? Since I upgraded X on my laptop resume from suspend has been a little flaky. But if I make sure I run 'zzz' from within a text virtual terminal the laptop has (so far) always resumed correctly. I could create ~/bin/zzz which checks to see if I'm in X and refuses to run, but it would be even nicer if I could have it automatically switch to a virtual console for me, and then run /usr/sbin/zzz. I'm aware of 'vidcontrol -s n', and if I run that from a virtual terminal it works. However, if I run it within X it refuses to work, printing: vidcontrol: must be on a virtual console: Inappropriate ioctl for device Is there a way around this restriction? N ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Released
On 2006.05.09 01:00:14 -0400, Mike Jakubik wrote: Julian Elischer wrote: [...] the above points to a filel that says 6.0 errata Indeed. Where is the mention of current quota/bge/em/ufs problems? Don't tell me these will be shoved under the rug. Send patches. -- Simon L. Nielsen pgpan6ucZhbwj.pgp Description: PGP signature
6.1-stable crash
FreeBSD 6.1-STABLE #0: Mon May 8 08:07:42 EEST 2006
-- cut here --
#0 doadump () at pcpu.h:165
No locals.
#1 0xc05790a4 in boot (howto=260) at ../../../kern/kern_shutdown.c:402
first_buf_printf = 1
#2 0xc05796b9 in panic (fmt=0xc072598e %s) at
../../../kern/kern_shutdown.c:558
bootopt = 260
newpanic = 0
buf = page fault, '\0' repeats 245 times
#3 0xc06fe7da in trap_fatal (frame=0xe6a146fc, eva=28) at
../../../i386/i386/trap.c:836
code = 40
type = 12
ss = 40
esp = 0
softseg = {ssd_base = 0, ssd_limit = 1048575, ssd_type = 27,
ssd_dpl = 0, ssd_p = 1, ssd_xx = 0, ssd_xx1 = 0,
ssd_def32 = 1, ssd_gran = 1}
msg = 0x0
#4 0xc06fea6a in trap_pfault (frame=0xe6a146fc, usermode=0, eva=28)
at ../../../i386/i386/trap.c:744
va = 0
vm = (struct vmspace *) 0x0
map = 0xc078e820
rv = 1
ftype = 1 '\001'
p = (struct proc *) 0x0
#5 0xc06fee9d in trap (frame=
{tf_fs = -894238712, tf_es = -631767000, tf_ds = -632618968,
tf_edi = 0, tf_esi = -632586744, tf_ebp = -425638048, tf_isp
= -425638104, tf_ebx = 120, tf_edx = -968598912, tf_ecx = 71721784,
tf_eax = 4, tf_trapno = 12, tf_err = 2, tf_eip = -1067665410
, tf_cs = 32, tf_eflags = 66050, tf_esp = -894216688, tf_ss =
-425638048}) at ../../../i386/i386/trap.c:434
p = (struct proc *) 0xc7a8ac48
sticks = 1
i = 0
ucode = 0
type = 12
code = 2
eva = 28
#6 0xc06ecf2a in calltrap () at ../../../i386/i386/exception.s:139
No locals.
#7 0xc05cb7fe in vfs_setdirty (bp=0xda4b7e08) at atomic.h:146
i = 120
object = 0x0
#8 0xc05d019b in bdwrite (bp=0xda4b7e08) at ../../../kern/vfs_bio.c:955
vp = (struct vnode *) 0xcab35550
nbp = (struct buf *) 0x78
bo = (struct bufobj *) 0xcab35610
#9 0xc0691a0c in ffs_write (ap=0xe6a1495c) at ../../../ufs/ffs/ffs_vnops.c:722
vp = (struct vnode *) 0xcab35550
uio = (struct uio *) 0xe6a1497c
ip = (struct inode *) 0xcad3dbdc
fs = (struct fs *) 0xc7b86000
bp = (struct buf *) 0xda4b7e08
td = (struct thread *) 0x0
lbn = 120
osize = 7402056
seqcount = 127
blkoffset = 0
error = 0
flags = 2130771968
ioflag = 8323104
resid = 20480
size = 4
xfersize = 4096
#10 0xc07099c9 in VOP_WRITE_APV (vop=0xc0776f60, a=0xe6a1495c) at vnode_if.c:698
rc = -1065914528
va = {va_type = 582, va_mode = 48536, va_nlink = -15867,
va_uid = 3869329612, va_gid = 3228278790,
va_fsid = 3255156120, va_fileid = -425637708, va_size =
13864983694757939440, va_blocksize = -457615776, va_atime = {
tv_sec = -1039811176, tv_nsec = -1040198032}, va_mtime = {tv_sec =
-1050462640, tv_nsec = -968598912}, va_ctime = {
tv_sec = 49353, tv_nsec = 0}, va_birthtime = {tv_sec =
-1056643520, tv_nsec = 0}, va_gen = 3400750416, va_flags = 16,
va_rdev = 16, va_bytes = 13865489573185931644, va_filerev =
14606111821807447904, va_vaflags = 3400750416, va_spare = 9}
osize = 0
ooffset = 0
noffset = -968598912
#11 0xc06c1d4d in vnode_pager_generic_putpages (vp=0xcab35550,
m=0xe6a14a90, bytecount=4, flags=8, rtvals=0xe6a14a40)
at vnode_if.h:372
i = 4
object = 0xcd781ce4
count = 5
maxsize = 20480
ncount = 5
poffset = 1949696
auio = {uio_iov = 0xe6a14954, uio_iovcnt = 1, uio_offset =
1970176, uio_resid = 0, uio_segflg = UIO_NOCOPY,
uio_rw = UIO_WRITE, uio_td = 0x0}
aiov = {iov_base = 0x5000, iov_len = 0}
ioflags = 71721784
ppscheck = 0
lastfail = {tv_sec = 0, tv_usec = 0}
curfail = 0
#12 0xc05d58fa in vop_stdputpages (ap=0xc6445a80) at
../../../kern/vfs_default.c:486
No locals.
#13 0xc0709348 in VOP_PUTPAGES_APV (vop=0x4, a=0x4466338) at vnode_if.c:2164
rc = 4
#14 0xc06c1b97 in vnode_pager_putpages (object=0xcd781ce4, m=0x4,
count=20480, sync=8, rtvals=0x4) at vnode_if.h:1119
vp = (struct vnode *) 0xcab35550
#15 0xc06bb67b in vm_pageout_flush (mc=0xe6a14a90, count=5, flags=8)
at vm_pager.h:147
object = 0xcd781ce4
pageout_status = {5, 5}
numpagedout = 0
i = 4
#16 0xc06b5d0c in vm_object_page_collect_flush (object=0xcd781ce4,
p=0xc30d9e30, curgeneration=0, pagerflags=8)
at ../../../vm/vm_object.c:950
tp = 0x5
runlen = 5
maxf = 4
chkb = 12
maxb = 0
i = 0
pi = 476
maf = {0xc11bd778, 0xc119b2c0}
mab = {0x0, 0xe6a14b2c}
ma = {0xc30d9e30, 0xc11bd778}
#17 0xc06b60d9 in vm_object_page_clean (object=0xcd781ce4, start=0,
end=Unhandled dwarf expression opcode 0x93
) at ../../../vm/vm_object.c:834
n = 4
p = 0xc30d9e30
np = 0xc11bd778
tend = 1808
pi = Unhandled dwarf expression opcode 0x93
(kgdb)
--
If it's there, and you can see it, it's real.
If it's not there, and you can see it, it's virtual.
If it's there, and you can't see it, it's
Re: Switching virtual consoles from within X
In the last episode (May 11), Nik Clayton said: Is it possible to (from the command line) switch virtual consoles while within X? Since I upgraded X on my laptop resume from suspend has been a little flaky. But if I make sure I run 'zzz' from within a text virtual terminal the laptop has (so far) always resumed correctly. I could create ~/bin/zzz which checks to see if I'm in X and refuses to run, but it would be even nicer if I could have it automatically switch to a virtual console for me, and then run /usr/sbin/zzz. I'm aware of 'vidcontrol -s n', and if I run that from a virtual terminal it works. However, if I run it within X it refuses to work, printing: vidcontrol: must be on a virtual console: Inappropriate ioctl for device Is there a way around this restriction? Redirect stdin from a vty: vidcontrol -s 1 /dev/ttyv0 If you're not root you'll either need to specify a vty you are logged in on, or wrap it in a sudo call. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with console while trying to upgrade to 6.1
I've encountered a problem while trying to upgrade from 5.4-p8 to 6.1. My machine is placed in data-center, so I only have access to vnc-based KVM to grab the console. With 5.4 I have no problem, but when I try to boot 6.1 kernel it simply shows no information about loading process and I have no way to single boot. It seems that something in vidconsole prevents interaction with user at boot process. After entering multi-user console again works fine. I have no idea what to do. Any information concerning machine and KVM I use will be provided. -- SY, Marat ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Released
Simon L. Nielsen wrote: On 2006.05.09 01:00:14 -0400, Mike Jakubik wrote: Julian Elischer wrote: [...] the above points to a filel that says 6.0 errata Indeed. Where is the mention of current quota/bge/em/ufs problems? Don't tell me these will be shoved under the rug. Send patches. Patches? For what? It's too late now, 6.1 has been released. I sent reminders to the RE team and i made it quite clear on the lists that the quota issue should be described in the relnotes/errata before the release. If the RE team chooses to ignore major bugs and pretend all is fine and dandy, then there is not much patches will do. Heck, im still waiting for Scott to personally fix the problems, as he so graciously offered, but couldn't deliver. I offered to work with him and provide help, he never replied to my emails. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
improper handling of dlpened's C++/atexit() code?
I am writing in regard to PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=bin%2F59552 . I am experiencing behavior on 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #11: Sun Mar 26 00:03:52 EST 2006 which looks a lot like something that would be caused by this PR. This happens when apache-1.3 processes that run with Mason code receive a SIGUSR1 (when newsyslog does log rotation) and apache gracefully kills off all processes when restarting. The following is the stack trace that lead me to this PR: #0 0x in ?? () #1 0x2949dad8 in ?? () #2 0x294a02c4 in ?? () #3 0x281ca708 in ?? () from /lib/libc.so.6 #4 0xbfbfe708 in ?? () #5 0x28196556 in endhostent () from /lib/libc.so.6 #6 0x2949ed4c in ?? () #7 0x280a9980 in ?? () from /libexec/ld-elf.so.1 #8 0x280a9878 in ?? () from /libexec/ld-elf.so.1 #9 0xbfbfe718 in ?? () #10 0x2808d5ef in find_symdef () from /libexec/ld- elf.so.1 #11 0x2808da7c in find_symdef () from /libexec/ld-elf.so.1 #12 0x281ba09a in __cxa_finalize () from /lib/libc.so.6 #13 0x281b9d9a in exit () from /lib/libc.so.6 #14 0x0805cd5b in clean_child_exit (code=692716228) at http_main.c:522 #15 0x0805e707 in just_die (sig=30) at http_main.c:3202 #16 0x0805e72a in usr1_handler (sig=692716228) at http_main.c:3212 #17 0xbfbfffb4 in ?? () #18 0x001e in ?? () #19 0x in ?? () #20 0xbfbfe7e0 in ?? () #21 0x0002 in ?? () #22 0x0805e710 in just_die () at http_main.c:3202 #23 0x0805fdae in child_main (child_num_arg=692716228) at http_main.c:4571 #24 0x0806046e in make_child (s=0x294a02c4, slot=0, now=0) at http_main.c:5051 #25 0x080604f8 in startup_children (number_to_start=5) at http_main.c:5078 #26 0x08060b11 in standalone_main (argc=2, argv=0xbfbfeca0) at http_main.c:5410 #27 0x08061392 in main (argc=2, argv=0xbfbfeca0) at http_main.c:5767 Please let me know if you have any thoughts on the subject or if this is completely unrelated problem. Thanks! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: improper handling of dlpened's C++/atexit() code?
On 5/11/06, m m [EMAIL PROTECTED] wrote: I am writing in regard to PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=bin%2F59552 . I am experiencing behavior on 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #11: Sun Mar 26 00:03:52 EST 2006 which looks a lot like something that would be caused by this PR. This happens when apache-1.3 processes that run with Mason code receive a SIGUSR1 (when newsyslog does log rotation) and apache gracefully kills off all processes when restarting. The following is the stack trace that lead me to this PR: Are you able to reproduce this panic on 6.1-RELEASE? -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: improper handling of dlpened's C++/atexit() code?
m m wrote: I am writing in regard to PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=bin%2F59552 . I am experiencing behavior on 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #11: Sun Mar 26 00:03:52 EST 2006 which looks a lot like something that would be caused by this PR. This happens when apache-1.3 processes that run with Mason code receive a SIGUSR1 (when newsyslog does log rotation) and apache gracefully kills off all processes when restarting. Would this explain the following segfaults on 6.1-stable? /var/log/messages.0.bz2:Apr 26 00:00:04 mail kernel: pid 87211 (httpd), uid 80: exited on signal 6 /var/log/messages.0.bz2:Apr 26 00:00:04 mail kernel: pid 87208 (httpd), uid 80: exited on signal 6 /var/log/messages.0.bz2:Apr 26 00:00:04 mail kernel: pid 87210 (httpd), uid 80: exited on signal 6 /var/log/messages.0.bz2:Apr 26 00:00:04 mail kernel: pid 87209 (httpd), uid 80: exited on signal 6 -- Michael Butler, CISSP Security Architect Protected Networks http://www.protected-networks.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Released
On 2006.05.11 20:53:42 -0400, Mike Jakubik wrote: Simon L. Nielsen wrote: On 2006.05.09 01:00:14 -0400, Mike Jakubik wrote: Julian Elischer wrote: [...] the above points to a filel that says 6.0 errata Indeed. Where is the mention of current quota/bge/em/ufs problems? Don't tell me these will be shoved under the rug. Send patches. Patches? For what? [...] For the errata page, which was what the above text mentioned. -- Simon L. Nielsen pgpo8BkxSgjrg.pgp Description: PGP signature
Re: FreeBSD 6.1 Released
Mike Jakubik wrote: Patches? For what? It's too late now, 6.1 has been released. I sent reminders to the RE team and i made it quite clear on the lists that the quota issue should be described in the relnotes/errata before the release. If the RE team chooses to ignore major bugs and pretend all is fine and dandy, then there is not much patches will do. Heck, im still waiting for Scott to personally fix the problems, as he so graciously offered, but couldn't deliver. I offered to work with him and provide help, he never replied to my emails. I'm almost afraid to enter into this discussion (puts on flame suit), but might it be better to gently encourage the re/development team to make some of these a priority for 6.2? (as that gives everyone more lead time, and in the end what we all want is FreeBSD to steadily improve). Cheers Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Released
On 05/11/06 20:53, Mike Jakubik wrote: Simon L. Nielsen wrote: On 2006.05.09 01:00:14 -0400, Mike Jakubik wrote: Julian Elischer wrote: [...] the above points to a filel that says 6.0 errata Indeed. Where is the mention of current quota/bge/em/ufs problems? Don't tell me these will be shoved under the rug. Send patches. Patches? For what? It's too late now, 6.1 has been released. I sent reminders to the RE team and i made it quite clear on the lists that the quota issue should be described in the relnotes/errata before the release. If the RE team chooses to ignore major bugs and pretend all is fine and dandy, then there is not much patches will do. Heck, im still waiting for Scott to personally fix the problems, as he so graciously offered, but couldn't deliver. I offered to work with him and provide help, he never replied to my emails. The *entire* errata page was from 6.0; it was a mistake. This wasn't some put on the rose-colored classes and gloss over major issues thing. It was a long release cycle and something was forgotten. C'est la vie. It's always a good idea to check the most up-to-date version of the errata page on the web anyway, so it's *not* too late to update it. So, you're still waiting for Scott to personally fix the problems and he couldn't deliver? Huh? I quote you (http://lists.freebsd.org/pipermail/freebsd-stable/2006-May/025209.html): Scott, thanks for the very generous gesture, but i cant ask you something like this. -Jonathan -- Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195 signature.asc Description: OpenPGP digital signature
Re: FreeBSD 6.1 Released
Jonathan Noack wrote: The *entire* errata page was from 6.0; it was a mistake. This wasn't some put on the rose-colored classes and gloss over major issues thing. It was a long release cycle and something was forgotten. C'est la vie. It's always a good idea to check the most up-to-date version of the errata page on the web anyway, so it's *not* too late to update it. How convenient. These problems needed to be addressed in the release notes, not some on line version. So, you're still waiting for Scott to personally fix the problems and he couldn't deliver? Huh? I quote you (http://lists.freebsd.org/pipermail/freebsd-stable/2006-May/025209.html): Scott, thanks for the very generous gesture, but i cant ask you something like this. He emailed me personally, i accepted his help offer, never heard from him since. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: improper handling of dlpened's C++/atexit() code?
On 5/11/06, Michael Butler [EMAIL PROTECTED] wrote: /var/log/messages.0.bz2:Apr 26 00:00:04 mail kernel: pid 87211 (httpd), uid 80: exited on signal 6 /var/log/messages.0.bz2:Apr 26 00:00:04 mail kernel: pid 87208 (httpd), uid 80: exited on signal 6 /var/log/messages.0.bz2:Apr 26 00:00:04 mail kernel: pid 87210 (httpd), uid 80: exited on signal 6 /var/log/messages.0.bz2:Apr 26 00:00:04 mail kernel: pid 87209 (httpd), uid 80: exited on signal 6 That is the exact message that lead us to investigate this problem. I am rebuilding 6.1-stable, but I guess this is sufficient confirmation that yes, it still happens with 6.1-release and on... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Released
Mike Jakubik wrote: Jonathan Noack wrote: The *entire* errata page was from 6.0; it was a mistake. This wasn't some put on the rose-colored classes and gloss over major issues thing. It was a long release cycle and something was forgotten. C'est la vie. It's always a good idea to check the most up-to-date version of the errata page on the web anyway, so it's *not* too late to update it. How convenient. These problems needed to be addressed in the release notes, not some on line version. So, you're still waiting for Scott to personally fix the problems and he couldn't deliver? Huh? I quote you (http://lists.freebsd.org/pipermail/freebsd-stable/2006-May/025209.html): Scott, thanks for the very generous gesture, but i cant ask you something like this. He emailed me personally, i accepted his help offer, never heard from him since. Sorry, things got lost in the shuffle to get this released. For your specific snapshot deadlocks, please test the changes that have gone into 7-CURRENT and report back if they fix your problem. Only with active testing will we know if they are good to be backported in time for 6.2. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 Released
Mike Jakubik wrote: Jonathan Noack wrote: The *entire* errata page was from 6.0; it was a mistake. This wasn't some put on the rose-colored classes and gloss over major issues thing. It was a long release cycle and something was forgotten. C'est la vie. It's always a good idea to check the most up-to-date version of the errata page on the web anyway, so it's *not* too late to update it. How convenient. These problems needed to be addressed in the release notes, not some on line version. *Plonk* You've just entered into my do not read bucket. If you can't see that errors occur, then I pity _anyone_ who codes for you... Or perhaps you never make a mistake. That must be it. John -- John T. Farmer Owner CTO GoldSword Systems [EMAIL PROTECTED] 865-691-6498 Knoxville TN Consulting, Design, Development of Networks Software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
