[Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2017-05-15 Thread Kai-Heng Feng
If this still happens on latest mainline kernel, you need to raise the issue to linux-usb mailing list. ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2017-05-07 Thread Christopher M. Penalver
** Tags added: kernel-bug-exists-upstream-4.10.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610979 Title: Call Trace disabling IRQ 17, affects USB mouse To manage notifications about this bug

Re: [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2017-04-13 Thread js1
I have done irqpoll in the past, and it didn't help. I will try again with 4.10.10. On Thu, Apr 13, 2017 at 11:58 AM, Kai-Heng Feng wrote: > Did you see the message "[ 795.982336] irq 17: nobody cared (try booting with > the "irqpoll" option) > "? > > Can you try

[Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2017-04-13 Thread Kai-Heng Feng
Did you see the message "[ 795.982336] irq 17: nobody cared (try booting with the "irqpoll" option) "? Can you try to boot with kernel parameter "irqpoll"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2017-03-30 Thread js1
Just happened on 4.10.5-041005-generic #201703220931. Did not experience with 4.10.1. [ 685.335137] irq 17: nobody cared (try booting with the "irqpoll" option) [ 685.335145] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.10.5-041005-generic #201703220931 [ 685.335146] Hardware name:

Re: [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2017-02-13 Thread js1
Just happened with a 4.8 kernel: [ 1317.106797] irq 17: nobody cared (try booting with the "irqpoll" option) [ 1317.106804] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.8.17-040817-generic #201701090438 [ 1317.106805] Hardware name: /DP35DP, BIOS DPP3510J.86A.0572.2009.0715.2346

Re: [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2017-02-05 Thread js1
Seems to be happening more frequently on 4.4 kernels. Just happened again on 4.4.0-57. I'm also running without the nvidia proprietary drivers, just nouveau. [ 476.598833] irq 17: nobody cared (try booting with the "irqpoll" option) [ 476.598843] CPU: 1 PID: 0 Comm: swapper/1 Not tainted

Re: [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2016-11-09 Thread js1
Is there a way to build the kernel package such that it supports the nvidia drivers? On Wed, Nov 9, 2016 at 3:18 AM, Christopher M. Penalver wrote: > ** Tags added: needs-upstream-testing > > -- > You received this bug notification because you are subscribed to

[Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2016-11-09 Thread Christopher M. Penalver
** Tags added: needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610979 Title: Call Trace disabling IRQ 17, affects USB mouse To manage notifications about this bug go to:

Re: [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2016-11-05 Thread js1
Just happened on 4.4.0-45-generic. [ 795.982336] irq 17: nobody cared (try booting with the "irqpoll" option) [ 795.982345] CPU: 2 PID: 0 Comm: swapper/2 Tainted: P OE 4.4.0-45-generic #66-Ubuntu [ 795.982348] Hardware name: /DP35DP, BIOS

Re: [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2016-11-02 Thread js1
I'll take another look at the mainline kernels. I will say one of the recent kernel apt-get updates (4.4.0-4[35]) seems not to have this problem as frequently. On Wed, Nov 2, 2016 at 9:00 AM, Christopher M. Penalver wrote: > js1, to keep this relevant to

[Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2016-11-02 Thread Christopher M. Penalver
js1, to keep this relevant to upstream, one would want check for, and test the latest mainline kernel (now 4.9-rc3) as it is released. Could you please advise? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2016-10-31 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610979

[Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2016-09-01 Thread js1
Building the 4.8 kernel from Mainline. My monitor setup really requires the nvidia drivers. The nouveau from the 4.8 build is not very useful, and the prepackage build used a different gcc and is not compatible with the dkms. -- You received this bug notification because you are a member of

[Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2016-09-01 Thread Christopher M. Penalver
** Tags added: latest-bios-0572 regression-potential -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610979 Title: Call Trace disabling IRQ 17, affects USB mouse To manage notifications about this

Re: [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2016-08-09 Thread js1
Noticed this happening since upgrading to 16.04. But, I also started using a usb mouse on this particular computer around the same time. I'll give the upstream kernels a try and report back. On Tue, Aug 9, 2016, 12:45 Joseph Salisbury wrote: > Did this issue

[Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

2016-08-09 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8