on 23/04/2013 01:50 Shawn Webb said the following:
Let me know if there's anything I can do or more information you need.
You can try to enter ddb and examine what the threads are doing / waiting for.
--
Andriy Gapon
___
freebsd-current@freebsd.org
I have similar problem when start X server with intel driver.
On Monday 22 April 2013 18:50:37 Shawn Webb wrote:
Hey All,
I'm on r249745 on amd64. For the past few weeks, my box hasn't been able to
completely turn off or reboot. The box sits at the console at the All
buffers synced message.
On Apr 17, 2013, at 21:16, Jung-uk Kim j...@freebsd.org wrote:
On 2013-04-17 06:07:47 -0400, Dimitry Andric wrote:
On Apr 17, 2013, at 07:31, Jan Beich jbe...@tormail.org wrote:
Dimitry Andric d...@freebsd.org writes: On Apr 16, 2013, at
00:42, Jan Beich jbe...@tormail.org wrote:
...
Maybe
After doing a
route add host 127.0.0.1 -blackhole
on a FreeBSD 8.3 host I noticed that nc host 80 would instantly return with
ENETUNRACH, instead of timing out, while blackhole routing to a real host would
time out. Checking in CURRENT (october 2012) reveals the same behaviour:
#
TB --- 2013-04-23 19:50:20 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-04-23 19:50:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
Hello,
just upgraded from r245115 to r249810 and now box reliably panics on
boot a second after mounting root.
Trace:
#9 0x8066a443 in calltrap ()
at /usr/src/head/sys/amd64/amd64/exception.S:228
#10 0x8051fe75 in propagate_priority (td=value optimized out)
at
Hello,
I would like to replace Giant with a local sx lock in sysvshm code.
Looked really straightforward so maybe I missed something.
Patch: http://people.freebsd.org/~mjg/patches/sysvshm-giant-sx.patch
Inlined version for comments:
diff --git a/sys/kern/sysv_shm.c b/sys/kern/sysv_shm.c
index
Hi,
On Apr 22, 2013, at 2:56, Baptiste Daroussin b...@freebsd.org wrote:
As anyone been able to test this patch?
I've been running with it for a few days. I've done a reinstall of all ports
plus a few portmaster -a runs without pkgng database corruption. I've not
tested it for very long, but
More investigation. AFAIU, we can't come to this point
if __mtx_lock_sleep() passed a NULL ts. So ts wasn't NULL
before call to propagate_priority(). The turnstile_wait()
saves ts on td:
738:td-td_blocked = ts;
So I can obtain it:
(kgdb) fr 11
#11 0x805206b2 in turnstile_wait
P.S. Panic isn't reproducible with INVARIANTS :(
--
Totus tuus, Glebius.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
On Tue, Apr 23, 2013 at 10:38:23PM +0200, Mateusz Guzik wrote:
Hello,
I would like to replace Giant with a local sx lock in sysvshm code.
Looked really straightforward so maybe I missed something.
At very least, the shmget_existing() is no longer functional.
The sx is owned around tsleep(),
On Tue, Apr 23, 2013 at 08:44:43PM +, Eggert, Lars wrote:
Hi,
On Apr 22, 2013, at 2:56, Baptiste Daroussin b...@freebsd.org wrote:
As anyone been able to test this patch?
I've been running with it for a few days. I've done a reinstall of all ports
plus a few portmaster -a runs
On Tue, Apr 23, 2013 at 11:55:32PM +0300, Konstantin Belousov wrote:
On Tue, Apr 23, 2013 at 10:38:23PM +0200, Mateusz Guzik wrote:
I would like to replace Giant with a local sx lock in sysvshm code.
Looked really straightforward so maybe I missed something.
At very least, the
On Tue, Apr 23, 2013 at 3:26 AM, Artyom Mirgorodskiy
artyom.mirgorod...@gmail.com wrote:
I have similar problem when start X server with intel driver.
On Monday 22 April 2013 18:50:37 Shawn Webb wrote:
Hey All,
I'm on r249745 on amd64. For the past few weeks, my box hasn't been able
to
I don't use fuse.
Artyom MirgorodskiyOn Tue, Apr 23, 2013 at 3:26 AM,
artyom.mirgorod...@gmail.com[1] wrote:
I have similar problem when start X server with intel driver.
I am seeing the same thing on my 9.1-STABLE box. It was running a kernel from
Jan. 27, but after updating on April
Hi,
On Tue, 23 Apr 2013 15:50:58 -0700
Kevin Oberman rkober...@gmail.com wrote:
On Tue, Apr 23, 2013 at 3:26 AM, Artyom Mirgorodskiy
artyom.mirgorod...@gmail.com wrote:
I have similar problem when start X server with intel driver.
On Monday 22 April 2013 18:50:37 Shawn Webb wrote:
TB --- 2013-04-24 00:51:19 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-04-24 00:51:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
17 matches
Mail list logo
