swap_pager / SCB time outs?
Just upgraded my server to newest kernel, did a 'make -j16 buildworld' and
an installworld with no problems, and then started building newest kde ...
woke up to this all over my screen ...
console was locked, ctl-alt-esc made no difference, had to cold-boot to
get the system back up again ...
Jun 11 06:48:20 thelab /boot/kernel/kernel: swap_pager: indefomplete. Interrupts may
not be functioning.
Jun 11 06:48:20 thelab /boot/kernel/kernel: swap_pager: indefomplete. Interrupts may
not be functioning.
Jun 11 07:02:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 73496, size: 4096
Jun 11 07:02:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 73496, size: 4096
Jun 11 07:06:20 thelab /boot/kernel/kernel: ahc0: Timedout SCB already complete.
Interrupts may not be functioning.
Jun 11 07:06:20 thelab /boot/kernel/kernel: ahc0: Timedout SCB already complete.
Interrupts may not be functioning.
Jun 11 07:10:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 27920, size: 4096
Jun 11 07:10:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 27920, size: 4096
Jun 11 07:15:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 27920, size: 4096
Jun 11 07:15:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 27920, size: 4096
Jun 11 07:22:20 thelab /boot/kernel/kernel: ahc0: Timedout SCB already complete.
Interrupts may not be functioning.
Jun 11 07:22:20 thelab /boot/kernel/kernel: ahc0: Timedout SCB already complete.
Interrupts may not be functioning.
Jun 11 07:33:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 27920, size: 4096
Jun 11 07:33:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 27920, size: 4096
Jun 11 07:42:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 83504, size: 4096
Jun 11 07:42:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 83504, size: 4096
Jun 11 07:45:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 83504, size: 4096
Jun 11 07:45:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 83504, size: 4096
Jun 11 07:51:20 thelab /boot/kernel/kernel: ahc0: Timedout SCB already complete.
Interrupts may not be functioning.
Jun 11 07:51:20 thelab /boot/kernel/kernel: ahc0: Timedout SCB already complete.
Interrupts may not be functioning.
Jun 11 07:55:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 84760, size: 8192
Jun 11 07:55:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 84760, size: 8192
Jun 11 08:03:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 84760, size: 8192
Jun 11 08:03:20 thelab /boot/kernel/kernel: swap_pager: indefinite wait buffer:
device: da1s1b, blkno: 84760, size: 8192
Jun 11 08:11:20 thelab /boot/kernel/kernel: ahc0: Timedout SCB already complete.
Interrupts may not be functioning.
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Tonights panic: free_newdirblk+0x73: movl %eax,0x10(%edx)
Just upgraded to latest sources, doesn't look like the swap issue ... was
performing a 'make -j16 buildworld' when it panic'd ...
Fataltrap 12: page fault while in kernel mode
cpuid = 0; lapic.id =
fault virtual address = 0x12
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc020abff
stack pointer = 0x10:0xcb75dbbc
frame pointer = 0x10:0xcb75dbc4
code segmnt = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 17 (swi3: cambio)
kernel: type 12 trap, code=0
Stopped at free_newdirblk+0x73:movl%eax,0x10(%edx)
db trace
free_newdirblk+0x73
handle_written_inodeblock+0x29e
softdep_disk_write_complete+0x6a
bufdone+0xbc
bufdonebio+0xf
dadone+0x214
camisr+0x1d7
ithread_lopp+0x330
fork_exit+0xbc
fork_trampoline+0x8
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
RE: Tonights panic: free_newdirblk+0x73: movl %eax,0x10(%e
Okay, running a new buildworld right now ... give it a half hour or so :) On Wed, 23 May 2001, John Baldwin wrote: Looks like %edx is 0x2 then. In other post, the faulting va was 0x11 with the same instruction, meaning that %edx is 0x1. So it looks like it isn't a NULL pointer dereference. It may be related to the VM stuff in that it may be that a buffer is being manipulated somewhere without Giant being held while being manipulated with Giant being held somewhere else? Or it could be a softupdates bug. :-P Is this an SMP machine? Ah, yes it is. Next time you see this, can you display 'show pcpu' for each CPU (show pcpu does the current cpu, show cpu some decimal number displays the info on CPU some decimal number). Okay, this is no problem ... Also, can you get a backtrace of each process that is running? trace on x86 can take the pid of a process to get a backtrace of as a parameter, and the show pcpu commands should show you what process was executing on the other CPU (including its pid). Oops ... neat, now it just locked up solid and ctl-alt-esc doesn't even get me to debugger :( ah well, will try and recreate the error and report back ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic: merge_inode_lists+0x86: movl %eax,0x10(%edx)
Just upgraded to latest sources, doesn't look like the swap issue ... was
performing a 'make -j16 buildworld' when it panic'd ...
Fataltrap 12: page fault while in kernel mode
cpuid = 0; lapic.id =
fault virtual address = 0x11
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc020d646
stack pointer = 0x10:0xcce9ac04
frame pointer = 0x10:0xcce9ac0c
code segmnt = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 62131 (sh)
kernel: type 12 trap, code=0
Stopped at merge_inode_lists+0x86: movl%eax,0x10(%edx)
db trace
merge_inode_lists+0x86
softdep_setup_freeblocks+0x21c
ffs_truncate+0x1d0
ufs_inactive+0x9a
ufs_vnoperate+0x15
vrele+0x16e
ufs_close+0x198
ufs_vnoperate+0x15
vn_close+0x40
vn_closefile+0x23
fdrop+0xb9
closef+0x9b
fdfree+0x44
exit1+0x5eb
sys_exit+0x15
syscall+0x645
syscall_with_err_pushed+0x1b
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: make installworld runs out of space on / ...
On Fri, 11 May 2001, jack wrote: On May 12 The Hermit Hacker wrote: My / directory, right now, has 12Meg free on it ... if I do a make installworld, it will fail due to no space left on device ... Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted on /dev/da1s1a 63503460151240879%1858 1401212% / Has anyone run into this one? Yes, with softupdates enabled on / Is there a way of fixing it? tunefs -n disable / worked for me. d'oh, hadn't thought of that ... will do that before I do my next make installworld, thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make installworld runs out of space on / ...
On Fri, 11 May 2001, Will Andrews wrote: On Sat, May 12, 2001 at 12:47:30AM -0300, The Hermit Hacker wrote: My / directory, right now, has 12Meg free on it ... if I do a make installworld, it will fail due to no space left on device ... Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted on /dev/da1s1a 63503460151240879%1858 1401212% / Has anyone run into this one? Is there a way of fixing it? I can't find anything on / that isn't supposed to be there, or is relatively large ;( rm -rf /var/tmp/install.* /var and /tmp are seperate file systems ... but, I do have softupdates enabled, like someone else suggested :( To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
nfsd/mountd problems?
have checked /usr/src/UPDATING, and found:
20010319:
portmap had changed name to rpcbind for maximum POLA in your
current world. /etc/hosts.{allow,deny} needs changes. nfs and
other rpc based programs that rely on portmapper will not work
without updates to /etc/hosts.{allow,deny}.
But my hosts.allow is up to date as of May 5th ...
May 12 01:10:40 thelab nfsd:[6310]: rpcb_unset failed
May 12 01:17:33 thelab nfsd:[20226]: rpcb_unset failed
May 12 01:17:48 thelab mountd[21102]: can't delete exports for /
May 12 01:17:48 thelab mountd[21102]: can't delete exports for /home
May 12 01:17:48 thelab mountd[21102]: can't delete exports for /tmp
May 12 01:17:48 thelab mountd[21102]: can't delete exports for /usr
May 12 01:17:48 thelab mountd[21102]: can't delete exports for /usr/local
May 12 01:17:48 thelab mountd[21102]: can't delete exports for /var
May 12 01:17:48 thelab mountd[21105]: can't register UDP RPCMNT_VER1 service
May 12 01:17:48 thelab mountd[21105]: can't register UDP RPCMNT_VER3 service
May 12 01:17:48 thelab mountd[21105]: can't register TCP RPCMNT_VER1 service
May 12 01:17:48 thelab mountd[21105]: can't register TCP RPCMNT_VER3 service
May 12 01:17:48 thelab mountd[21105]: can't register UDP6 RPCMNT_VER1 service
May 12 01:17:48 thelab mountd[21105]: can't register UDP6 RPCMNT_VER3 service
May 12 01:17:48 thelab mountd[21105]: can't register TCP6 RPCMNT_VER1 service
May 12 01:17:48 thelab mountd[21105]: can't register TCP6 RPCMNT_VER3 service
May 12 01:17:48 thelab mountd[21105]: could not create any services
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
panic: lockmgr: draining against myself
doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd
with:
panic: lockmgr: draining against myself
cpuid = 1; lapic.id = 0100
Debugging("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Stopped at DEbuger+0x46: pushl %ebx
trace shows:
Debugger
panic
lockmgr
vop_stdlock
ufs_vnoperate
vclean
vgonel
vrecycle
ufs_inactive
ufs_vnoperate
vput
handle_workitem_freeblocks
softdep_setup_freeblocks
ffs_truncate
ufs_inactive
ufs_vnoperate
vrele
vn_close
vn_closefile
fdrop
closef
close
syscall
syscall_with_err_pushed
Based on kernel upgraded/installed on April 6th ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: panic: lockmgr: draining against myself
just as a heads up, was just able to recreate it with a simple 'make
install' ... didn't need the -j16 to do it ...
On Sat, 7 Apr 2001, The Hermit Hacker wrote:
doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd
with:
panic: lockmgr: draining against myself
cpuid = 1; lapic.id = 0100
Debugging("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Stopped atDEbuger+0x46: pushl %ebx
trace shows:
Debugger
panic
lockmgr
vop_stdlock
ufs_vnoperate
vclean
vgonel
vrecycle
ufs_inactive
ufs_vnoperate
vput
handle_workitem_freeblocks
softdep_setup_freeblocks
ffs_truncate
ufs_inactive
ufs_vnoperate
vrele
vn_close
vn_closefile
fdrop
closef
close
syscall
syscall_with_err_pushed
Based on kernel upgraded/installed on April 6th ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: panic: lockmgr: draining against myself
problem appears to be fsck related ... fsck -p was only doing two out of 6
of my file systems .. manually ran fsck on each, and right now am doing a
buildworld for last nights upgrade and we'll see what happens ...
On Sat, 7 Apr 2001, The Hermit Hacker wrote:
just as a heads up, was just able to recreate it with a simple 'make
install' ... didn't need the -j16 to do it ...
On Sat, 7 Apr 2001, The Hermit Hacker wrote:
doing a 'make -j16 install' on kdebase from cvs, it eventually panic'd
with:
panic: lockmgr: draining against myself
cpuid = 1; lapic.id = 0100
Debugging("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Stopped at DEbuger+0x46: pushl %ebx
trace shows:
Debugger
panic
lockmgr
vop_stdlock
ufs_vnoperate
vclean
vgonel
vrecycle
ufs_inactive
ufs_vnoperate
vput
handle_workitem_freeblocks
softdep_setup_freeblocks
ffs_truncate
ufs_inactive
ufs_vnoperate
vrele
vn_close
vn_closefile
fdrop
closef
close
syscall
syscall_with_err_pushed
Based on kernel upgraded/installed on April 6th ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
panic: spin lock sched lock ...
just panic'd, couldn't even get to the ddb prompt this time ...
panic: spin lock sched lock held by 0xcb34b840 for 5 seconds
cpuid = 1; lapic.id = 0100
Debugger("panic")
CPU1 stopping CPUs ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ssh: no RSA support in libssl and libcrypto. See ssl(8).
how does one fix this? *puzzled look* there is no ssl(8) that I can seem
to find to See, and nothing apparent in the UPGRADING file ... system
uptodate as of last night, and mergemaster just finished completing ...
ssh: no RSA support in libssl and libcrypto. See ssl(8).
Disabling protocol version 1
DH_generate_key
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: spin lock panic ...
On Fri, 23 Mar 2001, John Baldwin wrote:
On 24-Mar-01 The Hermit Hacker wrote:
On Fri, 23 Mar 2001, John Baldwin wrote:
On 24-Mar-01 The Hermit Hacker wrote:
Over the past few days, I reformatted my computer clean, installed
4.2-RELEASE onto her and just finished upgrading to the latest 5.x kernel
and world ... went to ports/x11/XFree86-4 and did a 'make install' ...
after awhile, it panic'd as below:
panic: spin lock sched lock held by 0xcb332840 for 5 seconds
cpuid = 1; lapic.id = 0100
Debugger("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Now, I do have DDB enabled in the kernel ... but, for the life of me, I
can't seem to find any docs on the keystroke required to drop into it :(
'man ddb' doesn't document it that I can find, nor does LINT ...
Uhh, if it panic'd, it should already be in ddb at a db prompt assuming you
have DDB in your kernel.
didn't ... last line was as above ... I've even tested my DDB to make sure
I can get to the db prompt after alfred reminded me of the ctl-alt-esc to
get there, and it works ...
Well, that meants it most likely deadlocked trying to get into the debugger. I
haven't seen any deadlocks like this in months though.
I swear, my compuer is just so special :) it hasn't happened since
... re started the X compile, it finished fine and installed .. *shrug*
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
panic: resource_list_alloc
just upgraded my tree and did a reinstall ... trace is:
resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at resource_list_alloc+0xd3
isa_alloc_resource() @ +0xd0
bus_alloc_resource() @ +0x5f
opti_detect @ +0x99
mss_detect @ +0x52
mss_probe @ +0x30a
device_probe_child @ +0xca
device_probe_and_attach @ +0x41
isa_probe_children @ +0xde
configure @ +0x32
mi_startup @ +0x6e
begin @ +0x29
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: panic: resource_list_alloc
doing so right now ... one quick/stupid question ... how does one
'reinstall' a new kernel so that you don't lose the /boot/kernel.old (aka
backup that worked)? I've been moving files around before installing the
rebuilt kernel, but that doesn't sound very efficient ... :)
thanks ..
On Sat, 24 Mar 2001, John Baldwin wrote:
On 25-Mar-01 The Hermit Hacker wrote:
just upgraded my tree and did a reinstall ... trace is:
resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
resource_list_alloc+0xd3
isa_alloc_resource() @ +0xd0
bus_alloc_resource() @ +0x5f
opti_detect @ +0x99
This is the second such one I've seen in opti_detect. I'm guessing that 'mms'
is a sound driver? If so, can you try taking it out of your kernel to see if
that is what is causing the panic?
mss_detect @ +0x52
mss_probe @ +0x30a
device_probe_child @ +0xca
device_probe_and_attach @ +0x41
isa_probe_children @ +0xde
configure @ +0x32
mi_startup @ +0x6e
begin @ +0x29
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: panic: resource_list_alloc
removing pcm fixes the panic, it appears ...
On Sat, 24 Mar 2001, John Baldwin wrote:
On 25-Mar-01 The Hermit Hacker wrote:
just upgraded my tree and did a reinstall ... trace is:
resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
resource_list_alloc+0xd3
isa_alloc_resource() @ +0xd0
bus_alloc_resource() @ +0x5f
opti_detect @ +0x99
This is the second such one I've seen in opti_detect. I'm guessing that 'mms'
is a sound driver? If so, can you try taking it out of your kernel to see if
that is what is causing the panic?
mss_detect @ +0x52
mss_probe @ +0x30a
device_probe_child @ +0xca
device_probe_and_attach @ +0x41
isa_probe_children @ +0xde
configure @ +0x32
mi_startup @ +0x6e
begin @ +0x29
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
spin lock panic ...
Over the past few days, I reformatted my computer clean, installed
4.2-RELEASE onto her and just finished upgrading to the latest 5.x kernel
and world ... went to ports/x11/XFree86-4 and did a 'make install' ...
after awhile, it panic'd as below:
panic: spin lock sched lock held by 0xcb332840 for 5 seconds
cpuid = 1; lapic.id = 0100
Debugger("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Now, I do have DDB enabled in the kernel ... but, for the life of me, I
can't seem to find any docs on the keystroke required to drop into it :(
'man ddb' doesn't document it that I can find, nor does LINT ...
Thanks ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: spin lock panic ...
On Fri, 23 Mar 2001, Alfred Perlstein wrote: * The Hermit Hacker [EMAIL PROTECTED] [010323 16:09] wrote: Now, I do have DDB enabled in the kernel ... but, for the life of me, I can't seem to find any docs on the keystroke required to drop into it :( 'man ddb' doesn't document it that I can find, nor does LINT ... ctrl+alt+esc. perfect, thanks ... is this actually documented somewhere that I'm forgetting to look? :( To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: spin lock panic ...
On Fri, 23 Mar 2001, John Baldwin wrote:
On 24-Mar-01 The Hermit Hacker wrote:
Over the past few days, I reformatted my computer clean, installed
4.2-RELEASE onto her and just finished upgrading to the latest 5.x kernel
and world ... went to ports/x11/XFree86-4 and did a 'make install' ...
after awhile, it panic'd as below:
panic: spin lock sched lock held by 0xcb332840 for 5 seconds
cpuid = 1; lapic.id = 0100
Debugger("panic")
CPU1 stopping CPUs: 0x0001... stopped.
Now, I do have DDB enabled in the kernel ... but, for the life of me, I
can't seem to find any docs on the keystroke required to drop into it :(
'man ddb' doesn't document it that I can find, nor does LINT ...
Uhh, if it panic'd, it should already be in ddb at a db prompt assuming you
have DDB in your kernel.
didn't ... last line was as above ... I've even tested my DDB to make sure
I can get to the db prompt after alfred reminded me of the ctl-alt-esc to
get there, and it works ...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
BP6 motherboard and hangs ...
Anyone have any experience with the Abit BP6 motherboards? I've been
reporting and talking about problems with -CURRENT the past little while,
where when I start X, it pretty much dies soon after ... well, this
weekend, I needed to make my system Dual-BOOT into W2K Professional Server
for some work I'm doing (installing FreeBSD in vmware over w2k to run some
server software) and W2K hangs solid also ...
I'm starting to wonder if its a motherboard problem and has nothing to do
with OS ...
Anyone with experience here?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: More on system hangs ... IRQ related?
On Sun, 4 Mar 2001, The Hermit Hacker wrote:
On Sun, 4 Mar 2001, John Baldwin wrote:
On 04-Mar-01 The Hermit Hacker wrote:
On Sun, 4 Mar 2001, Alex Zepeda wrote:
On Sun, Mar 04, 2001 at 03:18:39PM -0400, The Hermit Hacker wrote:
My sound card overlaps with fxp0, and fxp1 overlaps with the
HighPoint controller ...
Grasping at straws here ...
Ditch the HPT366, it's crap and will cause system instabilities with
"fast" hard drives. I'm not sure what you have attached to it, but I've
had problems with {either,both} an IBM ATA100 HDD and a Western Digital
ATA66 drive attached. Apparently the ATA100 counterpart from HighPoint
isn't so bad.
Okay, everything in my box is SCSI, so I'm not suspecting the HPT... its
more the pcm fxp that I'm thinking ...
how does the OS handle having both devices hit simultaneously on the same
IRQ?
The IRQ fires and is masked. We then run both handlers, one after the other,
and when they have finished re-enable the IRQ.
Okay, are there any known problems with the SB128 cards? Figuring that it
couldn't hurt to remove it, I did ... so far, X hasn't hung ... not
conclusive yet, am going to let it run over night, with KDE2 compiling in
the background, and see if its still runnin in the morning ... if it is,
will try putting the SB128 back in and seeing if it once more causes it to
hang ...
But, so far, so good *cross fingers*
Of course, as everyone knew (and I wished against unsuccessfully), it
still hung :(
Ah well, will re-tackle it when I get back from SF, even if it means
leaving it overnight ...
One question ... yesterday, when I did leave it running, and came back to
my computer, my xterm that I had kermit running in was full of "binary
data" ... you know, the hieroglyphics? I just started up a new
xterm/kermit to reset it, but if it hangs in that state, I'm definitely
not going to have anything to show anyone ... is there any reason why
there are binary codes (if I want it scroll, I can see the occasional
'diamond' popping up on the screen, and hear the occasional bell) in that
output, and any way of suppressing them?
Thanks ...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: Using serial console to debug system hangs ...
On Sun, 4 Mar 2001, John Baldwin wrote: On 04-Mar-01 The Hermit Hacker wrote: On Sat, 3 Mar 2001, John Baldwin wrote: On 04-Mar-01 The Hermit Hacker wrote: Wow, that was painful ... after 2 hrs, I got as far as: Yeah, it spews out a lot of crap. :-/ You prolly want to use a 115200 serial console if at all possible. Should've mentioned that earlier.. Okay, reading NOTES, it says that 9600 is the default ... does that mean I should be able to attach at 115200 and it should auto-upgrade, or do I have to recompile kernel iwth CONSPEED=115200 for this? Either recompile or use the loader tunable 'machdep.conspeed' I think. However, you'll probably want the bootstrap to work on teh serial console as well, in which case you need to set the speed in make.conf (see /etc/defaults/make.conf) and recompile and reinstall boot2 and the loader. Okay, now you are going beyond my experiences :( First, I changed CONSPEED to 115200, but sysctl is still registering 9600: thelab# sysctl machdep.conspeed machdep.conspeed: 9600 manually doing 'sysctl -w machdep.conspeed=115200' appears to work though ... But, after modifying my make.conf, what do I have to recompile? Are we just talking a rebuild and install of the kernel itself? I'm going to try that ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
More on system hangs ... IRQ related?
Morning ...
I'm having a bugger of a time getting anywhere with the KTR stuff,
for, as soon as I enable it, the system slows down so badly that I can't
get into X to hang it ...
Figure that I'd try killing off *everything* not required (named,
ethernet interfaces, etc), so that there was less happening, I started up
X ... wouldn't hang.
Rebooted the machine, so that everything was running 'as per
normal', and started X ... dead in no time.
Looking at the IRQs that my machine is running with, according to
dmesg, I notice a few 'overlaps', and wonder if that could be the cause?
dmesg | grep irq
IOAPIC #0 intpin 2 - irq 0
IOAPIC #0 intpin 19 - irq 2
IOAPIC #0 intpin 18 - irq 10
IOAPIC #0 intpin 17 - irq 11
IOAPIC #0 intpin 16 - irq 12
ata0: at 0x1f0 irq 14 on atapci0
ahc0: Adaptec 2940 Ultra SCSI adapter port 0xcc00-0xccff mem 0xf020-0xf0200fff
irq 11 at device 13.0 on pci0
pcm0: AudioPCI ES1370 port 0xd000-0xd03f irq 2 at device 17.0 on pci0
atapci1: HighPoint HPT366 ATA66 controller port
0xdc00-0xdcff,0xd800-0xd803,0xd400-0xd407 irq 10 at device 19.0 on pci0
atapci2: HighPoint HPT366 ATA66 controller port
0xe800-0xe8ff,0xe400-0xe403,0xe000-0xe007 irq 10 at device 19.1 on pci0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio1 at port 0x2f8-0x2ff irq 3 on isa0
fxp0: Intel Pro 10/100B/100+ Ethernet port 0xc400-0xc43f mem
0xf010-0xf01f,0xf0201000-0xf0201fff irq 2 at device 9.0 on pci0
fxp1: Intel Pro 10/100B/100+ Ethernet port 0xc800-0xc83f mem
0xf000-0xf00f,0xf0202000-0xf0202fff irq 10 at device 11.0 on pci0
My sound card overlaps with fxp0, and fxp1 overlaps with the
HighPoint controller ...
Grasping at straws here ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: Using serial console to debug system hangs ...
On Sun, 4 Mar 2001, Manfred Antar wrote: You have to recompile the boot stuff also, after changing the line in make.conf: # The default serial console speed is 9600. Set the speed to a larger value # for better interactive response. # BOOT_COMCONSOLE_SPEED= 57600 Then cd /sys/boot ; make depend all install. I forget if you then need to relabel the disk or not. ie : disklabel -B da0 this worked great, thanks ...disklabel wasn't required, it appears ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Using serial console to debug system hangs ...
On Sat, 3 Mar 2001, John Baldwin wrote: On 04-Mar-01 The Hermit Hacker wrote: Wow, that was painful ... after 2 hrs, I got as far as: Yeah, it spews out a lot of crap. :-/ You prolly want to use a 115200 serial console if at all possible. Should've mentioned that earlier.. Okay, I'm up to 115200, still a lot of crap ;) Any lower mask I can set things at to get enough info, without so much flowing up the screen? I can understand why she's so unresponsive, just wondering if there is a way of reducing the amount of debugging without losing too much ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More on system hangs ... IRQ related?
On Sun, 4 Mar 2001, John Baldwin wrote:
On 04-Mar-01 The Hermit Hacker wrote:
On Sun, 4 Mar 2001, Alex Zepeda wrote:
On Sun, Mar 04, 2001 at 03:18:39PM -0400, The Hermit Hacker wrote:
My sound card overlaps with fxp0, and fxp1 overlaps with the
HighPoint controller ...
Grasping at straws here ...
Ditch the HPT366, it's crap and will cause system instabilities with
"fast" hard drives. I'm not sure what you have attached to it, but I've
had problems with {either,both} an IBM ATA100 HDD and a Western Digital
ATA66 drive attached. Apparently the ATA100 counterpart from HighPoint
isn't so bad.
Okay, everything in my box is SCSI, so I'm not suspecting the HPT... its
more the pcm fxp that I'm thinking ...
how does the OS handle having both devices hit simultaneously on the same
IRQ?
The IRQ fires and is masked. We then run both handlers, one after the other,
and when they have finished re-enable the IRQ.
Okay, are there any known problems with the SB128 cards? Figuring that it
couldn't hurt to remove it, I did ... so far, X hasn't hung ... not
conclusive yet, am going to let it run over night, with KDE2 compiling in
the background, and see if its still runnin in the morning ... if it is,
will try putting the SB128 back in and seeing if it once more causes it to
hang ...
But, so far, so good *cross fingers*
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Problem with sio in -current ... possible cause of hangs?
Morning all ...
I'm trying to get my serial console to work on my desktop, and
appear to be failing miserably at even just getting it to accept a 'getty'
serial connection, let alone serial console ...
First, my X/mouse runs on /dev/ttyd1 ... if I startx, my mouse
does work, but X hangs *very* quickly. Based on this, I know that
/dev/ttyd1 does work, at least for a short time.
Now, to confirm ... a NULL modem cable *is* pin 2-3, 3-2, right?
rx-tx, tx-rx? I've tested the cable using a multi-meter, just to make
sure that it is doing what I expect ...
If I plug my cable from /dev/ttyd0 - /dev/ttyd1 on the same
machine, run getty on /dev/ttyd1 and use kermit to connect to /dev/cuaa0,
I get no response back, which is why I'm wondering about sio ...
I've also tried connecting my serial port on my laptop to both
/dev/ttyd0 and /dev/ttyd1, and run getty, and that doesn't get any login
prompt either ...
Since, albeit briefly, I know that /dev/ttyd1 does work when X
starts up, I'd expect that getty would give me a login prompt if I enabled
it on that port, no?
I'm running -CURRENT as of Feb 27th, and am just about to upgrade
again ... dmesg shows my sio devices as:
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
Which look right to me ...
I've scan'd /usr/src/UPGRADING to see if there was something in
the past that I might have missed concerning sio, but couldn't find
anything ...
And, sio is defined in my kernel as simple 'device sio' ...
Thoughts?
Thanks ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: Problem with sio in -current ... possible cause of hangs?
Woo hoo ... got the serial console working ... I had put -D into
/boot.config, vs -P ...
... neat ... I got all the boot info on my serial console, then the login
prompt went to the main screen, and no control on either one ...
is that supposed to happen?
On Sat, 3 Mar 2001, John Baldwin wrote:
On 03-Mar-01 The Hermit Hacker wrote:
Morning all ...
I'm trying to get my serial console to work on my desktop, and
appear to be failing miserably at even just getting it to accept a 'getty'
serial connection, let alone serial console ...
First, my X/mouse runs on /dev/ttyd1 ... if I startx, my mouse
does work, but X hangs *very* quickly. Based on this, I know that
/dev/ttyd1 does work, at least for a short time.
Now, to confirm ... a NULL modem cable *is* pin 2-3, 3-2, right?
rx-tx, tx-rx? I've tested the cable using a multi-meter, just to make
sure that it is doing what I expect ...
If I plug my cable from /dev/ttyd0 - /dev/ttyd1 on the same
machine, run getty on /dev/ttyd1 and use kermit to connect to /dev/cuaa0,
I get no response back, which is why I'm wondering about sio ...
Try turning clocal off on the host and port you are running kermit on. Even
then, I still have yet to get getty to work at all, it's always stuck in
'siodcd'. I've noticed via debugging output that the DCD change bit does raise
for a read, but that teh DCD status bit stays at zero the entire time. The
sio driver seems to ignore the change bit and only read the status bit, so it
thinks DCD is never raised and hangs forever on open. Note that I can get a
getty fine on a serial console, just not on a /dev/ttydX that's not also the
serial console. :( I've had this problem since before PRE_SMPNG however.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Using serial console to debug system hangs ...
Well, after some hurdles with getting the serial console to work, I've now
go it to work ... I put the two sysctl commands into a file so that I
could run it as a script:
#!/bin/sh
sysctl -w debug.ktr.mask=0x1208
sysctl -w debug.ktr.verbose=2
When I 'try' to run it, I get all the 'KTR'(?) messages on my serial
console, something is changing/happening so fast that my ssh connection
into the machine hangs before I finish typing in the shell script:
enable_kernel_debug: 3 lines, 72 characters.
thelab# !./
needless to say, running the command to hang the computer is proving
difficult :)
Then again, if I do a cold boot of the machine, the messages stop
scrolling up the console, but a cut-n-paste of them is sort of illegible:
k0clo.c/k...c/.k4e3r8n /RkEeLr n(_scplionc)k .scch2e0d9 lRoEcLk (s[p0xicn0)
32c1al1l8o0]ut r[=00x ca0t 31.d./8.2.0/] ker=r0n/ akte r.n._c/l.o./ckk.ecrn:4/k3e8r
e_cpluo1c k..c/:.2.0/9k
rcnp/uk0e r.n./.l.o/ckke.rcn./3k5e0r nG_OcTl o(cskp.icn.)2 0s3c hGeOdT
l(oscpki n[)0 xccall2o1u1t8 0[]0 xrc=003 1adt8 2.0.]/ ..0/k aertn
./.k/er..n_/ckllorcnk/.kecr:n35_0c
.ok.uc1: 2.0.3/
.c/pkue0r.n/.k/.er./n_kcelrnoc/kke.crn.4_c38l ocRkEL. c(.s2p09in )R ELs ch(sepd
iln)oc kc al[0loxuct03 [210x18c003] 1rd=802 0a] t r=..0/ a..t
/.k.er/.n./.ckerenrn_c/lkoerckn_.ccl:4oc3k8
:20u91
.c.p/u.0. /.k.e/r.n.//kkeerrnn_/ckleorcnk_.ccl.o3c5k0. cG.O2T0 3( sGpOiTn )(
sspcihne)d claolclko u[t0 x[c00x3213118d08]2 0r]= 0r =a0t a.t.
///.k.e/0ke/rkne/rkne_rcnl_occlko.cck:.3c5:02
p3c
uc1p u.0. ///.k.e/rkne/rkne/rkne_rcnl_occlko.cck..4c3.82 RE LR E(Ls
p(isnp)i ns)c hceadl lloouctk [[00xxcc003312d1812800]] rr==00 aatt
////kkeerrnn//kkeerrnn__cclloocckk..cc::24398
ccppuu01 ////kkeerrnn//kkeerrnn__cclloocckk..cc..230530 GGOOTT
((ssppiinn)) csaclhleodu tl o[c0kx c[003x1cd0832201]1 8r0=]0 ra=t0 .a.t
then again, looking at it, it looks like everything is going in duplicates?
suggestions?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: Using serial console to debug system hangs ...
Wow, that was painful ... after 2 hrs, I got as far as:
thelab# ./enable_debug
debug.ktr.mask: 1 - 4608
debug.ktr.verbose: 0 - 2
waiting for X server to begin accepting connections .
XFree86 Version 4.0.2 / X Window System
(protocol Version 11, revision 0, vendor release 6400)
Release Date: 18 December 2000
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems. (See http://www.XFree86.Org/FAQ)
Operating System: FreeBSD 5.0-CURRENT i386 [ELF]
Module Loader present
(==) Log file: "/var/log/XFree86.0.log", Time: Sat Mar 3 22:08:37 2001
(==) Using config file: "/root/XF86Config"
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (??) unknown.
(==) ServerLayout "Simple Layout"
(**) |--Screen "Screen 1" (0)
(**) | |--Monitor "Samtron 95P"
(**) | |--Device "TNT"
(**) |--Input Device "Mouse1"
(**) |--Input Device "Keyboard1"
(**) XKB: rules: "xfree86"
(**) XKB: model: "microsoft"
(**) XKB: layout: "us"
(**) FontPath set to
"/usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(--) Using syscons driver with X support (version 2.0)
and gave up ... am going to try again just before I go to bed tonight,
hopefully its running (and hung) by the time I get up in the morning ;)
On Sat, 3 Mar 2001, John Baldwin wrote:
On 04-Mar-01 The Hermit Hacker wrote:
Well, after some hurdles with getting the serial console to work, I've now
go it to work ... I put the two sysctl commands into a file so that I
could run it as a script:
#!/bin/sh
sysctl -w debug.ktr.mask=0x1208
sysctl -w debug.ktr.verbose=2
When I 'try' to run it, I get all the 'KTR'(?) messages on my serial
console, something is changing/happening so fast that my ssh connection
into the machine hangs before I finish typing in the shell script:
enable_kernel_debug: 3 lines, 72 characters.
thelab# !./
Put the sysctl's and the command that hangs the machine into one script and run
that one shell script..
needless to say, running the command to hang the computer is proving
difficult :)
Then again, if I do a cold boot of the machine, the messages stop
scrolling up the console, but a cut-n-paste of them is sort of illegible:
k0clo.c/k...c/.k4e3r8n /RkEeLr n(_scplionc)k .scch2e0d9 lRoEcLk
(s[p0xicn0) 32c1al1l8o0]ut r[=00x ca0t 31.d./8.2.0/] ker=r0n/ akte
r.n._c/l.o./ckk.ecrn:4/k3e8r
e_cpluo1c k..c/:.2.0/9k
rcnp/uk0e r.n./.l.o/ckke.rcn./3k5e0r nG_OcTl o(cskp.icn.)2 0s3c
hGeOdT l(oscpki n[)0 xccall2o1u1t8 0[]0 xrc=003 1adt8 2.0.]/ ..0/k aertn
./.k/er..n_/ckllorcnk/.kecr:n35_0c
.ok.uc1: 2.0.3/
.c/pkue0r.n/.k/.er./n_kcelrnoc/kke.crn.4_c38l ocRkEL. c(.s2p09in )R
ELs ch(sepd iln)oc kc al[0loxuct03 [210x18c003] 1rd=802 0a] t r=..0/ a..t
/.k.er/.n./.ckerenrn_c/lkoerckn_.ccl:4oc3k8
:20u91
.c.p/u.0. /.k.e/r.n.//kkeerrnn_/ckleorcnk_.ccl.o3c5k0. cG.O2T0 3(
sGpOiTn )( sspcihne)d claolclko u[t0 x[c00x3213118d08]2 0r]= 0r =a0t a.t.
///.k.e/0ke/rkne/rkne_rcnl_occlko.cck:.3c5:02
p3c
uc1p u.0. ///.k.e/rkne/rkne/rkne_rcnl_occlko.cck..4c3.82 RE LR
E(Ls p(isnp)i ns)c hceadl lloouctk [[00xxcc003312d1812800]] rr==00 aatt
////kkeerrnn//kkeerrnn__cclloocckk..cc::24398
ccppuu01 ////kkeerrnn//kkeerrnn__cclloocckk..cc..230530
GGOOTT ((ssppiinn)) csaclhleodu tl o[c0kx c[003x1cd0832201]1 8r0=]0 ra=t0
.a.t
Hmm, it's colliding with itself a lot. Unfortunately, to make this useful over
the serial console, you need to shut up all the sio lock messages. Hmmm, well
for now try just using a 'debug.ktr.mask' of 0x1200 to skip all the mutex
operations. If we need them later on, then I will try and get some other work
done to make it easier to shut up certain mutexes in the log output without
having to change each individual mutex operation.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: System hangs with -current ...
On Thu, 1 Mar 2001, John Baldwin wrote: On 01-Mar-01 The Hermit Hacker wrote: any comments on this? any way of doing this without a serial console? thanks ... The data is too much to make a normal console feasible, although you could try cranking up the console to hte highest res (80x60 or 132x60, etc.) you can and let it freeze and then write down those 60 lines adn maybe that will be enough to figure it out. However, if its looping this won't work. :( I've no idea atm why the serial console isn't working for you. Inability to actually find a NULL modem cable, actually :( Checked two local shops, and neither of them carry one ... just hijacked one from work for the weekend, so will hit this tonight and report anything I can come up with ... On Wed, 28 Feb 2001, The Hermit Hacker wrote: Yup, definitely doesn't like me using the console ... just tried it again, and its as if it can't scroll up the screen to send more data or something? I just rebooted, and then ssh'd in from remote ... type'd the two sysctl commands, and got: cpu1 ../../i386/i386/trap.c.181 GOT (spin) sched lock [0xc0320f20] r=0 at ../../i386/i386/trap.c:181 cpcsocp/../i386/i386/trap.c.217 REL (spin) sched l on my screen ... type'd exactly as seen ... and that's it ... console is now locked again ... On Tue, 27 Feb 2001, The Hermit Hacker wrote: Okay, can't seem to find a 9pin-9pin NULL modem cable in this 'pit of the earth' town, so figured I'd do the sysctl commands on my console and use an ssh connection into the machine to run the 'hanging sequence' ... the console flashed a bunch of 'debugging info' and then hung solid ... I could still login remotely and whatnot, type commands, just nothing was happening on the console, couldn't change vty's, nothing ... is it supposed to do that? *raised eyebrow* On Thu, 22 Feb 2001, John Baldwin wrote: On 23-Feb-01 The Hermit Hacker wrote: On Thu, 22 Feb 2001, John Baldwin wrote: On 22-Feb-01 The Hermit Hacker wrote: Okay, I have to pick up a NULL modem cable tomorrow and dive into this ... finally ... The various KTR_ that you mention below, these are kernel settings that I compile into the kernel? Yes. You want this: options KTR options KTR_EXTEND options KTR_COMPILE=0x1208 okay, just so that I understand ... I compile my kernel with these options, and then run the two sysctl commands you list below? the KTR_COMPILE arg looks similar to the ktr_mask one below, which is why I'm confirming ... Yes. KTR_COMPILE controls what KTR tracepoints are actually compiled into the kernel. The ktr_mask sysctl controls a runtime mask that lets you choose which of the compiled in masks you want to enable. I have manpages for this stuff, but they are waiting for doc guys to review them. The mtx_quiet.patch is old and won't apply to current now I'm afraid. On Tue, 2 Jan 2001, John Baldwin wrote: On 02-Jan-01 The Hermit Hacker wrote: Over the past several months, as others have reported, I've been getting system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but ctl-alt-esc doesn't break me to the debugger ... I'm not complaining about the hangs, if I was overly concerned, I'd run -STABLE, but I'm wondering how one goes about providing debug information on them other then through DDB? Not easily. :( If you can make the problem easily repeatable, then you can try turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND), setting up a serial console that you log the output of, create a shell script that runs the following commands: #!/bin/sh # Turn on KTR_INTR, KTR_PROC, and KTR_LOCK sysctl -w debug.ktr_mask=0x1208 sysctl -w debug.ktr_verbose=2 run_magic_command_that_hangs_my_machine and run the script. You probably want to run it over a tty or remote login so tthat the serial console output is just the logging (warning, it will be very verbose!). Also, you probably want to use http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of the irrelevant and cluttery mutex trace messages. Note that having this much logging on will probably slow the machine to a crawl as well, so you may have to just start this up and go off and do something else until it hangs. :-/ Another alternative is to rig up a NMI debouncer and use it to break into the debugger. Then you can start poking around to see who owns
RE: System hangs with -current ...
any comments on this? any way of doing this without a serial console?
thanks ...
On Wed, 28 Feb 2001, The Hermit Hacker wrote:
Yup, definitely doesn't like me using the console ... just tried it again,
and its as if it can't scroll up the screen to send more data or
something?
I just rebooted, and then ssh'd in from remote ... type'd the two sysctl
commands, and got:
cpu1 ../../i386/i386/trap.c.181 GOT (spin) sched lock [0xc0320f20] r=0 at
../../i386/i386/trap.c:181
cpcsocp/../i386/i386/trap.c.217 REL (spin) sched l
on my screen ... type'd exactly as seen ... and that's it ... console is
now locked again ...
On Tue, 27 Feb 2001, The Hermit Hacker wrote:
Okay, can't seem to find a 9pin-9pin NULL modem cable in this 'pit of the
earth' town, so figured I'd do the sysctl commands on my console and use
an ssh connection into the machine to run the 'hanging sequence' ... the
console flashed a bunch of 'debugging info' and then hung solid ... I
could still login remotely and whatnot, type commands, just nothing was
happening on the console, couldn't change vty's, nothing ...
is it supposed to do that? *raised eyebrow*
On Thu, 22 Feb 2001, John Baldwin wrote:
On 23-Feb-01 The Hermit Hacker wrote:
On Thu, 22 Feb 2001, John Baldwin wrote:
On 22-Feb-01 The Hermit Hacker wrote:
Okay, I have to pick up a NULL modem cable tomorrow and dive into this ...
finally ...
The various KTR_ that you mention below, these are kernel settings that I
compile into the kernel?
Yes. You want this:
options KTR
options KTR_EXTEND
options KTR_COMPILE=0x1208
okay, just so that I understand ... I compile my kernel with these
options, and then run the two sysctl commands you list below? the
KTR_COMPILE arg looks similar to the ktr_mask one below, which is why I'm
confirming ...
Yes. KTR_COMPILE controls what KTR tracepoints are actually compiled into
the kernel. The ktr_mask sysctl controls a runtime mask that lets you choose
which of the compiled in masks you want to enable. I have manpages for this
stuff, but they are waiting for doc guys to review them.
The mtx_quiet.patch is old and won't apply to current now I'm afraid.
On Tue, 2 Jan 2001, John Baldwin wrote:
On 02-Jan-01 The Hermit Hacker wrote:
Over the past several months, as others have reported, I've been
getting
system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but
ctl-alt-esc doesn't break me to the debugger ...
I'm not complaining about the hangs, if I was overly concerned, I'd run
-STABLE, but I'm wondering how one goes about providing debug
information
on them other then through DDB?
Not easily. :( If you can make the problem easily repeatable, then you
can
try
turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND),
setting
up
a serial console that you log the output of, create a shell script that
runs
the following commands:
#!/bin/sh
# Turn on KTR_INTR, KTR_PROC, and KTR_LOCK
sysctl -w debug.ktr_mask=0x1208
sysctl -w debug.ktr_verbose=2
run_magic_command_that_hangs_my_machine
and run the script. You probably want to run it over a tty or remote
login
so
tthat the serial console output is just the logging (warning, it will be
very
verbose!). Also, you probably want to use
http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of
the
irrelevant and cluttery mutex trace messages. Note that having this much
logging on will probably slow the machine to a crawl as well, so you may
have
to just start this up and go off and do something else until it hangs.
:-/
Another alternative is to rig up a NMI debouncer and use it to break into
the
debugger. Then you can start poking around to see who owns sched_lock,
etc.
Thanks ...
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G.
RE: System hangs with -current ...
Okay, can't seem to find a 9pin-9pin NULL modem cable in this 'pit of the
earth' town, so figured I'd do the sysctl commands on my console and use
an ssh connection into the machine to run the 'hanging sequence' ... the
console flashed a bunch of 'debugging info' and then hung solid ... I
could still login remotely and whatnot, type commands, just nothing was
happening on the console, couldn't change vty's, nothing ...
is it supposed to do that? *raised eyebrow*
On Thu, 22 Feb 2001, John Baldwin wrote:
On 23-Feb-01 The Hermit Hacker wrote:
On Thu, 22 Feb 2001, John Baldwin wrote:
On 22-Feb-01 The Hermit Hacker wrote:
Okay, I have to pick up a NULL modem cable tomorrow and dive into this ...
finally ...
The various KTR_ that you mention below, these are kernel settings that I
compile into the kernel?
Yes. You want this:
options KTR
options KTR_EXTEND
options KTR_COMPILE=0x1208
okay, just so that I understand ... I compile my kernel with these
options, and then run the two sysctl commands you list below? the
KTR_COMPILE arg looks similar to the ktr_mask one below, which is why I'm
confirming ...
Yes. KTR_COMPILE controls what KTR tracepoints are actually compiled into
the kernel. The ktr_mask sysctl controls a runtime mask that lets you choose
which of the compiled in masks you want to enable. I have manpages for this
stuff, but they are waiting for doc guys to review them.
The mtx_quiet.patch is old and won't apply to current now I'm afraid.
On Tue, 2 Jan 2001, John Baldwin wrote:
On 02-Jan-01 The Hermit Hacker wrote:
Over the past several months, as others have reported, I've been
getting
system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but
ctl-alt-esc doesn't break me to the debugger ...
I'm not complaining about the hangs, if I was overly concerned, I'd run
-STABLE, but I'm wondering how one goes about providing debug
information
on them other then through DDB?
Not easily. :( If you can make the problem easily repeatable, then you
can
try
turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND),
setting
up
a serial console that you log the output of, create a shell script that
runs
the following commands:
#!/bin/sh
# Turn on KTR_INTR, KTR_PROC, and KTR_LOCK
sysctl -w debug.ktr_mask=0x1208
sysctl -w debug.ktr_verbose=2
run_magic_command_that_hangs_my_machine
and run the script. You probably want to run it over a tty or remote
login
so
tthat the serial console output is just the logging (warning, it will be
very
verbose!). Also, you probably want to use
http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of
the
irrelevant and cluttery mutex trace messages. Note that having this much
logging on will probably slow the machine to a crawl as well, so you may
have
to just start this up and go off and do something else until it hangs.
:-/
Another alternative is to rig up a NMI debouncer and use it to break into
the
debugger. Then you can start poking around to see who owns sched_lock,
etc.
Thanks ...
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: System hangs with -current ...
Yup, definitely doesn't like me using the console ... just tried it again,
and its as if it can't scroll up the screen to send more data or
something?
I just rebooted, and then ssh'd in from remote ... type'd the two sysctl
commands, and got:
cpu1 ../../i386/i386/trap.c.181 GOT (spin) sched lock [0xc0320f20] r=0 at
../../i386/i386/trap.c:181
cpcsocp/../i386/i386/trap.c.217 REL (spin) sched l
on my screen ... type'd exactly as seen ... and that's it ... console is
now locked again ...
On Tue, 27 Feb 2001, The Hermit Hacker wrote:
Okay, can't seem to find a 9pin-9pin NULL modem cable in this 'pit of the
earth' town, so figured I'd do the sysctl commands on my console and use
an ssh connection into the machine to run the 'hanging sequence' ... the
console flashed a bunch of 'debugging info' and then hung solid ... I
could still login remotely and whatnot, type commands, just nothing was
happening on the console, couldn't change vty's, nothing ...
is it supposed to do that? *raised eyebrow*
On Thu, 22 Feb 2001, John Baldwin wrote:
On 23-Feb-01 The Hermit Hacker wrote:
On Thu, 22 Feb 2001, John Baldwin wrote:
On 22-Feb-01 The Hermit Hacker wrote:
Okay, I have to pick up a NULL modem cable tomorrow and dive into this ...
finally ...
The various KTR_ that you mention below, these are kernel settings that I
compile into the kernel?
Yes. You want this:
options KTR
options KTR_EXTEND
options KTR_COMPILE=0x1208
okay, just so that I understand ... I compile my kernel with these
options, and then run the two sysctl commands you list below? the
KTR_COMPILE arg looks similar to the ktr_mask one below, which is why I'm
confirming ...
Yes. KTR_COMPILE controls what KTR tracepoints are actually compiled into
the kernel. The ktr_mask sysctl controls a runtime mask that lets you choose
which of the compiled in masks you want to enable. I have manpages for this
stuff, but they are waiting for doc guys to review them.
The mtx_quiet.patch is old and won't apply to current now I'm afraid.
On Tue, 2 Jan 2001, John Baldwin wrote:
On 02-Jan-01 The Hermit Hacker wrote:
Over the past several months, as others have reported, I've been
getting
system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but
ctl-alt-esc doesn't break me to the debugger ...
I'm not complaining about the hangs, if I was overly concerned, I'd run
-STABLE, but I'm wondering how one goes about providing debug
information
on them other then through DDB?
Not easily. :( If you can make the problem easily repeatable, then you
can
try
turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND),
setting
up
a serial console that you log the output of, create a shell script that
runs
the following commands:
#!/bin/sh
# Turn on KTR_INTR, KTR_PROC, and KTR_LOCK
sysctl -w debug.ktr_mask=0x1208
sysctl -w debug.ktr_verbose=2
run_magic_command_that_hangs_my_machine
and run the script. You probably want to run it over a tty or remote
login
so
tthat the serial console output is just the logging (warning, it will be
very
verbose!). Also, you probably want to use
http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of
the
irrelevant and cluttery mutex trace messages. Note that having this much
logging on will probably slow the machine to a crawl as well, so you may
have
to just start this up and go off and do something else until it hangs.
:-/
Another alternative is to rig up a NMI debouncer and use it to break into
the
debugger. Then you can start poking around to see who owns sched_lock,
etc.
Thanks ...
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: System hangs with -current ...
Okay, I have to pick up a NULL modem cable tomorrow and dive into this ...
finally ...
The various KTR_ that you mention below, these are kernel settings that I
compile into the kernel?
On Tue, 2 Jan 2001, John Baldwin wrote:
On 02-Jan-01 The Hermit Hacker wrote:
Over the past several months, as others have reported, I've been getting
system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but
ctl-alt-esc doesn't break me to the debugger ...
I'm not complaining about the hangs, if I was overly concerned, I'd run
-STABLE, but I'm wondering how one goes about providing debug information
on them other then through DDB?
Not easily. :( If you can make the problem easily repeatable, then you can try
turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND), setting up
a serial console that you log the output of, create a shell script that runs
the following commands:
#!/bin/sh
# Turn on KTR_INTR, KTR_PROC, and KTR_LOCK
sysctl -w debug.ktr_mask=0x1208
sysctl -w debug.ktr_verbose=2
run_magic_command_that_hangs_my_machine
and run the script. You probably want to run it over a tty or remote login so
tthat the serial console output is just the logging (warning, it will be very
verbose!). Also, you probably want to use
http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of the
irrelevant and cluttery mutex trace messages. Note that having this much
logging on will probably slow the machine to a crawl as well, so you may have
to just start this up and go off and do something else until it hangs. :-/
Another alternative is to rig up a NMI debouncer and use it to break into the
debugger. Then you can start poking around to see who owns sched_lock, etc.
Thanks ...
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: System hangs with -current ...
On Thu, 22 Feb 2001, John Baldwin wrote:
On 22-Feb-01 The Hermit Hacker wrote:
Okay, I have to pick up a NULL modem cable tomorrow and dive into this ...
finally ...
The various KTR_ that you mention below, these are kernel settings that I
compile into the kernel?
Yes. You want this:
options KTR
options KTR_EXTEND
options KTR_COMPILE=0x1208
okay, just so that I understand ... I compile my kernel with these
options, and then run the two sysctl commands you list below? the
KTR_COMPILE arg looks similar to the ktr_mask one below, which is why I'm
confirming ...
The mtx_quiet.patch is old and won't apply to current now I'm afraid.
On Tue, 2 Jan 2001, John Baldwin wrote:
On 02-Jan-01 The Hermit Hacker wrote:
Over the past several months, as others have reported, I've been getting
system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but
ctl-alt-esc doesn't break me to the debugger ...
I'm not complaining about the hangs, if I was overly concerned, I'd run
-STABLE, but I'm wondering how one goes about providing debug information
on them other then through DDB?
Not easily. :( If you can make the problem easily repeatable, then you can
try
turning on KTR in your kernel (see NOTES, you will need KTR_EXTEND), setting
up
a serial console that you log the output of, create a shell script that runs
the following commands:
#!/bin/sh
# Turn on KTR_INTR, KTR_PROC, and KTR_LOCK
sysctl -w debug.ktr_mask=0x1208
sysctl -w debug.ktr_verbose=2
run_magic_command_that_hangs_my_machine
and run the script. You probably want to run it over a tty or remote login
so
tthat the serial console output is just the logging (warning, it will be
very
verbose!). Also, you probably want to use
http://www.FreeBSD.org/~jhb/patches/mtx_quiet.patch to shut up most of the
irrelevant and cluttery mutex trace messages. Note that having this much
logging on will probably slow the machine to a crawl as well, so you may
have
to just start this up and go off and do something else until it hangs. :-/
Another alternative is to rig up a NMI debouncer and use it to break into
the
debugger. Then you can start poking around to see who owns sched_lock, etc.
Thanks ...
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary:
scrappy@{freebsd|postgresql}.org
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
proper kernel config procedure ...
it u sed to be that one would do 'config -r file' to config a kernel, so
that it removed the old /sys/compile/file directory ... -r was removed,
so is it no longer required to remove the old directory before building
the new kernel, or ... ?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: startx/startkde hangs -CURRENT ...
On Sat, 17 Feb 2001, Alex Zepeda wrote: Now, if I start X, the whole machine hangs solid ... Where? By all means, set KDE_DEBUG, and capture the startx output, and do something with the coredumps so that you encode the pid into the file name, since many kde crashes will be in kdeinit (since it's used to launch programs via shlibs).. actually, after a reboot, I figured I'd do a 'make -j3 buildworld' to see what happens there, without X started, and the whole system hangs that way too ... so, we're in the clear for X/KDE right now ... Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
I just got hurt by this, in a sense ... buildworld and installworld all
worked great, but as soon as I tried to a 'startx', it told me that
libm.so.2 had an unresolved symbol __sF ... I just rebuilt my X, figure
just the result of the bump in libm.so.n major ...
On Sat, 17 Feb 2001, Manfred Antar wrote:
At 03:36 PM 2/17/2001 -0800, Matthew Jacob wrote:
One system got stuck in the current __sF bork... I'm not stuck with:
cc -o make_hash -O -pipe -I. -I/usr/src/lib/libncurses
-I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses
-I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE
-DNDEBUG -DHAVE_CONFIG_H -DTERMIOS -DMAIN_PROGRAM
/usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/comp_hash.c
/usr/lib/libgcc.so: undefined reference to `__sF'
*** Error code 1
Stop in /usr/src/lib/libncurses.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
Any advice?
What is the date of your system (libc) ? Before Feb 10 or between the 10th and the
16th ?
If before Feb 10 I would resup , remove /usr/obj and try again.
If in the period between the 10th and 16th , you might need to restore from tape or
other means
then try again.I just did a make world from a system from the 10th and current src
and it built fine
Manfred
==
|| [EMAIL PROTECTED] ||
|| Ph. (415) 681-6235 ||
==
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
On Sat, 17 Feb 2001, Manfred Antar wrote:
At 08:17 PM 2/17/2001 -0400, The Hermit Hacker wrote:
I just got hurt by this, in a sense ... buildworld and installworld all
worked great, but as soon as I tried to a 'startx', it told me that
libm.so.2 had an unresolved symbol __sF ... I just rebuilt my X, figure
just the result of the bump in libm.so.n major ...
I don't think any of the libs were bumped recently except for libc and
that was backed out. There was a patch posted that bumped some of the
libs but that was withdrawn. I think you might have libs built from
some of the stuff that was backed or not a totally current source. I'm
using X compiled on the 8th of Feb with a current world as of 2 hours
ago and no problem
Okay, I did a cvsup today, and am running on newest kernel, with a
{build,install}world completed (and rebooted since) ... something appears
broken in newest code?
gmake[4]: Entering directory `/usr/base/kde/qt-copy/tutorial/t7'
g++ -c -I/usr/base/kde/qt-copy/include -pipe -O2 -o lcdrange.o lcdrange.cpp
g++ -c -I/usr/base/kde/qt-copy/include -pipe -O2 -o main.o main.cpp
/usr/base/kde/qt-copy/bin/moc lcdrange.h -o moc_lcdrange.cpp
/usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "__sF"
gmake[4]: *** [moc_lcdrange.cpp] Error 1
gmake[4]: Leaving directory `/usr/base/kde/qt-copy/tutorial/t7'
gmake[3]: *** [t7] Error 2
gmake[3]: Leaving directory `/usr/base/kde/qt-copy/tutorial'
gmake[2]: *** [all] Error 2
ls -lt /usr/lib/libstdc++*
-r--r--r-- 1 root wheel 575168 Feb 17 17:01 /usr/lib/libstdc++_p.a
-r--r--r-- 1 root wheel 285608 Feb 17 17:01 /usr/lib/libstdc++.so.3
lrwxr-xr-x 1 root wheel 14 Feb 17 17:01 /usr/lib/libstdc++.so - libstdc++.so.3
-r--r--r-- 1 root wheel 515044 Feb 17 17:01 /usr/lib/libstdc++.a
Recompiling X from ports fixed my libm.so.* problem with __sF ... and
every binary I have in /usr/local right now has been rebuilt since 17:01's
installworld ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
Samehere:
static const char rcsid[] =
"$FreeBSD: src/lib/libc/stdio/findfp.c,v 1.15 2001/02/16 21:09:49 imp
Exp $";
On Sat, 17 Feb 2001, Warner Losh wrote:
What version of src/lib/libc/stdio/findfp.c do you have?
I'm using 1.15 here w/o any problems:
static const char rcsid[] =
"$FreeBSD: src/lib/libc/stdio/findfp.c,v 1.15 2001/02/16 21:09:49 imp Exp $";
Warner
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
On Sat, 17 Feb 2001, Warner Losh wrote: In message [EMAIL PROTECTED] The Hermit Hacker writes: : static const char rcsid[] = : "$FreeBSD: src/lib/libc/stdio/findfp.c,v 1.15 2001/02/16 21:09:49 imp : Exp $"; Then I don't understand the error at all. __sF should be defined in libc.so.5. What does ldconfig have to say? ldconfig -r | grep libc. 0:-lcom_err.2 = /usr/lib/libcom_err.so.2 2:-lcrypt.2 = /usr/lib/libcrypt.so.2 11:-lc.4 = /usr/lib/libc.so.4 12:-lc_r.4 = /usr/lib/libc_r.so.4 13:-lcalendar.2 = /usr/lib/libcalendar.so.2 14:-lcam.2 = /usr/lib/libcam.so.2 43:-lcipher.2 = /usr/lib/libcipher.so.2 44:-lcrypto.1 = /usr/lib/libcrypto.so.1 56:-lc.5 = /usr/lib/libc.so.5 57:-lc_r.5 = /usr/lib/libc_r.so.5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
the thing that is confusing me is that I'm getting through most of the
qt-copy compile before I get hit with it ... I'm doing a fresh 'make
world' on the machine, just in case ... then I'm going to try David's
idea, if that doesn't work ...
On Sat, 17 Feb 2001, Warner Losh wrote:
In message [EMAIL PROTECTED] The Hermit
Hacker writes:
: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "__sF"
: Recompiling X from ports fixed my libm.so.* problem with __sF ... and
: every binary I have in /usr/local right now has been rebuilt since 17:01's
: installworld ...
That's very odd since we've not removed __sF from libc yet, and that
the removal that was there was only for a couple of days.
Warner
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
On Sat, 17 Feb 2001, Warner Losh wrote: In message [EMAIL PROTECTED] The Hermit Hacker writes: : On Sat, 17 Feb 2001, Warner Losh wrote: : : In message [EMAIL PROTECTED] The Hermit Hacker writes: : : static const char rcsid[] = : : "$FreeBSD: src/lib/libc/stdio/findfp.c,v 1.15 2001/02/16 21:09:49 imp : : Exp $"; : : Then I don't understand the error at all. __sF should be defined in : libc.so.5. What does ldconfig have to say? : : ldconfig -r | grep libc. : 0:-lcom_err.2 = /usr/lib/libcom_err.so.2 : 2:-lcrypt.2 = /usr/lib/libcrypt.so.2 : 11:-lc.4 = /usr/lib/libc.so.4 : 12:-lc_r.4 = /usr/lib/libc_r.so.4 : 13:-lcalendar.2 = /usr/lib/libcalendar.so.2 : 14:-lcam.2 = /usr/lib/libcam.so.2 : 43:-lcipher.2 = /usr/lib/libcipher.so.2 : 44:-lcrypto.1 = /usr/lib/libcrypto.so.1 : 56:-lc.5 = /usr/lib/libc.so.5 : 57:-lc_r.5 = /usr/lib/libc_r.so.5 OK. This looks good. What does ldd say for the binary complaining? And what does libc.so point to? ls -lt libc.* -r--r--r-- 1 root wheel 599916 Feb 17 17:00 libc.so.5 lrwxr-xr-x 1 root wheel9 Feb 17 17:00 libc.so - libc.so.5 -r--r--r-- 1 root wheel 1240424 Feb 17 17:00 libc.a -r--r--r-- 1 root wheel 599116 Feb 15 21:10 libc.so.5.20010213 -r--r--r-- 1 root wheel 581944 Nov 9 01:45 libc.so.4 All looks well here ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
On Sat, 17 Feb 2001, Warner Losh wrote: In message [EMAIL PROTECTED] The Hermit Hacker writes: : the thing that is confusing me is that I'm getting through most of the : qt-copy compile before I get hit with it ... I'm doing a fresh 'make : world' on the machine, just in case ... then I'm going to try David's : idea, if that doesn't work ... OK. Things just don't make sense unless you are bringing in the libc.so.5.20010213 library by mistake somehow I don't know ... before I started all this, I did rm -rf's on /usr/X11R6 and /usr/local, so that I was starting as close to clean as I could ... a 'make -j16 world' is just finishing now, so I'm diving into a second attempt at qt-copy ... might have been an 'interim' sort of problem, where my first 'make installworld' wasn't clean *shrug* *cross fingers* Will appraise if qt-copy fails or succeeds ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
On Sat, 17 Feb 2001, The Hermit Hacker wrote: On Sat, 17 Feb 2001, Warner Losh wrote: In message [EMAIL PROTECTED] The Hermit Hacker writes: : the thing that is confusing me is that I'm getting through most of the : qt-copy compile before I get hit with it ... I'm doing a fresh 'make : world' on the machine, just in case ... then I'm going to try David's : idea, if that doesn't work ... OK. Things just don't make sense unless you are bringing in the libc.so.5.20010213 library by mistake somehow I don't know ... before I started all this, I did rm -rf's on /usr/X11R6 and /usr/local, so that I was starting as close to clean as I could ... a 'make -j16 world' is just finishing now, so I'm diving into a second attempt at qt-copy ... might have been an 'interim' sort of problem, where my first 'make installworld' wasn't clean *shrug* *cross fingers* Will appraise if qt-copy fails or succeeds ... Found it ... your thought of using the .2001* library directed me to look at the 'moc' in qt-copy, which has it link'd in ... not sure where it is pulling that from, but have wip'd out everything and am restarting ... :( Thanks for all your patience on this ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
On Sat, 17 Feb 2001, Warner Losh wrote: In message [EMAIL PROTECTED] The Hermit Hacker writes: : Thanks for all your patience on this ... No worries. I just want to make sure that we have things working. Well, I'm still getting my occasional hangs on heavy load ... just tried a 'gmake -j6' on qt-copy and 'make -j16 world' on /usr/src, and she hung solid ... :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: got stuck in the current __sF foo...
On Sat, 17 Feb 2001, Warner Losh wrote: In message [EMAIL PROTECTED] The Hermit Hacker writes: : On Sat, 17 Feb 2001, Warner Losh wrote: : : In message [EMAIL PROTECTED] The Hermit Hacker writes: : : Thanks for all your patience on this ... : : No worries. I just want to make sure that we have things working. : : Well, I'm still getting my occasional hangs on heavy load ... just tried a : 'gmake -j6' on qt-copy and 'make -j16 world' on /usr/src, and she hung : solid ... :) Well, that's snmpng :-) that's what I figure ... and something I've learnt to live with :) the short-term inconvience is worth the long-term gains ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
startx/startkde hangs -CURRENT ...
Just wipe'd out /var/db/pkg/* and rebuilt everything since the recent
problems with FILE ... figured safer to start clean then worry about each
one as they come up ...
Now, if I start X, the whole machine hangs solid ...
kernel is as of Feb 15th ... am going to re-upgrade now, just in case that
helps ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
lastest kernel from cvs ( sh exists with signal 8 )
just tried to reboot with a latest build (from this afternoon), and upon
reboot, it gives:
pid 6 (sh), uid 0: exited with signal 8
when /etc/rc tries to run, and, of course, won't let me get to single user
mode for same reason ...
checked /usr/src/UPDATING, and nothing in there seems to apply ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: lastest kernel from cvs ( sh exists with signal 8 )
d'oh, did it backwards again ... buildkernel then buildworld ... let me go
back and rebuild kernel and see if that is all it was in my case ...
On Sun, 21 Jan 2001, Peter Wemm wrote:
The Hermit Hacker wrote:
just tried to reboot with a latest build (from this afternoon), and upon
reboot, it gives:
pid 6 (sh), uid 0: exited with signal 8
when /etc/rc tries to run, and, of course, won't let me get to single user
mode for same reason ...
checked /usr/src/UPDATING, and nothing in there seems to apply ...
We were discussing this and a couple of other related strange things
that turned up. I might have broken the npx code with my last config(8)
change and the corresponding #ifdefs. I have not gone back over it all
again but will shortly. Given that two people have this sort of problem
now, things are pointing to the npx commits somehow. You did rebuild config,
right?
Can you please check the opt_npx.h file in your build directory and make sure
it has "#define DEV_NPX 1" in it?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: lastest kernel from cvs ( sh exists with signal 8 )
On Sun, 21 Jan 2001, Peter Wemm wrote:
The Hermit Hacker wrote:
d'oh, did it backwards again ... buildkernel then buildworld ... let me go
back and rebuild kernel and see if that is all it was in my case ...
Argh! I wish people would stop using buildkernel! :-( It calls config(8)
in such a way that buries the warning messages where people dont see.
config(8) is meant to be used interactively :-(
well, according to /usr/src/UPDATING, that is the documented way to do
things, or at least two out of 4 of them:
To build a kernel
-
If you are updating from a prior version of FreeBSD (even one just
a few days old), you should follow this procedure. With a
/usr/obj tree with a fresh buildworld,
make buildkernel KERNEL=YOUR_KERNEL_HERE
make installkernel KERNEL=YOUR_KERNEL_HERE
To just build a kernel when you know that it won't mess you up
--
cd src/sys/{i386,alpha}/conf
config KERNEL_NAME_HERE [1]
cd ../../compile/KERNEL_NAME_HERE
make depend
make
make install
[1] If in doubt, -r might help here.
If this fails, go to the "To build a kernel" section.
To rebuild everything and install it on the current system.
---
make world
Build a new kernel, see above.
To upgrade from 4.x-stable to current
-
make buildworld
make buildkernel KERNEL=YOUR_KERNEL_HERE
cp src/sys/${MACHINE_ARCH}/GENERIC.hints /boot/device.hints [2]
make installkernel KERNEL=YOUR_KERNEL_HERE
make installworld
[1]
reboot
If this is wrong, can we get that updated?
Even /usr/src/README references and steers ppl to buildkernel:
"The ``buildkernel'' and ``installkernel'' targets build and install the
kernel and the modules (see below)"
I have no probs with switching back to the more 'manual way' of cd'ng into
conf and using config, etc ... I just got the impression awhile back that
using buildkernel/installkernel was the recommended way of doing this, so
switched to it ...
On Sun, 21 Jan 2001, Peter Wemm wrote:
The Hermit Hacker wrote:
just tried to reboot with a latest build (from this afternoon), and upon
reboot, it gives:
pid 6 (sh), uid 0: exited with signal 8
when /etc/rc tries to run, and, of course, won't let me get to single use
r
mode for same reason ...
checked /usr/src/UPDATING, and nothing in there seems to apply ...
We were discussing this and a couple of other related strange things
that turned up. I might have broken the npx code with my last config(8)
change and the corresponding #ifdefs. I have not gone back over it all
again but will shortly. Given that two people have this sort of problem
now, things are pointing to the npx commits somehow. You did rebuild confi
g,
right?
Can you please check the opt_npx.h file in your build directory and make su
re
it has "#define DEV_NPX 1" in it?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
Marc G. Fournier ICQ#7615664 IRC Nick: Scrapp
y
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.or
g
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
On Sat, 20 Jan 2001, Mark Murray wrote: on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? I don't have CCD, and got home last night from the office and mine was hung also, on a kernel from the day before ... being in X, pretty much nothing I could do to try and debug it ... new laptop gets in this week, so will be setting up the whole serial console debugging env ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current hangs...
On Sat, 20 Jan 2001, John Baldwin wrote: On 20-Jan-01 The Hermit Hacker wrote: On Sat, 20 Jan 2001, Mark Murray wrote: on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times now hung the machine so that only reset got any attention simply by make -j 128 world Do you have an easy way to narrow it down to CCD by doing the same thing but without ccd involvement? I don't have CCD, and got home last night from the office and mine was hung also, on a kernel from the day before ... being in X, pretty much nothing I could do to try and debug it ... new laptop gets in this week, so will be setting up the whole serial console debugging env ... Is it SMP, and does it have multiple SCSI disks hanging off of the same device? yes and yes ... ahc1: Adaptec 2940 Ultra SCSI adapter port 0xcc00-0xccff mem 0xef10-0xef100fff irq 17 at device 13.0 on pci0 da0 at ahc1 bus 0 target 0 lun 0 da0: SEAGATE ST36530N 1281 Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 6208MB (12715920 512 byte sectors: 255H 63S/T 791C) da1 at ahc1 bus 0 target 1 lun 0 da1: WDIGTL WD91 ULTRA2 1.00 Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 8727MB (17873040 512 byte sectors: 255H 63S/T 1112C) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Darn Soundblaster Live :(
try enabling both and seeing if that fixes it?
On Mon, 15 Jan 2001, Adriaan Erasmus wrote:
I still have problems compiling my kernel.
All I want to do is add a pcm device
I have a Soundblaster Live and I must add a pcm device in my new kernel config file.
Every time I make the thing hangs up. I never had this problem b4 and I think its
has something to do with my CPU choice in my config file so here is the million
dollar question.
If I have a Celeron 400 which CPU type should I choose
i586 or i686
HELP !!!
Adriaan Erasmus
--====--
I would change the world,
but God would never give
me the source code.
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Soundblaster 64 PCI
On Sun, 14 Jan 2001, Michael Wells wrote: Hi all, I just got round to popping the lid on my machine and installing a Soundblaster 64 PCI card. I already had pcm in my kernel. It's working, but there are some Strange Things Happening. Firstly, here's /dev/sndstat: FreeBSD Audio Driver (newpcm) Jan 5 2001 12:50:04 Installed devices: pcm0: AudioPCI ES1371 at io 0xec00 irq 16 (1p/1r channels duplex) (Aside: is that really the chipset on the Soundblaster 64?). I get kernel warnings since I installed the card: Jan 14 13:00:15 sunrise /boot/kernel/kernel: pcm0: hwptr went backwards 2112 - 1888 I'm using FreeBSD Current, built on 5 January 2001. What I've got is some very strange sounds when I run mpg123 on a standard MP3 file. It's going through /dev/dsp and appears to play the samples at a very slow speed, with weird echoes. It's like a special effect. Using the -a flag with mpg123 allows me to play through /dev/audio, which sounds right except that it's distorted. At all volume levels, the audio sounds overdriven, and I know this is not due to impedance mismatches or faults elsewhere having used the card in Linux with the same cabling arrangements, amplifier etc. If this is a known problem, I'll stop for now and watch out for fixes. If it's not the expected behaviour from the PCM driver though, can anyone advise? Okay, just checked and it appears tha htis is the same error that I'm seeing on mine, as reported yesterday ... not sure if its known or not, but its not "just you" ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Soundblaster 64 PCI
yup, just confirmed ... it does it with splay as well ...
On Sun, 14 Jan 2001, The Hermit Hacker wrote:
On Sun, 14 Jan 2001, Cameron Grant wrote:
If this is a known problem, I'll stop for now and watch out for fixes.
If it's not the expected behaviour from the PCM driver though, can
anyone advise?
Okay, just checked and it appears tha htis is the same error that I'm
seeing on mine, as reported yesterday ... not sure if its known or not,
but its not "just you" ...
are either of you using esound or xmms? if so, i know the cause of this and
it will be fixed shortly, once my primary development box recovers from
killing its cpu.
if not, i'll try to reproduce this.
for me, I tried using splay ... but, not sure how old my compile was, so
am just installing a new copy and will report back ...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
System hangs with -current ...
Over the past several months, as others have reported, I've been getting
system hangs using 5.0-CURRENT w/ SMP ... I've got DDB enabled, but
ctl-alt-esc doesn't break me to the debugger ...
I'm not complaining about the hangs, if I was overly concerned, I'd run
-STABLE, but I'm wondering how one goes about providing debug information
on them other then through DDB?
Thanks ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
do a 'make -k world' ... I had the same problem with vi, and the same
SegFault ... by using -k, it bypasses the error, which allows it to get to
the point that the newer vi is installed, which doesn't SegFault ...
On Tue, 2 Jan 2001, Charlie Root wrote:
All the machines that I have running Current dumped core at the same
place this morning.
=== share/termcap
ex - /usr/src/share/termcap/termcap.src /usr/src/share/termcap/reorder
/dev/null
Segmentation fault - core dumped
*** Error code 139
Stop in /usr/src/share/termcap.
*** Error code 1
For a couple of days now, I haven't been able to use vi because it also
dumps core on all the machines except the only one that was able to
build world and a new kernel yesterday, just good timing I guess. I
haven't seen this on the list.
Thanks,
ed
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: growfs(8) for FreeBSD
On Fri, 8 Dec 2000, Alexander Langer wrote: Thus spake The Hermit Hacker ([EMAIL PROTECTED]): Stripe'd file systems (or concat ones) ... what growfs allows is someone to add an n+1 drive to their RAID/Stripe and increase the size of the file No, vinum can do this alone. But you couldn't grow the _fs_ after that, so there was no use for this vinum feature. Okay, that is what I said ... "add an n+1 drive to ... and increase the size of the file system" ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: growfs(8) for FreeBSD
Erk, I fear you mis-understand ... FreeBSD has a feature called 'VINUM',
which is a volume manager ... basically, it allows you to create RAID or
Stripe'd file systems (or concat ones) ... what growfs allows is someone
to add an n+1 drive to their RAID/Stripe and increase the size of the file
system by that drive, without having to backup the drive, re-format and
then restore ...
I've used Solaris' version and have been much waiting for it to become
available under FreeBSD ...
On Thu, 7 Dec 2000, Rogier R. Mulhuijzen wrote:
Is it also capable of shrinking filesystems? I've sometimes wanted to grow
my /var or / slice using space freed by shrinking /usr (on a default
partitioned disk). Up to now I've solved it through symlinks, but that
doesn't really deserve the beauty award. I'd imagine a lot of new users
wouldn't mind being able to change partition size on a fully configured
machine without having to resort to backup, reslice, restore
Anyways, sounds like a very handy tool already!
Just my $0,02
DocWilco
At 10:34 7-12-00 -0800, you wrote:
Hi,
Due to vinum it is no problem to add disks and grow your volumes but up to
now you couldn't easily make use of that new space for a file system, except
using sequence of ufsdump/newfs/ufsrestore or something similar.
Thomas ([EMAIL PROTECTED]) and me ([EMAIL PROTECTED]) have written a growfs(8)
for FreeBSD. Currently we can only grow unmounted file systems (in a clean
state) without any active snapshots inside. It is foreseen to enhance
growfs to
grow mounted file systems as well, and handle active snapshots correctly.
This requires some infrastructure which is then only available in FreeBSD-5,
whilst the current design runs also happily on FreeBSD-4 and FreeBSD-3
(tested) and possibly even on FreeBSD-2 (untested).
To help us gathering the needed data for fixing bugs in growfs we additionally
wrote ffsinfo(8), a (very) extended version of dumpfs.
We've sent a couple of snapshots of our code to Kirk McKusick and to Greg
Lehey. Greg also volunteered :-) for reviewing the code. We also maintain
some sort of (for some contractual reasons unilaterally) contact with Don
Coleman who is doing the same thing for BSD/OS.
--
Ciao
Christoph :-)
M$: Where do you want to go today?
Linux:Where do you want to go tomorrow?
FreeBSD: Are you guys comming, or what?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Current CVS kernel panic ...
Just upgraded the kernel, rebooted and it hung/panic'd with:
panic: spin lock sched lock held by 0x0xc02a73el for 5 seconds
cpuid = 1; lapic.id = 0100
Debugger("panic")
I have DDB enabled, and ctl-alt-esc doesn't break to the debugger, so its
totally hung here ...
dual-cpu celeron, smp enabled ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: Current kernel build failure -- cam_periph.c
On Wed, 6 Dec 2000, John Baldwin wrote: On 07-Dec-00 Manfred Antar wrote: I've been trying to build a current kernel from current sources for a day now and I keep getting this: I'm looking at this. My initial guess is maybe a gcc bug, as mtx_exit() compiles in dozens of other places just fine (and has for months now). ah, so I take it a 'make buildworld' doesn't fix thsi one :) ah well, had to do it anyway ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: system hangs ... not sure how to debug ...
On Mon, 27 Nov 2000, Alfred Perlstein wrote: * The Hermit Hacker [EMAIL PROTECTED] [001127 18:12] wrote: Morning all ... Every since the SMPng code went into -current way back when, I've been experiencing hangs ... and am not quite sure how to debug this. I'm in X all the time, so breaking to the debugger to see where its hanging isn't possible ... Some kernels its relatively easy to trigger, some kernels are harder to trigger, but they all do at some point in time ... Can someone suggestion a method of being able to debug this? Serial console, add BREAK_TO_DEBUGGER (sp?) to your kernel config and hook your laptop up to it. actually, got everything compiled nicely, rebooted and figured I'd pound the system the best way I know how: while(1) make -j16 world end system hung solid ... ctl-alt-esc won't even get me to DDB ... this kernel seems to do it faster then the previous one ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: system hangs ... not sure how to debug ...
On Mon, 27 Nov 2000, Alfred Perlstein wrote: * Alfred Perlstein [EMAIL PROTECTED] [001127 21:56] wrote: * The Hermit Hacker [EMAIL PROTECTED] [001127 18:12] wrote: Morning all ... Every since the SMPng code went into -current way back when, I've been experiencing hangs ... and am not quite sure how to debug this. I'm in X all the time, so breaking to the debugger to see where its hanging isn't possible ... Some kernels its relatively easy to trigger, some kernels are harder to trigger, but they all do at some point in time ... Can someone suggestion a method of being able to debug this? Serial console, add BREAK_TO_DEBUGGER (sp?) to your kernel config and hook your laptop up to it. Marc, I noticed you tried the BREAK_TO_DEBUGGER and whatnot already, perhaps letting us know what hardware you have in your smp box might help some, I'm running SMP and doing buildworlds and kernel compiles without a problem. I'm not however, running X nor doing any desktop work on it. I think I also figured out what makes the box so damn sluggish when doing lots of IO *bops dillon* :) well, here's a current dmesg .. any more detail then that needed? Copyright (c) 1992-2000 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.0-CURRENT #0: Sun Nov 26 18:22:52 AST 2000 [EMAIL PROTECTED]:/usr/local/mp3/obj/usr/local/base/src/sys/kernel Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (467.73-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 268435456 (262144K bytes) avail memory = 258248704 (252196K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc0309000. Preloaded elf module "random.ko" at 0xc030909c. Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00fdef0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: NVidia GeForce 256 graphics accelerator at 0.0 irq 16 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: Intel 82371AB/EB (PIIX4) USB controller at 7.2 irq 11 Timecounter "PIIX" frequency 3579545 Hz pci0: Intel 82371AB Power management controller at 7.3 ahc0: Adaptec 2910/15/20/30C SCSI adapter port 0xc400-0xc4ff mem 0xef00-0xef000fff irq 19 at device 9.0 on pci0 aic7850: Single Channel A, SCSI Id=7, 3/255 SCBs vx0: 3COM 3C590 Etherlink III PCI port 0xc800-0xc81f irq 18 at device 11.0 on pci0 utp[*utp*]: disable 'auto select' with DOS util! address 00:20:af:f7:8f:d2 Warning! Defective early revision adapter! ahc1: Adaptec 2940 Ultra SCSI adapter port 0xcc00-0xccff mem 0xef001000-0xef001fff irq 17 at device 13.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs pci0: unknown card (vendor=0x1274, dev=0x5000) at 17.0 irq 19 atapci1: HighPoint HPT366 ATA66 controller port 0xdc00-0xdcff,0xd800-0xd803,0xd400-0xd407 irq 18 at device 19.0 on pci0 ata2: at 0xd400 on atapci1 atapci2: HighPoint HPT366 ATA66 controller port 0xe800-0xe8ff,0xe400-0xe403,0xe000-0xe007 irq 18 at device 19.1 on pci0 ata3: at 0xe000 on atapci2 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0400 can't assign resources unknown: PNP0501 can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 acd0: CDROM CD-ROM 32X/AKU at ata0-master using PIO4 Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: DEC DLT2700 851A Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transf
RE: -current kernel hangs machine solid ...
gah ... okay, first "problem" is coming up with a serial console, as I
only have the one machine ... but, am going to search one out and save
this email ... will come back to it once I get it setup that far ...
thanks ...
On Tue, 28 Nov 2000, John Baldwin wrote:
On 28-Nov-00 The Hermit Hacker wrote:
Just tried to build a kernel based on sources from today, to enable
BREAK_TO_DEBUGGER so that I can try and get in and see where its hanging
... the compile hung the machine solid. Even hitting the
'numlock'/'capslock' on my keyboard generated no results ...
It is spinning with interrupts disabled, probably due to holding a spinlock for
far too long. Debugging this is not all that fun. :-P If you can rig up an
NMI switch, you can use that to drop into ddb and then use 'x' to see who owns
various mutexes (sched_lock and callout_mtx being the primary spin mutexes of
concern). If you compile your kernel with WITNESS and MUTEX_DEBUG, then you
can use 'x' to look at the sched_lock and callout_mtx mutex structures, find
the pointer to the mtx_debug structure, and examine that to find the mtxd_file
and mtxd_line members. Then you can look at those (x/s to look at the filename
as a string) to find the filename and line number when the mutex was last
acquired. Grr, except that this is broken for spin mutexes. If you are
patient, you can try rigging up a serial console, compile KTR into your kernel
as so:
options KTR
options KTR_EXTEND
options KTR_COMPILE=(KTR_LOCK|KTR_PROC|KTR_INTR)
Then when the machine has booted, log in via ssh or a tty other than the serial
console and type the following:
# sysctl -w debug.ktr_mask=0x1208
# sysctl -w debug.ktr_verbose=2
# while (1) do
make -j 16 buildworld
end
Unfortunately, there is a chance the machine will die before it hangs due to
exceeding the stack space. In that case, you can _try_ bumping UPAGES, but
that didn't help on my test machines. :-/ However, if your machine doesn't
blow up and die, then when it hangs, the KTR output dumped to the serial console
(which you should probably log to a file via script or somesuch) will show what
mutex was acquired and where it was acquired that is causing the hang.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: system hangs ... not sure how to debug ...
well, John just gave a good break down on what needs to be done to debug
it ... do you have easy access to a serial console? I'm trying to
scrounge up hardware at this end to do it with, but its difficult :)
On 28 Nov 2000, Michael Harnois wrote:
On Tue, 28 Nov 2000 12:17:14 -0400 (AST), The Hermit Hacker [EMAIL PROTECTED] said:
this kernel seems to do it faster then the previous one ...
That's been my observation over the past 24 hours too.
--
Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA
[EMAIL PROTECTED] [EMAIL PROTECTED]
Where ignorance is our master, there is
no possibility of real peace. -- the Dalai Lama
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: system hangs ... not sure how to debug ...
no sweat I'll try and hijack a laptop from work tomorrow for a couple
of days, or wait for hte boss to get back from her trip and hijack hers
... if nothing for tomorrow, early next week instead ...
On 28 Nov 2000, Michael Harnois wrote:
On Tue, 28 Nov 2000 19:34:03 -0400 (AST), The Hermit Hacker [EMAIL PROTECTED] said:
well, John just gave a good break down on what needs to be done
to debug it ... do you have easy access to a serial console? I'm
trying to scrounge up hardware at this end to do it with, but
its difficult :)
no, i don't ...
--
Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA
[EMAIL PROTECTED] [EMAIL PROTECTED]
Where ignorance is our master, there is
no possibility of real peace. -- the Dalai Lama
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
system hangs ... not sure how to debug ...
Morning all ...
Every since the SMPng code went into -current way back when, I've
been experiencing hangs ... and am not quite sure how to debug this. I'm
in X all the time, so breaking to the debugger to see where its hanging
isn't possible ...
Some kernels its relatively easy to trigger, some kernels are
harder to trigger, but they all do at some point in time ...
Can someone suggestion a method of being able to debug this?
thanks ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
-current kernel hangs machine solid ...
Just tried to build a kernel based on sources from today, to enable
BREAK_TO_DEBUGGER so that I can try and get in and see where its hanging
... the compile hung the machine solid. Even hitting the
'numlock'/'capslock' on my keyboard generated no results ...
going to try and get a clean compile by booting into my older kernel, and
see what happens ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Any plans to fix -current anytime soon?
was fixed yesterday, or, at least, I've done a buildworld since
experiencing this problem ...
On Mon, 27 Nov 2000, Jordan Hubbard wrote:
I know this:
=== usr.bin/netstat
cc -O -pipe -Wall -DIPSEC -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include
-c /usr/src/usr.bin/netstat/if.c
In file included from /usr/obj/usr/src/i386/usr/include/net/if_var.h:78,
from /usr/src/usr.bin/netstat/if.c:49:
/usr/obj/usr/src/i386/usr/include/sys/mbuf.h:120: `MSIZE' undeclared here (not i
n a function)
Is still being debated but it's also been broken for a few days now
and we really should either fix it or just back it out since it's
delaying build testing of *other* stuff. Thanks!
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
make buildworld broken ... CVS from today ...
Just tried to do a buildworld, got as far as netstat before it barf'd
with:
=== usr.bin/netstat
cc -O -pipe -Wall -DIPSEC -DINET6 -DIPSEC
-I/usr/obj/usr/local/base/src/i386/usr/include -c
/usr/local/base/src/usr.bin/netstat/if.c
In file included from /usr/obj/usr/local/base/src/i386/usr/include/net/if_var.h:78,
from /usr/local/base/src/usr.bin/netstat/if.c:49:
/usr/obj/usr/local/base/src/i386/usr/include/sys/mbuf.h:120: `MSIZE' undeclared here
(not in a function)
/usr/obj/usr/local/base/src/i386/usr/include/sys/mbuf.h:120: size of array
`MH_databuf' has non-integer type
/usr/obj/usr/local/base/src/i386/usr/include/sys/mbuf.h:123: `MSIZE' undeclared here
(not in a function)
/usr/obj/usr/local/base/src/i386/usr/include/sys/mbuf.h:123: size of array `M_databuf'
has non-integer type
/usr/obj/usr/local/base/src/i386/usr/include/sys/mbuf.h:239: `MCLBYTES' undeclared
here (not in a function)
*** Error code 1
Stop in /usr/local/base/src/usr.bin/netstat.
*** Error code 1
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld broken ... CVS from today ...
On Sun, 26 Nov 2000, Jonathan Lemon wrote: In article local.mail.freebsd-current/[EMAIL PROTECTED] you write: Just tried to do a buildworld, got as far as netstat before it barf'd with: === usr.bin/netstat cc -O -pipe -Wall -DIPSEC -DINET6 -DIPSEC -I/usr/obj/usr/local/base/src/i386/usr/include -c /usr/local/base/src/usr.bin/netstat/if.c In file included from /usr/obj/usr/local/base/src/i386/usr/include/net/if_var.h:78, from /usr/local/base/src/usr.bin/netstat/if.c:49: /usr/obj/usr/local/base/src/i386/usr/include/sys/mbuf.h:120: `MSIZE' undeclared here (not in a function) Already fixed. great, grabbing a new copy now, thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: device_tagenb in sys/cam/cam_xpt.c
damn, and I thought it was cause I didn't do a buildworld before my
buildkernel ... ;(
On Tue, 31 Oct 2000, Valentin Chopov wrote:
After last changes , device_tagenb is not defined in sys/cam/cam_xpt.c
Thanks,
Val
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
kernel trap 12 with interrupts disabled?
kernel of today, during a make world, generates:
Oct 23 18:32:18 thelab /boot/kernel/kernel: kernel trap 12 with interrupts disabled
Oct 23 18:32:32 thelab /boot/kernel/kernel: kernel trap 12 with interrupts disabled
Oct 23 18:32:39 thelab /boot/kernel/kernel: kernel trap 12 with interrupts disabled
and then hangs solid ...
I'm running the ahc driver for the following card:
ahc0: Adaptec 2940 Ultra SCSI adapter port 0xc800-0xc8ff mem 0xef00-0xef000fff
irq 17 at device 13.0 on pci0
aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs
known problem, or new one?
thanks ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Hangs on 'heavy' diskaccess
On Fri, 13 Oct 2000, Mark Huizer wrote: A few of my machines are getting hangs, running -current. At the moment of the hang, everything freezes, no more keyboard response, so I can't do any debugging. What I know about the machine at the moment is this: It's doing disk intensitive stuff (like a cvsup mirror doing a cvsup to sync with the master). So it seems like it is deadlocking in there somewhere. Do other people have these problems as well? yup, I can usually trigger it with a simple 'make world', but a 'make -j16 world' accelerates it ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't get into single user mode - panic: ffs_valloc: dup alloc
On Tue, 10 Oct 2000, Michael Lucas wrote:
It's not just you. I just assumed I had done something wrong.
Hitting ^C during bootup fsck gets me a single-user prompt.
ah, good, that got me back up and running, thanks :)
On Mon, Oct 09, 2000 at 10:01:11PM -0400, Marc G. Fournier wrote:
morning all ...
Well, I swear I have to be missing something here that is going to
make me slap my forehead, but I can't get into single user mode :(
I hit the space bar, type in 'boot -s' and it goes through all the
normal start up procedures, sets up the networking, etc ...
The reason I'm trying to get into single user mode is cause I
can't get into multi-user without it doing:
=
Recovering vi editor sessions
mode = 0100600, inum = 729, fs = /tmp
panic: ffs_valloc: dup alloc
cpuid = 0; lapic.id =
Debugger("panic")
CPU0 stopping CPUs: 0x0002... stopped
and a trace of:
Debugger() @ +0x38
panic() @ +0xa0
ffs_valloc()@ +0xf5
ufs_makeinode() @ +0x5a
ufs_create()@ +0x28
ufs_vnoperate() @ +0x15
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Michael Lucas
[EMAIL PROTECTED]
http://www.blackhelicopters.org/~mwlucas/
Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: can't get into single user mode - panic: ffs_valloc: dup alloc
On Tue, 10 Oct 2000, Szilveszter Adam wrote: On Tue, Oct 10, 2000 at 02:06:24PM -0300, The Hermit Hacker wrote: On Tue, 10 Oct 2000, Michael Lucas wrote: It's not just you. I just assumed I had done something wrong. Hitting ^C during bootup fsck gets me a single-user prompt. ah, good, that got me back up and running, thanks :) What system are you expriencing this on? -current as of two days ago ... am just rebuilding based on todays sources now ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ahc-related panics
try the newest cvsup sources ... justin just committed a change that
allowed me to get through a 'make buildworld' over here, where I was
getting the error listed before previous to it ...
On Sun, 8 Oct 2000, Bob Bishop wrote:
Hi,
I'm getting repeatable panics with -current, related to ahc. I'm seeing lots of
ahc:0:A:0: ahc_intr - referenced scb not valid during seqint 0x71 scb(nn)
WARNING no cammand for scb nn (cmdcmplt)
plus the WARNING without the other message. Eventually it panics with a
kernel-mode page fault, typically either in ahc_set_recoveryscb() in the
softinterrupt thread or in ahc_match_scb() in the ahc interrupt thread.
This is an SMP box building the world with -j8, so fairly busy.
--
Bob Bishop (0118) 977 4017 international code +44 118
[EMAIL PROTECTED]fax (0118) 989 4254
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ahc panic on 24hr kernel ...
source code CVSup as of early this morning, system is a dual celeron, with
the following scsi controller:
ahc0: Adaptec 2940 Ultra SCSI adapter port 0xc800-0xc8ff mem 0xef00-0xef000fff
irq 17 at device 13.0 on pci0
after little time after rebooting, and sped up by doing a make world, I
get:
-
Fatal trap 12: page fault while in kernel mode
cpuid = 1; lapic.id = 0100
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0131464
stack pointer = 0x10:0xcb7a3e90
frame pointer = 0x10:0xcb7a3ea0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 6
current process = 16 ( irq 17: ahc0 )
kernel: type 12 trap, code = 0
CPU1 stopping CPUs: 0x0001... stopped
Stopped at ahc_match_scb+0x18: movl 0(%esi),%eax
and a trace from DDB shows:
ahc_match_scb() @ +0x18
ahc_search_qinfifo @ +0xf7
ahc_freeze_devq @ +0x5d
ahc_handle_seqint @ +0x135
ahc_freebsd_intr@ +0x97
ithd_loop @ +0x6f
fork_trampoline @ +0x44
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
make -j16 world causes ffs_valloc() failure ...
newest source code, cvsup an hour ago or so ... if I do a build of the
kernel (to enable DDB), it compiles fine. If I do a 'make -j16 world', it
panic's with the following:
mode = 0100600, inum = 729, fs = /tmp
panic: ffs_valloc: dup alloc
cpuid = 0; lapic.id =
and a DDB trace that look slike:
panic()
ffs_valloc()
ufs_makeinode()
ufs_create()
ufs_vnoperate()
vn_open()
open()
syscall()
Xint0x80_syscall()
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: aic7xxx changes break kernel builds
On Sun, 17 Sep 2000, Steve Kargl wrote: hotrats:root[211] setenv KERNEL HOTRATS hotrats:root[212] make buildkernel -- Rebuilding kernel(s) -- === HOTRATS mkdir -p /usr/obj/usr/src/sys cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -r -d /usr/obj/usr/src/sys/HOTRATS HOTRATS Don't forget to do a ``make depend'' Kernel build directory is /usr/obj/usr/src/sys/HOTRATS cd /usr/obj/usr/src/sys/HOTRATS; MAKESRCPATH=/usr/src/sys/dev/aic7xxx make -f /usr/src/sys/dev/aic7xxx/Makefile make: cannot open /usr/src/sys/dev/aic7xxx/Makefile. *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It has been this way since last night 10pm PST. Anyone have a tip on generating the missing Makefile? I hit the same, went into /sys/i386/conf and ran 'config' and built the kernel "the old fashioned way", and it went through perfectly ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: someone MFC something to -stable recently that would explain...
have done that and it appears to have fixed the problem ... wish I could
remember where I rad that 'buildkernel' was supposed to build anytying the
kernel requird :(
On Wed, 13 Sep 2000, Paul Herman wrote:
On Tue, 12 Sep 2000, The Hermit Hacker wrote:
I'm going from a fresh install of 4.1-RELEASE - 4.1-STABLE, or, at least,
trying to ... and I'm building the kernel as 'make buildkernel' ...
cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include
-D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2
/usr/src/sys/i386/i386/locore.s
/tmp/ccg38208.s: Assembler messages:
/tmp/ccg38208.s:1743: Error: .space specifies non-absolute value
/tmp/ccg38208.s:2454: Error: undefined symbol L0^A in operation setting PTmap
/tmp/ccg38208.s:2454: Error: undefined symbol PDRSHIFT in operation setting PTmap
Did you "make buildworld" first? I don't remember exactly when
binutils was updated, but it could have something to do with that.
When in doubt after a cvsup, always build world first before building
a kernel.
-Paul.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: docs on how to upgraded boot loader ...
Ah, okay, for some reason I was looking at the 'disklabel -B' stuff, but
that never worked :( I've gotten into the habit of doing the whole
'buildkernel/buildworld/etc' procedure, and just hadn['t gotten to the
point doing the 'installworld' :(
thanks ...
On Thu, 7 Sep 2000, Warner Losh
wrote:
In message [EMAIL PROTECTED] The Hermit Hacker
writes:
: How do I upgrade it 'with the new kernel', as the UPDATING file
: suggests? I've looked at the man pages for loader, and it doesn't suggest
: anything ... help?
cd /usr/src
make buildworld
make buildkernel
make installkernel
cd sys
make install
cd ..
Optionally reboot in single user mode
cd /usr/src
make installworld
Or if you like taking chances, and with the fixes I just committed:
# assume that /usr/obj exists from prior run
cd /usr/src/lib/libstand
make depend make all # add install here w/o my fixes
cd ../../sys
make depend make all install
cd i386/conf
config FOO
cd ../../compile/FOO
make depend make all install
reboot
But we've had enough changes in sys recently that you'll need new
libkvm utilities, so you might as well do the first series of
commands.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
mouse works!!
serial mouse works with currrent sources ... thanks guys
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
SMP changes committed ... ?
I thought one of the SMP developers announced that it was now committed,
yet I haven't seen any commit messages for it ... I'm running the newest
patch, so am waiting for the commit messages before I actually do my next
upgrade ...
Did I mis-read a message from earlier today?
thanks ..
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMP changes committed ... ?
On Fri, 8 Sep 2000, Greg Lehey wrote: On Thursday, 7 September 2000 at 3:11:27 -0300, The Hermit Hacker wrote: I thought one of the SMP developers announced that it was now committed, yet I haven't seen any commit messages for it ... I'm running the newest patch, so am waiting for the commit messages before I actually do my next upgrade ... Did I mis-read a message from earlier today? There were only two relatively short commit messages. ah, okay, the patch I applied before teh commits felt like there should be a bunch of messages ;( thanks for confirming :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'interrupt-level buffer overflows' for sio device?
On Thu, 7 Sep 2000, Warner Losh wrote: Also, this is interrupt level overflows. We can run the fast interrupts fast enough to harvest characters from the hardware. What's not happening is that sio's bottom half isn't being run fast enough so the interrupt level buffers overflow. Okay, I'm a little confused here ... from what I'm reading/following, this isn't a new problem ... or is it? If not, why has it suddenly manifested itself with the new SMP code? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 'interrupt-level buffer overflows' for sio device?
On Thu, 7 Sep 2000, Warner Losh wrote: In message [EMAIL PROTECTED] The Hermit Hacker writes: : Okay, I'm a little confused here ... from what I'm reading/following, this : isn't a new problem ... or is it? If not, why has it suddenly manifested : itself with the new SMP code? It seems to be new with the SMP code. At least that's what my reading of the original message is. That was what I thought when I wrote the original message ... it just scares me sometimes how quickly things get acknowledged as a problem in the Open Source community, especially after dealign with tech support at Sun and getting the complete run around ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
docs on how to upgraded boot loader ...
How do I upgrade it 'with the new kernel', as the UPDATING file
suggests? I've looked at the man pages for loader, and it doesn't suggest
anything ... help?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Installed SMP patch and now mouse doesn't work?
Have nothing else to go on yet ... I updated both the current source code
and installed the SMP patch from Sept 5th. Everything installed great,
rebooted and I can work in character mode ... go to X, and the mouse gives
me no activity, where it did just before the upgrade ...
Am still investigating at this end, but if anyone else has experience
similar and knows how to fix?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
'interrupt-level buffer overflows' for sio device?
this corresponds to the device I have the mouse on ... the machine has
only been up 18hrs ... not sure where else to look ... I'm referencing
/dev/ttyd1, like I've always done for my mouse, and just checked /dev (ran
MAKEDEV ttyd1) to make sure nothing has changed there ...
Help?
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
sio1: 32 more interrupt-level buffer overflows (total 32)
sio1: 123 more interrupt-level buffer overflows (total 155)
sio1: 135 more interrupt-level buffer overflows (total 290)
sio1: 134 more interrupt-level buffer overflows (total 424)
sio1: 30 more interrupt-level buffer overflows (total 454)
sio1: 12 more interrupt-level buffer overflows (total 466)
sio1: 40 more interrupt-level buffer overflows (total 506)
sio1: 133 more interrupt-level buffer overflows (total 639)
sio1: 135 more interrupt-level buffer overflows (total 774)
sio1: 134 more interrupt-level buffer overflows (total 908)
sio1: 135 more interrupt-level buffer overflows (total 1043)
sio1: 68 more interrupt-level buffer overflows (total )
sio1: 118 more interrupt-level buffer overflows (total 1229)
sio1: 14 more interrupt-level buffer overflows (total 1243)
sio1: 20 more interrupt-level buffer overflows (total 1263)
sio1: 119 more interrupt-level buffer overflows (total 1382)
sio1: 134 more interrupt-level buffer overflows (total 1516)
sio1: 135 more interrupt-level buffer overflows (total 1651)
sio1: 57 more interrupt-level buffer overflows (total 1708)
sio1: 3 more interrupt-level buffer overflows (total 1711)
sio1: 31 more interrupt-level buffer overflows (total 1742)
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Installed SMP patch and now mouse doesn't work?
On Wed, 6 Sep 2000, John Baldwin wrote: The Hermit Hacker wrote: Have nothing else to go on yet ... I updated both the current source code and installed the SMP patch from Sept 5th. Everything installed great, rebooted and I can work in character mode ... go to X, and the mouse gives me no activity, where it did just before the upgrade ... Am still investigating at this end, but if anyone else has experience similar and knows how to fix? Uh, all of the SMPng boxes so far haven't had mice. :P Is your mouse a serial mouse? There seem to be some problems with input on the sio devices. That would be her ... :) Its my home machine, which is why I run -current on it ... am willing to try anything/everything towards debugging and repairing it ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: hotmail now running win2000
On Wed, 9 Aug 2000, Brian Hechinger wrote:
Irwan Hadi drunkenly mumbled...
But I guess soon they will change all their freeBSD servers ;(
and I wonder, how many people should be employed by Microsoft, just to
press the restart button at their 2000 servers for Hotmail, in case they
got BSOD ?
it's called the APC MasterSwitch (or similar peoduct by alternate vendor)
reboot machines over the network. takes the place of 64.2% of all people
employed with the word microsoft in their title.
and they do have their own 'Foundry' like product that they can use as a
front end ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: hotmail now running win2000
On Tue, 8 Aug 2000, Irwan Hadi wrote: At 12:44 AM 8/9/00 -0400, Brian Hechinger wrote: Irwan Hadi drunkenly mumbled... But I guess soon they will change all their freeBSD servers ;( and I wonder, how many people should be employed by Microsoft, just to press the restart button at their 2000 servers for Hotmail, in case they got BSOD ? it's called the APC MasterSwitch (or similar peoduct by alternate vendor) reboot machines over the network. takes the place of 64.2% of all people employed with the word microsoft in their title. Including MCSE, MCP , etc ? ;) :) BTW how can the administrator of hotmail determine if a server is BSOD or not then ?, because they have 2000 servers and I think without enough employees to watch the system and how can APC master switch reboot the machine in case it BSOD ? use something like netsaint to monitor those machines? and the APC master switch is web administered, so it would be too easy to build a quick perl script to trigger a power outlet correspondign to the partiular server that was n olonger responding ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse frozen in X when returning from text console
On Thu, 27 Jul 2000, David Scheidt wrote: On Wed, 26 Jul 2000, Jos Backus wrote: :[This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using :the ati driver module.] : :Something I noticed today: switch to text console from X using C-A-F1; upon :return, the mouse cursor is frozen. moused appears to still work because I :can cut/paste text in the text console. Restarting moused doesn't help. : I don't have this problem, using XFree86 4.0.1, the ati module, /dev/psm0, and a current from early june. I do have a problem that some Solaris One suggestion was made that I might have been the result of the recent changes to the syscons driver ... something about entropy? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse frozen in X when returning from text console
On Thu, 27 Jul 2000, Jose M. Alcaide wrote: Benedikt Schmidt wrote: Same problem here on current (make world + kernel last week) with Xfree86 4.0.1 using a V3000 and and ps2 mouse. I tried using "Device" "/dev/mouse" with moused and "Device" "/dev/psm0" without moused. With both settings the mouse is frozen after switching back to X. I didn't have this problem with Xfree 4.0. It just appeared when I updated to the new 4.0.1 port. I don't have this problem on Linux using Xfree86 4.0.1 on the same computer. This problem is not specifically related to -CURRENT; it happens with XFree86 4.0.1 when the configured mouse protocol is "Auto". Another glitch: "Protocol SysMouse" does not work with moused; however, "Protocol Mousesystems" does. Mine is set to (5.0-CURRENT): Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol""MouseMan" Option "Device" "/dev/ttyd1" EndSection And (4.1RC): Section "Pointer" Protocol"MouseMan" Device "/dev/psm0" BaudRate1200 Resolution 100 Buttons 3 EndSection To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse frozen in X when returning from text console
On Thu, 27 Jul 2000, Benedikt Schmidt wrote: On Wed, Jul 26, 2000 at 03:53:15PM -0700, Jos Backus wrote: [This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using the ati driver module.] Something I noticed today: switch to text console from X using C-A-F1; upon return, the mouse cursor is frozen. moused appears to still work because I can cut/paste text in the text console. Restarting moused doesn't help. Is anybody else seeing this? Same problem here on current (make world + kernel last week) with Xfree86 4.0.1 using a V3000 and and ps2 mouse. I tried using "Device" "/dev/mouse" with moused and "Device" "/dev/psm0" without moused. With both settings the mouse is frozen after switching back to X. I didn't have this problem with Xfree 4.0. It just appeared when I updated to the new 4.0.1 port. I don't have this problem on Linux using Xfree86 4.0.1 on the same computer. Make that three ... same environment except a GeoForce256 Video card ... all worked well with XFree4.0 ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
KDE2 hangs in 5.0-CURRENT but not in 4.1RC ...
I've been spending the past few days trying to get KDE2 from anoncvs to work on my 5.0-CURRENT machine, totally unsuccessfully. I can get it to compile and then run 'startx', but it appears to hang on the ksmserver process ... Will Andrews, who is working on the KDE2 ports, has the same thing running on his 4.1RC system, so I'm starting to wonder if the "bug" is in FreeBSD vs KDE2 ... From what I've been able to determine, the 'hang' is in ksmserver, which is the last thing that 'startkde' runs. After it hangs, I've done a 'gcore' of the process, with the results showing the following: Script started on Sun Jul 23 01:19:11 2000 gdb `which ksmserver` core.12615 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... warning: exec file is newer than core file. Core was generated by `ksmserver'. Reading symbols from /usr/local/lib/libkdecore.so.3...done. Reading symbols from /usr/local/lib/libkde-qt-addon.so.3...done. Reading symbols from /usr/X11R6/lib/libSM.so.6...done. Reading symbols from /usr/X11R6/lib/libICE.so.6...done. Reading symbols from /usr/local/lib/libDCOP.so.1...done. Reading symbols from /usr/local/lib/libqt.so...done. Reading symbols from /usr/local/lib/libpng.so.4...done. Reading symbols from /usr/lib/libz.so.2...done. Reading symbols from /usr/local/lib/libjpeg.so.9...done. Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Reading symbols from /usr/lib/libstdc++.so.3...done. Reading symbols from /usr/lib/libm.so.2...done. Reading symbols from /usr/lib/libc.so.4...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x289659c4 in select () from /usr/lib/libc.so.4 (gdb) bt #0 0x289659c4 in select () from /usr/lib/libc.so.4 #1 0x2881a1b5 in _XWaitForReadable () from /usr/X11R6/lib/libX11.so.6 #2 0x2881ab59 in _XRead () from /usr/X11R6/lib/libX11.so.6 #3 0x2881b69c in _XReply () from /usr/X11R6/lib/libX11.so.6 #4 0x28807520 in XInternAtom () from /usr/X11R6/lib/libX11.so.6 #5 0x28872b62 in _XimFilterPropertyNotify () from /usr/X11R6/lib/libX11.so.6 #6 0x288391f5 in XFilterEvent () from /usr/X11R6/lib/libX11.so.6 #7 0x282e1c28 in QApplication::x11ProcessEvent () from /usr/local/lib/libqt.so #8 0x282e16cf in QApplication::processNextEvent () from /usr/local/lib/libqt.so #9 0x2837fa0b in QApplication::enter_loop () from /usr/local/lib/libqt.so #10 0x282e165b in QApplication::exec () from /usr/local/lib/libqt.so #11 0x80546f1 in main (argc=2, argv=0xbfbffa90) at main.cpp:80 (gdb) quit exit exit Script done on Sun Jul 23 01:19:30 2000 I'm at a loss as to where to look from here ... but if the same code appears to be working fine under 4.1RC and not 5.0-CURRENT, suspecting a bug in KDE2 appears to be the wrong path to be searching ... Thoughts? Comments? Suggestions on where further to look? Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RSA problem with SSH ...
Just upgraded to the newest -current, and now can't use SSH:
ssh: no RSA support in libssl and libcrypto. See ssl(8).
Tried to read the 'ssl(8)' man page, but it comes back as:
man 8 ssl
No entry for ssl in section 8 of the manual
man ssl
No manual entry for ssl
Did mergemaster and saw the 'MAKE_RSAINTL' setting in
/etc/defaults/make.conf, so did that and did a new 'make world' ...
Even saw the note about /usr/ports/security/rsaref and installed that, no
difference ...
Read through /usr/src/UPDATING and can't seem to find anything that
applies other then the mentioning of RANDOMDEV, which I have configured in
...
So ... what am I missing that this missing man page seems to be indicated
as the answer? :)
Thanks ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
