Re: Spinlock panic in FreeBSD 7

2011-12-17 Thread Andriy Gapon
on 17/12/2011 00:38 Charlie Martin said the following: > (This was originally posted to freebsd-hackers, I'm reposting following email > suggestions.) > > We've observed a panic in FreeBSD 7 (7.2-PRERELEASE FreeBSD) several times > that > we've not been able to track down. Upgrading is not an op

Re: [head tinderbox] failure on mips/mips

2011-12-17 Thread Bjoern A. Zeeb
On 17. Dec 2011, at 02:39 , Bjoern A. Zeeb wrote: > On 16. Dec 2011, at 16:42 , Dimitry Andric wrote: > >> On 2011-12-16 16:46, FreeBSD Tinderbox wrote: >> ... >>> ===> usr.sbin/bsnmpd/modules/snmp_mibII (all) >>> cc -fpic -DPIC -O -pipe -G0 >>> -I/src/usr.sbin/bsnmpd/modules/snmp_mibII/../../

[head tinderbox] failure on mips/mips

2011-12-17 Thread FreeBSD Tinderbox
TB --- 2011-12-17 10:38:16 - tinderbox 2.8 running on freebsd-current.sentex.ca TB --- 2011-12-17 10:38:16 - starting HEAD tinderbox run for mips/mips TB --- 2011-12-17 10:38:16 - cleaning the object tree TB --- 2011-12-17 10:38:25 - cvsupping the source tree TB --- 2011-12-17 10:38:25 - /usr/bin/c

Re: 9.0-RC1 panic in tcp_input: negative winow.

2011-12-17 Thread Pawel Jakub Dawidek
On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote: > An update. I've sent Pawel a testing patch to see if my hypothesis is correct > (www.freebsd.org/~jhb/patches/tcp_negwin_test.patch). If it is then I intend > to commit www.freebsd.org/~jhb/patches/tcp_negwin2.patch as the fix. Unfo

Sleeping thread (tid 100033, pid 16): panic in FreeBSD 10.0-CURRENT/amd64 r228662

2011-12-17 Thread O. Hartmann
Since three days for now I get a panic when I shutdown or reboot my FreeBSD 10.0-CURREN/amd64 box: Sleeping thread (tid 100033, pid 16) owns a non sleepable lock panic: sleeping thread cpuid = 0 PID 16 is always USB on my box. Any advice or tip to get rid of it? Oliver signature.asc Descript

Re: Sleeping thread (tid 100033, pid 16): panic in FreeBSD 10.0-CURRENT/amd64 r228662

2011-12-17 Thread Alexander Kabaev
On Sun, 18 Dec 2011 01:09:00 +0100 "O. Hartmann" wrote: > Sleeping thread (tid 100033, pid 16) owns a non sleepable lock > panic: sleeping thread > cpuid = 0 > > PID 16 is always USB on my box. You really need to give us a backtrace when you quote panics. It is impossible to make any sense of t

Re: SCHED_ULE should not be the default

2011-12-17 Thread Bruce Cran
On 13/12/2011 09:00, Andrey Chernov wrote: I observe ULE interactivity slowness even on single core machine (Pentium 4) in very visible places, like 'ps ax' output stucks in the middle by ~1 second. When I switch back to SHED_4BSD, all slowness is gone. I'm also seeing problems with ULE on a

Re: Sleeping thread (tid 100033, pid 16): panic in FreeBSD 10.0-CURRENT/amd64 r228662

2011-12-17 Thread mdf
On Sat, Dec 17, 2011 at 5:45 PM, Alexander Kabaev wrote: > On Sun, 18 Dec 2011 01:09:00 +0100 > "O. Hartmann" wrote: > >> Sleeping thread (tid 100033, pid 16) owns a non sleepable lock >> panic: sleeping thread >> cpuid = 0 >> >> PID 16 is always USB on my box. > > You really need to give us a ba

Re: SCHED_ULE should not be the default

2011-12-17 Thread Andrey Chernov
On Sun, Dec 18, 2011 at 05:51:47PM +1100, Ian Smith wrote: > On Sun, 18 Dec 2011 02:37:52 +, Bruce Cran wrote: > > On 13/12/2011 09:00, Andrey Chernov wrote: > > > I observe ULE interactivity slowness even on single core machine (Pentium > > > 4) in very visible places, like 'ps ax' output s