MEXTFREE

2001-12-21 Thread Chad David
MEXTFREE results in a call to _mext_free() which is only defined within subr_mbuf.c, and is not static. Should the prototype be moved into sys/mbuf.h, or should MEXTFREE be moved into subr_mbuf.c, or is it ok like this? Thanks. -- Chad David[EMAIL PROTECTED] ACNS Inc. Calgary,

Re: vm_zeropage priority problems.

2001-12-21 Thread Bruce Evans
On Fri, 21 Dec 2001, Luigi Rizzo wrote: > Don't know how interesting this can be, but i am writing > (no plans to commit it, unless people find it interesting) > some code to implement a weight-based instead of priority-based > scheduler. The code is basically the WF2Q+ scheme which is > already

Re: MULTI_DRIVER_MODULE

2001-12-21 Thread Chad David
On Fri, Dec 21, 2001 at 09:55:37PM -0800, Peter Wemm wrote: > Chad David wrote: > > Does anybody have an example of how to call MULTI_DRIVER_MODULE? It > > looks broken to me, but I could of course be wrong... > > I would not recommend using it. Just use several DRIVER_MODULE > declarations as

Re: MULTI_DRIVER_MODULE

2001-12-21 Thread Peter Wemm
Chad David wrote: > Does anybody have an example of how to call MULTI_DRIVER_MODULE? It > looks broken to me, but I could of course be wrong... I would not recommend using it. Just use several DRIVER_MODULE declarations as required. In fact, I think I might remove it since nothing uses it yet.

MULTI_DRIVER_MODULE

2001-12-21 Thread Chad David
Does anybody have an example of how to call MULTI_DRIVER_MODULE? It looks broken to me, but I could of course be wrong... Thanks. -- Chad David[EMAIL PROTECTED] ACNS Inc. Calgary, Alberta Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current"

Yet another panic at pgfind()

2001-12-21 Thread Jun Kuriyama
This is yesterday's -current. Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = fault virtual address = 0x114 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01b6c40 stack pointer = 0x10:0xf1947cd8 frame pointe

Forward: if_fxp.c typo?

2001-12-21 Thread Jun Kuriyama
Hmm, -current has same problem. It should fix in -current... --- Begin Message --- Hi all, fxp_stop() of the latest fxp driver do SOFTWARE_RESET when called. Shouldn't this be SELECTIVE_RESET? As I'm not familiar with fxp, would someone check and commit it to the repositry? The current cod

subscribe

2001-12-21 Thread Tony Sterrett
subscribe -- We got a thousand points of light, For the homeless man We got a kinder gentler machine gun hand - Neil Young To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: spam

2001-12-21 Thread Julian Stacey
> I can only hope that our illustrious congress has grown as tired of > spam as I have and will fix the law to simply ban it. > -Matt That would help, (most SPAM I receive even in Germany is from USA), but spammers would move offshore from USA

KSE changes available

2001-12-21 Thread Julian Elischer
The latest round of KSE changes are available from http://www.freebsd.org/~julian/thediff These changes represent a work in progress. Basically the state is: GENERIC compiles (I don't know yet if it runs but I doubt it.) The following changes have been made: The 'thread' structure is no longer

Re: /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "__stdoutp"

2001-12-21 Thread Ruslan Ermilov
On Fri, Dec 21, 2001 at 11:53:49AM -0800, Doug White wrote: > On Fri, 21 Dec 2001, Jean Louis Ntakpe wrote: > > > Some binaries, especially from the ports tree on my > > system just failed to start, bringing the message: > > > > /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "

Re: /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol"__stdoutp"

2001-12-21 Thread Doug White
On Fri, 21 Dec 2001, Jean Louis Ntakpe wrote: > Some binaries, especially from the ports tree on my > system just failed to start, bringing the message: > > /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "__stdoutp" > > Could somebody give me a hint what I'm missing here. /u

/usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "__stdoutp"

2001-12-21 Thread Jean Louis Ntakpe
Hi, Some binaries, especially from the ports tree on my system just failed to start, bringing the message: /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol "__stdoutp" Could somebody give me a hint what I'm missing here. Since I couldn't start "cvsup", my system ist somewhat

Re: vm_zeropage priority problems.

2001-12-21 Thread Luigi Rizzo
Don't know how interesting this can be, but i am writing (no plans to commit it, unless people find it interesting) some code to implement a weight-based instead of priority-based scheduler. The code is basically the WF2Q+ scheme which is already part of dummynet, adapted to processes. It is quite

Re: vm_zeropage priority problems.

2001-12-21 Thread John Baldwin
On 21-Dec-01 Bruce Evans wrote: > On Fri, 21 Dec 2001, Luigi Rizzo wrote: > >> On Sat, Dec 22, 2001 at 12:46:40AM +1100, Bruce Evans wrote: >> > I think pri_native is just an implementation detail which shouldn't >> > be used or visible to threads. It used used by the priority propagation >> >

Re: FYI: Panic at in_pcbremlists()

2001-12-21 Thread Jun Kuriyama
At Fri, 21 Dec 2001 10:06:38 -0600 (CST), Jonathan Lemon wrote: > >I got a panic with today's current. I don't know I can reproduce this > >panic or not... > > This probably is in: > > 1015if (LIST_FIRST(&phd->phd_pcblist) == NULL) { > 1016LIST_RE

Re: FYI: Panic at in_pcbremlists()

2001-12-21 Thread Jonathan Lemon
In article [EMAIL PROTECTED]> you write: > >I got a panic with today's current. I don't know I can reproduce this >panic or not... This probably is in: 1015if (LIST_FIRST(&phd->phd_pcblist) == NULL) { 1016LIST_REMOVE(phd, phd_hash); 1017

panic on 12/20/01 current

2001-12-21 Thread Kenneth Culver
Hi, I have just managed to repetedly panic -CURRENT... How you ask? I'll tell you :-D The short story is "Run a linux version of XFree86," here's the long story: first, I got the linux version of XFree86, along with all it's driver modules (compliled under linux of course). Then in /usr/compat

Re: vm_zeropage priority problems.

2001-12-21 Thread Bruce Evans
On Fri, 21 Dec 2001, Luigi Rizzo wrote: > On Sat, Dec 22, 2001 at 12:46:40AM +1100, Bruce Evans wrote: > > I think pri_native is just an implementation detail which shouldn't > > be used or visible to threads. It used used by the priority propagation > > mechanism to hold the original pri_level.

FYI: Panic at in_pcbremlists()

2001-12-21 Thread Jun Kuriyama
I got a panic with today's current. I don't know I can reproduce this panic or not... Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0100 fault virtual address = 0x14 fault code = supervisor write, page not present instruction pointer = 0x8:0xc02141

Re: vm_zeropage priority problems.

2001-12-21 Thread Luigi Rizzo
On Sat, Dec 22, 2001 at 12:46:40AM +1100, Bruce Evans wrote: > I think pri_native is just an implementation detail which shouldn't > be used or visible to threads. It used used by the priority propagation > mechanism to hold the original pri_level. Threads should just use their > original priori

Re: vm_zeropage priority problems.

2001-12-21 Thread Bruce Evans
On Thu, 20 Dec 2001, John Baldwin wrote: > On 20-Dec-01 Luigi Rizzo wrote: > > On Thu, Dec 20, 2001 at 12:16:03PM -0800, John Baldwin wrote: > >> However, kthreads should tsleep() with their current priority, not PPAUSE. > > > > "current" meaning pri_level or pri_native ? What if one tries to > >

http://www.fun-club.net

2001-12-21 Thread [EMAIL PROTECTED]
ù‘–³—¿‚Åøò¶‚g 18Ë–¢–ž‚¨’f‚è ù‘ƒ}ƒjƒA•KŒ©ù©a’JŽü•Ó‚́gƒGƒbƒ`GAL`•Ï‘ԐlÈC•ƒƒŠƒƒŠ y‘¨300–¼zøòy¶'‚È‚Ü'ƒGƒbƒ`z ŽÊ^•tƒOƒ‰ƒrƒA–³—¿‚ÅŽw’èZŠ‚Ö‹}‘—ù© ù‚’´‹‰ØƒrƒfƒIùž‹­sŽû˜^‘±s’†! y‹ÆŠENO1‚Ì•i‘µ‚¦•ƒ}ƒjƒAƒbƒNz –³—¿‚ňê“xŒ©‚Äù© ‚¢ùž‚±‚ƃAƒ‹ƒˆ Úùvhttp://www.fun-club.net a’Jƒtƒ@ƒ“ƒNƒ