Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265498AbTIDTHq (ORCPT ); Thu, 4 Sep 2003 15:07:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265507AbTIDTHp (ORCPT ); Thu, 4 Sep 2003 15:07:45 -0400 Received: from www.inreko.ee ([195.222.18.2]:50188 "EHLO www.inreko.ee") by vger.kernel.org with ESMTP id S265498AbTIDTHo (ORCPT ); Thu, 4 Sep 2003 15:07:44 -0400 Date: Thu, 4 Sep 2003 22:07:39 +0300 From: Marko Kreen To: linux-kernel Subject: [OOPS] 2.4.22 / HPT372N Message-ID: <20030904190426.GA31977@l-t.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1677 Lines: 43 As i used the pen&paper method for oops tracking i dont have full oops. In hpt366.c function hpt372_tune_chipset line 427: list_conf = pci_bus_clock_list(speed, (struct chipset_bus_clock_list_entry *) pci_get_drvdata(dev)); pci_get_drvdata(dev) returns NULL. Crash happens only if there are some devices attached to hpt. lspci -vv: 02:00.0 RAID bus controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 06) Subsystem: Triones Technologies, Inc. HPT370A Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=128K] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Full config, dmesg(of a non-crash boot) & lspci: http://www.l-t.ee/marko/hptcrash.tgz - 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/