search for: e114

https://bugs.freedesktop.org/show_bug.cgi?id=87885 Bug ID: 87885 Summary: Fan speed of Nvidia GeForce 9600GT (G94) constantly too high Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

...entation, I am trying to create an xml to share an existing network namespace with another container. I am running libvirt 1.2.15. Here is the xml: <domain type='lxc' xmlns:lxc='http://libvirt.org/schemas/domain/lxc/1.0'> <name>nt</name> <uuid>43c00192-e114-4e29-8ce7-4b5487f60a75</uuid> <memory unit='KiB'>65536</memory> <currentMemory unit='KiB'>65536</currentMemory> <vcpu placement='static'>1</vcpu> <cputune> <shares>2000</shares> </cputune> <...

https://bugs.freedesktop.org/show_bug.cgi?id=98852 Bug ID: 98852 Summary: Nvidia graphics card fan not running or to slow, danger of overheating Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=80901 Priority: medium Bug ID: 80901 Assignee: nouveau at lists.freedesktop.org Summary: [NVCF] PWM fan speed too high under kernel 3.15 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: gianni at rootcube.net Hardware: x86-64 (AMD64)

...>> On 22/11/17 04:06, Ilia Mirkin wrote: >>> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>> Martin's question was very long, but it boils down to this: >>> >>> How do we compute the correct values to write into the e114/e118 pwm >>> registers based on the VBIOS contents and current state of the board >>> (like temperature). >> >> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >> GF119+, or 0x200cd/d0 on Kepler+. >> >> At least, it looks like we...

...d than > what's in that code. Absolutely :) I have not updated Nouveau yet, in fear of setting a value lower than what the proprietary driver does... > > Martin's question was very long, but it boils down to this: > > How do we compute the correct values to write into the e114/e118 pwm > registers based on the VBIOS contents and current state of the board > (like temperature). Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on GF119+, or 0x200cd/d0 on Kepler+. At least, it looks like we know which PWM controler we need to drive, so I did not wan...

...efb f1c5 stored_cheksum = 3efbf1c5 calculated_cheksum = 3efbf1c5 packet_send plain: 0000 0000 0303 41f2 5ed2 a112 7e29 03ff 7095 fd74 29ac 0a29 3201 8556 64bc 4b27 dc4d c8b2 e789 f1b0 7be5 899c b5a4 494e e114 7453 29f3 846e f923 5eea 35d4 07c7 c2d8 28f2 167f a5ba 01ad 6274 cfc1 c64c 9f24 da82 fbcd 6d81 1c66 4ff8 0484 1b62 12b8 d83e 37a2 00b3 abde 85f1 ca1b bf80 1864 8b6c d5c4 1ad8 819e 59b5 6331 ee5f 4814 cfb6 c439 dd42 edc0 a9f8 99fd 1969 0000 0003 705b 27e1 encrypted: 0000 0094 0000 0000 0303 41f2 5ed...

...Mirkin wrote: >>>>> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>>>> Martin's question was very long, but it boils down to this: >>>>> >>>>> How do we compute the correct values to write into the e114/e118 pwm >>>>> registers based on the VBIOS contents and current state of the board >>>>> (like temperature). >>>> >>>> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >>>> GF119+, or 0x200cd/d0 on Kepler+. >&...

...gt;>> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>>>>>> Martin's question was very long, but it boils down to this: >>>>>>> >>>>>>> How do we compute the correct values to write into the e114/e118 pwm >>>>>>> registers based on the VBIOS contents and current state of the board >>>>>>> (like temperature). >>>>>> >>>>>> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >>>>>>...

Hi Martin, I was asked to clarify a few things: (1) Are all the user reports of loud fans on Fermi-era GPUs? (2) When the VBIOS POSTs the card, it loads initial ucode onto the Falcon processor (PMU), which will do basic fan management on its own. We call this init ucode "IFR" (Init From ROM). nvidia.ko will restore the IFR ucode when unloaded. I assume the loud fan symptom occurs

...answer, Andy! > > On 22/11/17 04:06, Ilia Mirkin wrote: >> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >> Martin's question was very long, but it boils down to this: >> >> How do we compute the correct values to write into the e114/e118 pwm >> registers based on the VBIOS contents and current state of the board >> (like temperature). > > Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on > GF119+, or 0x200cd/d0 on Kepler+. > > At least, it looks like we know which PWM controler w...

...ml to >share an existing network namespace with another container. I am running >libvirt 1.2.15. > >Here is the xml: > ><domain type='lxc' xmlns:lxc='http://libvirt.org/schemas/domain/lxc/1.0'> > > <name>nt</name> > <uuid>43c00192-e114-4e29-8ce7-4b5487f60a75</uuid> > <memory unit='KiB'>65536</memory> > <currentMemory unit='KiB'>65536</currentMemory> > <vcpu placement='static'>1</vcpu> > <cputune> > <shares>2000</shares> >...

...n_set, I believe). The bios stuff is parsed in nvkm/subdev/bios/fan.c and therm.c, although I believe Martin's latest analysis is more advanced than what's in that code. Martin's question was very long, but it boils down to this: How do we compute the correct values to write into the e114/e118 pwm registers based on the VBIOS contents and current state of the board (like temperature). We generally do this right, but appear to get it extra-wrong for certain GPUs. Cheers, -ilia

...namespace with another container. I am running >> libvirt 1.2.15. >> >> Here is the xml: >> >> <domain type='lxc' xmlns:lxc='http://libvirt.org/schemas/domain/lxc/1.0'> >> >> <name>nt</name> >> <uuid>43c00192-e114-4e29-8ce7-4b5487f60a75</uuid> >> <memory unit='KiB'>65536</memory> >> <currentMemory unit='KiB'>65536</currentMemory> >> <vcpu placement='static'>1</vcpu> >> <cputune> >> <shares>2000&...

...1/17 04:06, Ilia Mirkin wrote: >>>> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>>> Martin's question was very long, but it boils down to this: >>>> >>>> How do we compute the correct values to write into the e114/e118 pwm >>>> registers based on the VBIOS contents and current state of the board >>>> (like temperature). >>> >>> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >>> GF119+, or 0x200cd/d0 on Kepler+. >>> >>>...

...gt;>>>>> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>>>>> Martin's question was very long, but it boils down to this: >>>>>> >>>>>> How do we compute the correct values to write into the e114/e118 pwm >>>>>> registers based on the VBIOS contents and current state of the board >>>>>> (like temperature). >>>>> >>>>> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >>>>> GF119+, or 0x200cd/...

...gt;>> On Tue, Nov 21, 2017 at 8:29 PM, Andy Ritger <aritger at nvidia.com> wrote: >>>>>>> Martin's question was very long, but it boils down to this: >>>>>>> >>>>>>> How do we compute the correct values to write into the e114/e118 pwm >>>>>>> registers based on the VBIOS contents and current state of the board >>>>>>> (like temperature). >>>>>> >>>>>> Unfortunately, it can also be the e11c/e120 couple, or 0x200d8/dc on >>>>>>...