ib/libc_r.so.5
#2 0x281b6015 in _thread_exit () from /usr/lib/libc_r.so.5
#3 0x281af42e in _pq_init () from /usr/lib/libc_r.so.5
#4 0x281b1cd5 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5
#5 0x0 in ?? ()
/ Thomas Stromberg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, 26 Aug 2000, Mike Smith wrote:
> This is not an "IDE RAID" controller. It's an IDE controller with some
> lame "RAID" software in the BIOS. We don't support this.
Hopefully this thread will save the next poor soul who tries this.
Just to put the final nail in the coffin.. I went ahea
(excuse complete ignorance as far as IDE RAID below)
For the buildbox here, I decided to go ahead with Soren's ATA-100 RAID
suggestion, and bought an Abit KT7-RAID motherboard, which has an onboard
Highpoint HPT-370 ATA-100 RAID. I'm using two 15G IBM 75GX drives on it.
So after a long day of ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephan van Beerschoten wrote:
> btw, I have some big problems with the new version of mtree .. it seems
that
> the -L flag has been abandoned.. which results in almost every port I try
> to install failing.. I have recompiled mtree from the tree and
Doug White wrote:
>
> On Wed, 19 Jul 2000, Doug Barton wrote:
> > As for geometry, I tried both with and without "dangerously
> > dedicated." My understanding was that if I used the dos partition entry
> > method that we should be able to pick up the geometry correctly, but
> > should I try
le commerce, inc. 1.919.657.1317
bless(\$Perl++);# the power to hack. http://www.perl.com/
#include/* the power to serve. http://www.freebsd.org/ */
On Thu, 6 Jul 2000, Doug Barton wrote:
> On Thu,
'panic: RAM parity error, likely hardware failure.'
This one had me confused at first, because it blamed a RAM parity
error. As this is a brand new machine (Gateway GP-800), so I first thought
I got a bad batch. Then I realized this only happens with apps that try to
do sound stuff. It's also dou
For now I'm just using mpg123 (gqmpeg works too of course, as a front-end,
but I hate it's list manager).. mpg123 seems to work fine on all of my
-current machines.
thomas r. stromberg [EMAIL PROTEC
As far as keeping them "up to date", this is what we do:
- Have a local cvsup-mirror server
- All FreeBSD workstations and servers cvsup (just ports) off of it
nightly.
- Our central build server (which doubles as an insanely overpowered SMP
dns server), builds -STABLE, and all kernels nightly
Sorry about the html posting, it seems that Mozilla M13 decided to rape my
message. I hate html postings just as much as you do (thank god for
procmail filters), and will send this one using pine so Mozilla doesn't
try to rethink my e-mail for me.
Kernel:
===
FreeBSD karma.afterthought.org
Just letting you guys know, the nasty multiple-read bug in procfs still
exists. I'm preparing a new smashwidgets report for 4.0 (should be ready
for tommorow, will post here), and in the process happened to shoot myself
in the foot by having two breakwidgets scripts go simultaneously. breakwidg
We're currently looking at upgrading several of our FreeBSD servers
(dual PIII-600's, 66MHz PCI) and some Sun Ultra's to Gigabit Ethernet.
We plan to hook these machines into our Cisco Catalyst 5000 server. They
will most likely move to be running FreeBSD 4.x by the time that we
actually get our b
On 13-Jan-2000 Matthew Dillon wrote:
>:> Sometimes we just want to nfs-mount things on the same
>:> machine.
>:
>:Sick, poor in performance and the wrong tool for the job.
>:See mount_null(8) for more details on how to do it right.
>:
Unfortunately, you still end up needing to do this for some
"Andrey A. Chernov" wrote:
>
> On Tue, Nov 30, 1999 at 10:49:57AM -0500, Thomas Stromberg wrote:
> > [root@karma] dumpon> dumpon /dev/wd0s1b
> > dumpon: /dev/wd0s1b: must specify a block device
> > [root@karma] dumpon> dumpon /dev/rwd0s1b
> &g
"
> I see no needs of this change. I have -current dumpon/savecore work with
> old entrly like /dev/wd0...
> savecore understand both character and old block devices now.
>
While I see your commit in cvsweb to savecore, I still run into this
(just cvsupp'd off of cvsup6.freebsd.org and rebuilt i
While this was mentioned in the commit log for dumpon.c by phk, I figure
I'd save you the loss of a kernel core to find out like the one I lost
this morning. In rc.conf (or wherever you load dumpon) make sure you
change it to using a raw device. dumpon no longer accepts block devices,
as they were
> :If you notice, both times it crashed on vm_map_insert.
>
> Try bumping up PMAP_SHPGPERPROC. From LINT:
>
> #
> # Set the number of PV entries per process. Increasing this can
> # stop panics related to heavy use of shared memory. However, that can
> # (combined with large amounts of ph
While doing some testing (and actually, in the middle of me trying to
post some results) for the FreeBSD Auditing project, my 4.0-CURRENT box
crashed. These tests involved a barrage of automated exec() calls which
I suspect is what tore it down. I had a similar crash two weeks ago, but
did not hav
David O'Brien wrote:
>
> On Thu, Nov 11, 1999 at 03:29:05PM -0500, Thomas Stromberg wrote:
> > I just happened to notice this today. For some reason 'grep' seems to
> > think that 'set' output is binary, not text. Seems that GNU grep 2.3 is
> >
I just happened to notice this today. For some reason 'grep' seems to
think that 'set' output is binary, not text. Seems that GNU grep 2.3 is
a little too sensitive to text/binary detection. This only seems to
affect -CURRENT because -STABLE runs GNU grep 2.0. (This was committed
October 28th).
;smartest'
way, seeing as anyone who is running a serious firewall would disable
kld's immediately anyhow.
So my question is, what's the direction we're taking here?
--
=======
Thomas Stromberg,
CURRENT #0: Tue
Oct 12 14:23:39 EDT 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/SPENTA_MAINYU i386
--
=======
Thomas Stromberg, Assistant IS Manager / Systems Guru
smtp:[EMAIL PROTECTED]
.0 on pci0
pcm0: using I/O space register mapping at 0x1080
es1371: codec vendor revision 0
es1371: codec features none
es1371: stereo enhancement: no 3D stereo enhancement
--
=======
Thomas Stromberg, Assis
it.. but it still remains an issue for me. Still get that panic
(though it is almost assuredly the problem, as the next event IS the PNP
probe).
This is of course, assuming I'm not misunderstanding something.
--
Med vanlig halsingar,
----------
= DPL 0, pres 1, def32 0, gran 0
processor eflags= interrupt enabled, resume, IOPL = 0
current process = Idle
interrupt mask = net tty bio cam
kernel: type 9 trap, code=0
Stopped at 0xbc28:
--
Med vanlig halsingar,
---------
25 matches
Mail list logo