On 10/14/2018 2:19 PM, Mateusz Guzik wrote:
> On 10/14/18, Mike Tancsa wrote:
>> On 10/13/2018 12:48 PM, Allan Jude wrote:
>>> Strange that your crash is in ZFS here...
>>>
>>> Can you take a crash dump?
>>>
>>> It looks like something is trying to write to uninitialized memory here.
>> I will
On 10/14/18, Mike Tancsa wrote:
> On 10/13/2018 12:48 PM, Allan Jude wrote:
>>
>> Strange that your crash is in ZFS here...
>>
>> Can you take a crash dump?
>>
>> It looks like something is trying to write to uninitialized memory here.
>
> I will need to pop in another drive or can I do a netdump
On 10/13/2018 12:48 PM, Allan Jude wrote:
>
> Strange that your crash is in ZFS here...
>
> Can you take a crash dump?
>
> It looks like something is trying to write to uninitialized memory here.
I will need to pop in another drive or can I do a netdump at this point ?
---Mike
--
In message <8f033c7c-af8f-1ebc-d787-548634f10...@freebsd.org>, Allan
Jude write
s:
> On 10/12/2018 11:52, Mike Tancsa wrote:
> > I am guessing this does not have anything to do with vmm being loaded,
> > but hardware being initialized in a particular order? If I load vmm in
> > loader.conf, the
On 10/12/2018 11:52, Mike Tancsa wrote:
I am guessing this does not have anything to do with vmm being loaded,
but hardware being initialized in a particular order? If I load vmm in
loader.conf, the box panics at boot up. However, manually loading it
all seems to work. Hardware is PRIME
I am guessing this does not have anything to do with vmm being loaded,
but hardware being initialized in a particular order? If I load vmm in
loader.conf, the box panics at boot up. However, manually loading it
all seems to work. Hardware is PRIME X370-PRO, AMD Ryzen 5 1600X 32G
RAM. FreeBSD
I'm installing on a pc98 machine (The NEC PC-9821 Nr Lavie).
About 40% into the base install, I got the following panic:
kernel: trap 12 trap, code=0
Stopped at ufs_ihashget+0x70: cmpl 0x30(%eax),%ebx
db tr
ufs_ihashget(c1ee6000,2128,2,c8957854,c4ddc0ae) at ufs_ihashget_0x70
ffs_vget(...) at
Hi,
On this machine i'm running -CURRENT from around the end of april, so
apologies if this has already been corrected, however i haven't seen
anything similar reported before. Panic while writing a core file for a
program that died on signal 11. Toshiba laptop, usually perfectly stable,
On Fri, 17 May 2002, Gavin Atkinson wrote:
Panic while writing a core file for a
program that died on signal 11. Toshiba laptop, usually perfectly stable,
resumed from suspend about two minutes before and was in the process of
loading KDE... This panic has only ever happened once. there were
