All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 110714] Xorg crashes randomly because of memory leak
Date: Fri, 12 Jul 2019 05:23:10 +0000	[thread overview]
Message-ID: <bug-110714-8800-B2LEmi1Qhn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110714-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 4377 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=110714

--- Comment #11 from Peter Draganov <pdraganov-8RvTx9/d5SBBDgjK7y7TUQ@public.gmane.org> ---
> what GPU do you have? I am especially interested in the amount of VRAM it has.
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev
a2) (prog-if 00 [VGA controller])
        Subsystem: Micro-Star International Co., Ltd. [MSI] N210 [Geforce 210]
PCIe graphics adapter
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 31
        NUMA node: 0
        Region 0: Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
        Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Region 3: Memory at ce000000 (64-bit, prefetchable) [size=32M]
        Region 5: I/O ports at ec00 [size=128]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [60] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
                Address: 00000000fee02004  Data: 4026
        Capabilities: [78] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
unlimited, L1 <64us
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
SlotPowerLimit 75.000W
                DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
                        RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr-
TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Exit
Latency L0s <256ns, L1 <4us
                        ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
                LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s (ok), Width x16 (ok)
                        TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-,
OBFF Not Supported
                         AtomicOpsCap: 32bit- 64bit- 128bitCAS-
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-,
OBFF Disabled
                         AtomicOpsCtl: ReqEn-
                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
                         Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB,
EqualizationComplete-, EqualizationPhase1-
                         EqualizationPhase2-, EqualizationPhase3-,
LinkEqualizationRequest-
        Capabilities: [b4] Vendor Specific Information: Len=14 <?>
        Capabilities: [100 v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
                        Status: NegoPending- InProgress-
        Capabilities: [128 v1] Power Budgeting <?>
        Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1
Len=024 <?>
        Kernel driver in use: nouveau
        Kernel modules: nouveau

I was with another old NVidia card when crashes started, so I decided to
replace it, but this did not help. I was with Fedora 22 intil April and started
upgrading it every day. Crashes started when I reached Fedora 24-25-26 probably
and continues until last Fedora 30, if this can help.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 5220 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2019-07-12  5:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20  8:38 [Bug 110714] New: Xorg crashes randomly because of memory leak bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-110714-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-05-20 10:03   ` [Bug 110714] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-20 11:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-20 18:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-03  6:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-03  6:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-03  7:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-03 12:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-04 10:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-05 12:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-11 17:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-12  5:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-07-12  8:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-12 11:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-12 12:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-22 20:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-22 20:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-22 20:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-22 22:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-06 16:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-06 16:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-06 16:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-07 14:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-07 14:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-110714-8800-B2LEmi1Qhn@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.