linux-kernel - Re: atyfb rmmod & vram crash, 2.6.24, 2.6.25-rc8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 3 Apr 2008 13:19:05 +0300
From:	"Denys Fedoryshchenko" <denys@...p.net.lb>
To:	linux-kernel@...r.kernel.org
Subject: Re: atyfb rmmod & vram crash, 2.6.24, 2.6.25-rc8

On Thu, 3 Apr 2008 11:23:36 +0300, Ville  wrote
> This region is always 16MB regardless of how much actual RAM is on 
> the card.
Yes, you are right.
There is 4 chips KM4132G512Q10, each 16Mbit, so it is 8192Kbyte.

> 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.
On some settings it was enough, it was my mistake to try set it to higher
value. But in fact it is difficult to find any documentation, that value is in
Kbyte. Probably at least it have to be documented to be visible in modinfo.

> 
> Does this only happen after the failure caused by the bad vram parameter?
Yes, only by bad vram parameter.


--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/