On Thu, May 21, 2009 at 11:47:54AM +0200, Attilio Rao wrote:
> Please try the patch here:
> http://www.freebsd.org/~attilio/notify.diff
As promised I checked againts 7.2-STABLE of today (cvsup ended
at 15:17 CEST, GTM+2, Italy time with DST) and ... it works !
(added and removed a disk 4 times, e
On Thu, May 21, 2009 at 11:47:54AM +0200, Attilio Rao wrote:
>> Bad news: I removed the second disk during rebuilding and it
>> still crash. I take a screen shapshot with camera because of
>> too many messages for write down by hand :)
>> Image, src tarball and info here (about 2.2MB):
>> ftp://
2009/5/21 Riccardo Torrini :
> On Wed, May 20, 2009 at 10:21:23AM -0400, John Baldwin wrote:
>
>> Try this. It reverts the single-CCB part of the previous
>> commit while keeping the other fixes. I missed that the
>> CCB might still be in flight when we schedule another rescan.
>
> Applied to mpt
On Wed, May 20, 2009 at 10:21:23AM -0400, John Baldwin wrote:
> Try this. It reverts the single-CCB part of the previous
> commit while keeping the other fixes. I missed that the
> CCB might still be in flight when we schedule another rescan.
Applied to mpt_raid.c,v 1.15.2.1 2008/07/28 17:05:09
On Tuesday 12 May 2009 12:10:25 pm Riccardo Torrini wrote:
> On Tue, May 12, 2009 at 11:44:20AM -0400, John Baldwin wrote:
>
> > If you can get a stack trace, that would be most helpful.
> > My guess is that the recovery thread is holding the mpt lock
> > and calling some CAM routine which attempt
On Tuesday 12 May 2009 12:10:25 pm Riccardo Torrini wrote:
> On Tue, May 12, 2009 at 11:44:20AM -0400, John Baldwin wrote:
>
> > If you can get a stack trace, that would be most helpful.
> > My guess is that the recovery thread is holding the mpt lock
> > and calling some CAM routine which attempt
On Tue, May 12, 2009 at 11:44:20AM -0400, John Baldwin wrote:
> If you can get a stack trace, that would be most helpful.
> My guess is that the recovery thread is holding the mpt lock
> and calling some CAM routine which attempts to relock it via
> cam_periph_lock(). A stack trace would be most
On Tuesday 12 May 2009 11:20:14 am Riccardo Torrini wrote:
> On Mon, May 11, 2009 at 02:07:19PM -0400, John Baldwin wrote:
>
> > Do you have kernel crashdumps enabled and a swap partition?
> > If so, do you happen to have any files in /var/crash?
>
> Yes, but I'm unable to produce a crash dump :
On Mon, May 11, 2009 at 02:07:19PM -0400, John Baldwin wrote:
> Do you have kernel crashdumps enabled and a swap partition?
> If so, do you happen to have any files in /var/crash?
Yes, but I'm unable to produce a crash dump :-(
Tryed even with voodoo, added and removed options to
kernel (kdb, gd
On Monday 11 May 2009 12:55:22 pm Riccardo Torrini wrote:
> On Mon, May 11, 2009 at 09:53:21AM -0400, John Baldwin wrote:
>
> >> What can I do now?
>
> > Can you get more details on the crash, perhaps a crash dump?
>
> All what you want, but you need to drive me, I was unable
> to setup serial/d
On Thursday 07 May 2009 11:50:12 am Riccardo Torrini wrote:
> I just submitted a follow-up to PR kern/130330 with the same
> info. Maybe I found the committed lines doing the crash.
>
> Please see PR for more detailed info (and cc: this thread to me).
>
> I restricted the time window of the prob
On Mon, May 11, 2009 at 09:53:21AM -0400, John Baldwin wrote:
>> What can I do now?
> Can you get more details on the crash, perhaps a crash dump?
All what you want, but you need to drive me, I was unable
to setup serial/debug console so I must wrote down by hand
(followed handbook, tryed all sp
12 matches
Mail list logo
