on 16/08/2011 23:43 Steven Hartland said the following:
>
> - Original Message - From: "Andriy Gapon"
> To: "Steven Hartland"
> Cc:
> Sent: Tuesday, August 16, 2011 9:30 PM
> Subject: Re: debugging frequent kernel panics on 8.2-RELEASE
>
>
>> on 15/08/2011 17:56 Steven Hartland said t
on 17/08/2011 14:12 Andriy Gapon said the following:
> A little bit later I will send you another patch that, I hope, will produce
> better
> diagnostics for this crash (without DDB in kernel).
The patch:
Index: sys/amd64/amd64/trap.c
==
- Original Message -
From: "Andriy Gapon"
To: "Steven Hartland"
Cc:
Sent: Wednesday, August 17, 2011 12:12 PM
Subject: Re: debugging frequent kernel panics on 8.2-RELEASE
on 16/08/2011 23:43 Steven Hartland said the following:
- Original Message - From: "Andriy Gapon"
T
on 17/08/2011 15:15 Steven Hartland said the following:
>> define allpcpu
>> set $i = 0
>> while ($i <= mp_maxid)
>> p *cpuid_to_pcpu[$i]
>> set $i = $i + 1
>> end
>> end
>> allpcpu
>
> Here's the output.
[snip]
> $3 = {pc_curthread = 0xff06b7f9c000, pc_idlethread = 0xff0012d85460,
> pc_fp
I tried mfsBSD installation on Dell T110 with PERC H200A and 4x 500GB
SATA disks. If I create zpool with RAIDZ, the boot immediately hangs
with following error:
ZFS: i/o error - all block copies unavailable
ZFS: can't read MOS
ZFS: unexpected object set type 0
ZFS: unexpected object set type 0
- Original Message -
From: "Andriy Gapon"
To: "Steven Hartland"
Cc:
Sent: Wednesday, August 17, 2011 1:56 PM
Subject: Re: debugging frequent kernel panics on 8.2-RELEASE
on 17/08/2011 15:15 Steven Hartland said the following:
define allpcpu
set $i = 0
while ($i <= mp_maxid)
p *cp
On 17.08.11 16:35, Miroslav Lachman wrote:
I tried mfsBSD installation on Dell T110 with PERC H200A and 4x 500GB
SATA disks. If I create zpool with RAIDZ, the boot immediately hangs
with following error:
May be it that the BIOS does not see all drives at boot?
__
Hi,
Mike Tancsa wrote
in <4e15a08c.6090...@sentex.net>:
mi> On 7/7/2011 7:32 AM, Mike Tancsa wrote:
mi> > On 7/7/2011 4:20 AM, Kostik Belousov wrote:
mi> >>
mi> >> BTW, we had a similar panic, "spinlock held too long", the spinlock
mi> >> is the sched lock N, on busy 8-core box recently upgrad
Quoth Hiroki Sato on Thursday, 18 August 2011:
> Hi,
>
> Mike Tancsa wrote
> in <4e15a08c.6090...@sentex.net>:
>
> mi> On 7/7/2011 7:32 AM, Mike Tancsa wrote:
> mi> > On 7/7/2011 4:20 AM, Kostik Belousov wrote:
> mi> >>
> mi> >> BTW, we had a similar panic, "spinlock held too long", the spinlo
On 8/17/2011 1:38 PM, Hiroki Sato wrote:
> Any progress on the investigation?
Unfortunately, I cannot reproduce it yet with a debugging kernel :(
---Mike
>
> --
> spin lock 0x80cb46c0 (sched lock 0) held by 0xff01900458c0 (tid
> 100489) too long
> panic: spin lock held to
2011/8/17 Hiroki Sato :
> Hi,
>
> Mike Tancsa wrote
> in <4e15a08c.6090...@sentex.net>:
>
> mi> On 7/7/2011 7:32 AM, Mike Tancsa wrote:
> mi> > On 7/7/2011 4:20 AM, Kostik Belousov wrote:
> mi> >>
> mi> >> BTW, we had a similar panic, "spinlock held too long", the spinlock
> mi> >> is the sched l
2011/8/17 Daniel Kalchev :
> On 17.08.11 16:35, Miroslav Lachman wrote:
>>
>> I tried mfsBSD installation on Dell T110 with PERC H200A and 4x 500GB SATA
>> disks. If I create zpool with RAIDZ, the boot immediately hangs with
>> following error:
>>
> May be it that the BIOS does not see all drives a
Artem Belevich wrote:
2011/8/17 Daniel Kalchev:
On 17.08.11 16:35, Miroslav Lachman wrote:
I tried mfsBSD installation on Dell T110 with PERC H200A and 4x 500GB SATA
disks. If I create zpool with RAIDZ, the boot immediately hangs with
following error:
May be it that the BIOS does not see all
Attilio Rao wrote
in :
at> 2011/8/17 Hiroki Sato :
at> > Hi,
at> >
at> > Mike Tancsa wrote
at> > in <4e15a08c.6090...@sentex.net>:
at> >
at> > mi> On 7/7/2011 7:32 AM, Mike Tancsa wrote:
at> > mi> > On 7/7/2011 4:20 AM, Kostik Belousov wrote:
at> > mi> >>
at> > mi> >> BTW, we had a similar pa
Thanks to the debug that Steven provided and to the help that I received from
Kostik, I think that now I understand the basic mechanics of this panic, but,
unfortunately, not the details of its root cause.
It seems like everything starts with some kind of a race between terminating
processes in a
On Wed, Aug 17, 2011 at 10:52:01AM -0700, Chip Camden wrote:
> Quoth Hiroki Sato on Thursday, 18 August 2011:
> > Hi,
> >
> > Mike Tancsa wrote
> > in <4e15a08c.6090...@sentex.net>:
> >
> > mi> On 7/7/2011 7:32 AM, Mike Tancsa wrote:
> > mi> > On 7/7/2011 4:20 AM, Kostik Belousov wrote:
> > mi
On Wed, Aug 17, 2011 at 11:21:42PM +0300, Andriy Gapon wrote:
[skip]
> But I also would like to use this opportunity to discuss how we can
> make it easier to debug such issue as this. I think that this problem
> demonstrates that when we treat certain junk in kernel address value
> as a userland
On Wed, Aug 17, 2011 at 12:40 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
> Thank you guys, you are right. The BIOS provides only 1 disk to the loader!
> I checked it from loader prompt by lsdev (booted from USB external HDD).
>
> So I will try to make a small zpool mirror for root and boot (if
- Original Message -
From: "Andriy Gapon"
Thanks to the debug that Steven provided and to the help that I received from
Kostik, I think that now I understand the basic mechanics of this panic, but,
unfortunately, not the details of its root cause.
It seems like everything starts with
Quoth Jeremy Chadwick on Wednesday, 17 August 2011:
> >
> > I'm also getting similar panics on 8.2-STABLE. Locks up everything and I
> > have to power off. Once, I happened to be looking at the console when it
> > happened and copied dow the following:
> >
> > Sleeping thread (tif 100037, pid 0
Hiroki Sato wrote
in <20110818.043332.27079545013461535@allbsd.org>:
hr> Attilio Rao wrote
hr> in :
hr>
hr> at> 2011/8/17 Hiroki Sato :
hr> at> > Hi,
hr> at> >
hr> at> > Mike Tancsa wrote
hr> at> > in <4e15a08c.6090...@sentex.net>:
hr> at> >
hr> at> > mi> On 7/7/2011 7:32 AM, Mike Tan
2011/8/18 Hiroki Sato :
> Hiroki Sato wrote
> in <20110818.043332.27079545013461535@allbsd.org>:
>
> hr> Attilio Rao wrote
> hr> in :
> hr>
> hr> at> 2011/8/17 Hiroki Sato :
> hr> at> > Hi,
> hr> at> >
> hr> at> > Mike Tancsa wrote
> hr> at> > in <4e15a08c.6090...@sentex.net>:
> hr> at>
2011/8/18 Hiroki Sato :
> Hiroki Sato wrote
> in <20110818.043332.27079545013461535@allbsd.org>:
>
> hr> Attilio Rao wrote
> hr> in :
> hr>
> hr> at> 2011/8/17 Hiroki Sato :
> hr> at> > Hi,
> hr> at> >
> hr> at> > Mike Tancsa wrote
> hr> at> > in <4e15a08c.6090...@sentex.net>:
> hr> at>
On Wed, Aug 17, 2011 at 05:01:05PM -0700, Chip Camden wrote:
> Quoth Jeremy Chadwick on Wednesday, 17 August 2011:
> > >
> > > I'm also getting similar panics on 8.2-STABLE. Locks up everything and I
> > > have to power off. Once, I happened to be looking at the console when it
> > > happened an
Quoth Attilio Rao on Thursday, 18 August 2011:
> 2011/8/18 Hiroki Sato :
> > Hiroki Sato wrote
> > in <20110818.043332.27079545013461535@allbsd.org>:
> >
> > hr> Attilio Rao wrote
> > hr> in
> > :
> > hr>
> > hr> at> 2011/8/17 Hiroki Sato :
> > hr> at> > Hi,
> > hr> at> >
> > hr> at> > Mi
25 matches
Mail list logo
