Date: Wed, 3 Jan 1996 20:46:12 +0300 (GMT+0300) From: Alex Kluev <alex@tubank.msk.su> To: Stefan Esser <se@zpr.uni-koeln.de> Cc: questions@freebsd.org Subject: Re: Adaptec 294x problem Message-ID: <Pine.BSI.3.90.960103204225.22381A-100000@hobbit.tubank.msk.su> In-Reply-To: <199601012041.AA18165@Sysiphos>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! this is what we got after compiling in the pcibus.c from the
FreeBSD-current :
[cut here]
pcibus_setup(1a): mode1res=0x00000000(0x80000000)
pcibus_setup(1b): mode1res=0x80000000(0xff000001)
pcibus_check: device - is there (id=20000e11)
Probing for devices on the PCI bus:
configuration mode 1 allows 32 devices
pci0:0 Compaq, device 0x2000, class=old (misc)[no driver assigned]
map(10): mem32(23c08)
map(14): mem32(1c3c98)
map(18): mem32(1c3ca8)
map(1c): mem32(39940)
map(20): io(20000e10)
vga0 <VGA compatible display device> rev 252 on pci0:10
mapreg[10] type=0 addr=40000000 size=1000000
ahc0: <Adaptec 2940 SCSI host adapter> rev 3 int a irq255 on pci0:14
ahc0: reading board settings
ahc0: Reading SEEPROM...
ahc0: SEEPROM read failed, using leftover BIOS values
ahc0: 2940 single channel , SCSI Id=7, aic=7870, 0 SCBs.
stray irq 0
ahc: Downloading sequencer program ... start irq 0
stray irq 0
stray irq 0
stray irq 0
too many stray irq 0's; not logging any more
[cut here]
After this point everything hangs with a continous bell from the speaker.
Stefan, if only we had some docs on the PCI chipsets, we could try to
help with this situation. Could you spare any docs?
Regards,
Alex
-------------------------------------------------------------------------------
+ Alex Kluev ..."The life is a short warm moment, +
+ Internet: alex@tubank.msk.su And the death is a long cold rest..."+
+ Phone: +7 (095) 913-3089 Pink Floyd "Obscured by clouds" +
+ Fax: +7 (095) 330-6793 +
+ PGP Key fingerprint = 2E 46 74 FB D1 B4 E4 63 D3 9D A1 16 2B F0 F3 6B +
+------------------------------------------------------------------------------
On Mon, 1 Jan 1996, Stefan Esser wrote:
> On Dec 30, 15:41, Alex Kluev wrote:
> } Subject: Re: Adaptec 294x problem
> } OK, here comes two verbose boot logs. First one is GENERIC, second one is
> } a fixed kernel. Sorry, the AHA board was taken from me, but I will get it
> } back after the NewYear's celebrations.
> }
> } I hope this will help.
>
> Thanks!
>
> } pcibus_setup(1): mode1res=0x8000000c (0x80000000), mode2res=0x0c (0x0e)
>
> Yes, this is a know buggy chip set ...
> But they seem to have broken it even more by now!
>
> } pcibus_setup(1): mode1res=0x8000000c (0x80000000), mode2res=0x0c (0x0c)
> } pcibus_setup(2): mode1res=0x00000000 (0x80000000)
> } pcibus_setup(3): mode1res=0x80000000 (0xff000001)
> } pcibus_check: device 0 is there (id=20000e11)
> } Probing for devices on the PCI bus:
> } configuration mode 1 allows 32 devices.
> } pci0:0: Compaq, device=0x2000, class=old (misc) [no driver assigned]
>
> The fix I put in before was for the Compaq chip set
> with device ID 0x1000, and this one behaves different
> even again.
>
> But the code in FreeBSD-current does know how to deal
> with them ...
>
> Your proposed fix is in fact only working by accident.
> The 0x0e is for Configuration Mode 2 detecion, while
> the Compaq uses Mode 1. By changing the 0x0e into 0x0c,
> you make the Mode 2 test succeed, but later Mode 1 is
> (correctly) used to access the PCI configuration space
> anyway.
>
> You can of course use the kernel with your patch on
> the Compaq, but the better solution would be to use
> /sys/i386/isa/pcibus.c from FreeBSD-current, since
> that file contains a new and improved probe code ...
>
> Regards, STefan
> --
> Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021
> Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160
> ==============================================================================
> http://www.zpr.uni-koeln.de/~se <se@ZPR.Uni-Koeln.DE>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.90.960103204225.22381A-100000>