Igor Roboul wrote:
I have tracked external source of problem.
FreeBSD-CURRENT (at least 5.0-CURRENT-20020917-JPSNAP) could not find
CD-ROM (at least IDE Sony 52sp) if it set to MASTER mode. If I set
CD-ROM to SLAVE on both pprimary and secondary ATA controllers,
FreeBSD sees it.
I'll send
Oct 13 20:00 PDT sources:
Script started on Thu Oct 17 21:38:23 2002
Not loading printing treats...
/var/crash gdb -k kernel.ko.debug
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome
Luigi Rizzo wrote:
at which point you can proceed by specifying ufs:md0 as the root
path, and everything works fine.
It certainly used to work (though i do not remember if the root path
came out as md0c or just md0) up to a couple of months ago, roughly.
Does this ring any bell on what
I have tracked external source of problem.
FreeBSD-CURRENT (at least 5.0-CURRENT-20020917-JPSNAP) could not find
CD-ROM (at least IDE Sony 52sp) if it set to MASTER mode. If I set
CD-ROM to SLAVE on both pprimary and secondary ATA controllers,
FreeBSD sees it.
I'll send dmesg of both cases later.
I have just discovered the hard way that the kthread.9 manual page is
slightly out of date.
Having never done man page work before, I've attached a diff of the
proposed change and if someone could give this a once-over and fix
and/or commit it, that'd rock.
Thanks. =)
--
Benno Rice
[EMAIL
Hi,
this is -current as of Oct 8.
Fatal trap 12: page fault while in vm86 mode
fault virtual address = 0xc4182
fault code = user read, page not present
instruction pointer = 0xc000:0x4182
stack pointer = 0x0:0xfc0
frame pointer = 0x0:0x0
code segment
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2: cleaning up the object tree
This is a repost. Forgive me if you see it twice, but it didn't turn up in
the -current list.
Hi,
Just had another panic, same kmem_malloc(). I did a trace but forgot to
write the traceback down. In any case, there was a semop() call in the
traceback. Furthermore, this might be interesting:
On (2002/10/18 19:38), Benno Rice wrote:
I have just discovered the hard way that the kthread.9 manual page is
slightly out of date.
Having never done man page work before, I've attached a diff of the
proposed change and if someone could give this a once-over and fix
and/or commit it,
Lo ppl,
yesterday i tried to build current with files i sucked 2 or 3 days ago via
cvsup. I
followed the instructions of the handbook precisely, and got successfully to
the step
make buildkernel.
After that, i dropped into single user mode and started make installworld.
It failed
at some
Hi,
- you have to build and install the new kernel
- reboot into single user mode.
- and continue with make installworld
bye,
Pascal Giannakakis schrieb:
Lo ppl,
yesterday i tried to build current with files i sucked 2 or 3 days ago via
cvsup. I
followed the instructions of the handbook
I'm having problems with emacs 20.7 running under X:
#emacs
Fatal error (11).Segmentation fault (core dumped)
but emacs -nw works fine (i.e. without X).
This started after doing a portupgrade -fa to solve
the _sF symbol problem.
I've recompiled every package that emacs depends on
and still no
On Fri, 18 Oct 2002 08:00:19 -0700
walt [EMAIL PROTECTED] wrote:
I suppose I need to build emacs with debugging enabled?
Any hints how to do that?
Anyone else seeing this problem?
xemacs dies here. Global variables are getting corrupted somehow during
startup.
--
Alexander Kabaev
To
Does this happen on a current with this patch applied too?
Index: usb_port.h
===
RCS file: /home/ncvs/src/sys/dev/usb/usb_port.h,v
retrieving revision 1.58
diff -u -r1.58 usb_port.h
--- usb_port.h 2 Oct 2002 07:44:20 -
Josef Karthauser [EMAIL PROTECTED] wrote:
Does this happen on a current with this patch applied too?
I'm certain I tried this already :(
--
Brian Fundakowski Feldman \'[ FreeBSD ]''\
[EMAIL PROTECTED] [EMAIL PROTECTED] \ The Power to Serve! \
On 17-Oct-2002 Lars Eggert wrote:
Hi,
I'm tracking down a lock order reversal for hsu@, and just came across
this other locking panic twice in the last few hours. I run with WITNESS
and WITNESS_SKIPSPIN, and have never seen this happen unless I set
debug.witness_ddb=1. The name of the
On 17-Oct-2002 Kris Kennaway wrote:
I just got the following panic on one of the gohan machines, running a
somewhat recent -current:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xa0
fault code = supervisor write, page not present
instruction
On 18-Oct-2002 walt wrote:
I'm having problems with emacs 20.7 running under X:
#emacs
Fatal error (11).Segmentation fault (core dumped)
but emacs -nw works fine (i.e. without X).
This started after doing a portupgrade -fa to solve
the _sF symbol problem.
I've recompiled every
John Baldwin wrote:
What is line 488 of src/sys/kern/kern_descrip.c?
fhold(fp) in do_dup().
Lars
--
Lars Eggert [EMAIL PROTECTED] USC Information Sciences Institute
smime.p7s
Description: S/MIME Cryptographic Signature
On 18-Oct-2002 Lars Eggert wrote:
John Baldwin wrote:
What is line 488 of src/sys/kern/kern_descrip.c?
fhold(fp) in do_dup().
Hrm. You can try adding some KASSERT()'s that the reference
count of that struct file isn't zero or negative.
--
John Baldwin [EMAIL PROTECTED]
On Thu, 17 Oct 2002, Luigi Rizzo wrote:
Hi,
on a freshly cvsupped source tree, i notice that picobsd images
with a preloaded MD_ROOT cannot boot anymore: the kernel goes up
to this stage:
Mounting root from ufs:/dev/md0c
setrootbyname failed
ffs_mountroot: can't find
On Fri, 18 Oct 2002, Scott Long wrote:
[...]
**Warning, rant**
The ports collection is one of the crown jewels of FreeBSD.
Unfortunately, even as more ports committers are added, more and
more ports break or become harder to build. On top of that,
pkg_add has become close to worthless now
On Fri, 18 Oct 2002, Scott Long wrote:
[...]
**Warning, rant**
The ports collection is one of the crown jewels of FreeBSD.
Unfortunately, even as more ports committers are added, more and
more ports break or become harder to build. On top of that,
pkg_add has become close to
On Fri, Oct 18, 2002 at 08:00:19AM -0700, walt wrote:
Anyone else seeing this problem?
The only issue I have with emacs (I'm using xemacs 21.1.14) is that it
hangs quite often. Usually when I do a lot of mouse scrolling. This
seems to be a recent thing.
- alex
To Unsubscribe: send mail to
I have just discovered the hard way that the kthread.9 manual page is
slightly out of date.
Having never done man page work before, I've attached a diff of the
proposed change and if someone could give this a once-over and fix
and/or commit it, that'd rock.
Thanks. =)
Thanks. I knew
On Fri, 18 Oct 2002, Long, Scott wrote:
Nate Lawson wrote:
On Fri, 18 Oct 2002, Scott Long wrote:
[...]
**Warning, rant**
The ports collection is one of the crown jewels of FreeBSD.
Unfortunately, even as more ports committers are added, more and
more ports break or become harder
On 18-Oct-2002 Alex Zepeda wrote:
On Fri, Oct 18, 2002 at 08:00:19AM -0700, walt wrote:
Anyone else seeing this problem?
The only issue I have with emacs (I'm using xemacs 21.1.14) is that it
hangs quite often. Usually when I do a lot of mouse scrolling. This
seems to be a recent
Terry,
At 23:07 18/10/2002, you wrote:
Ben Stuyts wrote:
Furthermore, this might be interesting: the last vmstat -m log
before the panic. Maybe someone can check if these values are reasonable?
The system has 64 MB memory and has been up for about 24 hrs with almost no
load.
On Fri, Oct 18, 2002 at 05:37:22PM -0400, Long, Scott wrote:
No, the systems people do do stuff wrong. It's been plainly pointed
out many times recently when someone does something wrong. However,
what's wrong with a little cooperation? If a port breaks because of
a system change, the
I just saw a strange panic on a dual CPU x86:
(kernel from Tuesday)
panic: uma_zalloc_arg: Returning an empty bucket.
cpuid = 0; lapic.id =
Debugger(panic)
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db tr
Debugger(c03477a6,0,c035a2ba,d69b6bc0,1) at Debugger+0x55
On Fri, Oct 18, 2002 at 02:20:59PM -0700, Kent Stewart wrote:
In 40 years of using computers, nothing has changed. The system's
people are still primadona's and do nothing wrong.
Get used to it :). Unfortunately!! People don't install OSes because
of the OS as much as the codes they can
On Fri, Oct 18, 2002 at 01:37:02AM -0600, Scott Long wrote:
The ports collection is one of the crown jewels of FreeBSD.
Unfortunately, even as more ports committers are added, more and
more ports break or become harder to build. On top of that,
pkg_add has become close to worthless now that
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2: cleaning up the object tree
Long, Scott wrote:
Yes, I'm sorry if it sounded like I was picking on the ports committers.
Changes due to standards compliance, architecture changes, etc, all
wreak havoc on ports, and hopefully the pace of that will slow down.
Unfortunately, the direction of FreeBSD is what it is, and the
Terry Lambert wrote:
Kent Stewart wrote:
In 40 years of using computers, nothing has changed. The system's
people are still primadona's and do nothing wrong.
Get used to it :). Unfortunately!! People don't install OSes because
of the OS as much as the codes they can run on it. The importance
Date: Fri, 18 Oct 2002 23:06:53 +0200 (CEST)
From: BOUWSMA Beery [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Stupid UFS2 questions...
[IPv6-only address above; strip the obvious for IPv4-only mail replies]
In trying to track down a panic I had while mounting a
Will Andrews wrote:
On Fri, Oct 18, 2002 at 01:37:02AM -0600, Scott Long wrote:
The ports collection is one of the crown jewels of FreeBSD.
Unfortunately, even as more ports committers are added, more and
more ports break or become harder to build. On top of that,
pkg_add has become close
Ben Stuyts wrote:
Almost 5.3M of unswappable physical memory dedicated to semaphores
seems like a bit much.
Yes, and it increases continuously, for example when I fetch new mail (over
pop) from my windows pc. The pc stores this again on a network drive, so
both qpopper and smbd are
A new set of 5.0 packages has been uploaded and is making its way out
to mirror sites. I will soon be sending out mail to all maintainers
of broken ports asking for submissions of fixes (or at least reporting
the breakage to the relevant vendors).
In the meantime, please visit
Apparently, On Sat, Oct 19, 2002 at 12:19:57AM +0200,
Ben Stuyts said words to the effect of;
Terry,
At 23:07 18/10/2002, you wrote:
Ben Stuyts wrote:
Furthermore, this might be interesting: the last vmstat -m log
before the panic. Maybe someone can check if these values are
Kent Stewart wrote:
In 40 years of using computers, nothing has changed. The system's
people are still primadona's and do nothing wrong.
Get used to it :). Unfortunately!! People don't install OSes because
of the OS as much as the codes they can run on it. The importance tree
is inverted.
* Jake Burkholder [EMAIL PROTECTED] [021018 18:26] wrote:
semop() leaks memory. An important free() was removed by alfred in
rev 1.55. Try this.
Oh' c'mon, isn't MP-safeness a bit more important than a some
little memory leak, ram is cheap! processors aren't!
Seriously, I just checked in
42 matches
Mail list logo
