try list *(0x[address]) .
That line is mtx_unlock(), which makes no sense (as mtx_lock succeeded fine.)
-a
On 5 January 2016 at 18:13, Shawn Webb wrote:
> Thanks for the quick reply! Here's some more debugging output:
>
> === Begin Log ===
> (kgdb) bt
> #0 doadump (textdump=0) at pcpu.h:221
Thanks for the quick reply! Here's some more debugging output:
=== Begin Log ===
(kgdb) bt
#0 doadump (textdump=0) at pcpu.h:221
#1 0x8037c78b in db_dump (dummy=, dummy2=false,
dummy3=0, dummy4=0x0) at /usr/src/sys/ddb/db_command.c:533
#2 0x8037c57e in db_command (cmd_table=0x0
looks like a null pointer deference. What's kgdb show at that IP?
-a
On 5 January 2016 at 17:57, Shawn Webb wrote:
> Hey All,
>
> Here's a kernel panic I'm experiencing by enabling net.inet.ip.random_id
> at boot.
>
> I'm on latest HEAD on amd64 in bhyve. I'll soon-ish be testing on native
> h
Hey All,
Here's a kernel panic I'm experiencing by enabling net.inet.ip.random_id
at boot.
I'm on latest HEAD on amd64 in bhyve. I'll soon-ish be testing on native
hardware with VIMAGE enabled.
=== Begin Log ===
Kernel page fault with the following non-sleepable locks held:
exclusive sleep mutex
On Mon, Jan 04, 2016 at 12:08:43PM -0800, NGie Cooper wrote:
> > It looks like a libc problem though, because I’ve run into this
> > issue with both /bin/sh and bash (my default login shell). I’m not
> > sure why this isn’t reproing on my VM (yet).
> > This doesn’t repro in universe10a.freebsd.org
On Tue, Jan 5, 2016 at 3:54 AM, Andriy Gapon wrote:
> Is there a limit on the environment's size?
>
If memory serves, this is bounded by ARG_MAX in sys/syslimits.h. The value
is not tunable as far as I know, so if you want to experiment with changing
it you will have to change syslimits.h and r
Hello, i'm test new driver
https://wiki.freebsd.org/Graphics/Update%20i915%20GPU%20driver%20to%20Linux%203.8
My monitor have WXGA+ 16:10 1440 900, not correct detected, only 4:3
Modeline. Full log https://bsdnir.info/files/Xorg.i915_01-16.log
CPU: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (3192.68-
* >> Are those the only MCA errors you're seeing? The reason I ask is that
there's an errata in the X5600 series which can cause an "internal timer
error" MCA to be logged after another uncorrectable MCA occurs.*
90% are these MCA errors regarding rest of the 10% there is no log for it
such as on
each time the MCA error occurs, server went down. So please guide how do we
suppose to tackle this issue ?
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/FreeBsd-MCA-Panic-Crash-tp6064691p6065041.html
Sent from the freebsd-current mailing list archive at Nabble.com.
90% are these MCA errors regarding rest of the 10% there is no log for it
such as one of the supermicro was rebooted two days ago but it was unable to
generate crashdump under /var/crash directory though dump is enabled in
rc.conf but we've no idea what went wrong :
dumpdev="AUTO"
dumpdir="/var/cr
We're thinking to replace x5690 with x5675 CPUs.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/FreeBsd-MCA-Panic-Crash-tp6064691p6065039.html
Sent from the freebsd-current mailing list archive at Nabble.com.
___
freebsd-current
On Tue, Jan 05, 2016 at 01:07:40PM +0200, Konstantin Belousov wrote:
> On Mon, Jan 04, 2016 at 10:05:21PM -0800, Benno Rice wrote:
> > Hi Konstantin,
> >
> > I recently updated my dev box to r292962. After doing this I attempted to
> > set up PostgreSQL 9.4. When I ran initdb the last phase hung.
bcc: current@
Moving the discussion to transport@.
On 12/28/15 at 12:25P, Sam Kumar wrote:
> Hello,
> I am working with the code for the TCP Stack. I noticed that support for
> Challenge Acks have been added since the latest release (10.2.0), and I
> think I may have found a bug in how they relate
On Tue, Jan 05, 2016 at 01:07:40PM +0200, Konstantin Belousov wrote:
> On Mon, Jan 04, 2016 at 10:05:21PM -0800, Benno Rice wrote:
> > Hi Konstantin,
> >
> > I recently updated my dev box to r292962. After doing this I attempted to
> > set up PostgreSQL 9.4. When I ran initdb the last phase hung.
On Mon, Jan 04, 2016 at 10:05:21PM -0800, Benno Rice wrote:
> Hi Konstantin,
>
> I recently updated my dev box to r292962. After doing this I attempted to set
> up PostgreSQL 9.4. When I ran initdb the last phase hung. Using procstat -kk
> I found it appeared to be stuck in a loop inside a posix
On 05/01/2016 10:45, Andriy Gapon wrote:
>
> Very weird, this suddenly started happening to me but with libreoffice. I can
> not correlate the problem with any actions / events.
>
> stderr:
> soffice.bin: environment corrupt; missing value for QT_IM_MO
>
> gdb:
> Core was generated by `soffice
Very weird, this suddenly started happening to me but with libreoffice. I can
not correlate the problem with any actions / events.
stderr:
soffice.bin: environment corrupt; missing value for QT_IM_MO
gdb:
Core was generated by `soffice.bin'.
Program terminated with signal SIGABRT, Aborted.
#0
17 matches
Mail list logo
