So I'm trying to get the kernel to drop into ddb when it spews witness
stuff.. stuff like:
Aug 18 23:22:28 blarf kernel: ../../../vm/uma_core.c:1332: could sleep with process
lock locked from ../../../kern/kern_exec.c:360
Aug 18 23:22:28 blarf last message repeated 2 times
Aug 18 23:28:12
Matthew N. Dodd wrote:
On Sat, 17 Aug 2002, Mark Murray wrote:
If I do a make -jN world build on my dual MMX/200 box, I usually end
up in tears (well, a panic anyway). This is completely reproducible, and
the panic always happens in swapout_procs while vmdaemon is running.
Anyone else
On 19 Aug, Alex Zepeda wrote:
../../../kern/kern_synch.c:454: sleeping with mntvnode locked from
../../../kern/vfs_subr.c:2789
panic: from debugger
cpuid = 0; lapic.id =
---
GNU gdb 5.2.0 (FreeBSD) 20020627
This GDB was configured as i386-undermydesk-freebsd...
#10
Hello, Crist!
You wrote to Radko Keves [EMAIL PROTECTED] on Fri, 16 Aug 2002
12:38:54 -0700:
CJC On Fri, Aug 16, 2002 at 03:01:47PM +0200, Radko Keves wrote:
i try to load ipl.ko
#kldload -v /boot/kernel/ipl.ko kldload: can't load
/boot/kernel/ipl.ko: Exec format error
CJC [snip]
Dag-Erling Smorgrav wrote:
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2:
Dear User,
The message sent by [EMAIL PROTECTED] is infected by a virus and
has not been delivered. DrWeb antivirus filter reports:
--- DrWeb report ---
DrWeb found next viruses:
ÉÎÆÉÃÉÒÏ×ÁÎ Trojan.IframeExec
ÉÎÆÉÃÉÒÏ×ÁÎ Win32.HLLM.Klez.4
---
Dear User,
The message sent by [EMAIL PROTECTED] is infected by a virus and
has not been delivered. DrWeb antivirus filter reports:
--- DrWeb report ---
DrWeb found next viruses:
ÉÎÆÉÃÉÒÏ×ÁÎ Trojan.IframeExec
ÉÎÆÉÃÉÒÏ×ÁÎ Win32.HLLM.Klez.4
---
--
Rebuilding the temporary build tree
--
stage 1: bootstrap tools
--
stage 2: cleaning up the object tree
On Mon, 19 Aug 2002, Jason wrote:
Wierd, I have it running just peachy on a dual P3 900 box
It runs mostly okay on my dual P3/600, although for the last couple of
months it has a tendency to panic with a bdwrite: buffer is not busy on
average 2-3 times a day (per approx 15 hour run) Such is
Title: ½Åû¼¸ÞÀÏÆû
¼º¸í
Áֹεî·Ï ¹øÈ£ (-ÀÔ·Â)
Á÷Àå ÀüÈ
ÈÞ´ëÆù
Is it just me or is libstdc++ linking broken on -current right now?
Kde3 complains:
c++ -DNDEBUG -DNO_DEBUG -O2 -O -pipe -march=pentiumpro -fmemoize-lookups
-fsave-memoized -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE
-DQT_NO_COMPAT -DQT_NO_ASCII_CAST -o kappfinder -pthread
On 12 Aug 2002 12:40:20 +0400, Vladimir B. Grebenschikov wrote:
There is patch to teach rcNG do not try dhcp on not-connected ethernet.
simply put
ifconfig_fxp0=dhcp-if-carrier
into rc.conf
It will be interested to somebody
For what it's worth, I think this rocks.
Theoretically
On Mon, 19 Aug 2002, Jason wrote:
Wierd, I have it running just peachy on a dual P3 900 box
Just so nobody else replies to this with something similar we're talking
about PENTIUMS.
Not the P3, P2, Alpha or anything else.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E |
Security Advisory FreeBSD-SA-02:38.signed-error
i try to patch it (of cource in current ;( ) and:
The text leading up to this was:
--
|Index: sys/i386/isa/vesa.c
|diff -u sys/i386/isa/vesa.c:1.32 sys/i386/isa/vesa.c:1.32.10.1
|--- sys/i386/isa/vesa.c:1.32 Sat Jan 29
On Mon, Aug 19, 2002 at 01:22:52PM +0100, Josef Karthauser wrote:
Is it just me or is libstdc++ linking broken on -current right now?
I was able to compile kde3 yesterday ... you may have an old C++ header
in place which causes namespace issues. try removing them and doing the
installworld
On Mon, 19 Aug 2002 16:29:36 +0200 Radko Keves wrote:
Security Advisory FreeBSD-SA-02:38.signed-error
[patch output]
i know that patch wasn't for current, but is it needed to patch it ?
no. -current is the development branch and thus there are virtually
never advisories. -current is risky
my kernel can't detect fdc anymore when loading acpi. does anybody else
have such issues?
i know that it worked with a Aug 6 or a Aug 3 kernel, this was the last
time i accessed my fd0.
though reverting to a -D 08/06/2002 src/sys doesn't bring the desired
effect (working fdc).
if i prevent
On Mon, Aug 19, 2002 at 04:53:08PM +0200, Jan Stocker wrote:
for your own code, you seem to lack -lstdc++
This shouldn't be the prob...
You never have to add -lstdc++ by hand... using g++ to link has to
include it by itself.
yeah... I just did a little experimenting, seems to be a
Hi Josef,
On Mon, 19 Aug 2002 13:22:52 +0100
Josef Karthauser [EMAIL PROTECTED] wrote:
Is it just me or is libstdc++ linking broken on -current right now?
Remove /usr/include/g++ before making your next installworld.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
I've started to type in my mental sticky notes, have at it:
http://people.freebsd.org/~phk/TODO/
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
+---[ Poul-Henning Kamp ]--
|
| I've started to type in my mental sticky notes, have at it:
|
| http://people.freebsd.org/~phk/TODO/
Unfortunate choice of acronym there d8)
--
Totally Holistic Enterprises Internet| | Andrew Milton
The
Poul-Henning Kamp wrote:
I've started to type in my mental sticky notes, have at it:
http://people.freebsd.org/~phk/TODO/
Could you please modify reference to each of the tasks to be link to
the list of the relevant patches available so far, so that anybody who
wants to pick up the
In message [EMAIL PROTECTED], Maxim Sobolev writes:
Poul-Henning Kamp wrote:
I've started to type in my mental sticky notes, have at it:
http://people.freebsd.org/~phk/TODO/
Could you please modify reference to each of the tasks to be link to
the list of the relevant patches
On Thu, Aug 15, 2002 at 03:47:47PM -0700, Terry Lambert wrote:
And we all know how successful that was, right?
On the other side, we all know how successfull we were trying to get GCC
2.95.x bugs fixed for us, right? Do you really want to repeat this
deeply satisfying experiment
Hi!
Why can't we get rid of VOP_READ(.. UIO_NOCOPY...) call in sendfile()?
Me, I can't quite understand what UIO_NOCOPY means... As long as
sendfile() function already plays around pages, it can use VOP_GETPAGES().
The following patch looks works for me. Could anybody said if it has any
benefits
:Hi!
:
:Why can't we get rid of VOP_READ(.. UIO_NOCOPY...) call in sendfile()?
:Me, I can't quite understand what UIO_NOCOPY means... As long as
:sendfile() function already plays around pages, it can use VOP_GETPAGES().
:The following patch looks works for me. Could anybody said if it has any
unsubscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Aug 19, 2002 at 11:12:54AM -0400, Alexander Kabaev wrote:
Hi Josef,
On Mon, 19 Aug 2002 13:22:52 +0100
Josef Karthauser [EMAIL PROTECTED] wrote:
Is it just me or is libstdc++ linking broken on -current right now?
Remove /usr/include/g++ before making your next installworld.
On Mon, 19 Aug 2002, Matthew Dillon wrote:
:Why can't we get rid of VOP_READ(.. UIO_NOCOPY...) call in sendfile()?
:Me, I can't quite understand what UIO_NOCOPY means... As long as
:sendfile() function already plays around pages, it can use VOP_GETPAGES().
:The following patch looks works
Matthew N. Dodd wrote:
On Mon, 19 Aug 2002, Jason wrote:
Wierd, I have it running just peachy on a dual P3 900 box
Just so nobody else replies to this with something similar we're talking
about PENTIUMS.
Not the P3, P2, Alpha or anything else.
Yes. My ASUS Dual P90 machine has the
On Mon, 19 Aug 2002, Terry Lambert wrote:
Yes. My ASUS Dual P90 machine has the same problem. I just thought it
was the MP Spec compliance level of the BIOS, and gave up running
-current. I guess it's not just me. 8-(.
Its likely that we've got the same motherboard.
Mine is a
On Mon, Aug 19, 2002 at 01:56:38AM -0700, Don Lewis wrote:
This is getting triggered by the kern.vnode sysctl. SMP or UP?
SMP kernel, 1 processor until I find a lower profile heatsink.
Offhand
I have a hard time seeing how the sequence
vref(vp)
do cpu bound stuff
Poul-Henning Kamp wrote:
I've started to type in my mental sticky notes, have at it:
http://people.freebsd.org/~phk/TODO/
| Kernel stack depth warning.
|
| Write a function which checks the amount of kernel stack used and
| print a warning if it exceeds a sysctl-able limit.
| The
David O'Brien wrote:
And we all know how successful that was, right?
On the other side, we all know how successfull we were trying to get GCC
2.95.x bugs fixed for us, right? Do you really want to repeat this
deeply satisfying experiment again?
That was because the patches
On Sun, Aug 18, 2002 at 05:27:13PM -0700, Alex Zepeda wrote:
Should I set debug.witness_ddb to 1 and get a trace from it? Or has this
one already been seen?
It already fell over in exec, here's what it said:
GNU gdb 5.2.0 (FreeBSD) 20020627
Copyright 2002 Free Software Foundation, Inc.
GDB
Josef Karthauser wrote:
Is it just me or is libstdc++ linking broken on -current right now?
Kde3 complains:
c++ -DNDEBUG -DNO_DEBUG -O2 -O -pipe -march=pentiumpro -fmemoize-lookups
-fsave-memoized -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE
-DQT_NO_COMPAT
: call VOP_GETPAGES() on a block of pages instead of just one. I'm
: guessing that is not being done because it's about 100 lines of code
: to do it right. It's easier just to call vn_rdwr() and let the
: system do the clustering.
:
:This argument seems to apply to
On Mon, Aug 19, 2002 at 01:04:55PM -0700, Terry Lambert wrote:
Blah Terry, TOTALLY 110% INCORRECT. The situation was the same as our
FreeBSD 3.x users that still post PR's against RELENG_3 and want us to
fix things. Even where there was complete patches against 2.94.3
available; the
When I do a 'make obj' in /usr/src I get this fatal error:
/usr/src/lib/libc/locale/Makefile.inc: line 14
followed by a long error message.
Note that this error did not appear until after I did a
rm -rf /usr/obj and then a make obj.
The reason I did the rm /usr/obj is that I was getting
kernel
At 05:34 PM 8/19/2002 -0800, walt wrote:
When I do a 'make obj' in /usr/src I get this fatal error:
/usr/src/lib/libc/locale/Makefile.inc: line 14
followed by a long error message.
Note that this error did not appear until after I did a
rm -rf /usr/obj and then a make obj.
The reason I did the
Hey... I am new here and just want to check things out for a bit and see
if I can't pitch in...
At the very least I will try to build CURRENT from time to time and run
some programs... maybe somewhere down the road I can commit something
worthwhile.
I also wanted to see if my filter worked
I have gotten 3 ffs_blkfree() panics today (2 while background fsck'ing).
The most detail I've been able to get is:
dev=ad0s2a bno=544437089 bsize=16384 size=16384
panic: ffs_blkfree: bad size
cpuid=1, lapic.id=
a traceback shows:
ffs_blkfree()
indir_trunc()
On Mon, Aug 19, 2002 at 08:19:53PM -0500, [EMAIL PROTECTED] wrote:
Looking forward to working with you all...
What? Darwin wasn't good enough for you?
Yuk, yuk, yuk.
Good luck getting it running :)
- alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in
Darwin is just one of my pursuits :)
I am currently just going to play around with current when I have time :)
I actually do care to make FBSD 5.0 kickass if I can help... even as a
tester.
Dave
On Monday, August 19, 2002, at 09:13 PM, Alex Zepeda wrote:
On Mon, Aug 19, 2002 at 08:19:53PM
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Hey... I am new here and just want to check things out for a bit and see
if I can't pitch in...
At the very least I will try to build CURRENT from time to time and run
some programs... maybe somewhere down the road I can commit something
Thanks for the tip!
On Monday, August 19, 2002, at 09:21 PM, Mike Barcroft wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Hey... I am new here and just want to check things out for a bit and
see
if I can't pitch in...
At the very least I will try to build CURRENT from time to time
Hey List...
Today's kernel panics when starting kde. No panic screen just reboots.
Reverting to Saturday's kernel solves the problem.
Machine is a 500MHz Celeron, usually very stable even on -current.
Beech
--
---
Beech
If anyone is interested both David O'Brien and I are experiencing
what looks like data corruption under -current.
On a dual SMP AMD 1.9ghz box I'm seeing the vim port somehow corrupt
patched files.
I really don't have the time or energy to backtrack -current to
figure out when or why this
48 matches
Mail list logo
