Announcement

Collapse
No announcement yet.

Linux 3.16-rc5 Kernel Released

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux 3.16-rc5 Kernel Released

    Phoronix: Linux 3.16-rc5 Kernel Released

    Linus Torvalds continued in his Sunday tradition of releasing a new test build of the upcoming Linux kernel release...

    http://www.phoronix.com/vr.php?view=MTc0MDk

  • #2
    I wonder if 3.15 will make it into Debian testing before the freeze.

    Comment


    • #3
      Hey guys, if any of you are having problems with kernel 3.15+ in dual AMD graphics systems, please add yourself to this bug report:
      https://bugzilla.kernel.org/show_bug.cgi?id=79701

      Comment


      • #4
        I have problem with muxless radeon card when runpm is enabled (by default). When card is turned off xserver does not detect it at startup and thus cause that card is not loaded and cannot be used.

        When I change power control from auto to on then card is turned on and never turned off when not used. So these commands (at *correct* pci card address) can be used to touch graphics card and turn it on for some seconds (until auto power management turn if off):

        $ echo on > /sys/bus/pci/devices/0000:01:00.0/power/control || true
        $ echo auto > /sys/bus/pci/devices/0000:01:00.0/power/control || true

        So if I call these commands *before* starting Xserver then radeon card working fine.

        Comment


        • #5
          Originally posted by asdfblah View Post
          Hey guys, if any of you are having problems with kernel 3.15+ in dual AMD graphics systems, please add yourself to this bug report:
          https://bugzilla.kernel.org/show_bug.cgi?id=79701
          I'll add feedback to the bugzilla report, but I've only seen that behavior when I enabled _OSC in my BIOS (it was disabled by-default). With _OSC enabled, I got some PCIEHP error on startup pointing to some PCI device, and the freezing every few seconds (specifically, the mouse cursor would become really hitchy for a bit, then be fine, then repeat).

          Leaving _OSC disabled didn't show any PCIEHP-related errors during startup.

          Comment


          • #6
            @Espionage724: What is _OSC? And how can it be enabled in BIOS?

            Comment


            • #7
              Originally posted by pali View Post
              @Espionage724: What is _OSC? And how can it be enabled in BIOS?
              I'm not entirely sure what it is, but dmesg mentions ASPM along with _OSC, so I think it's basically a power-saving feature of some kind (probably with hotplugging devices).

              I have an unlocked BIOS on my Acer Aspire V3-551G-X419 and it has an _OSC toggle under advanced features or something like that (some sleep settings, HPET, and APIC were also in the section).

              dmesg: http://pastebin.com/raw.php?i=qCqnq1AC

              Code:
              [    0.164761] .... node  #0, CPUs:      #1
              [    0.175853] [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
              [    0.179893]  #2
              [    0.190988] [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
              [    0.205706]  #3
              [    0.205706] [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
              [    0.207861] x86: Booted up 1 node, 4 CPUs
              [    0.207865] smpboot: Total of 4 processors activated (18365.56 BogoMIPS)
              [    0.208867] devtmpfs: initialized
              [    0.212948] PM: Registering ACPI NVS region [mem 0x0006e000-0x0006ffff] (8192 bytes)
              [    0.212951] PM: Registering ACPI NVS region [mem 0xafabf000-0xafbbefff] (1048576 bytes)
              [    0.214222] pinctrl core: initialized pinctrl subsystem
              [    0.214305] RTC time:  8:40:59, date: 07/14/14
              [    0.214389] NET: Registered protocol family 16
              [    0.214598] cpuidle: using governor ladder
              [    0.214601] cpuidle: using governor menu
              [    0.214717] ACPI: bus type PCI registered
              [    0.214719] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
              [    0.214896] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
              [    0.214899] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
              [    0.215004] PCI: Using configuration type 1 for base access
              [    0.220892] ACPI: Added _OSI(Module Device)
              [    0.220902] ACPI: Added _OSI(Processor Device)
              [    0.220907] ACPI: Added _OSI(3.0 _SCP Extensions)
              [    0.220912] ACPI: Added _OSI(Processor Aggregator Device)
              [    0.228637] ACPI: Executed 1 blocks of module-level executable AML code
              [    0.240048] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
              [    0.263593] ACPI: Interpreter enabled
              [    0.263617] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140424/hwxface-580)
              [    0.263636] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140424/hwxface-580)
              [    0.263702] ACPI: (supports S0 S3 S4 S5)
              [    0.263708] ACPI: Using IOAPIC for interrupt routing
              [    0.264474] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
              [    0.407482] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
              [    0.407491] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
              [    0.407500] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
              [    0.407853] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
              [    0.408328] PCI host bridge to bus 0000:00
              [    0.408331] pci_bus 0000:00: root bus resource [bus 00-ff]
              [    0.408334] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]
              [    0.408336] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff]
              [    0.408338] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
              [    0.408341] pci_bus
              Last edited by Espionage724; 07-14-2014, 06:09 AM.

              Comment


              • #8
                Originally posted by Espionage724 View Post
                I'm not entirely sure what it is, but dmesg mentions ASPM along with _OSC, so I think it's basically a power-saving feature of some kind (probably with hotplugging devices).

                I have an unlocked BIOS on my Acer Aspire V3-551G-X419 and it has an _OSC toggle under advanced features or something like that (some sleep settings, HPET, and APIC were also in the section).
                Man, THANK YOU!!
                I also have an unlocked BIOS in my HP laptop... I just disabled OSC and now I'm running 3.16.0-rc2 without any kind of problems...
                This is why I love linux, the people sharing their knowledge makes it great!
                And yeah, I've had many problems in this laptop because of ACPI stuff... sadly, I couldn't even edit the DSDT because it would crash the Intel tool! (lol)
                Anyway, I'm reporting this and also linking to this thread. Again, thank you very much!

                Comment


                • #9
                  If you plan to switch to 3.15/3.16 beware of this bug: https://bugs.freedesktop.org/show_bug.cgi?id=79980
                  ## VGA ##
                  AMD: X1950XTX, HD3870, HD5870
                  Intel: GMA45, HD3000 (Core i5 2500K)

                  Comment


                  • #10
                    I bet Linus just copy/pasted that from a previous kernel cycle. Efficiency...

                    Comment


                    • #11
                      Originally posted by darkbasic View Post
                      If you plan to switch to 3.15/3.16 beware of this bug: https://bugs.freedesktop.org/show_bug.cgi?id=79980
                      Interesting. None of my R600 or RadeonSI systems suffer from this issue in either 3.15 or 3.16 -- mesa or mesa-git.

                      Comment


                      • #12
                        i keep seeing this under 3.16 but have no clue under which product to file the bug under.

                        Code:
                        [ 1372.059584] alloc_contig_range test_pages_isolated(1abfec, 1abff0) failed
                        [ 1419.062792] alloc_contig_range test_pages_isolated(1abfb0, 1abfb8) failed
                        [ 1476.779339] alloc_contig_range test_pages_isolated(1ac090, 1ac09a) failed
                        [ 1476.779348] alloc_contig_range test_pages_isolated(1ac090, 1ac09b) failed
                        [ 1476.779354] alloc_contig_range test_pages_isolated(1ac090, 1ac09f) failed
                        causing graphics problems with programs hanging or pausing for seconds in KDE, once i saw every desktop program lockup but firefox still worked, it's weird.

                        Comment


                        • #13
                          Originally posted by deadite66 View Post
                          i keep seeing this under 3.16 but have no clue under which product to file the bug under.

                          Code:
                          [ 1372.059584] alloc_contig_range test_pages_isolated(1abfec, 1abff0) failed
                          [ 1419.062792] alloc_contig_range test_pages_isolated(1abfb0, 1abfb8) failed
                          [ 1476.779339] alloc_contig_range test_pages_isolated(1ac090, 1ac09a) failed
                          [ 1476.779348] alloc_contig_range test_pages_isolated(1ac090, 1ac09b) failed
                          [ 1476.779354] alloc_contig_range test_pages_isolated(1ac090, 1ac09f) failed
                          causing graphics problems with programs hanging or pausing for seconds in KDE, once i saw every desktop program lockup but firefox still worked, it's weird.
                          I did a search for "alloc_contig_range test_pages_isolated" in http://lxr.free-electrons.com/search , and I found this: http://lxr.free-electrons.com/source/mm/page_alloc.c
                          I have no clue why that would happen. I guess you should google it. (there is, for example, this: http://www.spinics.net/lists/linux-mm/msg70500.html )

                          Comment


                          • #14
                            Originally posted by darkbasic View Post
                            If you plan to switch to 3.15/3.16 beware of this bug: https://bugs.freedesktop.org/show_bug.cgi?id=79980
                            For the record, I experience none of this with 3.15 kernels (don't use 3.16 yet) but I only have APUs : 1 Kaveri, 1 Temash and 2 Brazos.
                            Maybe it's related only to discrete cards?

                            Comment


                            • #15
                              Originally posted by deadite66 View Post
                              i keep seeing this under 3.16 but have no clue under which product to file the bug under.

                              Code:
                              [ 1372.059584] alloc_contig_range test_pages_isolated(1abfec, 1abff0) failed
                              [ 1419.062792] alloc_contig_range test_pages_isolated(1abfb0, 1abfb8) failed
                              [ 1476.779339] alloc_contig_range test_pages_isolated(1ac090, 1ac09a) failed
                              [ 1476.779348] alloc_contig_range test_pages_isolated(1ac090, 1ac09b) failed
                              [ 1476.779354] alloc_contig_range test_pages_isolated(1ac090, 1ac09f) failed
                              causing graphics problems with programs hanging or pausing for seconds in KDE, once i saw every desktop program lockup but firefox still worked, it's weird.
                              I see now what you mean, I got the same error message.
                              I still cannot run 3.16 without the desktop feeling laggy (e.g., when switching windows), and the last time I ran it, the whole system hung completely... I also had to disable _OSC again, because the bug hasn't been fixed. These things are terrible, IMO...

                              Comment

                              Working...
                              X