Messages in this thread | | | Subject | problems with 2.1.112 PCI | Date | Mon, 3 Aug 1998 09:25:42 PDT | From | "Marty Leisner" <> |
| |
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
| |