With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video memory misdetected as 512 Mb : result was kernel panic in worst case and memory crash in best case

Bug #1737423 reported by Jean COLIN
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Under XP
card detected as
PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&3A321F38&0&48F0

PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&3A321F38&0&48F0

PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1
PCI\VEN_10DE&DEV_0221&CC_030000

memory range 94000000 94FFFFFF
memory range C0000000 DFFFFFFF
memory range 92000000 92FFFFFF
IRQ 09
IO range 03B0 03BB
IO range 03C0 03DF
memory range 000A0000 000BFFFF

Processeur graphique : GeForce 6200
Version du pilote : 307.83
Prise en charge DirectX : 9.0c
Horloge principale : 300 MHz
Débit de données mémoire : 1064 MHz
Interface de mémoire : 64 bits
Mémoire : 256 Mo
Type de mémoire : DDR2
Version BIOS vidéo : 5.44.A2.10.26
IRQ : 9
Bus : PCI

correctly detected as 256Mb and working

Under linux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:0000:0000 rev 161, Mem @ 0x94000000/16777216, 0xc0000000/536870912, 0x92000000/16777216, BIOS @ 0x????????/131072
card bad detection ... 0xc0000000/536870912 correct adress, wrong size 536870912 soit 512Mo

output of:

sudo lshw -C display; lsb_release -a; uname -a

is

jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
  *-display
       description: Display controller
       produit: 82865G Integrated Graphics Controller
       fabriquant: Intel Corporation
       identifiant matériel: 2
       information bus: pci@0000:00:02.0
       version: 02
       bits: 32 bits
       horloge: 33MHz
       fonctionnalités: pm bus_master cap_list rom
       configuration: driver=i915 latency=0
       ressources: irq:16 mémoire:a0000000-a7ffffff mémoire:90000000-9007ffff portE/S:1800(taille=8)
  *-display
       description: VGA compatible controller
       produit: NV44A [GeForce 6200]
       fabriquant: NVIDIA Corporation
       identifiant matériel: 9
       information bus: pci@0000:03:09.0
       version: a1
       bits: 32 bits
       horloge: 66MHz
       fonctionnalités: pm vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=40 maxlatency=1 mingnt=5
       ressources: irq:21 mémoire:94000000-94ffffff mémoire:c0000000-dfffffff mémoire:92000000-92ffffff mémoire:e0000000-e001ffff
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
Linux jean-Soisy 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 11:56:31 UTC 2017 i686 i686 i686 GNU/Linux

Attempted to find where the memory size detection lies in the code, but was too far in the labyrinth for me.

Regards

Jean COLIN
---
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jean 2206 F.... pulseaudio
 /dev/snd/controlC0: jean 2206 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=2ae1454f-4490-4a9a-aea5-55daa49c243c
InstallationDate: Installed on 2015-08-08 (985 days ago)
InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820)
MachineType: IBM 8429RG7
Package: linux (not installed)
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-144-generic root=UUID=0f7280ad-8482-48be-9433-13ca09f7304a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-144-generic N/A
 linux-backports-modules-3.13.0-144-generic N/A
 linux-firmware 1.127.24
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: trusty
Uname: Linux 3.13.0-144-generic i686
UpgradeStatus: Upgraded to trusty on 2015-08-08 (985 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/06/2005
dmi.bios.vendor: IBM
dmi.bios.version: 2AKT51AUS
dmi.board.name: IBM
dmi.board.vendor: IBM
dmi.chassis.asset.tag: ������������������������
dmi.chassis.type: 4
dmi.chassis.vendor: IBM
dmi.modalias: dmi:bvnIBM:bvr2AKT51AUS:bd07/06/2005:svnIBM:pn8429RG7:pvr:rvnIBM:rnIBM:rvr:cvnIBM:ct4:cvr:
dmi.product.name: 8429RG7
dmi.sys.vendor: IBM

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1737423/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Jean COLIN (carl174) wrote :

Difficult to determine package
-could the driver itself (nouveau or proprietary)
-could be false information given by the kernel to the driver...

seems to have similarities with
https://h-node.org/videocards/view/fr/379/NVIDIA-Corporation-NV44A--GeForce-6200----rev-a1-

detected as 512Mo by sysinfo

lspci verbose give
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev a1) (prog-if 00 [VGA controller])
 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: 40 (1250ns min, 250ns max)
 Interrupt: pin A routed to IRQ 21
 Region 0: Memory at 94000000 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at c0000000 (32-bit, prefetchable) [size=512M]
 Region 2: Memory at 92000000 (32-bit, non-prefetchable) [size=16M]
 [virtual] Expansion ROM at e0000000 [disabled] [size=128K]
 Capabilities: [60] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: nouveau

in
/usr/share/misc/pci.ids.gz
timestamp 2015

group is
 0221 NV44A [GeForce 6200]
  1043 81e1 N6200/TD/256M/A
  3842 a341 256A8N341DX

attempted (to limit video card memory use)
in /etc/X11/xorg.conf
Section "NVIDIA Corporation NV44A [GeForce 6200] (rev a1)"
    Driver "nouveau"
    Busid "03:09.0"
    VideoRam 262144
EndSection

has not worked

made several others attempts, none worked
Not able to determine if the reason is incorrect syntax (explanations are hardly available) or not

Actually, i think that one possibility is :
card memory range is 512Mo (de C0000000 à DFFFFFFF = 512Mo) , but only 256mb populated

Regards

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1737423

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: trusty
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc3

Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Jean COLIN (carl174) wrote :

This computer is installed in a secondary house, and it is not planned to use it before March 2010

Was fresh install

Will run command apport-collect 1737423 but in some month

Will test the kernel you indicate, but in some month

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Jean COLIN (carl174) wrote :

installed v4.15-rc3 and booted

HardInfo 0.5.1 continues to display 512Mo memory (wrong, real is 256)
-PCI Devices-
VGA compatible controller : NVIDIA Corporation NV44A [GeForce 6200] (rev a1) (prog-if 00 [VGA controller])
Memory 512MB(32-bit,prefetchable)

Revision history for this message
Jean COLIN (carl174) wrote :

installed v4.15-rc3 and booted

HardInfo 0.5.1 continues to display 512Mo memory (wrong, real is 256)
-PCI Devices-
VGA compatible controller : NVIDIA Corporation NV44A [GeForce 6200] (rev a1) (prog-if 00 [VGA controller])
Memory 512MB(32-bit,prefetchable)

Regards

tags: added: apport-collected
description: updated
Revision history for this message
Jean COLIN (carl174) wrote : AlsaInfo.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : BootDmesg.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : CRDA.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : IwConfig.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : Lspci.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : Lsusb.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : ProcEnviron.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : ProcModules.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : PulseList.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : UdevDb.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : UdevLog.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote : WifiSyslog.txt

apport information

Revision history for this message
Jean COLIN (carl174) wrote :

addaed tag kernel-bug-exists-upstream
regards

tags: added: kernel-bug-exists-upstream
removed: apport-collected
tags: added: apport-collected
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you try v4.17-rc3?

Revision history for this message
Jean COLIN (carl174) wrote :

Will use the computer saturday 12, will make the test (may be sunday)

Regards ans thanks

Revision history for this message
Jean COLIN (carl174) wrote :

Hello

Attempted to try v4.17-rc3

BUT, v4.17-rc3 not available in 1386 ...

Attempted to try v4.17-rc4 in i386 (available)

BUT got a dependency problem linux-image AND linux-base

AND Got an error when installing linux base ... AND finally got an error when attempting to uninstall linux image 4.17 rc4

dpkg: erreur de traitement du paquet linux-image-4.17.0-041700rc4-generic (--remove) :
 le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 127
Des erreurs ont été rencontrées pendant l'exécution :
 linux-image-4.17.0-041700rc4-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

seems that bugs are multiplicating (like cartoon rabbits)

So, if you have a solution to recover a clean situation, prerequired for next attempt

Regards

Revision history for this message
Jean COLIN (carl174) wrote :

in file
/var/lib/dpkg/info/linux-image-4.17.0-041700rc4-generic.prerm

had to comment out

#linux-check-removal $version

to be able to remove
linux-image-4.17.0-041700rc4-generic

and then be able to make further test

A little annoying...

Regards

Revision history for this message
Jean COLIN (carl174) wrote :

Attempted to try v4.17-rc5

got a dependency problem ... linux-base (>=4.5ubuntu1~16.04.1

So the answer of the question "Can you try v4.17-rc3?" is NO because

v4.17-rc5 i386 not vailable

v4.17-rc4 i386 impossible to install

v4.17-rc5 i386 dependecy problem

Regards

Jean COLIN

Revision history for this message
Jean COLIN (carl174) wrote : re: [Bug 1737423] Re: With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video memory misdetected as 512 Mb : result was kernel panic in worst case and memory crash in best case
Download full text (5.3 KiB)

Hello

The answer of the question "Can you try v4.17-rc3?" is NO because

v4.17-rc3 i386 not available

v4.17-rc4 i386 impossible to install and very difficult to remove to be able to go futher

     in file /var/lib/dpkg/info/linux-image-4.17.0-041700rc4-generic.prerm

     had to comment out #linux-check-removal $version

v4.17-rc5 i386 got dependecy problem

    linux-base (>=4.5ubuntu1~16.04.1)

Regards

Jean COLIN

> Message du 08/05/18 07:41
> De : "Kai-Heng Feng"
> A : <email address hidden>
> Copie à :
> Objet : [Bug 1737423] Re: With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video memory misdetected as 512 Mb : result was kernel panic in worst case and memory crash in best case
>
> Can you try v4.17-rc3?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737423
>
> Title:
> With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video
> memory misdetected as 512 Mb : result was kernel panic in worst case
> and memory crash in best case
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> Under XP
> card detected as
> PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&3A321F38&0&48F0
>
> PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1\4&3A321F38&0&48F0
>
> PCI\VEN_10DE&DEV_0221&SUBSYS_00000000&REV_A1
> PCI\VEN_10DE&DEV_0221&CC_030000
>
> memory range 94000000 94FFFFFF
> memory range C0000000 DFFFFFFF
> memory range 92000000 92FFFFFF
> IRQ 09
> IO range 03B0 03BB
> IO range 03C0 03DF
> memory range 000A0000 000BFFFF
>
> Processeur graphique : GeForce 6200
> Version du pilote : 307.83
> Prise en charge DirectX : 9.0c
> Horloge principale : 300 MHz
> Débit de données mémoire : 1064 MHz
> Interface de mémoire : 64 bits
> Mémoire : 256 Mo
> Type de mémoire : DDR2
> Version BIOS vidéo : 5.44.A2.10.26
> IRQ : 9
> Bus : PCI
>
> correctly detected as 256Mb and working
>
>
> Under linux
> file /var/log/Xorg.0.log
> contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:0000:0000 rev 161, Mem @ 0x94000000/16777216, 0xc0000000/536870912, 0x92000000/16777216, BIOS @ 0x????????/131072
> card bad detection ... 0xc0000000/536870912 correct adress, wrong size 536870912 soit 512Mo
>
> output of:
>
> sudo lshw -C display; lsb_release -a; uname -a
>
> is
>
> jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
> [sudo] password for jean:
> *-display
> description: Display controller
> produit: 82865G Integrated Graphics Controller
> fabriquant: Intel Corporation
> identifiant matériel: 2
> information bus: pci@0000:00:02.0
> version: 02
> bits: 32 bits
> horloge: 33MHz
> fonctionnalités: pm bus_master cap_list rom
> configuration: driver=i915 latency=0
> ressources: irq:16 mémoire:a0000000-a7ffffff mémoire:90000000-9007ffff portE/S:1800(taille=8)
> *-display
> description: VGA compatible controller
> produit: NV44A [GeForce 6200]
> fabriquant: NVIDIA Corporation
> identifiant matériel: 9
> information bus: pci@0000:03:09.0
> version: a1
> bits: 32 bits
> horloge: 66MHz
> fonctionnalités: pm vga_controller bus_master cap_list rom
> configuration: driver=nouveau latency=40 maxlatency=1 mingnt=5
> res...

Read more...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Sorry didn't notice that you use i386 instead of AMD64.

Do you see this bug under AMD64?

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/nouveau

Revision history for this message
Jean COLIN (carl174) wrote :
Download full text (42.8 KiB)

Hello

Not tested under AMD64

My problem is to have a graphic processor on a (old pentium) computer without agp port to be able to edit video.

I made the choice to have in this secondary house an old (at very low cost) desktop computer with a comfortable 24' screen and to travel with an usb key (lighter than a portable computer)

And my (Main use at home) is an AMD64 with graphic processor on video card

I looked at my notes about this computer

with nvidia proprietary driver, had problem

with nouveau, worked with screen connected with VGA cable, but not correctly centered (something like colomn 1 outside the screen)

with nouveau, connected with DVI cable, had problem

file (copied month ago) /var/log/Xorg.0.log

contained (key elements i noted)

18.759] (--) PCI: (0:3:9:0) 10de:0221:0000:0000 rev 161, Mem @ 0x94000000/16777216, 0xc0000000/536870912, 0x92000000/16777216, BIOS @ 0x????????/131072

[    18.806] (==) Matched nvidia as autoconfigured driver 1
[    18.806] (==) Matched nouveau as autoconfigured driver 2

[    18.810] (II) LoadModule: "nvidia"
[    18.814] (WW) Warning, couldn't open module nvidia
[    18.814] (II) UnloadModule: "nvidia"
[    18.815] (II) Unloading nvidia
[    18.815] (EE) Failed to load module "nvidia" (module does not exist, 0)
[    18.815] (II) LoadModule: "nouveau"
[    18.819] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[    18.825] (II) Module nouveau: vendor="X.Org Foundation"
[    18.825]     compiled for 1.15.0, module version = 1.0.10
[    18.826]     Module class: X.Org Video Driver
[    18.826]     ABI class: X.Org Video Driver, version 15.0

So, wrong detection at 18.759 before loading nividia and nouveau

0xc0000000/536870912 adresse correct , but size 536870912 = 512Mo incorrect

searched in the source i was able to find, arrived at

nouveau_device_get_param(struct nouveau_device *dev,
             uint64_t param, uint64_t *value)
{
    struct nouveau_device_priv *nvdev = nouveau_device(dev);
    struct drm_nouveau_getparam g;
    int ret;

    if (!nvdev || !value)
        return -EINVAL;

    g.param = param;
    ret = drmCommandWriteRead(nvdev->fd, DRM_NOUVEAU_GETPARAM,
                  &g, sizeof(g));
    if (ret)
        return ret;

    *value = g.value;
    return 0;
}

attempted to limit use of memory, using, VideoRam 262144 but not succeeded

For me, the goog thing to do is to be able to recover the information obtained at hardware level

done lspci

jean@jean-Soisy:~$ lspci -v -s 03:09.0
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev a1) (prog-if 00 [VGA controller])
    Flags: bus master, 66MHz, medium devsel, latency 40, IRQ 21
    Memory at 94000000 (32-bit, non-prefetchable) [size=16M]
    Memory at c0000000 (32-bit, prefetchable) [size=512M]
    Memory at 92000000 (32-bit, non-prefetchable) [size=16M]
    [virtual] Expansion ROM at e0000000 [disabled] [size=128K]
    Capabilities:
    Kernel driver in use: nouveau

done lspci in verbose mode

jean@jean-Soisy:~$ sudo lspci -v -k -x -s 03:09.0
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev a1) (prog-if 00 [V...

Revision history for this message
Jean COLIN (carl174) wrote :
Download full text (3.1 KiB)

Found some document about size determination in pci devices

had run lspi
jean@jean-Soisy:~$ sudo lspci -vv -k -xxxx -s 03:09.0
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev a1) (prog-if 00 [VGA controller])
 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: 40 (1250ns min, 250ns max)
 Interrupt: pin A routed to IRQ 21
 Region 0: Memory at 94000000 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at c0000000 (32-bit, prefetchable) [size=512M]
 Region 2: Memory at 92000000 (32-bit, non-prefetchable) [size=16M]
 [virtual] Expansion ROM at e0000000 [disabled] [size=128K]
 Capabilities: [60] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Kernel driver in use: nouveau
00: de 10 21 02 06 01 b0 02 a1 00 00 03 00 28 00 00
10: 00 00 00 94 08 00 00 c0 00 00 00 92 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 60 00 00 00 00 00 00 00 09 01 05 01
40: 00 00 00 00 02 00 30 00 03 00 00 1f 00 00 00 00
50: 00 00 00 00 01 00 00 00 ce d6 23 00 0f 00 00 00
60: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 01 04 40 c1 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

So, value defines as BAR1 located at adress 0x14 in parameters with value 08 00 00 c0

means : adress is 0xc0000000 with 0x8 = prefetchable

for memory size determination methos is
https://wiki.osdev.org/PCI
https://stackoverflow.com/questions/19006632/how-is-a-pci-pcie-bar-size-determined/39618552#39618552

To determine the amount of address space needed by a PCI device, you must save the original value of the BAR,
write a value of all 1's to the register, then read it back.
The amount of memory can then be determined by masking the information bits, performing a bitwise NOT ('~' in C), and incrementing the value by 1. The original value of the BAR should then be restored.

on my computer : using sudo bless
parameter are located at /sys/bus/pci/devices/0000:03:09.0/config
replaced 08 00 00 c0 by ff ff ff ff then, computer blocked, but was able to read 08 00 00 e0

that means
dropping 4 bits LSB -> 00 00 00 e0
inverting bitwise ff ff ff 10
adding one 00 00 00 20 means 512 M

BUT https://www.xilinx.com/Attachment/PCI_SPEV_V3_0.pdf
6.2.5.1. Address Maps
Devices are free to consume more address space than required

after explanation of a computation method, precision is given

The resultant 32-bit value is the memory/I/O range size decoded by the register.

I Think that the problem is here = adress space decoded, but not populated

Regards

Jean CO...

Read more...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Looks like the RAM size is correctly detected:
[ 10.572891] nouveau [ DEVICE][0000:03:09.0] BOOT0 : 0x04a100a1
[ 10.572897] nouveau [ DEVICE][0000:03:09.0] Chipset: NV44A (NV4A)
[ 10.572903] nouveau [ DEVICE][0000:03:09.0] Family : NV40
[ 10.579195] nouveau [ VBIOS][0000:03:09.0] checking PRAMIN for image...
[ 10.579208] nouveau [ VBIOS][0000:03:09.0] ... signature not found
[ 10.579213] nouveau [ VBIOS][0000:03:09.0] checking PROM for image...
[ 10.900540] nouveau [ VBIOS][0000:03:09.0] ... appears to be valid
[ 10.900544] nouveau [ VBIOS][0000:03:09.0] using image from PROM
[ 10.900760] nouveau [ VBIOS][0000:03:09.0] BIT signature found
[ 10.900767] nouveau [ VBIOS][0000:03:09.0] version 05.44.a2.10.01
[ 10.913241] nouveau [ DEVINIT][0000:03:09.0] adaptor not initialised
[ 10.913253] nouveau [ VBIOS][0000:03:09.0] running init tables
[ 10.931444] nouveau [ PFB][0000:03:09.0] RAM type: DDR2
[ 10.931448] nouveau [ PFB][0000:03:09.0] RAM size: 256 MiB

You can use HWE stack for newer kernel and newer Xorg:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Ubuntu_14.04_LTS_-_Trusty_Tahr
[ 10.931451] nouveau [ PFB][0000:03:09.0] ZCOMP: 0 tags

Revision history for this message
Jean COLIN (carl174) wrote :
Download full text (4.5 KiB)

upgraded to 16.04
now kernel is (standard 16.04) 4.4.0-130-generic(i686)

seems that kernel detected
[ 0.195806] pci 0000:03:09.0: [10de:0221] type 00 class 0x030000
[ 0.195830] pci 0000:03:09.0: reg 0x10: [mem 0x94000000-0x94ffffff]
[ 0.195840] pci 0000:03:09.0: reg 0x14: [mem 0xc0000000-0xdfffffff pref]
[ 0.195850] pci 0000:03:09.0: reg 0x18: [mem 0x92000000-0x92ffffff]
[ 0.195876] pci 0000:03:09.0: reg 0x30: [mem 0x00000000-0x0001ffff pref]

then vga
[ 0.209868] vgaarb: setting as boot device: PCI:0000:00:02.0
[ 0.209868] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.209868] vgaarb: device added: PCI:0000:03:09.0,decodes=io+mem,owns=none,locks=none
[ 0.209868] vgaarb: loaded
[ 0.209868] vgaarb: bridge control possible 0000:03:09.0
[ 0.209868] vgaarb: no bridge control possible 0000:00:02.0

then nouveau
[ 2.503759] nouveau 0000:03:09.0: enabling device (0104 -> 0106)
[ 2.504397] nouveau 0000:03:09.0: NVIDIA NV44A (04a100a1)

[ 2.684040] nouveau 0000:03:09.0: bios: version 05.44.a2.10.01

[ 2.702984] nouveau 0000:03:09.0: fb: 256 MiB DDR2
[ 2.783562] [TTM] Zone kernel: Available graphics memory: 439234 kiB
[ 2.783569] [TTM] Zone highmem: Available graphics memory: 1022630 kiB
[ 2.783572] [TTM] Initializing pool allocator
[ 2.783585] [TTM] Initializing DMA pool allocator
[ 2.783612] nouveau 0000:03:09.0: DRM: VRAM: 252 MiB
[ 2.783617] nouveau 0000:03:09.0: DRM: GART: 128 MiB
[ 2.783624] nouveau 0000:03:09.0: DRM: TMDS table version 1.1
[ 2.783628] nouveau 0000:03:09.0: DRM: DCB version 3.0
[ 2.783633] nouveau 0000:03:09.0: DRM: DCB outp 00: 02001310 00000028
[ 2.783640] nouveau 0000:03:09.0: DRM: DCB outp 01: 01001312 00000020
[ 2.783645] nouveau 0000:03:09.0: DRM: DCB outp 02: 01010300 00000028
[ 2.783649] nouveau 0000:03:09.0: DRM: DCB outp 03: 020223f1 00c0c030
[ 2.783653] nouveau 0000:03:09.0: DRM: DCB conn 00: 0000
[ 2.783657] nouveau 0000:03:09.0: DRM: DCB conn 01: 2230
[ 2.783661] nouveau 0000:03:09.0: DRM: DCB conn 02: 0110
[ 2.783665] nouveau 0000:03:09.0: DRM: DCB conn 03: 0111
[ 2.783668] nouveau 0000:03:09.0: DRM: DCB conn 04: 0113
[ 2.783682] nouveau 0000:03:09.0: DRM: Adaptor not initialised, running VBIOS init tables.
[ 2.783968] nouveau 0000:03:09.0: DRM: Saving VGA fonts
[ 2.874057] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.874063] [drm] Driver supports precise vblank timestamp query.
[ 2.874073] nouveau 0000:03:09.0: DRM: 0xD2AC: Parsing digital output script table
[ 2.930799] nouveau 0000:03:09.0: DRM: MM: using M2MF for buffer copies
[ 2.930820] nouveau 0000:03:09.0: DRM: Setting dpms mode 3 on TV encoder (output 3)
[ 2.980033] usb 1-5: new high-speed USB device number 4 using ehci-pci
[ 3.016034] nouveau 0000:03:09.0: No connectors reported connected with modes
[ 3.016097] [drm] Cannot find any crtc or sizes - going 1024x768
[ 3.016472] nouveau 0000:03:09.0: DRM: allocated 1024x768 fb: 0x9000, bo f6357400
[ 3.016665] nouveau 0000:03:09.0: fb1: nouveaufb frame buffer device
[ 3.016683] [drm] Initialized nouveau 1.3.1 20120801 for 0...

Read more...

Revision history for this message
Jean COLIN (carl174) wrote :

Made a test yesterday, to see if the "normal update" has an effect
Result was kernel panic, as previous
see attached screen capture

Revision history for this message
Jean COLIN (carl174) wrote :

-Version-
Kernel : Linux 4.4.0-131-generic (i686)
Compiled : #157-Ubuntu SMP Thu Jul 12 15:49:15 UTC 2018
Distribution : Ubuntu 16.04.5 LTS

Brad Figg (brad-figg)
tags: added: cscc
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.