Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932643AbZABW4v (ORCPT ); Fri, 2 Jan 2009 17:56:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758463AbZABW4i (ORCPT ); Fri, 2 Jan 2009 17:56:38 -0500 Received: from ppp-110-61.adsl.restena.lu ([158.64.110.61]:35044 "EHLO bonbons.gotdns.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757436AbZABW4g convert rfc822-to-8bit (ORCPT ); Fri, 2 Jan 2009 17:56:36 -0500 X-Greylist: delayed 354 seconds by postgrey-1.27 at vger.kernel.org; Fri, 02 Jan 2009 17:56:36 EST Date: Fri, 2 Jan 2009 23:50:34 +0100 From: Bruno =?UTF-8?B?UHLDqW1vbnQ=?= To: Bartlomiej Zolnierkiewicz Cc: linux-ide@vger.kernel.org, Linux Kernel , linux-scsi@vger.kernel.org Subject: Re: S3 with pata_via fails to resume, ide_via82Cxxx works Message-ID: <20090102235034.5660b85a@neptune.home> In-Reply-To: <200901022213.53606.bzolnier@gmail.com> References: <20081230185037.7ec94e94@neptune.home> <20081231201535.4d86c159@neptune.home> <20081231232412.173c87a7@neptune.home> <200901022213.53606.bzolnier@gmail.com> X-Mailer: Claws Mail 3.6.1 (GTK+ 2.12.11; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2533 Lines: 60 On Fri, 02 January 2009 Bartlomiej Zolnierkiewicz wrote: -snip- > > > > I guess the binfmt-0000 is cause by XFS reading at wrong location > > on disc and kernel seeing random data as bin format signature. > > > > > > On reboot no more bootloader. > > hexdump with rescue system showed XFS magic in very first sector of > > the disc, (rescuing the GPT worked - I assume parted used copy at > > end of disc) though the first partition also got corrupted. > > > > This looks like the scan is pretty dangerous in case anything has a > > reference to a disc/partition on the scanned channel :( That's fine with me - eventually it would even be worth adding a printk() as reminder on code path for "scan" and "delete_devices" triggered when there exists an active user of the bus/device being probed. This way there is at least a notice in case something goes wrong (and when the locking is fixed a reminder to adjust the documentation) > I'm really sorry to hear it but "delete_devices" / "scan" interfaces > are currently not ready for use on actively used devices (there are > still some locking issues with the core code that need to be > addressed before this can be allowed). > > Even though HOWTO only mentions use for replacing devices (not > rescaning) I admit that it should be more clear about the above: > > From: Bartlomiej Zolnierkiewicz > Subject: [PATCH] ide: update warm-plug HOWTO > > Reported-by: Bruno Prémont > Signed-off-by: Bartlomiej Zolnierkiewicz > --- > Documentation/ide/warm-plug-howto.txt | 5 +++++ > 1 file changed, 5 insertions(+) > > Index: b/Documentation/ide/warm-plug-howto.txt > =================================================================== > --- a/Documentation/ide/warm-plug-howto.txt > +++ b/Documentation/ide/warm-plug-howto.txt > @@ -11,3 +11,8 @@ unplug old device(s) and plug new device > # echo -n "1" > /sys/class/ide_port/idex/scan > > done > + > +NOTE: please make sure that partitions are unmounted and that there > are +no other active references to devices before doing > "delete_devices" step, +also do not attempt "scan" step on devices > currently in use -- otherwise +results may be unpredictable and lead > to data loss if you're unlucky > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/