Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Apr 2005 12:10:29 -0400
From:      John Baldwin <jhb@FreeBSD.org>
To:        ticso@cicely.de
Cc:        freebsd-alpha@FreeBSD.org
Subject:   Re: MiataGL doesn't boot in 5.4-RC2
Message-ID:  <36c7b9df965e56594f437e41fc83cc59@FreeBSD.org>
In-Reply-To: <20050415103927.GV48482@cicely12.cicely.de>
References:  <20050412201350.GD602@pato.euesrg02.net> <20050412205104.GE40828@cicely12.cicely.de> <20050412210655.GA5737@freebie.xs4all.nl> <20050412212717.GF40828@cicely12.cicely.de> <20050414180341.GA15335@freebie.xs4all.nl> <20050414182217.GA15448@freebie.xs4all.nl> <20050415002328.GB2369@pato.euesrg02.net> <20050415103927.GV48482@cicely12.cicely.de>

next in thread | previous in thread | raw e-mail | index | archive | help

On Apr 15, 2005, at 6:39 AM, Bernd Walter wrote:

> On Fri, Apr 15, 2005 at 02:23:28AM +0200, Victor Balada Diaz wrote:
>> On Thu, Apr 14, 2005 at 08:22:17PM +0200, Wilko Bulte wrote:
>>> But I noticed something else in the system of the original poster:
>>> a TGA2 display card.  Any chance you can give it a try without that=20=

>>> one
>>> please?  There has been some fun with the various TGA display=20
>>> adapters in
>>> the past.
>>
>> I tried without the TGA card and it hangs in the same place. I can=20
>> provide
>> shell if needed.
>
> It has the card already done acording to boot log:
>   pci0: <display, VGA> at device 11.0 (no driver attached)
> The symptoms are the same as described by Jos=E9 M. Fandi=F1o in
> <42444922.794080FB@fadesa.es> a few days ago.
> Next in boot order should be ata access.
> In Jos=E9's case removing ata from kernel helped to boot, but he has
> devices attached that he needs.
>
> Victors machine has the IDE part of the Cypress chip probed the
> following:
> found-> vendor=3D0x1080, dev=3D0xc693, revid=3D0x00
>         bus=3D0, slot=3D7, func=3D1
>         class=3D01-01-80, hdrtype=3D0x00, mfdev=3D1
>         cmdreg=3D0x0045, statreg=3D0x0280, cachelnsz=3D0 (dwords)
>         lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 =
ns)
>         intpin=3Da, irq=3D238
>         map[10]: type 4, range 32, base 00000170, size  3, enabled
>         map[14]: type 4, range 32, base 00000374, size  2, enabled
>         map[20]: type 1, range 32, base 80140000, size 16, memory=20
> disabled
> found-> vendor=3D0x1080, dev=3D0xc693, revid=3D0x00
>         bus=3D0, slot=3D7, func=3D2
>         class=3D01-01-00, hdrtype=3D0x00, mfdev=3D1
>         cmdreg=3D0x0045, statreg=3D0x0280, cachelnsz=3D0 (dwords)
>         lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 =
ns)
>         intpin=3Db, irq=3D239
>         map[10]: type 1, range 32, base 80158000, size 12, enabled
>
> You can see a mapping at 0x170 of 8 Bytes, but the second channel
> has no mapping at 0x1f0.
> Wilko, can you compare this with your PC164SX?
> Would be interesting if removing the ata hints will help, as they are
> the one refering to the ISA compatibility adresses.

Our PCI code in 5.x and newer makes certain assumptions about resources=20=

for ATA controllers as well, so you may want to forward this on to=20
Soren and Warner to see if they have any ideas.

--=20
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =3D  http://www.FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36c7b9df965e56594f437e41fc83cc59>