Hi,
I have a 15 inch HP Spectre 360 running Fedora 28, it runs fine using nouveau video and wireless works. I tried to upgrade to Fedora 29. After upgrade with dnf it is fairly broken. Everything came up on the surface, but it was sluggish and sudo bash was very slow to authenticate and it was popping multiple oops messages at the top of the screen. I then did a fresh install of Fedora 29. This seemed to mostly work and no immediate sluggishness once done. I then upgraded using dnf to the latest software. This is where the bad behavior came from. After dnf upgrade sluggishness on sudo again as opposed to instantaneous authentication before dnf, wifi could now not be shut off. Oops messages on top of screen and complaining about one of the cpu's in dmesg and also complaining about Noveau. Wifi became broken and gnome network manager to shut it off wouldn't do anything. The icon showed as up with signal but a browser wouldn't work. When it popped up report screen to report kernel problem it was populated with no info and all you could really do was close it. Funny thing is I did a fresh install of 29 first on my Samsung laptop which has strictly intel graphics and different wireless and everything works 100% on that laptop.
Thanks, any thoughts would be appreciated, I put Fedora 28 back on the HP and its fine with all the latest software there.
Brian
On Wed, 2018-12-12 at 20:55 -0800, Mr Brian Domenick wrote:
Hi,
I have a 15 inch HP Spectre 360 running Fedora 28, it runs fine using nouveau video and wireless works. I tried to upgrade to Fedora 29. After upgrade with dnf it is fairly broken. Everything came up on the surface, but it was sluggish and sudo bash was very slow to authenticate and it was popping multiple oops messages at the top of the screen. I then did a fresh install of Fedora 29. This seemed to mostly work and no immediate sluggishness once done. I then upgraded using dnf to the latest software. This is where the bad behavior came from. After dnf upgrade sluggishness on sudo again as opposed to instantaneous authentication before dnf, wifi could now not be shut off. Oops messages on top of screen and complaining about one of the cpu's in dmesg and also complaining about Noveau. Wifi became broken and gnome network manager to shut it off wouldn't do anything. The icon showed as up with signal but a browser wouldn't work. When it popped up report screen to report kernel problem it was populated with no info and all you could really do was close it. Funny thing is I did a fresh install of 29 first on my Samsung laptop which has strictly intel graphics and different wireless and everything works 100% on that laptop.
Thanks, any thoughts would be appreciated, I put Fedora 28 back on the HP and its fine with all the latest software there.
You already posted an (apparently) identical message yesterday. Saying the same thing again with no new information is not helpful. A mailing list is not a Twitter feed. If you do have something to add, please do so as a reply to your original message so things stay organised.
poc
13.12.2018, 07:55, "Mr Brian Domenick" bdomenick@gmail.com:
Hi,
I have a 15 inch HP Spectre 360 running Fedora 28, it runs fine using nouveau video and wireless works. I tried to upgrade to Fedora 29. After upgrade with dnf it is fairly broken. Everything came up on the surface, but it was sluggish and sudo bash was very slow to authenticate and it was popping multiple oops messages at the top of the screen. I then did a fresh install of Fedora 29. This seemed to mostly work and no immediate sluggishness once done. I then upgraded using dnf to the latest software. This is where the bad behavior came from. After dnf upgrade sluggishness on sudo again as opposed to instantaneous authentication before dnf, wifi could now not be shut off. Oops messages on top of screen and complaining about one of the cpu's in dmesg and also complaining about Noveau. Wifi became broken and gnome network manager to shut it off wouldn't do anything. The icon showed as up with signal but a browser wouldn't work. When it popped up report screen to report kernel problem it was populated with no info and all you could really do was close it. Funny thing is I did a fresh install of 29 first on my Samsung laptop which has strictly intel graphics and different wireless and everything works 100% on that laptop.
Thanks, any thoughts would be appreciated, I put Fedora 28 back on the HP and its fine with all the latest software there.
Brian
Hi,
Please provide more details by https://src.fedoraproject.org/rpms/hw-probe.
sudo dnf install https://kojipkgs.fedoraproject.org/packages/hw-probe/1.4/2.fc28/noarch/hw-pr...
I'll look at the probe. Also please make a probe of the failed computer state if possible (repeat the dnf upgrade to f29).
Thank you.
Hi Andrey,
Thanks for responding. I can't really keep trashing and redoing my computer, its the only one I have right now. I uploaded the hw-probe to the database.
https://linux-hardware.org/?probe=3743010fb5
If you have any thoughts please let me know.
Thanks,
Brian
On 12/13/18 4:07 AM, Andrey Ponomarenko wrote:
13.12.2018, 07:55, "Mr Brian Domenick" bdomenick@gmail.com:
Hi,
I have a 15 inch HP Spectre 360 running Fedora 28, it runs fine using nouveau video and wireless works. I tried to upgrade to Fedora 29. After upgrade with dnf it is fairly broken. Everything came up on the surface, but it was sluggish and sudo bash was very slow to authenticate and it was popping multiple oops messages at the top of the screen. I then did a fresh install of Fedora 29. This seemed to mostly work and no immediate sluggishness once done. I then upgraded using dnf to the latest software. This is where the bad behavior came from. After dnf upgrade sluggishness on sudo again as opposed to instantaneous authentication before dnf, wifi could now not be shut off. Oops messages on top of screen and complaining about one of the cpu's in dmesg and also complaining about Noveau. Wifi became broken and gnome network manager to shut it off wouldn't do anything. The icon showed as up with signal but a browser wouldn't work. When it popped up report screen to report kernel problem it was populated with no info and all you could really do was close it. Funny thing is I did a fresh install of 29 first on my Samsung laptop which has strictly intel graphics and different wireless and everything works 100% on that laptop.
Thanks, any thoughts would be appreciated, I put Fedora 28 back on the HP and its fine with all the latest software there.
Brian
Hi,
Please provide more details by https://src.fedoraproject.org/rpms/hw-probe.
sudo dnf install https://kojipkgs.fedoraproject.org/packages/hw-probe/1.4/2.fc28/noarch/hw-pr...
I'll look at the probe. Also please make a probe of the failed computer state if possible (repeat the dnf upgrade to f29).
Thank you. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Hi Brian,
1. Looks like your problem is very similar to https://forums.fedoraforum.org/showthread.php?319806-Fedora-29-hates-my-cpu
Same 8550U CPU, same Intel+NVidia GPUs and same Fedora version upgrade according to the probe.
Summary of the discussion: the issue is fixed by adding nouveau.modeset=0 to the Linux boot options. Try it by changing GRUB_CMDLINE_LINUX in /etc/default/grub and run `grub2-mkconfig -o /boot/grub2/grub.cfg` (see https://fedoraproject.org/wiki/GRUB_2 for more info).
2. Your dmesg contains a lot of nouveau crashes: https://linux-hardware.org/index.php?probe=3743010fb5&log=dmesg
Can anyone look at this?
[ 4.106684] nouveau 0000:01:00.0: timeout [ 4.106734] WARNING: CPU: 5 PID: 438 at drivers/gpu/drm/nouveau/nvkm/subdev/pmu/base.c:86 nvkm_pmu_reset+0x14c/0x160 [nouveau] ... [ 4.106814] Call Trace: [ 4.106843] nvkm_pmu_init+0x16/0x40 [nouveau] [ 4.106866] nvkm_subdev_init+0xb2/0x200 [nouveau] [ 4.106894] nvkm_device_init+0x123/0x280 [nouveau] [ 4.106922] nvkm_udevice_init+0x41/0x60 [nouveau] [ 4.106945] nvkm_object_init+0x3e/0x100 [nouveau] [ 4.106966] nvkm_ioctl_new+0x170/0x220 [nouveau] [ 4.106987] ? nvkm_client_notify+0x30/0x30 [nouveau] [ 4.107015] ? nvkm_udevice_rd08+0x20/0x20 [nouveau] [ 4.107036] nvkm_ioctl+0xd8/0x170 [nouveau] [ 4.107057] nvif_object_init+0xbf/0x110 [nouveau] [ 4.107078] nvif_device_init+0xe/0x50 [nouveau] [ 4.107107] nouveau_cli_init+0x19a/0x570 [nouveau] [ 4.107110] ? _cond_resched+0x15/0x30 [ 4.107137] nouveau_drm_load+0x66/0x7f0 [nouveau] [ 4.107148] drm_dev_register+0x109/0x140 [drm] [ 4.107155] drm_get_pci_dev+0x8f/0x170 [drm] [ 4.107183] nouveau_drm_probe+0x1c0/0x260 [nouveau] [ 4.107185] local_pci_probe+0x41/0x90 [ 4.107187] pci_device_probe+0x188/0x1a0 [ 4.107189] really_probe+0x235/0x3a0 [ 4.107191] driver_probe_device+0xb3/0xf0 [ 4.107192] __driver_attach+0xdd/0x110 [ 4.107194] ? driver_probe_device+0xf0/0xf0 [ 4.107195] bus_for_each_dev+0x76/0xc0 [ 4.107197] ? klist_add_tail+0x3b/0x60 [ 4.107198] bus_add_driver+0x152/0x230 [ 4.107199] ? 0xffffffffc068e000 [ 4.107200] driver_register+0x6b/0xb0 [ 4.107201] ? 0xffffffffc068e000 [ 4.107203] do_one_initcall+0x46/0x1c3 [ 4.107205] ? _cond_resched+0x15/0x30 [ 4.107207] ? kmem_cache_alloc_trace+0x15f/0x1e0 [ 4.107209] do_init_module+0x5a/0x210 [ 4.107210] load_module+0x205d/0x22c0 [ 4.107212] ? __get_free_pages+0xd/0x30 [ 4.107214] ? __do_sys_init_module+0x13d/0x180 [ 4.107215] __do_sys_init_module+0x13d/0x180 [ 4.107217] do_syscall_64+0x5b/0x160 [ 4.107218] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Thank you.
15.12.2018, 11:42, "Mr Brian Domenick" bdomenick@gmail.com:
Hi Andrey,
Thanks for responding. I can't really keep trashing and redoing my computer, its the only one I have right now. I uploaded the hw-probe to the database.
https://linux-hardware.org/?probe=3743010fb5
If you have any thoughts please let me know.
Thanks,
Brian
On 12/13/18 4:07 AM, Andrey Ponomarenko wrote:
13.12.2018, 07:55, "Mr Brian Domenick" bdomenick@gmail.com:
Hi,
I have a 15 inch HP Spectre 360 running Fedora 28, it runs fine using nouveau video and wireless works. I tried to upgrade to Fedora 29. After upgrade with dnf it is fairly broken. Everything came up on the surface, but it was sluggish and sudo bash was very slow to authenticate and it was popping multiple oops messages at the top of the screen. I then did a fresh install of Fedora 29. This seemed to mostly work and no immediate sluggishness once done. I then upgraded using dnf to the latest software. This is where the bad behavior came from. After dnf upgrade sluggishness on sudo again as opposed to instantaneous authentication before dnf, wifi could now not be shut off. Oops messages on top of screen and complaining about one of the cpu's in dmesg and also complaining about Noveau. Wifi became broken and gnome network manager to shut it off wouldn't do anything. The icon showed as up with signal but a browser wouldn't work. When it popped up report screen to report kernel problem it was populated with no info and all you could really do was close it. Funny thing is I did a fresh install of 29 first on my Samsung laptop which has strictly intel graphics and different wireless and everything works 100% on that laptop.
Thanks, any thoughts would be appreciated, I put Fedora 28 back on the HP and its fine with all the latest software there.
Brian
Hi,
Please provide more details by https://src.fedoraproject.org/rpms/hw-probe.
sudo dnf install https://kojipkgs.fedoraproject.org/packages/hw-probe/1.4/2.fc28/noarch/hw-pr...
I'll look at the probe. Also please make a probe of the failed computer state if possible (repeat the dnf upgrade to f29).
Thank you.
On Tue, Dec 18, 2018 at 3:27 AM Andrey Ponomarenko < andrewponomarenko@yandex.ru> wrote:
Summary of the discussion: the issue is fixed by adding nouveau.modeset=0 to the Linux boot options. Try it by changing GRUB_CMDLINE_LINUX in /etc/default/grub and run `grub2-mkconfig -o /boot/grub2/grub.cfg` (see https://fedoraproject.org/wiki/GRUB_2 for more info).
If you're doing EFI booting and not BIOS then that would be /boot/efi/EFI/fedora/grub.cfg, correct?
Thanks, Richard
-
Andrey Ponomarenko -
Mr Brian Domenick -
Patrick O'Callaghan -
Richard Shaw