On Tue, Feb 18, 2014 at 03:43:28PM +0200, Andriy Gapon wrote:
> on 18/02/2014 15:39 Jeremie Le Hen said the following:
> > On Tue, Feb 18, 2014 at 03:31:53PM +0200, Andriy Gapon wrote:
> >>
> >> So, VV_ROOT is indeed set in v_vflag.
> >> Thank you.
> >
> > So there's no need for me to reboot with
Jeremie Le Hen wrote:
> Another instance, with a sligthly different stacktrace:
>
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
> 0xfe00e612ae40
> kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe00e612aef0
> vpanic() at vpanic+0x126/frame 0xfe00e612af30
> kassert_panic(
Another instance, with a sligthly different stacktrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00e612ae40
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe00e612aef0
vpanic() at vpanic+0x126/frame 0xfe00e612af30
kassert_panic() at kassert_panic+0x136/frame 0xfff
on 18/02/2014 15:39 Jeremie Le Hen said the following:
> On Tue, Feb 18, 2014 at 03:31:53PM +0200, Andriy Gapon wrote:
>>
>> So, VV_ROOT is indeed set in v_vflag.
>> Thank you.
>
> So there's no need for me to reboot with kib's patch, right?
You better ask kib. I do not see any misbehavior in ZF
on 15/02/2014 22:02 Konstantin Belousov said the following:
> On Sat, Feb 15, 2014 at 02:12:40PM +0200, Andriy Gapon wrote:
>> on 14/02/2014 21:18 Jeremie Le Hen said the following:
>>> I've just got another occurence of the exact same panic. Any clue how
>>> to debug this?
>>
>> Could you pleas
On Tue, Feb 18, 2014 at 03:31:53PM +0200, Andriy Gapon wrote:
>
> So, VV_ROOT is indeed set in v_vflag.
> Thank you.
So there's no need for me to reboot with kib's patch, right?
--
Jeremie Le Hen
Scientists say the world is made up of Protons, Neutrons and Electrons.
They forgot to mention Mor
on 18/02/2014 15:18 Jeremie Le Hen said the following:
> On Sat, Feb 15, 2014 at 02:12:40PM +0200, Andriy Gapon wrote:
>> on 14/02/2014 21:18 Jeremie Le Hen said the following:
>>> I've just got another occurence of the exact same panic. Any clue how
>>> to debug this?
>>
>> Could you please obtai
On Sat, Feb 15, 2014 at 02:12:40PM +0200, Andriy Gapon wrote:
> on 14/02/2014 21:18 Jeremie Le Hen said the following:
> > I've just got another occurence of the exact same panic. Any clue how
> > to debug this?
>
> Could you please obtain *vp from frame 12 ?
Sure:
$1 = {v_tag = 0x81501
On Sat, Feb 15, 2014 at 10:02:59PM +0200, Konstantin Belousov wrote:
> On Sat, Feb 15, 2014 at 02:12:40PM +0200, Andriy Gapon wrote:
> > on 14/02/2014 21:18 Jeremie Le Hen said the following:
> > > I've just got another occurence of the exact same panic. Any clue how
> > > to debug this?
> >
> >
Andriy Gapon wrote:
> on 14/02/2014 21:18 Jeremie Le Hen said the following:
> > I've just got another occurence of the exact same panic. Any clue
> > how
> > to debug this?
>
> Could you please obtain *vp from frame 12 ?
>
> The problem seems to be happening in this piece of ZFS code:
>
On Sat, Feb 15, 2014 at 02:12:40PM +0200, Andriy Gapon wrote:
> on 14/02/2014 21:18 Jeremie Le Hen said the following:
> > I've just got another occurence of the exact same panic. Any clue how
> > to debug this?
>
> Could you please obtain *vp from frame 12 ?
>
> The problem seems to be happenin
on 14/02/2014 21:18 Jeremie Le Hen said the following:
> I've just got another occurence of the exact same panic. Any clue how
> to debug this?
Could you please obtain *vp from frame 12 ?
The problem seems to be happening in this piece of ZFS code:
if (cnp->cn_flags & ISDOTDOT) {
On Tue, Feb 11, 2014 at 10:35:29AM +0100, Jeremie Le Hen wrote:
> On Mon, Feb 10, 2014 at 11:48:19PM +0200, Andriy Gapon wrote:
> >
> > stack trace from kgdb could be a good middle ground between ddb stack trace
> > and
> > a full vmcore file...
>
> Here we go:
>
> #1 0x80302ca5 in db_
On Mon, Feb 10, 2014 at 11:48:19PM +0200, Andriy Gapon wrote:
>
> stack trace from kgdb could be a good middle ground between ddb stack trace
> and
> a full vmcore file...
Here we go:
#1 0x80302ca5 in db_fncall (dummy1=,
dummy2=, dummy3=,
dummy4=) at /usr/src-svn/sys/ddb/db_c
stack trace from kgdb could be a good middle ground between ddb stack trace and
a full vmcore file...
on 10/02/2014 22:56 Jeremie Le Hen said the following:
> Hi,
>
> I run 11.0-CURRENT r260696 on amd64.
>
> I've got the following panic:
>
> panic: LK_RETRY set with incompatible flags (0x20040
15 matches
Mail list logo
