Re: Crashing netscape?

On Feb 21, 7:51pm, Alex Le Heux wrote: } Subject: Crashing netscape? } Hi, } } Am I the only one who's experiencing an amzing amount of crashes on } Netscape? } } It's been going on for quite some time now (months), upgrading Netscape or } switching from the Linux to the FreeBSD to the BSDI

Re: keymaps

On Jan 21, 9:40pm, Warner Losh wrote: } Subject: Re: keymaps } In message 199901220043.laa22...@lightning.itga.com.au Gregory Bond writes: } : my vote: A version of the standard keymap with CapsLock and LeftCtl } : functions swapped so the control key is under my left finger like } : God

Re: Heads up! New swapper and VM changes have been committed to -4.x

On Jan 26, 12:20pm, Dag-Erling Smorgrav wrote: } Subject: Re: Heads up! New swapper and VM changes have been committed to - } Brian Feldman gr...@unixhelp.org writes: } On 24 Jan 1999, Dag-Erling Smorgrav wrote: } These are dynamically linked, and will automatically pick up the new } libkvm.

Re: btokup().. patch to STYLE(9) (fwd)

On Jan 29, 12:05pm, Sheldon Hearn wrote: } Subject: Re: btokup().. patch to STYLE(9) (fwd) } The reason I'm interested in this (now tiresome) thread is that I'd much } rather have to read } } /* }* Bail out if the time left to next transaction is less than }* the duration

Re: btokup().. patch to STYLE(9) (fwd)

On Jan 29, 9:13am, Poul-Henning Kamp wrote: } Subject: Re: btokup().. patch to STYLE(9) (fwd) } } On the other hand style(9) should still firmly outlaw stuff like: } } /* wait 10 ms */ } if (((error = tsleep((caddr_t)dev, PPBPRI | PCATCH, } ppbpoll, hz/100)) !=

Re: btokup().. patch to STYLE(9) (fwd)

On Jan 29, 8:34am, Brian Somers wrote: } Subject: Re: btokup().. patch to STYLE(9) (fwd) } } My argument is that this sort of thing gets out of hand. I've seen } things such as } } if (((a == b) || (c == d))) } } where a, b, c d are just simple variables - there are so many } redundant

Re: Slow seq. write on Seagate ST36530N

On Feb 19, 2:15pm, Kenneth D. Merry wrote: } Subject: Re: Slow seq. write on Seagate ST36530N } } The Write Cache Enable (WCE) bit is in mode page 8. To check it: } } camcontrol modepage -n da -u 1 -v -m 8 } } To edit the mode page: } } camcontrol modepage -n da -u 1 -v -m 8 -e To make this

Re: swap-related problems

On Apr 15, 12:14pm, Peter Jeremy wrote: } Subject: Re: swap-related problems } Mikhail Teterin m...@misha.cisco.com wrote: } Worse then that, } it may be possible to use it at malloc time, but unless your program } runs and touches every page, the memory may not be available later. } } If you

Re: swap-related problems

On Apr 14, 4:40pm, Chuck Robey wrote: } Subject: Re: swap-related problems } On Wed, 14 Apr 1999, Anthony Kimball wrote: } Well, it's only needed if you want to be able to reliably execute ANSI } C code according to spec. I personally don't care. I'd be surprised } if core didn't though.

Re: ppbus causes hangs?

On Apr 29, 7:41pm, Mike Smith wrote: } Subject: Re: ppbus causes hangs? } } Try setting the flags on the 'ppc' device to 0x40 and _please_ report } the results. I also ran into this problem with a 4/30/1999 version of 3.1-stable on a Dell Dimension XPS R400. The 0x40 flag fixed the problem.

Re: ppbus causes hangs?

On May 2, 11:58pm, Don Lewis wrote: } Subject: Re: ppbus causes hangs? } On Apr 29, 7:41pm, Mike Smith wrote: } } Subject: Re: ppbus causes hangs? } } } } Try setting the flags on the 'ppc' device to 0x40 and _please_ report } } the results. } } I also ran into this problem with a 4/30/1999

patch for descriptor leak caused by KKIS.05051999.003b exploit

Could someone give the attached patch a try in -current? It fixes the file descriptor leak that the KKIS.05051999.003b exploit causes. This fix seems to work fine in -stable. I'd like to commit it to the current tree and merge it into -stable before the 3.2 code freeze. Index: uipc_usrreq.c

select + signal + truss = LOR

I don't believe I've seen any reports of this particular lock order reversal. I got it by pointing truss at syslogd. My kernel and world were built from a cvsup run slightly before Fri Nov 7 14:50:18 PST 2003. Sleeping on stopevent with the following non-sleepable locks held: exclusive sleep

serial console oddity

I've been seeing some wierd things for many months when using a serial console on my -CURRENT box. I finally had a chance to take a closer look today. It looks like the problem is some sort of interference between kernel output to the console and userland writes to /dev/console. I typically see

Re: serial console oddity

On 9 Nov, Bruce Evans wrote: On Sat, 8 Nov 2003, Don Lewis wrote: I've been seeing some wierd things for many months when using a serial console on my -CURRENT box. I finally had a chance to take a closer look today. It looks like the problem is some sort of interference between kernel

Re: serial console oddity

On 9 Nov, Bruce Evans wrote: For a non-half-baked fix, do somethng like: - never block in ttymsg(), but always wait for output to drain using tcdrain() in a single child process. It's probably acceptable for this to not report errors to ttymsg()'s caller. - limit children better. I

Re: serial console oddity

On 9 Nov, Don Lewis wrote: On 9 Nov, Bruce Evans wrote: On Sat, 8 Nov 2003, Don Lewis wrote: This is totally consistent until I kill -HUP syslogd, which I believe causes syslogd to close and open /dev/console, after which the syslog output appears correct on the console. When the syslogd

kernel trap 12 with interrupts disabled

I just got one of these shortly after I rebooted my November 7th -CURRENT box. DDB doesn't show much interesting. kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xbc04d753 fault code =

Re: kernel trap 12 with interrupts disabled

On 9 Nov, I wrote: I just got one of these shortly after I rebooted my November 7th -CURRENT box. DDB doesn't show much interesting. kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xbc04d753

Re: named pipes memory leak?

On 10 Nov, Lukas Ertl wrote: Hi, is there a known problem with named pipes in -CURRENT? The following shell script freezes a machine in several minutes and needs a power cycle. You can see the increasing memory in vmstat -z (unpcb) and netstat -u. The kernel is FreeBSD 5.1-CURRENT Tue

Re: named pipes memory leak?

On 10 Nov, Lukas Ertl wrote: On Mon, 10 Nov 2003, Don Lewis wrote: On 10 Nov, Lukas Ertl wrote: The following shell script freezes a machine in several minutes and needs a power cycle. You can see the increasing memory in vmstat -z (unpcb) and netstat -u. The kernel is FreeBSD 5.1

Re: named pipes memory leak?

On 11 Nov, Lukas Ertl wrote: On Tue, 11 Nov 2003, Lukas Ertl wrote: Unfortunately, we are still seeing a problem here: we are running uvscan (virus scanner), and while running it we are still seeing increasing unpcb usage and orphaned unix domain sockets. We added some debug printfs to the

Re: named pipes memory leak?

On 11 Nov, Don Lewis wrote: On 11 Nov, Lukas Ertl wrote: Sorry, I probably missed an important part: we're creating the FIFOs on nullfs mounts - the test script works great on plain UFS mounts, but the null layer seems to VREF the vnode once again, so v_usecount is 2, thus it is missong

Re: Still getting NFS client locking up

On 31 Oct, Kelley Reynolds wrote: --- Original Message --- From: Matt Smith [EMAIL PROTECTED] Sent: Fri, 31 Oct 2003 08:55:49 + To: Robert Watson [EMAIL PROTECTED] Subject: Re: Still gettnig NFS client locking up Robert Watson wrote: On Tue, 28 Oct 2003, Soren Schmidt wrote:

Re: checking stopevent 2!

On 15 Nov, Robert Watson wrote: On Sat, 15 Nov 2003, Andy Farkas wrote: These messages spew onto my console and into syslogd once every second: Heh. Sounds like your box is having a really bad day, we'll see if we can't get it fixed up over the next couple of weeks as things settle out

Re: named pipes memory leak?

On 11 Nov, Lukas Ertl wrote: On Tue, 11 Nov 2003, Lukas Ertl wrote: Unfortunately, we are still seeing a problem here: we are running uvscan (virus scanner), and while running it we are still seeing increasing unpcb usage and orphaned unix domain sockets. We added some debug printfs to the

vnode lock violation in today's -CURRENT

I just ran into this while running portupgrade. VOP_GETATTR: 0xc741e000 is not locked but should be Debugger(Lock violation. ) Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0 db tr Debugger(c08bf9aa,c9749c78,c741e000,c08bf9eb,e820c984) at Debugger+0x55

Re: Updated acpi_cpu patch

On 18 Nov, Lukas Ertl wrote: On Tue, 18 Nov 2003, Nate Lawson wrote: This excerpt from truckman@'s asl shows that 4 Cx states are only available when the AC adapter is not attached. (The C*NA memory addresses appear to be managed by the BIOS and not the AML but the PSR access is clear).

Re: Unfortunate dynamic linking for everything

On 18 Nov, Garance A Drosihn wrote: At 8:07 AM -0500 11/18/03, [EMAIL PROTECTED] wrote: If there hadn't been a noticed increase in cost by using all-shared-libs, then the measurements were done incorrectly. If the decision is made based upon allowing for 1.5X (at least)

Re: Unfortunate dynamic linking for everything

On 18 Nov, Robert Watson wrote: (2) Shells again, because they will be fork()d and exec()d frequently during heavily scripted activities, such as system boot, periodic events, large make jobs, etc. And presumably the only shell of interest is sh, although some of the supporting

null_lookup() vnode locking wierdness

I was trying to figure out why the VOP_UNLOCK() call in null_lookup() was violating a vnode locking assertion, so I tossed a bunch of ASSERT_VOP_LOCKED() calls into null_lookup(). I found something I don't understand ... ASSERT_VOP_LOCKED(dvp, null_lookup 1); if ((flags

Re: null_lookup() vnode locking wierdness

On 23 Nov, I wrote: I was trying to figure out why the VOP_UNLOCK() call in null_lookup() was violating a vnode locking assertion, so I tossed a bunch of ASSERT_VOP_LOCKED() calls into null_lookup(). I found something I don't understand ... ASSERT_VOP_LOCKED(dvp, null_lookup 1);

Re: 40% slowdown with dynamic /bin/sh

On 25 Nov, Daniel O'Connor wrote: On Tuesday 25 November 2003 11:52, Dan Nelson wrote: I'd greatly prefer that the the dynamic root default be backed out until a substantial amount of this performance can be recovered. What _REAL WORLD_ task does this slow down? Try timing cd

Re: pcm(4) related panic

On 25 Nov, Artur Poplawski wrote: Artur Poplawski [EMAIL PROTECTED] wrote: Hello, On a 5.1-RELEASE and 5.2-BETA machines I have been able

Re: pcm(4) related panic

On 25 Nov, Don Lewis wrote: On 25 Nov, Artur Poplawski wrote: Artur Poplawski [EMAIL PROTECTED] wrote: Hello, On a 5.1-RELEASE and 5.2

Re: panic on 5.2 BETA: blockable sleep lock

On 26 Nov, Stefan Ehmann wrote: I got the following panic twice when starting xawtv using 5.2 BETA (CVS from Oct 23) panic: blockable sleep lock (sleep mutex) sellck @/usr/src/sys/kern/sys_generic.c:1145 I don't think it is directly related to bktr since the last commit there was ~3 months

Re: panic on 5.2 BETA: blockable sleep lock

On 27 Nov, Stefan Ehmann wrote: On Wed, 2003-11-26 at 08:33, Don Lewis wrote: The problem is that selrecord() wants to lock a MTX_DEF mutex, which can cause a context switch if the mutex is already locked by another thread. This is contrary to what bktr_poll() wants to accomplish by calling

[patch] mtx_init() API violations

It's a good thing that the value of MTX_DEF is 0 ;-) This isn't a critical fix, but it probably should be done soon after the code freeze is lifted to prevent the spread if infection via cut and paste programming. Index: dev/ata/ata-all.c

Re: panic inserting CF card.

On 27 Nov, masta wrote: I'm able to reproduce a panic on demand. I simply insert my IBM Microdrive CF card into the PCM/CIA slot of the laptop, which is a Dell CPi, and panic! I build a kernel.debug in the hope somebody can help me analyze the back-trace. Oh by the way, the sources from

Re: panic on 5.2 BETA: blockable sleep lock

On 30 Nov, Stefan Ehmann wrote: On Fri, 2003-11-28 at 01:02, Don Lewis wrote: On 27 Nov, Stefan Ehmann wrote: On Wed, 2003-11-26 at 08:33, Don Lewis wrote: The problem is that selrecord() wants to lock a MTX_DEF mutex, which can cause a context switch if the mutex is already locked

Re: 5.2-BETA panic: page fault

On 30 Nov, Stefan Ehmann wrote: On Sun, 2003-11-30 at 11:13, Stefan Ehmann wrote: This happens to me several times a day (cvsup from yesterday didn't change anything). The panic message is always the same, the backtrace is different though (but always seems to be file system related in some

Re: 5.2-BETA panic: page fault

Can you reproduce this problem without bktr? #6 0xc06743d8 in calltrap () at {standard input}:94 #7 0xc0505b53 in _mtx_lock_flags (m=0x0, opts=0, file=0xc06bfc1d /usr/src/sys/kern/kern_lock.c, line=228) at /usr/src/sys/kern/kern_mutex.c:214 #8 0xc0502b54 in lockmgr

Re: 5.2-BETA panic: page fault

On 1 Dec, Stefan Ehmann wrote: On Mon, 2003-12-01 at 01:10, Don Lewis wrote: Can you reproduce this problem without bktr? snip You are getting a double panic, with the second happening during the file system sync. The code seems to be be tripping over the same mount list entry each time

Re: panic on 5.2 BETA: blockable sleep lock

On 1 Dec, Roger Hardiman wrote: Hi Please can someone commit the bktr patch for me to fix 5.2-BETA (as long as re@ approve). I don't have the resources. If you're happy with the patch, I'll pursue re@ approval for the commit. I'm not suprised that I haven't heard from him because this

Re: panic on 5.2 BETA: blockable sleep lock

On 1 Dec, Roger Hardiman wrote: Hi Please can someone commit the bktr patch for me to fix 5.2-BETA (as long as re@ approve). I don't have the resources. The patch has been committed with re@ approval. ___ [EMAIL PROTECTED] mailing list

Re: 5.2-BETA panic: page fault

On 1 Dec, Stefan Ehmann wrote: On Mon, 2003-12-01 at 01:10, Don Lewis wrote: Can you reproduce this problem without bktr? snip You are getting a double panic, with the second happening during the file system sync. The code seems to be be tripping over the same mount list entry each time

Re: BTX halts installing 5.x

On 2 Dec, Josh Paetzel wrote: I'm trying to install FreeBSD on a Dual Pentium Pro 200mhz 512K cache system and I am getting the following error: CD Loader 1.01 Building the boot loader arguements Looking up /BOOT/LOADER... Found Relocating the loader and the BTX Starting the BTX

Re: RE: net.inet.tcp.always_keepalive on as default ?

On Jun 5, 5:43pm, John-Mark Gurney wrote: } Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? } Garrett Wollman scribbled this message on Jun 5: } On Sat, 5 Jun 1999 16:09:00 -0400 (EDT), Brian Feldman gr...@unixhelp.org said: } } FWIW, I think only a fool would want a computer

Re: zpool: multiple IDs, CURRENT drops all pools after reboot

On 17 Sep, O. Hartmann wrote: Am Tue, 16 Sep 2014 22:06:36 +0100 Steven Hartland kill...@multiplay.co.uk schrieb: All that said you shouldnt end up with corrupt data no matter what. Are there any other symptoms? Has memory been checked for faults etc? Regards Steve The

Re: printing text file with LPD - non-printable characters

On 14 Oct, Beeblebrox wrote: We are using in production environments CUPS in the version 1.4.3; this has a component 'texttops' which supports UTF-8 encoded text (only) and prints UTF-8 nicely on the fly. Thanks for the input. Unfortunately, CUPS has been broken for me since May/14.

Re: pkg 1.4 freeze please test test test!

On 29 Oct, Baptiste Daroussin wrote: Hi all, We are starting the release process of pkg 1.4, we want to have a better release process than with every single previous version of pkg. For that we will need you help! pkg-devel has been updated to the latest version of pkg as of alpha2.

Re: pkg 1.4 freeze please test test test!

On 28 Oct, Don Lewis wrote: On 29 Oct, Baptiste Daroussin wrote: Hi all, We are starting the release process of pkg 1.4, we want to have a better release process than with every single previous version of pkg. For that we will need you help! pkg-devel has been updated to the latest

Re: pkg 1.4 freeze please test test test!

On 29 Oct, Baptiste Daroussin wrote: On Wed, Oct 29, 2014 at 01:15:16PM -0700, Don Lewis wrote: On 28 Oct, Don Lewis wrote: On 29 Oct, Baptiste Daroussin wrote: Hi all, We are starting the release process of pkg 1.4, we want to have a better release process than with every single

parallel buildworld breakage

I just got this failure during a make -j12 buildworld on head r280837. --- realinstall --- sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtbegin.o /usr/obj/usr/src/tmp/usr/lib/crtbegin.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtend.o

Re: Massive libxo-zation that breaks everything

On 3 Mar, David Chisnall wrote: On 3 Mar 2015, at 01:32, Andrey Chernov a...@freebsd.org wrote: So, why you ever need to modify wc? Just load wc inside your json/xml/etc writer, replacing its printf at the ld-elf.so level. You can't get structured output from printf() because printf()

Re: panic: object has cached pages on recent HEAD

On 6 Apr, To: curr...@freebsd.org wrote: I just got this panic on my port builder machine running a recent version of HEAD (last updated in the last few days): panic: object has cached pages on recent HEAD As you can see, I was pushing it really hard: last pid: 76867; load averages:

panic: object has cached pages on recent HEAD

I just got this panic on my port builder machine running a recent version of HEAD (last updated in the last few days): panic: object has cached pages on recent HEAD As you can see, I was pushing it really hard: last pid: 76867; load averages: 62.92, 41.93, 41.40up 7+10:24:04 13:45:01 448

null pointer dereference panic in cap_rights_contains() on 11.0-CURRENT r285785 amd64

I just got this panic while using poudriere to build packages for FreeBSD 8.4 i386. This is hand transcribed because I was not able to get a core file. Fatal trap 12: page fault while in kernel mode cpuid = 6; apic id = 16 fault virtual address = 0x0 fault code = supervisor read

Re: -current broken when MAKEOBJDIRPREFIX is set (was: src is on NFS)

On 19 Jul, O'Connor, Daniel wrote: On 19 Jul 2015, at 02:56, Simon J. Gerraty s...@juniper.net wrote: O'Connor, Daniel dar...@dons.net.au wrote: However, Crochet _does_ build on the NFS client _and_ when the source tree isn't in /usr/src which makes this issue very strange :-/ I've

11.0-CURRENT r290039 privileged instruction fault while in kernel mode

I just got this crash while running poudriere on a freshly upgraded 11.0-CURRENT machine. The instruction pointer value looks pretty strange. FreeBSD zipper.catspoiler.org 11.0-CURRENT FreeBSD 11.0-CURRENT #30 r290039: Tue Oct 27 00:08:00 PDT 2015

Re: 11.0-CURRENT r290039 privileged instruction fault while in kernel mode

On 28 Oct, Konstantin Belousov wrote: > On Tue, Oct 27, 2015 at 04:09:28PM -0700, Don Lewis wrote: >> I just got this crash while running poudriere on a freshly upgraded >> 11.0-CURRENT machine. The instruction pointer value looks pretty >> strange. >> >> >

Re: 11.0-CURRENT r290039 privileged instruction fault while in kernel mode

On 28 Oct, Konstantin Belousov wrote: > On Wed, Oct 28, 2015 at 10:16:12AM -0700, Don Lewis wrote: >> On 28 Oct, Konstantin Belousov wrote: >> > On Tue, Oct 27, 2015 at 04:09:28PM -0700, Don Lewis wrote: >> >> I just got this crash while running poudriere on a fresh

Re: libXO-ification - Why - and is it a symptom of deeper issues?

On 15 Nov, Allan Jude wrote: > On 2015-11-15 13:06, Garrett Cooper wrote: >> >>> On Nov 15, 2015, at 09:51, Andrey Chernov wrote: >>> On 15.11.2015 20:37, Adrian Chadd wrote: > On 15 November 2015 at 09:10, Dan Partelly wrote: > Meaning, is

Re: strange kernel crash

On 7 Nov, Bryan Drewery wrote: > On 11/7/2015 3:08 PM, Andriy Gapon wrote: >> On 07/11/2015 21:48, Bryan Drewery wrote: >>> On 11/6/15 3:20 AM, Andriy Gapon wrote: Unread portion of the kernel message buffer: Fatal trap 1: privileged instruction fault while in kernel mode >>> ...

Re: strange kernel crash

On 7 Nov, To: bdrew...@freebsd.org wrote: > On 7 Nov, Bryan Drewery wrote: >> On 11/7/2015 3:08 PM, Andriy Gapon wrote: >>> On 07/11/2015 21:48, Bryan Drewery wrote: On 11/6/15 3:20 AM, Andriy Gapon wrote: > Unread portion of the kernel message buffer: > > Fatal trap 1:

Re: strange kernel crash

On 6 Nov, Konstantin Belousov wrote: > On Fri, Nov 06, 2015 at 01:20:13PM +0200, Andriy Gapon wrote: >> Unread portion of the kernel message buffer: >> >> Fatal trap 1: privileged instruction fault while in kernel mode >> cpuid = 0; apic id = 00 >> instruction pointer =

Re: Wrong temperature with AMD and amdtemp.ko

On 3 Oct, Willem Jan Withagen wrote: > On 2-10-2015 23:32, Don Lewis wrote: >> On 2 Oct, Willem Jan Withagen wrote: >>> >>> Hi >>> >>> 10.2-STABLE FreeBSD 10.2-STABLE #0 r287102: Mon Aug 24 >>> >>> Processor: Opteron 6812, in Supe

Re: Instant panic while trying run ports-mgmt/poudriere

On 27 Aug, Lawrence Stewart wrote: On 08/27/15 09:36, John-Mark Gurney wrote: Andriy Gapon wrote this message on Sun, Aug 23, 2015 at 09:54 +0300: On 12/08/2015 17:11, Lawrence Stewart wrote: On 08/07/15 07:33, Pawel Pekala wrote: Hi K., On 2015-08-06 12:33 -0700, K. Macy km...@freebsd.org

Re: Instant panic while trying run ports-mgmt/poudriere

On 27 Aug, Don Lewis wrote: On 27 Aug, Lawrence Stewart wrote: On 08/27/15 09:36, John-Mark Gurney wrote: Andriy Gapon wrote this message on Sun, Aug 23, 2015 at 09:54 +0300: On 12/08/2015 17:11, Lawrence Stewart wrote: On 08/07/15 07:33, Pawel Pekala wrote: Hi K., On 2015-08-06 12:33

Re: Wrong temperature with AMD and amdtemp.ko

On 2 Oct, Willem Jan Withagen wrote: > > Hi > > 10.2-STABLE FreeBSD 10.2-STABLE #0 r287102: Mon Aug 24 > > Processor: Opteron 6812, in Supermicro H8SGL > > dev.cpu.7.temperature: 11.1C > dev.cpu.6.temperature: 11.1C > dev.cpu.5.temperature: 11.1C > dev.cpu.4.temperature: 11.1C >

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

On 25 Sep, Matt Smith wrote: > On Sep 24 21:52, Kurt Jaeger wrote: >>Hi! >> >>> > > Try dropping the attached patch in net/mediatomb/files. I submitted it >>> > > in March, in PR198436: >>> > > >>> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 >>> > >>> > Eh, now with an actual

Re: Port compilation fails on HEAD. works on 9 and 10 STABLE

On 25 Sep, Matt Smith wrote: > On Sep 25 01:00, Don Lewis wrote: >>On 25 Sep, Matt Smith wrote: >>> On Sep 24 21:52, Kurt Jaeger wrote: >>>>Hi! >>>> >>>>> > > Try dropping the attached patch in net/mediatomb/files. I >>

Re: panic: sbuf_vprintf called with a NULL sbuf pointer

On 2 Dec, John Baldwin wrote: > On Wednesday, December 02, 2015 01:25:56 PM Don Lewis wrote: >> > If you want to look at this further, try going to frame 16 and >> > dissassembling the >> > instructions before the call to see if you can spot which register the &g

Re: panic: sbuf_vprintf called with a NULL sbuf pointer

On 8 Dec, John Baldwin wrote: > On Monday, December 07, 2015 10:10:51 PM Don Lewis wrote: >> On 2 Dec, John Baldwin wrote: >> > On Wednesday, December 02, 2015 01:25:56 PM Don Lewis wrote: >> >> > If you want to look at this further, try going to fra

Re: panic: sbuf_vprintf called with a NULL sbuf pointer

On 2 Dec, John Baldwin wrote: > On Sunday, November 29, 2015 04:16:11 PM Don Lewis wrote: >> I got this strange panic the other day: >> >> panic: sbuf_vprintf called with a NULL sbuf pointer >> >> The machine was running this: >> >> FreeB

Re: XOR pt. 2

On 11 Dec, Michael McConville wrote: > Note that IFCAP_HWCSUM has two bits set. Because of this, it doesn't XOR > cleanly in the current if-else condition, but I'm not sure whether that > was intended. I just wanted to pass this by people in case it was a > logical bug. Yeah, the original code

Re: fork_findpid() - Fatal trap 12: page fault while in kernel mode

On 16 Dec, Konstantin Belousov wrote: > On Wed, Dec 16, 2015 at 12:21:16PM +0100, Fabian Keil wrote: >> Konstantin Belousov wrote: >> > It is the values of *p and *(p->p_pgrp) that are needed, from the frame 8. >> >> Unfortunately it's not available and apparently I removed

Re: fork_findpid() - Fatal trap 12: page fault while in kernel mode

On 17 Dec, Konstantin Belousov wrote: > On Wed, Dec 16, 2015 at 11:08:02AM -0800, Don Lewis wrote: >> I used to have a patch the deferred linking the new process into >> proctree/allproc until it was fully formed. The motivation was to get >> rid of all of the PRS_NEW s

Re: fork_findpid() - Fatal trap 12: page fault while in kernel mode

On 17 Dec, Mateusz Guzik wrote: > On Thu, Dec 17, 2015 at 11:48:08AM -0800, Don Lewis wrote: >> On 17 Dec, Konstantin Belousov wrote: >> > On Wed, Dec 16, 2015 at 11:08:02AM -0800, Don Lewis wrote: >> >> I used to have a patch the deferred linking the new process int

Re: fork_findpid() - Fatal trap 12: page fault while in kernel mode

On 18 Dec, Mateusz Guzik wrote: > On Thu, Dec 17, 2015 at 02:33:46PM -0800, Don Lewis wrote: >> On 17 Dec, Mateusz Guzik wrote: >> > On Thu, Dec 17, 2015 at 11:48:08AM -0800, Don Lewis wrote: >> >> On 17 Dec, Konstantin Belousov wrote: >> >> > On Wed

Re: fork_findpid() - Fatal trap 12: page fault while in kernel mode

On 18 Dec, Mateusz Guzik wrote: > On Fri, Dec 18, 2015 at 09:44:10AM -0800, Don Lewis wrote: >> On 18 Dec, Mateusz Guzik wrote: >> > On Thu, Dec 17, 2015 at 02:33:46PM -0800, Don Lewis wrote: >> >> On 17 Dec, Mateusz Guzik wrote: >> >> > On Thu, Dec

panic: sbuf_vprintf called with a NULL sbuf pointer

I got this strange panic the other day: panic: sbuf_vprintf called with a NULL sbuf pointer The machine was running this: FreeBSD zipper.catspoiler.org 11.0-CURRENT FreeBSD 11.0-CURRENT #31 r290224: Sat Oct 31 02:56:36 PDT 2015

Re: CAM Shingled Disk support patches available

On 19 Nov, Kenneth D. Merry wrote: > On Thu, Nov 19, 2015 at 12:48:41 -0600, Matthew D. Fuller wrote: >> On Wed, Nov 18, 2015 at 12:13:09PM -0500 I heard the voice of >> Kenneth D. Merry, and lo! it spake thus: >> > >> > Testing and comments are welcome. >> >> GELI does explicit handling of each

Re: VirtualBox network connectivity broken on recent -CURRENT

On 4 Jun, Alan Somers wrote: > On Fri, Jun 3, 2016 at 6:43 PM, Don Lewis <truck...@freebsd.org> wrote: >> On 3 Jun, Don Lewis wrote: >>> It looks like something changed in -CURRENT to break network >>> connectivity to VirtualBox guests. This was last known

Re: VirtualBox network connectivity broken on recent -CURRENT

On 4 Jun, Matthew Macy wrote: > > > > On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund > <rwest...@gmail.com> wrote > > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: > > > It looks like something changed in -CURRENT t

Re: VirtualBox network connectivity broken on recent -CURRENT

On 4 Jun, To: mm...@nextbsd.org wrote: > On 4 Jun, Matthew Macy wrote: >> >> >> >> On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund >> <rwest...@gmail.com> wrote >> > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: >

VirtualBox network connectivity broken on recent -CURRENT

It looks like something changed in -CURRENT to break network connectivity to VirtualBox guests. This was last known to work with r299139 (May 6th) and is definitely broken with r301229. The VirtualBox port revisions are: virtualbox-ose-4.3.38_1 virtualbox-ose-kmod-4.3.38 It looks

Re: VirtualBox network connectivity broken on recent -CURRENT

On 3 Jun, Don Lewis wrote: > It looks like something changed in -CURRENT to break network > connectivity to VirtualBox guests. This was last known to work with > r299139 (May 6th) and is definitely broken with r301229. The VirtualBox > port revisions are: > virtualb

Re: VirtualBox network connectivity broken on recent -CURRENT

On 5 Jun, Otacílio wrote: > Em 04/06/2016 23:04, Randy Westlund escreveu: >> On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: >>> It looks like something changed in -CURRENT to break network >>> connectivity to VirtualBox guests. This was last known to wor

patch for potential race-condition triggered panic in dummynet PIE AQM

There is a race in the PIE AQM code that can cause a panic. A patch is up for review here: . I'd appreciate it if some callout gurus could take a look. ___ freebsd-current@freebsd.org mailing list

Re: panic: sbuf_vprintf called with a NULL sbuf pointer

On 8 Dec, John Baldwin wrote: > On Tuesday, December 08, 2015 11:39:56 AM Don Lewis wrote: >> On 8 Dec, John Baldwin wrote: >> > On Monday, December 07, 2015 10:10:51 PM Don Lewis wrote: >> >> On 2 Dec, John Baldwin wrote: >> >> > On Wednesday,

Re: CURRENT slow and shaky network stability

On 28 Mar, O. Hartmann wrote: > Am Sat, 26 Mar 2016 14:26:45 -0700 (PDT) > Don Lewis <truck...@freebsd.org> schrieb: > >> On 26 Mar, Michael Butler wrote: >> > -current is not great for interactive use at all. The strategy of >> > pre-emptively dropping i

Re: CURRENT slow and shaky network stability

On 26 Mar, Michael Butler wrote: > -current is not great for interactive use at all. The strategy of > pre-emptively dropping idle processes to swap is hurting .. big time. > > Compare inactive memory to swap in this example .. > > 110 processes: 1 running, 108 sleeping, 1 zombie > CPU: 1.2%

Re: CURRENT slow and shaky network stability

On 26 Mar, Poul-Henning Kamp wrote: > > In message > > , Ultima writes: > >> A large zfs send [...] > > I am not running zfs. I am. I'm not seeing any unexpected problems. I haven't really loaded this system up

Re: CURRENT slow and shaky network stability

On 26 Mar, Poul-Henning Kamp wrote: > > In message > > , Adrian Chadd writes: > > I can second that -current isn't too great right now, and I also see > the breaking SSH sessions. > > I'm running: > > FreeBSD

Re: CURRENT slow and shaky network stability

On 1 Apr, O. Hartmann wrote: > Am Wed, 30 Mar 2016 00:28:39 -0700 (PDT) > Don Lewis <truck...@freebsd.org> schrieb: >> Do you use tmpfs? Anything stored in there will get stashed in inactive >> memory and/or swap. > [...] > > Yes, /var/run and /tmp are on tmp

Re: CURRENT slow and shaky network stability

On 29 Mar, To: ohart...@zedat.fu-berlin.de wrote: > On 28 Mar, Don Lewis wrote: >> On 28 Mar, O. Hartmann wrote: > >> If I get a chance, I try booting my FreeBSD 11 machine with less RAM to >> see if that is a trigger. > > I just tried cranking hw.physmen down t

Re: CURRENT slow and shaky network stability

On 28 Mar, Don Lewis wrote: > On 28 Mar, O. Hartmann wrote: > If I get a chance, I try booting my FreeBSD 11 machine with less RAM to > see if that is a trigger. I just tried cranking hw.physmen down to 8 GB on 11.0-CURRENT r297204, GENERIC kernel. /boot/loader.conf

Re: r299512 breaks dhclient on some networks

On 18 May, Ian FREISLICH wrote: > On 05/18/16 20:19, Don Lewis wrote >> It looks to me like r299512 is changing the format of the client >> identifier by inserting the struct hardware hlen field into it. That's >> not valid if htype is non-zero the way I interpret RFC 2132.

Re: r299512 breaks dhclient on some networks

On 18 May, Conrad Meyer wrote: > On Wed, May 18, 2016 at 5:19 PM, Don Lewis <truck...@freebsd.org> wrote: >> >> It looks to me like r299512 is changing the format of the client >> identifier by inserting the struct hardware hlen field into it. > > Yes. The proble

<    1   2   3   4   >