Messages in this thread | | | Date | Fri, 20 Apr 2001 12:25:07 +0200 | From | Francois Romieu <> | Subject | Re: epic100 error |
| |
Stefan Jaschke <s-jaschke@t-online.de> ecrit : [...] > I don't believe the motherboard or the BIOS have anything to do with, simply
It may give a clue because the machine I wrote this mail from is a 2.4.3 + 2*EtherPower II it looks rather fine (old asus motherbord, BX, backuped peaceful prod server): I tried 2.4.3 on some bp6+epic100 (2.4.0/1/2/3 + misc ac). No problems either.
Around the 10 of february, Arnd Bergmandd <std7652@et.FH-Osnabrueck.DE> had problems with the epic100. These appeared between two revisions of the driver that differ only in the use of DMA mapping I made at the moment. <digression> Fwiw, it was essentially a matter of coding-style as on x86 the DMA mapping actually called the former virt_to_phys and pci_dma_sync was rather empty. It made no design change. It may be possible I assumed some data were in memory as they are still in some cpu registers. I'll re-re-check that. </digression>
Summary: Arnd Bergmann: orig epic100 "DMA mapped epic100 (any version)" (<=2.4.0-ac9) VT8363 ok fscked but ok after bios update
Daniel Nofftz: 2.4.2 2.4.3 VT82C595 ok fscked. (no mention of bios experience)
Oliver Teuber: 2.2.19 2.4.3-ac7 VT82C598 ok fscked
Romieu: 2.2.xx 2.4.[123] 82443BX ok ok
Now it's complicated by the fact that between 2.4.2 and 2.4.3, you have DMA mapping + others changes in epic100 (they make sense imho).
What happen's if you compile 2.4.2 epic100 driver in a 2.4.3 tree (I) ?
[...] > Something between 2.4.0 and 2.4.3 breaks the epic100 driver. That's it.
So far it's hard to say where it comes from. I would really appreciate if you could give a look at (I). If it doesn't change anything and you have spare time, some feedback from bios experience will be welcome too.
-- Ueimor - 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/
| |