:> entirely contained within the current stack trace.
:All my kernels are now DDB kernels :) But since I do almost all of
:my work remotely they are DDB_UNATTENDED, and the machine I am panic-ing
:is not on the serial console server (sorry). I do have another question
:about DDB, I unstalled
> Another possibly re: debugging. If you compile up a kernel with
> options DDB and options BREAK_TO_DEBUGGER, the kernel will break into
> DDB when the panic occurs. You can then issue a 'trace' command to get
> a backtrace.
>
> This may be good enough to determine what the
:First, I would like to take this opportunity the thank Matt Dillon for
:his excellent work with NFS/TCP. Wow, way to go :)
:
:Now on to the real problem :)
:
:One of our users way able to reliably crash an NFS server 3 times today.
:I have since copied his program and have reliably crashed a sepe
Karl Denninger scribbled this message on May 21:
> One other suggestion, while I'm at it.
>
> The "dgb" driver has been marked "alpha quality" for a LONG time.
>
> I've had a fax server running on a PC/Xe 8 port card (64k shared RAM)
> for well over a year on one of these cards - and have NEVER h
One other suggestion, while I'm at it.
The "dgb" driver has been marked "alpha quality" for a LONG time.
I've had a fax server running on a PC/Xe 8 port card (64k shared RAM)
for well over a year on one of these cards - and have NEVER had a single
problem with it. That server gets a LOT of extre
Hi folks,
I've gotten my Ensoniq card installed and the driver configured, and it
works - sorta.
mpg123 has been the recommended "playback" mode for MPG files. Well and
fine.Except for one small problem:
If the system starts taking interrupts, I get "clicks", roughly
consona
On Fri, May 21, 1999 at 02:52:00PM -0600, Warner Losh wrote:
> In message <19990521114455.a...@denninger.net> Karl Denninger writes:
> : Got it.
>
> I'm still having my problem. I have the same lines in my kernel that
> yokota-san asked you to check...
>
> Warner
Well, the change to the atkb de
:In my view, the problem can be described like this.
:
:Some applications need to process data from their VA space, on some
:devices. If the data is going to/from a file, it looks perfectly
:well to copy it into kernel buffers, since the kernel does caching
:and improves disk I/O performance. Howev
> My hope was to map the user's buffer into kernel space so that I could do
> event driven io on the socket without having to context switch to an aiod
> for every io operation. Is this really a bad idea? I am a little
> concerned about running out of kernel address space, but I don't think
> tha
> > gdb -k kernel.1 vmcore.1
> > 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
> gdb -k kernel.1 vmcore.1
> 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.
> The
> > One of our users way able to reliably crash an NFS server 3 times today.
> > I have since copied his program and have reliably crashed a seperate and
> > unloaded machine with the exact same panic, "lockmgr: locking against
> > myself". I check the recent DG patches that went in after -RELEASE
In message <199905212052.oaa00...@harmony.village.org> Warner Losh writes:
: I'm still having my problem. I have the same lines in my kernel that
: yokota-san asked you to check...
Never mind
Warner
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in th
In message <19990521114455.a...@denninger.net> Karl Denninger writes:
: Got it.
I'm still having my problem. I have the same lines in my kernel that
yokota-san asked you to check...
Warner
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the
In message <19990521105306.a...@denninger.net> Karl Denninger writes:
: Note that this same config file (minus the "config" line that is deprecated
: and used to specify where root, swap, etc was) built the kernel that runs
: without problems a month or so back.
I'm seeing exactly the same thing w
On Fri, 21 May 1999, Mike Smith wrote:
> >
> > I really do not know how to describe the problem. But a friend here asks
> > me how to mmap a network buffer so that there is no need to copy the data
> > from user space to kernel space. We are not sure whether FreeBSD can
> > create a device file
Fixed, thanks!
Script started on Fri May 21 22:43:54 1999
relay# pwd
/usr/obj/usr/src/gnu/usr.bin/binutils/gdb
relay# ./gdb /bin/cat ./cat.core
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
>
>
> >I've got a problem that my KLD is "leaking" wired memory.
> >
> >It's not actually growing in size, vmstat -m shows a fairly constant
> allocation, >and certainly "high" isn't increasing. It's just that as I use it
> more, and more >memory gets wired down, and the system becomes unusable.
>
> I really do not know how to describe the problem. But a friend here asks
> me how to mmap a network buffer so that there is no need to copy the data
> from user space to kernel space. We are not sure whether FreeBSD can
> create a device file (mknod) for a network card, and if so, we can use t
On Fri, 21 May 1999, Ruslan Ermilov wrote:
> # uname -v
> FreeBSD 3.2-STABLE #0: Sun May 16 23:51:55 EEST 1999
> r...@relay.ucb.crimea.ua:/usr/src/sys/compile/CHYRO
>
> How to repeat:
Can you try this fix:
Index: solib.c
===
On Fri, 21 May 1999, Karl Denninger wrote:
> Diff follows.
>
> Note that this same config file (minus the "config" line that is deprecated
> and used to specify where root, swap, etc was) built the kernel that runs
> without problems a month or so back.
>
> I've looked through the commit logs an
>I've got a problem that my KLD is "leaking" wired memory.
>
>It's not actually growing in size, vmstat -m shows a fairly constant
allocation, >and certainly "high" isn't increasing. It's just that as I use it
more, and more >memory gets wired down, and the system becomes unusable.
[blah]
Just f
# uname -v
FreeBSD 3.2-STABLE #0: Sun May 16 23:51:55 EEST 1999
r...@relay.ucb.crimea.ua:/usr/src/sys/compile/CHYRO
How to repeat:
Script started on Fri May 21 21:20:49 1999
relay# cat
^\Quit (core dumped)
relay# gdb /bin/cat ./cat.core
GNU gdb 4.18
Copyright 1998 Free Software Foundation,
I really do not know how to describe the problem. But a friend here asks
me how to mmap a network buffer so that there is no need to copy the data
from user space to kernel space. We are not sure whether FreeBSD can
create a device file (mknod) for a network card, and if so, we can use the
mmap()
On Fri, 21 May 1999, Mark Tinguely wrote:
> (discussion moved from -questions to -hackers; bits included)
>
> > On Thursday, 20 May 1999 at 9:13:12 -0500, Mark Tinguely wrote:
> > > FYI:
> > >
> > > I am playing with the idea of a direct-insert PPP for future
> > SONET/ATM/DSL
> > > PPP
On Sat, 22 May 1999, Mark Newton wrote:
> Pavel Narozhniy wrote:
>
> > Does anybody heard about SGI releasing XFS source code?
>
> Yup, they're doing it.
>
> I would guess that FreeBSD would need a fairly thorough revamp of its
> handling of kernel memory allocation before XFS would be fully
Karl Denninger wrote:
>
> Got it.
>
> I figured it out just as you were sending this :-)
>
> This is one that should be noted somewhere (either in GENERIC or LINT);
> it bit me and it will bite others who have custom configuration files that
> they've been using for a while.
Like in /usr/src/UP
David Scheidt wrote:
>
> On 20 May 1999, R. Matthew Emerson wrote:
> :"Chuck Youse" writes:
> :> New daemon book?
> :> I must have missed that. Do you have the full title?
> :McKusick, Bostic, Karels, and Quarterman, The Design and Implementation
> :of the 4.4BSD Operating System, Addison-Wesley
I have found the problem and it is a problem with make. By chance I did
an ls -l of the directory and noticed the shared object was only 371
bytes and thought no that can't be right.
My makefile sez.
mysqlacc.so : mysqlacc.o
ld -Bshareable -o $@ $< -u _floor ../../lib/libV.a ...
Got it.
I figured it out just as you were sending this :-)
This is one that should be noted somewhere (either in GENERIC or LINT);
it bit me and it will bite others who have custom configuration files that
they've been using for a while.
--
--
Karl Denninger (k...@denninger.net) Web: fathers
>This morning I tried to boot that kernel. It comes up, but the console
>is dead! The DISPLAY is ok, but I have no keyboard control. Replugging
>the keyboard does not help.
>
>Here's the boot trace... (with a bit of annotation)
>
>Copyright (c) 1992-1999 The FreeBSD Project.
>Copyright (c) 1982,
> > 140c118,119
> > < devicesc0 at isa?
> > ---
> > > devicesc0 at isa?
> > >
> >
> > Why does this one show up? It shouldn't. You might want to retype it to
> > make sure there is no bogus char in there somewhere.
>
> There's a space after the
> Pavel Narozhniy wrote:
>
> > Does anybody heard about SGI releasing XFS source code?
>
> Yup, they're doing it.
>
> I would guess that FreeBSD would need a fairly thorough revamp of its
> handling of kernel memory allocation before XFS would be fully usable,
> though: XFS buffer management i
> > I want to convert these kernel options to sysctl variables. Where
> > should they be inserted into the tree? I was thinking of creating a
> > new 'cam' top-level category and put them there:
> >
> > cam.sa.space_timeout
> > cam.sa.rewind_timeout
> > cam.sa.erase_timeout
>
> These should
> I want to convert these kernel options to sysctl variables. Where
> should they be inserted into the tree? I was thinking of creating a
> new 'cam' top-level category and put them there:
>
> cam.sa.space_timeout
> cam.sa.rewind_timeout
> cam.sa.erase_timeout
These should be per-device par
On Fri, May 21, 1999 at 06:02:17PM +0200, Nick Hibma wrote:
> > < # atkbdc0 controlls both the keyboard and the PS/2 mouse
> > < controller atkbdc0 at isa? port IO_KBD
> > < device atkbd0 at isa? irq 1
> > < device psm0at isa? irq 12
> > ---
> > > # atkbdc0 con
> > Level-triggered interrupts are persistent conditions, not queueable
> > events. They typically require device-driver level intervention to be
> >
> > cleared. This is a major error in the PCI design (no surprises
> > there).
> >
> [ML] Whoa there! That's the MAJOR advantage of PCI
> < # atkbdc0 controlls both the keyboard and the PS/2 mouse
> < controller atkbdc0 at isa? port IO_KBD
> < device atkbd0 at isa? irq 1
> < device psm0at isa? irq 12
> ---
> > # atkbdc0 controls both the keyboard and the PS/2 mouse
> > controller atkbdc0 at isa?
Oh, one more thing.
When I say "locked up", I mean "locked".
As in the Numlock key doesn't toggle the LED state, neither does CAPS LOCK.
--
--
Karl Denninger (k...@denninger.net) Web: fathers.denninger.net
I ain't even *authorized* to speak for anyone other than myself, so give
up now on tryin
Diff follows.
Note that this same config file (minus the "config" line that is deprecated
and used to specify where root, swap, etc was) built the kernel that runs
without problems a month or so back.
I've looked through the commit logs and can't find anything that would lead
me to believe that m
Karl Denninger wrote:
>
> On Fri, May 21, 1999 at 05:37:40PM +0200, Graham Wheeler wrote:
> > Karl Denninger wrote:
> > >
> > > Hi folks,
> > >
> > > I built a new kernel last night and started a buildworld before going to
> > > bed. Just a "tracking" type of thing to see what the state of the wo
Hello,
Playing with nwfs I found that kernel execve routine calls
VOP_OPEN without following VOP_CLOSE. Instead it just do vrele which
causes call to VOP_INACTIVE. For other cases it seems that OPEN/CLOSE are
always called in pair.
This doesn't looks like a big problem bec
Could you post a diff against a GENERIC? If possible zap the GENERIC
file first and recreate it with a 'cvs update' if you have a repository
available, or with 'cvsup' if not.
Nick
On Fri, 21 May 1999, Karl Denninger wrote:
> On Fri, May 21, 1999 at 05:37:40PM +0200, Graham Wheeler wrote:
>
On Fri, May 21, 1999 at 05:37:40PM +0200, Graham Wheeler wrote:
> Karl Denninger wrote:
> >
> > Hi folks,
> >
> > I built a new kernel last night and started a buildworld before going to
> > bed. Just a "tracking" type of thing to see what the state of the world
> > is on FreeBSD.
> >
> > This
Karl Denninger wrote:
>
> Hi folks,
>
> I built a new kernel last night and started a buildworld before going to
> bed. Just a "tracking" type of thing to see what the state of the world
> is on FreeBSD.
>
> This morning I tried to boot that kernel. It comes up, but the console
> is dead! The
Hi folks,
I built a new kernel last night and started a buildworld before going to
bed. Just a "tracking" type of thing to see what the state of the world
is on FreeBSD.
This morning I tried to boot that kernel. It comes up, but the console
is dead! The DISPLAY is ok, but I have no keyboard co
These may go away soon as currently constituted because they are properly
a per-device type value.
On 21 May 1999, Dag-Erling Smorgrav wrote:
> I want to convert these kernel options to sysctl variables. Where
> should they be inserted into the tree? I was thinking of creating a
> new 'cam' t
On Fri, 21 May 1999, Zhihui Zhang wrote:
> (1) Open the file as read and write, using one file descriptor.
> (2) Open the file as read only and open it again as write only, using a
> total of two file descriptors.
>
> Method (2) is more clear in logic and uses a little more resource (file
you'
Doug Rabson wrote:
> On Thu, 20 May 1999, John Polstra wrote:
>
>> In article <373c3f3f.a99db...@cablenet.net>,
>> Damian Hamill wrote:
>> > I have a program that is dumping core.
>> >
>> > ---
>> > Here's the gdb output;
>> >
>> > Program termina
If I want to read and write a file, I can do it in two ways:
(1) Open the file as read and write, using one file descriptor.
(2) Open the file as read only and open it again as write only, using a
total of two file descriptors.
Method (2) is more clear in logic and uses a little more resource (f
Pavel Narozhniy wrote:
> Does anybody heard about SGI releasing XFS source code?
Yup, they're doing it.
I would guess that FreeBSD would need a fairly thorough revamp of its
handling of kernel memory allocation before XFS would be fully usable,
though: XFS buffer management is pretty full-on.
[.]
> > Why are you thinking of using user PPP for this? As you say, at the
> > data rates you're thinking of, it's not an optimal solution.
>
> no, only the LCP, NCP, authenication, dignostic messages for debugging
> is done in user space. this is small traffic to setup/maintain/tear down
Hello
Does anybody heard about SGI releasing XFS source code?
I had read article in Russian ZDnews about this issue. Author wrote
about Caldera people porting this journaling, 64-bit filesystem to
Linux.
[HE-He, time for question ;) ]
What about FreeBSD? Any plans?
P.S. Sorry for my poor Engl
On Fri, May 21, 1999 at 09:46:46AM -0400, Chuck Youse wrote:
> Is there any particular reason why this hasn't been pulled into the main
> tree? It's been around for a while, and in my experience performs stably.
> (on 2.2.x anyway). I was shocked when I discovered that I still needed to
> grab th
Is there any particular reason why this hasn't been pulled into the main
tree? It's been around for a while, and in my experience performs stably.
(on 2.2.x anyway). I was shocked when I discovered that I still needed to
grab the drivers and install them separately for 3.x.
Chuck Youse
Director
On Thu, 20 May 1999, Dan Moschuk wrote:
>
> | ¿Have you considered PostgreSQL? It is on the ports collection, and is a
> | heavy duty database engine, with transactions, subqueries (only partial
> | support), etc. Version 6.5 will be released in about two weeks, and it
> | adds MVCC (multi-versi
(discussion moved from -questions to -hackers; bits included)
> On Thursday, 20 May 1999 at 9:13:12 -0500, Mark Tinguely wrote:
> > FYI:
> >
> > I am playing with the idea of a direct-insert PPP for future SONET/ATM/DSL
> > PPP connections. here compression/ACCM are not a concern but higher
> I am currently having the author of the SDL-library on my box trying to
> cook up a port of the SDL-library for FreeBSD.
>
> SDL (Simple DirectMedia Layer) is the library used by Loki Software to
> build CIV:CTP
>
> As I have seen now the entire library works perfectly ;-)
>
> except for one t
> 1> Could it be possible to unite these ones in /src/sys/boot/i386/mbr/ ?
>
> It could be possible, yes. :)
>
> - Jordan
Seems a good idea: I'll do that, unless of course Ruslan wants to do
it himself.
At least one of the present MBRs is a bit too strictly correct,
and supports booting only fr
> Hi folks,
>
> When giving credit where it's due in my code, should I mention the
> code that I looked at, or the code on which _that_ was based?
>
> Put graphically:
>
> pkgA written by personA
>
> pkgB written by personB bits stolen from pkgA by personA
a couple of parentheses above
Hi folks,
When giving credit where it's due in my code, should I mention the
code that I looked at, or the code on which _that_ was based?
Put graphically:
pkgAwritten by personA
pkgBwritten by personB bits stolen from pkgA by personA
I am writing
pkgCwritten by personC (me)
On Fri, May 21, 1999 at 02:49:34AM -0700, Jordan K. Hubbard wrote:
> 1> Could it be possible to unite these ones in /src/sys/boot/i386/mbr/ ?
>
> It could be possible, yes. :)
>
> - Jordan
Well, probably my English is not so good, I'm sorry.
What's so funny?
--
Ruslan Ermilov Sysadmin
1> Could it be possible to unite these ones in /src/sys/boot/i386/mbr/ ?
It could be possible, yes. :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Hi!
Apparently, we have two distinct MBRs in the sources.
First one is in /usr/src/sbin/i386/fdisk.c, and could be
installed onto disk by ``fdisk -b'', for example.
The second one is in /usr/src/release/sysinstall/wizard.c,
and could be installed onto disk by ``sysinstall''.
It is confusing...
On Thu, 20 May 1999, Dan Moschuk wrote:
>
>| ¿Have you considered PostgreSQL? It is on the ports collection, and is a
>| heavy duty database engine, with transactions, subqueries (only partial
>| support), etc. Version 6.5 will be released in about two weeks, and it
>| adds MVCC (multi-version con
I want to convert these kernel options to sysctl variables. Where
should they be inserted into the tree? I was thinking of creating a
new 'cam' top-level category and put them there:
cam.sa.space_timeout
cam.sa.rewind_timeout
cam.sa.erase_timeout
DES
--
Dag-Erling Smorgrav - d...@flood.pin
On Thu, 20 May 1999, John Polstra wrote:
> In article <373c3f3f.a99db...@cablenet.net>,
> Damian Hamill wrote:
> > I have a program that is dumping core.
> >
> > ---
> > Here's the gdb output;
> >
> > Program terminated with signal 6, Abort trap.
>
On Fri, 21 May 1999, Ladavac Marino wrote:
> > -Original Message-
> > From: Mike Smith [SMTP:m...@smith.net.au]
> > Sent: Friday, May 21, 1999 2:16 AM
> > To: Joel Ray Holveck
> > Cc: Doug Rabson; Peter Wemm; Tommy Hallgren;
> > freebsd-hackers@FreeBSD.ORG
> > Subject:Re: L
> -Original Message-
> From: Mike Smith [SMTP:m...@smith.net.au]
> Sent: Friday, May 21, 1999 2:16 AM
> To: Joel Ray Holveck
> Cc: Doug Rabson; Peter Wemm; Tommy Hallgren;
> freebsd-hackers@FreeBSD.ORG
> Subject: Re: Lazy SPLs
>
> >
> > Why mask out the interrupts at all, instea
On Tue, May 18, 1999, Roger Hardiman wrote:
> I suppose the problems will be in Netscape and my XiGs Accel X 4.1.
Running a 4.0-CURRENT system always updated via CVSup (never
used snapshots), I can testify that the best way of keeping aout
compatibility is really just compiling world with -DWAN
70 matches
Mail list logo
