marty
------- Forwarded Message
Return-Path: owner-linux-kernel-outgoing@vger.rutgers.edu
Delivery-Date: Mon Aug 3 15:30:57 1998
Return-Path: <owner-linux-kernel-outgoing@vger.rutgers.edu>
Received: from alpha.xerox.com (firewall-user@alpha.Xerox.COM [13.1.64.93])
by gemini.sdsp.mc.xerox.com (8.8.7/8.8.7) with SMTP id PAA02278
for <leisner@sdsp.mc.xerox.com>; Mon, 3 Aug 1998 15:30:53 -0400 (EDT)
Received: from listserv.funet.fi ([128.214.248.27]) by alpha.xerox.com with SMTP id <52875(1)>; Mon, 3 Aug 1998 12:30:42 PDT
Received: from vger.rutgers.edu ([128.6.190.2]:31075 "EHLO vger.rutgers.edu" ident: "TIMEDOUT") by listserv.funet.fi with ESMTP id <10152-25702>; Mon, 3 Aug 1998 21:22:35 +0300
Received: by vger.rutgers.edu id <153912-1666>; Mon, 3 Aug 1998 12:10:51 -0400
Received: from alpha.Xerox.COM ([13.1.64.93]:2449 "HELO alpha.xerox.com" ident: "firewall-user") by vger.rutgers.edu with SMTP id <153999-1666>; Mon, 3 Aug 1998 11:44:19 -0400
Received: from gemini.sdsp.mc.xerox.com ([13.231.132.20]) by alpha.xerox.com with SMTP id <52471(2)>; Mon, 3 Aug 1998 10:40:05 PDT
Received: from gnu.sdsp.mc.xerox.com (gnu [13.231.133.90])
by gemini.sdsp.mc.xerox.com (8.8.7/8.8.7) with SMTP id MAA11818
for <linux-kernel@vger.rutgers.edu>; Mon, 3 Aug 1998 12:25:43 -0400 (EDT)
Received: from gnu (localhost) by gnu.sdsp.mc.xerox.com (4.1/client-1.3)
id AA12448; Mon, 3 Aug 98 12:25:42 EDT
Message-Id: <9808031625.AA12448@gnu.sdsp.mc.xerox.com>
To: linux-kernel@vger.rutgers.edu
Subject: problems with 2.1.112 PCI
Date: Mon, 3 Aug 1998 09:25:42 PDT
From: "Marty Leisner" <leisner@sdsp.mc.xerox.com>
X-Orcpt: rfc822;linux-kernel@vger.rutgers.edu
Sender: owner-linux-kernel@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Global-Processed: /etc/procmailrc mailhost Mon Aug 3 15:30:58 EDT 1998
I just tried 2.1.112 on a compudyne 486/DX4-100 machine.
It loops around
PCI: Discovered primary peer bus ....
when it hits 100, 01 and 02,
It panics (want to dereference a null pointer].
(when I turn on debugging, it scrolls by too fast to see).
I also played around with no bios/only direct access..
no luck...
/proc/pci (with 2.0.35) says:
: leisner@compudyne;cat /proc/pci
PCI devices found:
Bus 0, device 8, function 0:
Non-VGA device: NCR 53c810 (rev 1).
Medium devsel. IRQ 10. Master Capable. Latency=96.
I/O at 0xd000.
Non-prefetchable 32 bit memory at 0x3800000.
Bus 0, device 5, function 0:
Host bridge: Acer Incorporated M1435 (rev 0).
Slow devsel. Master Capable. No bursts.
2.1. used to work until recently (I think the last one I used
on this machine was 2.1.10?)
It works without PCI (which is fine since I rarely use the
PCI bus in that machine).
It probably would be desirable for the code to detect loops
and break out, disabling PCI...instead of infinite looping and then
oop'sing.
marty leisner@sdsp.mc.xerox.com
Don't confuse education with schooling.
Milton Friedman to Yogi Berra
- -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
------- End of Forwarded Message
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html