Re: [qubes-users] [qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-07-06 Thread 0spinboson
fyi: Ryzen pinctrl/gpio issue should be fixed in 4.11.9; not yet backported to 
4.9: 

commit 0ec03ce7d79dc9a5c47d26bab38c78075d42de9c
Author: Thomas Gleixner
Date:   Tue May 23 23:23:32 2017 +0200

pinctrl/amd: Use regular interrupt instead of chained

commit ba714a9c1dea85e0bf2899d02dfeb9c70040427c upstream.

The AMD pinctrl driver uses a chained interrupt to demultiplex the GPIO
interrupts. Kevin Vandeventer reported, that his new AMD Ryzen locks up
hard on boot when the AMD pinctrl driver is initialized. The reason is an
interrupt storm. It's not clear whether that's caused by hardware or
firmware or both.

Using chained interrupts on X86 is a dangerous endavour. If a system is
misconfigured or the hardware buggy there is no safety net to catch an
interrupt storm.

Convert the driver to use a regular interrupt for the demultiplex
handler. This allows the interrupt storm detector to catch the malfunction
and lets the system boot up.

This should be backported to stable because it's likely that more users run
into this problem as the AMD Ryzen machines are spreading.

Reported-by: Kevin Vandeventer
Link: https://bugzilla.suse.com/show_bug.cgi?id=1034261

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ef96e304-398d-4082-bcc3-85b1efe67de9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [qubes-devel] Re: Request for feedback: 4.9 Kernel

2017-07-05 Thread Ryan Tate

> On Jun 21, 2017, at 3:01 PM, Ryan Tate  wrote:
> 
> On Thursday, June 1, 2017 at 10:00:09 AM UTC-4, Pablo Di Noto wrote:
> 4) General feedback on the 4.9 kernel.
 
 Oh, yeah... I have started experiencing quite annoying internet 
 connectivity issues, very, very difficulty to troubleshot. Symptoms are:
 
 - Web browsing fails with ERR_EMPTY_RESPONSE, pages load partially never 
 reaching some of the content.
 ...((removed for brevity))
 It seems pretty repeatable, and would love to provide debugging info, 
 although I do not know where to look for.
>>> 
>>> I, too, encountered this issue and was unable to find
>>> the cause. Had to revert to 4.4.67-12 kernel. :(
>> 
>> Oh, well. I am not crazy then. :)
>> Maybe being a generic bug will make it worth debugging.
> 
> I had these issues as well. Oddly, some domains would load perfectly in an 
> AppVM, but then others that should be available (e.g. Google.com) would 
> suddenly break, then come back 5 minutes later. Those same domains would load 
> fine in curl on the netvm. This also hit non HTTP apps like email, messaging.
> 
> I was not able to revert my kernel as my wireless adapter fails under the old 
> kernel. However, I was able to fix by installing the fedora 25 template and 
> upgrading the stack of VMs involved (sys-net > sys-firewall > appvm) all to 
> the fedora-25 template. This seems to have eliminated the constant network 
> stalls.

Actually, this did not work. The issue has returned, is maddening, and makes 
Qubes close to unusable. I am trying to debug it, but really have no idea where 
to start. Anyway, no one should have false hope that F25 fixes any of this 
network stalling stuff, is the only reason I’m posting.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/580940E8-8B0F-478D-AAA8-04432819F1B4%40ryantate.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail