On 2016-06-02 18:17, Ngie Cooper wrote:
On Thu, Jun 2, 2016 at 3:05 PM, Michael Jung wrote:
On 2016-06-01 12:37, Michael Jung wrote:
Since upgrading to head r301040 I have started to get the above panic
while running
poudriere while building packages for 10.3-STABLE r301107.
On Thu, Jun 02, 2016 at 03:17:21PM -0700, Ngie Cooper wrote:
> On Thu, Jun 2, 2016 at 3:05 PM, Michael Jung wrote:
> > On 2016-06-01 12:37, Michael Jung wrote:
> >>
> >> Since upgrading to head r301040 I have started to get the above panic
> >> while running
> >> poudriere while
On Thu, Jun 2, 2016 at 3:05 PM, Michael Jung wrote:
> On 2016-06-01 12:37, Michael Jung wrote:
>>
>> Since upgrading to head r301040 I have started to get the above panic
>> while running
>> poudriere while building packages for 10.3-STABLE r301107.
>>
>> Unfortuately I can't
On 2016-06-01 12:37, Michael Jung wrote:
Since upgrading to head r301040 I have started to get the above panic
while running
poudriere while building packages for 10.3-STABLE r301107.
Unfortuately I can't tell you the previous version of head but it was
from some
months ago.
Since upgrading to head r301040 I have started to get the above panic
while running
poudriere while building packages for 10.3-STABLE r301107.
Unfortuately I can't tell you the previous version of head but it was
from some
months ago.
https://charon.gopai.com/core.txt.7
core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 6
...
pass3 at aacp0 bus 0 scbus0 target 3 lun 0
pass3: SEAGATE ST373454LC 0005 Fixed Uninstalled SCSI-3 device
pass3: 3.300MB/s transfers
SMP: AP CPU #1 Launched!
panic: _mtx_lock_sleep: recursed on non-recursive mutex vm map (system) @
/usr
Eh a reboot failed to show evidence of a recurrence.
Peace,
david (not particularly appreciating computer hardware just now)
--
David H. Wolfskill da...@catwhisker.org
Taliban: Evil men with guns afraid of truth from a 14-year old girl.
See
SMP: AP CPU #1 Launched!
panic: _mtx_lock_sleep: recursed on non-recursive mutex vm map (system) @
/usr/src/sys/vm/vm_kern.c:430
cpuid = 1
KDB: enter: panic
[ thread pid 13 tid 100010 ]
Stopped at kdb_enter+0x3d: movl$0,kdb_why
db bt
Tracing pid 13 tid 100010 td 0xc62ef930
kdb_enter
Hello. I just had a panic here. I'm running CURRENT as of 31st of October,
platform is i386. I have a crashdump available if anyone wants to take a
look at this.
Here's some output from gdb -k:
[EMAIL PROTECTED]:~/tmp/debug/2003-10-31 gdb -k kernel.debug vmcore.6
GNU gdb 5.2.1 (FreeBSD)
Hi,
I got this panic with an SMP kernel from yesterday, is this a known issue?
panic: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id =
fault virtual address = 0x70040045
fault code = supervisor read, page not present
10 matches
Mail list logo