From: "Ville Syrjälä" <syrjala@sci.fi>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: linux-fbdev-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: atyfb rmmod & vram crash, 2.6.24, 2.6.25-rc8
Date: Thu, 3 Apr 2008 11:23:36 +0300 [thread overview]
Message-ID: <20080403082336.GD16619@sci.fi> (raw)
In-Reply-To: <20080402124854.M56647@visp.net.lb>
On Wed, Apr 02, 2008 at 03:54:12PM +0300, Denys Fedoryshchenko wrote:
> VGA card i dont know how much RAM there actually, but lspci here shows looks
> like 16MB:
>
> 03:09.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev
> 5c) (prog-if 00 [VGA controller])
> Subsystem: ATI Technologies Inc Rage Pro Turbo
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping+ SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 66 (2000ns min), Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 21
> Region 0: Memory at f0000000 (32-bit, prefetchable) [size=16M]
This region is always 16MB regardless of how much actual RAM is on the
card.
> Loading without parameters
>
> atyfb: using auxiliary register aperture
> atyfb: 3D RAGE PRO (Mach64 GP, PQFP, PCI) [0x4750 rev 0x7c]
> atyfb: Mach64 BIOS is located at c0000, mapped at c00c0000.
> atyfb: BIOS frequency table:
> atyfb: PCLK_min_freq 984, PCLK_max_freq 23600, ref_freq 2950, ref_divider 64
> atyfb: MCLK_pwd 4200, MCLK_max_freq 7500, XCLK_max_freq 10000, SCLK_freq 5000
> atyfb: 8M SGRAM (1:1), 29.498928 MHz XTAL, 236 MHz PLL, 75 Mhz MCLK, 100 MHz XCLK
> atyfb: fb0: ATY Mach64 frame buffer device on PCI
>
> It detects 8M.
> If i put parameter vram=8
The vram paramter takes KB not MB.
Why do you want to override it anyway? It seems to detect the amount of
RAM just fine.
> And most interesting when i do rmmod
> tv1 ~ # rmmod atyfb
> Segmentation fault
Does this only happen after the failure caused by the bad vram parameter?
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <syrjala@sci.fi>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: linux-kernel@vger.kernel.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: atyfb rmmod & vram crash, 2.6.24, 2.6.25-rc8
Date: Thu, 3 Apr 2008 11:23:36 +0300 [thread overview]
Message-ID: <20080403082336.GD16619@sci.fi> (raw)
In-Reply-To: <20080402124854.M56647@visp.net.lb>
On Wed, Apr 02, 2008 at 03:54:12PM +0300, Denys Fedoryshchenko wrote:
> VGA card i dont know how much RAM there actually, but lspci here shows looks
> like 16MB:
>
> 03:09.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev
> 5c) (prog-if 00 [VGA controller])
> Subsystem: ATI Technologies Inc Rage Pro Turbo
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping+ SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 66 (2000ns min), Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 21
> Region 0: Memory at f0000000 (32-bit, prefetchable) [size=16M]
This region is always 16MB regardless of how much actual RAM is on the
card.
> Loading without parameters
>
> atyfb: using auxiliary register aperture
> atyfb: 3D RAGE PRO (Mach64 GP, PQFP, PCI) [0x4750 rev 0x7c]
> atyfb: Mach64 BIOS is located at c0000, mapped at c00c0000.
> atyfb: BIOS frequency table:
> atyfb: PCLK_min_freq 984, PCLK_max_freq 23600, ref_freq 2950, ref_divider 64
> atyfb: MCLK_pwd 4200, MCLK_max_freq 7500, XCLK_max_freq 10000, SCLK_freq 5000
> atyfb: 8M SGRAM (1:1), 29.498928 MHz XTAL, 236 MHz PLL, 75 Mhz MCLK, 100 MHz XCLK
> atyfb: fb0: ATY Mach64 frame buffer device on PCI
>
> It detects 8M.
> If i put parameter vram=8
The vram paramter takes KB not MB.
Why do you want to override it anyway? It seems to detect the amount of
RAM just fine.
> And most interesting when i do rmmod
> tv1 ~ # rmmod atyfb
> Segmentation fault
Does this only happen after the failure caused by the bad vram parameter?
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
next prev parent reply other threads:[~2008-04-03 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 12:54 atyfb rmmod & vram crash, 2.6.24, 2.6.25-rc8 Denys Fedoryshchenko
2008-04-02 21:55 ` Andrew Morton
2008-04-02 21:55 ` Andrew Morton
2008-04-03 5:22 ` Denys Fedoryshchenko
2008-04-03 5:30 ` Andrew Morton
2008-04-03 5:30 ` Andrew Morton
2008-04-03 8:23 ` Ville Syrjälä [this message]
2008-04-03 8:23 ` Ville Syrjälä
2008-04-03 10:10 ` Denys Fedoryshchenko
2008-04-03 10:19 ` Denys Fedoryshchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080403082336.GD16619@sci.fi \
--to=syrjala@sci.fi \
--cc=denys@visp.net.lb \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.