Bug 1464768 - When will it be resolved???? And a really very dated bug [NEEDINFO]
Summary: When will it be resolved???? And a really very dated bug
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 26
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-25 15:02 UTC by xzj8b3
Modified: 2018-04-04 18:32 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-02 18:03:07 UTC
Type: Bug
Embargoed:
xzj8b3: needinfo?


Attachments (Terms of Use)
When will it be resolved???? And a really very dated bug (82.72 KB, text/plain)
2017-06-25 15:02 UTC, xzj8b3
no flags Details

Description xzj8b3 2017-06-25 15:02:47 UTC
Created attachment 1291722 [details]
When will it be resolved???? And a really very dated bug

[    0.000000] microcode: microcode updated early to revision 0x20, date = 2017-01-27
[    0.000000] Linux version 4.11.6-301.fc26.x86_64 (mockbuild.fedoraproject.org) (gcc version 7.1.1 20170526 (Red Hat 7.1.1-2) (GCC) ) #1 SMP Tue Jun 20 16:17:33 UTC 2017
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.11.6-301.fc26.x86_64 root=/dev/mapper/fedora_fedora-root ro rd.lvm.lv=fedora_fedora/root rd.luks.uuid=luks-8ffd1aa2-728a-46a9-89a4-d2dd63afbdf8 rd.lvm.lv=fedora_fedora/swap rhgb quiet LANG=it_IT.UTF-8
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' forma
[    0.245600] ACPI : EC: interrupt blocked
[    0.247218] ACPI: \: Used as first EC
[    0.247219] ACPI: \: GPE=0xa, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.247220] ACPI: \: Used as boot ECDT EC to handle transactions
[    0.247454] ACPI: Executed 2 blocks of module-level executable AML code
[    0.254979] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.257368] ACPI: Dynamic OEM Table Load:
[    0.257375] ACPI: SSDT 0xFFFF948E251A0400 0003D3 (v01 PmRef  Cpu0Cst  00003001 INTL 20120711)
[    0.257807] ACPI: Dynamic OEM Table Load:
[    0.257814] ACPI: SSDT 0xFFFF948E25177800 0005AA (v01 PmRef  ApIst    00003000 INTL 20120711)
[    0.258293] ACPI: Dynamic OEM Table Load:
[    0.258298] ACPI: SSDT 0xFFFF948E25196600 000119 (v01 PmRef  ApCst    00003000 INTL 20120711)
[    0.259554] ACPI : EC: EC stopped
[    0.259555] ACPI : EC: EC started
[    0.259556] ACPI : EC: interrupt blocked
[    0.259693] ACPI: \_SB_.PCI0.LPCB.EC0_: Used as first EC
[    0.259695] ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0xa, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.259696] ACPI: \_SB_.PCI0.LPCB.EC0_: Used as boot DSDT EC to handle transactions
[    0.259697] ACPI: Interpreter enabled
[    0.259742] ACPI: (supports S0 S3 S4 S5)
[    0.259743] ACPI: Using IOAPIC for interrupt routing
[    0.259771] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.263780] ACPI: Power Resource [PC05] (on)
[    0.276131] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[    0.276136] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.276801] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
[    0.276802] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
[    0.277255] PCI host bridge to bus 0000:00
[    0.277258] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.277259] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[ 
[  119.733649] RAX: 0000000000000000 RBX: 0000001be0ab56b4 RCX: 000000000000001f
[  119.733650] RDX: 0000001be0ab56b4 RSI: ffff948e2ef96dd8 RDI: 0000000000000000
[  119.733651] RBP: ffffbe6100cfbe98 R08: cccccccccccccccd R09: 0000000000000018
[  119.733652] R10: ffffbe6100cfbe30 R11: 00000000000011ae R12: ffff948e2efa1600
[  119.733653] R13: ffffffff99ef3c60 R14: 0000000000000003 R15: ffffffff99ef3c78
[  119.733654]  </IRQ>
[  119.733659]  cpuidle_enter+0x17/0x20
[  119.733662]  call_cpuidle+0x23/0x40
[  119.733665]  do_idle+0x18a/0x200
[  119.733668]  cpu_startup_entry+0x71/0x80
[  119.733673]  start_secondary+0x154/0x190
[  119.733676]  start_cpu+0x14/0x14
[  119.733678] ---[ end trace f54bdecc64d70d68 ]---
[  119.739869] r8169 0000:02:00.0 enp2s0: link up



SEE FILES WHITE MORE DETAILS PLEACE!!!!!!

Comment 1 Laura Abbott 2018-02-28 03:57:07 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs.
 
Fedora 26 has now been rebased to 4.15.4-200.fc26.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27.
 
If you experience different issues, please open a new bug report for those.

Comment 2 xzj8b3 2018-03-01 14:37:38 UTC
With great regret passed momentarily to Windows 10 in that with an ATI R5 M230 with Open notebook driver warmed up too and every time I ran the fan was shooting at 1000, creating a crash..... Wifi and network no longer connect with latest kernels..... Hardware isn't ' recent, however I don't think it should create all these problems.... I have an Asus laptop with an I7-4510U

Hopefully within a year Fedora come back to shine!!!!!

Comment 3 xzj8b3 2018-03-01 14:38:18 UTC
With great regret passed momentarily to Windows 10 in that with an ATI R5 M230 with Open notebook driver warmed up too and every time I ran the fan was shooting at 1000, creating a crash..... Wifi and network no longer connect with latest kernels..... Hardware isn't ' recent, however I don't think it should create all these problems.... I have an Asus laptop with an I7-4510U

Hopefully within a year Fedora come back to shine!!!!!

Comment 4 xzj8b3 2018-04-04 18:32:20 UTC

Problems always due to the bug in the link below reported more correctly!!!!


https://bugzilla.redhat.com/show_bug.cgi?id=1560763


Note You need to log in before you can comment on or make changes to this bug.