From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cnshjsmin03.cn.alcatel-lucent.com (cnmailgate04.alcatel-sbell.com.cn [211.144.215.47]) by ozlabs.org (Postfix) with ESMTP id D710DB6EF0 for ; Wed, 30 Dec 2009 08:53:09 +1100 (EST) Message-ID: <4B3B30BF.3080504@alcatel-lucent.com> Date: Wed, 30 Dec 2009 05:51:43 -0500 From: gshan MIME-Version: 1.0 To: Benjamin Herrenschmidt Subject: Re: xmon & SCSI ATA devices References: <4B33197D.9000506@alcatel-lucent.com> <1262079428.2173.218.camel@pasglop> <4B3AD271.1050105@alcatel-lucent.com> <1262121685.2173.220.camel@pasglop> In-Reply-To: <1262121685.2173.220.camel@pasglop> Content-Type: text/html; charset=UTF-8 Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Benjamin Herrenschmidt wrote:

On Tue, 2009-12-29 at 23:09 -0500, gshan wrote:

Actually, the situation I described above has caused lots of disk issue.
The DPT (disk partition table) might be lost because of this. I think it's
broken the rule: xmon is assisting to resolve kernel issue, not cause
more.


Well, mostly xmon kicks in when you already oopsed or crashed so .. :-)

As I said, getting into the SCSI stack or similar would make the whole
thing extremely fragile. But you may want to hack something for
yourself, feel free to do so.

ok. Thank you very much for you suggestions, Ben ;-)

Cheers,
Ben.