Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754133AbYANVCW (ORCPT ); Mon, 14 Jan 2008 16:02:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751531AbYANVCI (ORCPT ); Mon, 14 Jan 2008 16:02:08 -0500 Received: from smtp5.pp.htv.fi ([213.243.153.39]:54848 "EHLO smtp5.pp.htv.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751440AbYANVCF (ORCPT ); Mon, 14 Jan 2008 16:02:05 -0500 Date: Mon, 14 Jan 2008 23:01:05 +0200 From: Adrian Bunk To: Stephen Hemminger Cc: Oliver Pinter =?utf-8?B?KFBpbnTDqXIgT2xpdsOpcik=?= , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, gregkh@suse.de Subject: Re: [BUG] skge 0000:02:05: read data parity error Message-ID: <20080114210105.GG9847@does.not.exist> References: <6101e8c40801141157j1ce7d3f0if2e4eb2344b6c844@mail.gmail.com> <20080114125200.28cb4c69@deepthought> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20080114125200.28cb4c69@deepthought> User-Agent: Mutt/1.5.17 (2007-12-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1626 Lines: 49 On Mon, Jan 14, 2008 at 12:52:00PM -0800, Stephen Hemminger wrote: > On Mon, 14 Jan 2008 20:57:49 +0100 > "Oliver Pinter (Pintér Olivér)" wrote: > > > Hi All! > > > > It is fully reproductable under 2.6.22.15, 2.6.23.13 (all tainted and > > not tainted [4 different kernel] ) and 2 different PC: > > > > [BUG] skge 0000:02:05: read data parity error > > [BUG] skge 0000:02:05: read data parity error > > > > steps: > > 1. login as root > > 2. start mc > > 3. cd /sys/bus/pci/drivers/skge/0000:02:05.0 > > 4. press F3 (mcview) on resource0 > > 5. the system hang up, without panic or bug ... only this message > > printed 2x: [BUG] skge 0000:02:05: read data parity error > > This is not a bug. > > The hardware has some debug registers that if accessed cause a read > back to the host. Since this can point anywhere, it will cause errors > or system hang. > > The point is don't do it. Is it really a good idea that _reading_ files under /sys can kill your machine? That sounds like a huge trap for people debugging their machine (or e.g. forgetting to exclude /sys from their backup). cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- 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/