Re: Yet another crash in FreeBSD 5.1

On Sunday, 3 August 2003 at 0:31:45 -0400, John Baldwin wrote: > > On 03-Aug-2003 Greg 'groggy' Lehey wrote: >> On Saturday, 2 August 2003 at 16:47:13 +0200, Eivind Olsen wrote: >>> [EMAIL PROTECTED]:~/tmp/debug > gdb -k kernel.debug >>> (kgdb) list *(g_dev_strategy+29) >> >> This is almost cert

Re: Yet another crash in FreeBSD 5.1

On 03-Aug-2003 Greg 'groggy' Lehey wrote: > On Saturday, 2 August 2003 at 16:47:13 +0200, Eivind Olsen wrote: >> --On 2. august 2003 02:11 -0700 Terry Lambert <[EMAIL PROTECTED]> >> wrote: db> trace g_dev_strategy(c2156024,c2153800,0,cfb528d0,c2099eca) at g_dev_strategy+0x29 launch

RE: Waiting on "allproc" w/ with non-sleepable locks held

On 01-Aug-2003 Lars Eggert wrote: > Hi, > > yet another funky console message with today's -current: > > Waiting on "allproc" with the following non-sleepablelocks held: > exclusive sleep mutex callout_dont_sleep r = 0 (0xc0371fa0) locked @ > /usr/src/sys/kern/kern_timeout.c:223 > > Got this t

RE: spin lock sched lock held for > 5 seconds

On 01-Aug-2003 Lars Eggert wrote: > Hi, > > got the following panic overnight running with all debugging options on > (WITNESS, MUTEX_DEBUG, DIAGNOSTIC, INVARIANTS; WITNESS_SKIPSPIN off): > > panic: spin lock sched lock held by 0xc658e130 for > 5 seconds > cpuid = 0; lapic.id = > Stack

RE: Fatal trap 12 under RELENG_5_1, anyone who can help?

On 01-Aug-2003 Eivind Olsen wrote: > Hello. > My FreeBSD RELENG_5_1 server (cvsupped 4 days ago) seems to have problems - > it crashes from time to time (approx. once a day). > > I've rebuilt the kernel with debug-symbols and enabled the debugger and > caught a crash tonight: > > Here's what I

RE: panic: blockable sleep lock (sleep mutex) sellck @kern/sys_generic.c:1192

On 01-Aug-2003 [EMAIL PROTECTED] wrote: > > Hi, I am running FreeBSD-5.1 current (cvsup from yesterday). > I got a SB Audigy 2, using the OSS > commercial sound drivers. I have been using the OSS > drivers without too much trouble in a 5.1-current > system of like 4 weeks ago (but I decided to f

port 0xd800-0xd80f at device 7.1on pci0

with dma enabled, a sysinstall will only work under the minimal install, and after a certain point, apparently using too much hard drive space (showed up with a tar -xvf ports.tar) causes a panic with anic errors disabling dma seems to solve all of my problems (just runs slowly, of course)

Re: Yet another crash in FreeBSD 5.1

I fear we may have gotten a bit off-topic. E From: Greg 'groggy' Lehey <[EMAIL PROTECTED]> To: Terry Lambert <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Yet another crash in FreeBSD 5.1 Date: Sun, 3 Aug 2003 11:21:41 +0930 On Saturday, 2 August 2003 at 18:36:24 -0700

Re: Yet another crash in FreeBSD 5.1

On Saturday, 2 August 2003 at 18:36:24 -0700, Terry Lambert wrote: > Greg 'groggy' Lehey wrote: >>> The information I gave him gets him to lines of source code, instead >>> of just function names with strange hexadecimal numbers that resolve >>> to instruction offsets that may be specific to his c

Re: Yet another crash in FreeBSD 5.1

Greg 'groggy' Lehey wrote: > > The information I gave him gets him to lines of source code, instead > > of just function names with strange hexadecimal numbers that resolve > > to instruction offsets that may be specific to his compile flags, > > date of checkout of the sources from CVS, etc.. > >

Re: Yet another crash in FreeBSD 5.1

Greg 'groggy' Lehey wrote: > > If this is repeatable for you, it's recommended that you compile > > Vinum statically into your kernel, so that you can look at the > > other symbols in the traceback and obtain source lines for them, > > as well. > > No. It is explicitly discouraged. It saves the

Re: Yet another crash in FreeBSD 5.1

On Saturday, 2 August 2003 at 18:06:36 -0700, Terry Lambert wrote: > Greg 'groggy' Lehey wrote: >>> Please take a look at an older thread named (IIRC) vinum or geom bug? >>> Greg asked for special debug output, but it never happened again for me. >>> A real murphy bug - it happend on three machine

Re: Yet another crash in FreeBSD 5.1

On Saturday, 2 August 2003 at 17:56:49 -0700, Terry Lambert wrote: > Greg 'groggy' Lehey wrote: >>> You don't actually need a crash dump to debug a stack traceback. >> >> Great! So you know the answer? Please submit a patch. >> >> Seriously, this is nonsense. Yes, it's a null pointer dereferenc

Re: Yet another crash in FreeBSD 5.1

Terry Lambert wrote: > There's no reason to be paranoid about your baby with me; unlike > some people, personally I like Vinum, so relax and realize that > I'm not trying to blame your code by trying to help him squeeze > more information out of the data he *is* able to gather. To follow this up:

Re: Yet another crash in FreeBSD 5.1

On Saturday, 2 August 2003 at 17:54:03 -0700, Terry Lambert wrote: > Eivind Olsen wrote: >> (kgdb) list *(launch_requests+448) >> No symbol "launch_requests" in current context. >> (kgdb) list *(vinumstart+2b2) >> No symbol "vinumstart" in current context. >> (kgdb) >> >> If anyone wants to take a

Re: Yet another crash in FreeBSD 5.1

Greg 'groggy' Lehey wrote: > > Please take a look at an older thread named (IIRC) vinum or geom bug? > > Greg asked for special debug output, but it never happened again for me. > > A real murphy bug - it happend on three machines once a day and after > > Gregs response nothing happened over weeks.

Re: Yet another crash in FreeBSD 5.1

Greg 'groggy' Lehey wrote: > > You don't actually need a crash dump to debug a stack traceback. > > Great! So you know the answer? Please submit a patch. > > Seriously, this is nonsense. Yes, it's a null pointer dereference. > What? That is precisely what doing what I suggested discovers, Gre

Re: Yet another crash in FreeBSD 5.1

Eivind Olsen wrote: > (kgdb) list *(launch_requests+448) > No symbol "launch_requests" in current context. > (kgdb) list *(vinumstart+2b2) > No symbol "vinumstart" in current context. > (kgdb) > > If anyone wants to take a look at this themselves I've put the compressed > (gzip) debug-kernel avail

Re: bge & vlan stranges

Tom Samplonius wrote: > Probably wouldn't be affective anyhow. L2 switches assume that they can > encapsulate 1500 byte ethernet frames into 802.1q properly. It is part of > the 802.1q standard. If the NIC can't understand the frame because it is > now 1504 bytes, it will be a layer 2 discard.

Re: Yet another crash in FreeBSD 5.1

On Saturday, 2 August 2003 at 16:47:13 +0200, Eivind Olsen wrote: > --On 2. august 2003 02:11 -0700 Terry Lambert <[EMAIL PROTECTED]> > wrote: >>> db> trace >>> g_dev_strategy(c2156024,c2153800,0,cfb528d0,c2099eca) at >>> g_dev_strategy+0x29 launch_requests(c299bf00,0,1,,47) at >>> lau

Re: Yet another crash in FreeBSD 5.1

On Saturday, 2 August 2003 at 17:00:59 +0200, Eivind Olsen wrote: > --On 2. august 2003 11:16 +0200 Bernd Walter <[EMAIL PROTECTED]> > wrote: >>> Looks like a problem in vinum. The other backtrace was the same, right? >> Please take a look at an older thread named (IIRC) vinum or geom bug? >> Gre

Re: Yet another crash in FreeBSD 5.1

On Saturday, 2 August 2003 at 2:11:24 -0700, Terry Lambert wrote: > Eivind Olsen wrote: >> Can anyone suggest what I do next to find out about this crash? > >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0x14 > > Dereference of NULL pointer; reference is for elemen

Re: bge & vlan stranges

Boris Kovalenko wrote: > No, this is test machine, I have installed it two days ago and have > firewall_type="OPEN" in my settings. So I have not disabled MTU path > discovery You are speaking of. Nevertheless, what is "substracted from > available MTU?" Why? The correct way it should work: > 1500

Re: groff and mkdep?

I wasn't running make with -e. I believe the commandline was similar to 'make -DNO_KERBEROS -DNO_WERROR buildworld', and never saw miscellaneous switches passed. So, yeah, it worked only after I unset CFLAGS and CXXFLAGS for that session's environment. Like I said, I'm generally new to this. Not so

Re: Anyone use WINE at all anywhere?

From: "Julian Elischer" <[EMAIL PROTECTED]> > > Is the re ANYONE that uses wine on -current...? > > for that matter, a -current user that uses wine on 4.x? > I set up wine on current to run D2GS (Diablo II Game Server) using XVFB. I haven't used wine for any other purposes than this. Scot

Re: Anyone use WINE at all anywhere?

On Fri, Aug 01, 2003 at 05:38:33PM -0700, Julian Elischer wrote: > Is the re ANYONE that uses wine on -current...? Sure, I use wine on current. However, the problems I seem to be getting are wine related and not due to problems with fbsd.. as far as I can tell. - alex _

Re: newsyslog problems with -C

At 2:38 AM +0200 8/2/03, Riccardo Torrini wrote: Looking into sources I found two close(fd). Here is the patch: -8<-[ patch ]-8<- # diff -u newsyslog.c.orig newsyslog.c --- newsyslog.c.origSun May 25 18:46:13 2003 +++ newsyslog.c Sat Aug 2 02:28:50 2003 @@ -1764,7 +1764,6 @@

Re: [PATCH] jail NG schript patch for mounting devfs and procfsautomatically

On 02.08.2003 01:29, Mike Makonnen wrote: On Tue, Jul 29, 2003 at 08:27:07PM +0200, Jens Rehsack wrote: On 29.07.2003 19:21, Mike Makonnen wrote: >On Tue, Jul 29, 2003 at 07:08:38PM +0200, Jens Rehsack wrote: >Yeah, I'll take care of this. I had asked scott to mail me his final >patch so I could c

Re: vfprintf() has a 4096-byte memory leak?

In the last episode (Aug 02), Ryan T. Dean said: > Aha. setbuf(stdout, NULL); does prevent the buffer from being > allocated. However, in the case of stdout and stderr, if you don't > setbuf() it to null, a buffer is malloc'd. The corresponding free() > is in fclose. So, if you [f]printf() to st

Re: Mozilla V1.3.1 crashing on FreeBSD 5.1-C (older cvsup level)

On Sat, 2003-08-02 at 16:20, Tom Parquette wrote: > Periodically, Mozilla V1.3.1 will appear to crash on some web sites. > I finally got the following messages out of it. It's not much but I was > hoping someone might have an idea. > > This was from an attempt to point at www.historychannel.com.

Re: bge & vlan stranges

On Sat, 2 Aug 2003, Terry Lambert wrote: ... > I suppose you want to do this because you are trunking a channel > that goes to a border device, and for some reason you have disabled > receipt of all ICMP, instead of only abusable ICMP, and thus you > have broken end-to-end path MTU discovery. >

Mozilla V1.3.1 crashing on FreeBSD 5.1-C (older cvsup level)

Periodically, Mozilla V1.3.1 will appear to crash on some web sites. I finally got the following messages out of it. It's not much but I was hoping someone might have an idea. This was from an attempt to point at www.historychannel.com. TIA $ export DISPLAY=Stargate.Tom.Parquette.name:0 $ mozi

ACLS on UFS2 from FreeBSD 5.1-RELEASE install.

Has anyone noticed the ACLS being disabled? tunefs -p /dev/da1s1c shows that ACLS are disabled on every partition I have, i've gone through them all. any reason why? tunefs: ACLs: (-a) disabled tunefs: MAC multilabel: (-l) d

Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)

On Sat, Aug 02, 2003 at 01:53:31AM -0700, Terry Lambert wrote: > Marcel Moolenaar wrote: > > But if we only use the dynamic allocation then it can only fail for > > a combination of 3rd party code. > > You meant to say static here, e.g. when there are two libraries > linked into a single aplicatio

[current tinderbox] failure on i386/i386

___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"

[current tinderbox] failure on amd64/amd64

TB --- 2003-08-02 17:11:23 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2003-08-02 17:11:23 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-08-02 17:13:57 - building world TB --- cd /

Re: groff and mkdep?

On Fri, Aug 01, 2003 at 11:08:33PM -0700, Peorth wrote: > That seems so weird. > CFLAGS and CXXFLAGS were set to something in the general environment, > for non-port builds, but I thought the FreeBSD make system used for > ports and such wouldn't get polluted by simply having that defined as a > va

[current tinderbox] failure on alpha/alpha

TB --- 2003-08-02 16:00:07 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-08-02 16:00:07 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-08-02 16:02:22 - building world TB --- cd /

Re: MSDOSFS woes

On Sat, 2 Aug 2003, Ruslan Ermilov wrote: > While working with Marcel on a bootable CD-ROM for IA64 issue, > I've stumbled upon the following problem. I needed to increase > the size of the EFI partition (which is an MS-DOS file system) > to 64M, and that made two of my machines stuck solidly --

Re: [current tinderbox] failure on i386/i386

Scott Long <[EMAIL PROTECTED]> writes: > Anyone know what is up with this? I'm not getting it on my LINT builds. revision 1.41 date: 2003/08/01 17:00:49; author: obrien; state: Exp; lines: +1 -1 Fix kernel build -- 'c' was the unused var, not 'lines'. DES -- Dag-Erling Smørgrav - [EMAIL PROT

Re: MSDOSFS woes

On Sat, Aug 02, 2003 at 05:00:45PM +0100, Bruce Cran wrote: > On Sat, Aug 02, 2003 at 06:08:50PM +0300, Ruslan Ermilov wrote: > > Gang, :-) > > > > While working with Marcel on a bootable CD-ROM for IA64 issue, > > I've stumbled upon the following problem. I needed to increase > > the size of the

Re: MSDOSFS woes

On Sat, Aug 02, 2003 at 06:08:50PM +0300, Ruslan Ermilov wrote: > Gang, :-) > > While working with Marcel on a bootable CD-ROM for IA64 issue, > I've stumbled upon the following problem. I needed to increase > the size of the EFI partition (which is an MS-DOS file system) > to 64M, and that made

Re: [current tinderbox] failure on i386/i386

Anyone know what is up with this? I'm not getting it on my LINT builds. Scott Tinderbox wrote: TB --- 2003-08-02 06:21:10 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-08-02 06:21:10 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -

MSDOSFS woes

Gang, :-) While working with Marcel on a bootable CD-ROM for IA64 issue, I've stumbled upon the following problem. I needed to increase the size of the EFI partition (which is an MS-DOS file system) to 64M, and that made two of my machines stuck solidly -- a lot of process are waiting on the "wdr

Re: vinum bug? (Re: Yet another crash in FreeBSD 5.1)

--On 2. august 2003 11:16 +0200 Bernd Walter <[EMAIL PROTECTED]> wrote: Looks like a problem in vinum. The other backtrace was the same, right? Please take a look at an older thread named (IIRC) vinum or geom bug? Greg asked for special debug output, but it never happened again for me. A real mur

usbd does not use detach

Hi, my usbd on -current does not call my script (or any command) given in the detach-value in usbd.conf. This is the output usbd: ucom0 matches ucom0 usbd: Found action 'Palm Handheld Device' for Palm Handheld, Palm, Inc. at ucom0usbd: action 0: Palm Handheld Device vndr=0x0830 prdct=0x0060 d

Re: Yet another crash in FreeBSD 5.1

--On 2. august 2003 02:11 -0700 Terry Lambert <[EMAIL PROTECTED]> wrote: db> trace g_dev_strategy(c2156024,c2153800,0,cfb528d0,c2099eca) at g_dev_strategy+0x29 launch_requests(c299bf00,0,1,,47) at launch_requests+0x448 vinumstart(c5ada2d0,0,c22ab000,cfb5294c,c02e5bc6) at vinumstart+0x2

Re: vinum bug? (Re: Yet another crash in FreeBSD 5.1)

[Sending to [EMAIL PROTECTED], and Kris copied in Greg so I'll also do that] --On 2. august 2003 02:00 -0700 Kris Kennaway <[EMAIL PROTECTED]> wrote: db> trace g_dev_strategy(c2156024,c2153800,0,cfb528d0,c2099eca) at g_dev_strategy+0x29 launch_requests(c299bf00,0,1,,47) at launch_reque

Re: sil3112 controller

--Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 02, 2003 at 04:48:07PM +0300, Petri Helenius wrote: > Christian Brueffer wrote: >=20 > >On Sat, Aug 02, 2003 at 11:19:48AM +0300, Petri Helenius wrote:

Re: sil3112 controller

Christian Brueffer wrote: On Sat, Aug 02, 2003 at 11:19:48AM +0300, Petri Helenius wrote: I just wish there would either be more functionality in the twe driver or somebody would come out with 8-12 port SATA controller. Looking at the issues for example the Adaptec SCSI RAIDs have, it seems S

warnpassword and warnexpire in 5.1 login.conf

Hello! Tried this question to the questions list with no response, perhaps current is the correct list for questions related to 5.1-RELEASE?? I am trying to use warnexpire and warnpassword in login.conf but with no result, are the warnexpire and warnpassword still used in 5.1 or have they been s

Re: sil3112 controller

--cHMo6Wbp1wrKhbfi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 02, 2003 at 11:19:48AM +0300, Petri Helenius wrote: >=20 > I just wish there would either be more functionality in the twe driver=20 > or somebody woul

Re: vfprintf() has a 4096-byte memory leak?

"Poul-Henning Kamp" wrote: In message <3F2B9C59.3060209 at cytherianage.net >, "Ryan T. Dean" writes: >/Hey all- /> >/I was doing some app debugging tonight, and noticed what appears to /> >/be a memory leak in vfprintf(). /> This is

What is it about kern_ktr.c ?

In message <[EMAIL PROTECTED]>, Tinderbox wri tes: >/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/kern_ktr.c: In >function `db_ktr_all': >/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/kern_ktr.c:273: >error: `lines' undeclared (first use in this function)

[current tinderbox] failure on sparc64/sparc64

TB --- 2003-08-02 10:36:54 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-08-02 10:36:54 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-08-02 10:39:03 - building world TB

Re: Anyone use WINE at all anywhere?

On Fri, 1 Aug 2003, Julian Elischer wrote: > Is the re ANYONE that uses wine on -current...? > > for that matter, a -current user that uses wine on 4.x? I use it a lot for 1 application, but I mostly use my version of a 6 month old version of -current for large parts of -current, and a 2.4 year o

Re: vfprintf() has a 4096-byte memory leak?

In message <[EMAIL PROTECTED]>, "Ryan T. Dean" writes: >Hey all- >I was doing some app debugging tonight, and noticed what appears to >be a memory leak in vfprintf(). This is probably the buffer which stdio uses for all I/O. Try calling setbuf(stdout, NULL); setbuf(stderr, N

vfprintf() has a 4096-byte memory leak?

Hey all- I was doing some app debugging tonight, and noticed what appears to be a memory leak in vfprintf(). I've tested it on -CURRENT and -STABLE; any program that makes use of vfprintf() (ie, uses printf) appears to have a 4096 byte memory leak. The memory is allocated on the first vfpr

Re: bge & vlan stranges

Terry Lambert wrote: Hello! Boris Kovalenko wrote: I have Compaq DL360G2 with Broadcom BCM5701 Gigabit Ethernet and FreeBSD 5.1R installed. There are no problems if I use bge as usual network card, but when I try to use 802.1Q vlans, I can't receive (only receive, sending is ok) packets more th

[current tinderbox] failure on ia64/ia64

TB --- 2003-08-02 09:22:53 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-08-02 09:22:53 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-08-02 09:25:33 - building world TB --- cd /home

Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)

On Fri, 1 Aug 2003, Julian Elischer wrote: > On Fri, 1 Aug 2003, Julian Elischer wrote: > > I also noticed that if we disable the 'splat' mode, we'd break sysVR4 > > binary code as they do that.. (though it's #if 0'd out at the moment) > > not to mention linux (more important..) though I might add

Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)

On Fri, 1 Aug 2003, Julian Elischer wrote: > looking at it further, it appears that NLDT is not really a > 'reservation' as much as a description of how much space we may > need to allocate initially. Correct, except it seems that there are some bugs from the kernel using the code and data select

[current tinderbox] failure on i386/pc98

TB --- 2003-08-02 07:52:40 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-08-02 07:52:40 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-08-02 07:58:15 - building world TB --- cd /home

Re: Anyone use WINE at all anywhere?

On Fri, Aug 01, 2003 at 05:38:33PM -0700, Julian Elischer wrote: # # Is the re ANYONE that uses wine on -current...? # # for that matter, a -current user that uses wine on 4.x? I use it on a 4.7 at work; the only apps I use are the word-, excel- and ppt viewers for the occasional doc/xl/ppt file

Re: vinum bug? (Re: Yet another crash in FreeBSD 5.1)

On Sat, Aug 02, 2003 at 02:00:52AM -0700, Kris Kennaway wrote: > On Sat, Aug 02, 2003 at 10:11:24AM +0200, Eivind Olsen wrote: > > > db> trace > > g_dev_strategy(c2156024,c2153800,0,cfb528d0,c2099eca) at g_dev_strategy+0x29 > > launch_requests(c299bf00,0,1,,47) at launch_requests+0x448

Re: Yet another crash in FreeBSD 5.1

Eivind Olsen wrote: > Can anyone suggest what I do next to find out about this crash? > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x14 Dereference of NULL pointer; reference is for element at offset 0x14 in some structure; this is the equivalent of 5 32 bit ints o

vinum bug? (Re: Yet another crash in FreeBSD 5.1)

On Sat, Aug 02, 2003 at 10:11:24AM +0200, Eivind Olsen wrote: > db> trace > g_dev_strategy(c2156024,c2153800,0,cfb528d0,c2099eca) at g_dev_strategy+0x29 > launch_requests(c299bf00,0,1,,47) at launch_requests+0x448 > vinumstart(c5ada2d0,0,c22ab000,cfb5294c,c02e5bc6) at vinumstart+0x2b2

Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)

Julian Elischer wrote: > + if (ldt_warnings++ < NUM_LDT_WARNINGS) { Still broken on rollover; use: + if (ldt_warnings < NUM_LDT_WARNINGS) { + ldt_warnings++; -- Terry ___ [EMAIL PROTECTED] mailing list

Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)

Marcel Moolenaar wrote: > But if we only use the dynamic allocation then it can only fail for > a combination of 3rd party code. You meant to say static here, e.g. when there are two libraries linked into a single aplication, and both libraries want to get entry #6, right? In the dynamic case, th

Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)

Julian Elischer wrote: It's not that likely to roll, but... > static int complained = 6; > > if (complained-- ) { if (complained) { complained--; > printf ("process (PID %d) Use static LDT allocation.\n", > td->td_proc->p_pid); > printf ("man i386_set_ldt for

Re: bge & vlan stranges

Boris Kovalenko wrote: > I have Compaq DL360G2 with Broadcom BCM5701 Gigabit Ethernet and > FreeBSD 5.1R installed. There are no problems if I use bge as usual > network card, but when I try to use 802.1Q vlans, I can't receive (only > receive, sending is ok) packets more then 1456 bytes! What is

Re: sil3112 controller

Soeren Schmidt wrote: So that drives could be assigned to a mirror / stripe set before installing without having to build the mirror on another machine first? (in this case the BIOS does not help) You cant boot from a stripe on a controller that doesn't have a BIOS to do it. Sure, but I ca

Yet another crash in FreeBSD 5.1

I've now had yet another crash under FreeBSD 5.1 (RELENG_5_1, cvsupped 5-6 days ago) and it looks almost the same as the crash I posted about yesterday (or was it the day before? Here's some output from DDB: Krasj 2.7.2003: Fatal trap 12: page fault while in kernel mode fault virtual address =

Re: sil3112 controller

It seems Petri Helenius wrote: > > Should there be an option to run atacontrol in sysinstall? hmm, maybe... > So that drives could be assigned to a mirror / stripe set before installing without > having to build the mirror on another machine first? > (in this case the BIOS does not help) You ca

[current tinderbox] failure on i386/i386

TB --- 2003-08-02 06:21:10 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-08-02 06:21:10 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-08-02 06:23:46 - building world TB --- cd /home

Re: world broken with a gcc 3.2 world? (resolution)

On Thu, 31 Jul 2003 11:27:56 +0200 Alexander Leidinger <[EMAIL PROTECTED]> wrote: > with a Jul 10 world, a clean /usr/obj and the sources as of yesterday I > get > ---snip--- > /big/usr/src/contrib/gcc/dwarf2out.c:11739:75: missing terminating ' character > /big/usr/src/contrib/gcc/dwarf2out.c:117

Re: [current tinderbox] failure on alpha/alpha

At Sat, 02 Aug 2003 00:47:45 -0600, Scott Long wrote: > > Is anyone willing to fix this? The warning is bogus as it's quite > obvious that the variable is being initialized. Strange that it doesn't > show up on other platforms. > > Scott I have already committed a workaround for this. /\ Hid