From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Buell Date: Mon, 03 Jan 2011 21:36:13 +0000 Subject: Re: Using s3virge card in Sun Blade 2000 Message-Id: <1294090573.17576.16.camel@lithium> List-Id: References: <1294083541.17576.11.camel@lithium> <20110103.114301.102556157.davem@davemloft.net> <1294086801.17576.14.camel@lithium> <20110103.123939.02282416.davem@davemloft.net> In-Reply-To: <20110103.123939.02282416.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: David Miller Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org On Mon, 2011-01-03 at 12:39 -0800, David Miller wrote: > > I've just started digging into the innards of the s3fb driver, my first > > attempt provoked this, simply by commenting out the check to see if it's > > not the primary device and exits with -ENODEV: > > > > Jan 3 20:16:29 sodium kernel: ERROR(1): Cheetah error trap taken > > afsr[0030100000000000] afar[00000000000003d0] TL1(0) > > Jan 3 20:16:29 sodium kernel: ERROR(1): TPC[105918d8] TNPC[105918dc] > > O7[10591884] TSTATE[4411001606] > > Jan 3 20:16:29 sodium kernel: ERROR(1): TPC > [s3fb]> > > Jan 3 20:16:29 sodium kernel: ERROR(1): M_SYND(0), E_SYND(0), Multiple > > Errors, Privileged > > I know, this is what happens if you call vga_*() with a NULL first parameter > on sparc64. It's accessing garbage addresses. OK. # lspci -vvxx -s 0:0:03 0000:00:03.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01) (prog-if 00 [VGA controller]) Subsystem: S3 Inc. ViRGE/DX Physical Slot: PCI 3 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-