On 05/03/2012 11:15 PM, Daniel Vetter wrote:
>>> Shot in the dark, let's disable msi a bit. Can you try the below patch?
>>
>> Yeah, no IRQ_NONE at the end of i915_driver_irq_handler now. So MSI is
>> busted, either in the card, the chipset or the kernel. Any idea how to
>> find out?
>
> Ok, so
On Thu, May 03, 2012 at 09:56:08PM +0200, Jiri Slaby wrote:
> On 04/11/2012 12:40 PM, Daniel Vetter wrote:
> > On Tue, Apr 10, 2012 at 01:34:11PM -0700, Jesse Barnes wrote:
> >> On Tue, 10 Apr 2012 22:32:12 +0200
> >> Daniel Vetter wrote:
> >>
> >>> On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri
On 04/11/2012 12:40 PM, Daniel Vetter wrote:
> On Tue, Apr 10, 2012 at 01:34:11PM -0700, Jesse Barnes wrote:
>> On Tue, 10 Apr 2012 22:32:12 +0200
>> Daniel Vetter wrote:
>>
>>> On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri Slaby wrote:
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
On Thu, 3 May 2012 14:54:22 -0700
Jesse Barnes wrote:
> On Thu, 03 May 2012 23:16:02 +0200
> Jiri Slaby wrote:
>
> > On 05/03/2012 11:15 PM, Daniel Vetter wrote:
> > >>> Shot in the dark, let's disable msi a bit. Can you try the below patch?
> > >>
> > >> Yeah, no IRQ_NONE at the end of
On Thu, 03 May 2012 23:16:02 +0200
Jiri Slaby wrote:
> On 05/03/2012 11:15 PM, Daniel Vetter wrote:
> >>> Shot in the dark, let's disable msi a bit. Can you try the below patch?
> >>
> >> Yeah, no IRQ_NONE at the end of i915_driver_irq_handler now. So MSI is
> >> busted, either in the card, the
On 04/11/2012 12:40 PM, Daniel Vetter wrote:
On Tue, Apr 10, 2012 at 01:34:11PM -0700, Jesse Barnes wrote:
On Tue, 10 Apr 2012 22:32:12 +0200
Daniel Vetter dan...@ffwll.ch wrote:
On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri Slaby wrote:
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
On Thu, May 03, 2012 at 09:56:08PM +0200, Jiri Slaby wrote:
On 04/11/2012 12:40 PM, Daniel Vetter wrote:
On Tue, Apr 10, 2012 at 01:34:11PM -0700, Jesse Barnes wrote:
On Tue, 10 Apr 2012 22:32:12 +0200
Daniel Vetter dan...@ffwll.ch wrote:
On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri
On 05/03/2012 11:15 PM, Daniel Vetter wrote:
Shot in the dark, let's disable msi a bit. Can you try the below patch?
Yeah, no IRQ_NONE at the end of i915_driver_irq_handler now. So MSI is
busted, either in the card, the chipset or the kernel. Any idea how to
find out?
Ok, so MSI is busted.
On Thu, 03 May 2012 23:16:02 +0200
Jiri Slaby jsl...@suse.cz wrote:
On 05/03/2012 11:15 PM, Daniel Vetter wrote:
Shot in the dark, let's disable msi a bit. Can you try the below patch?
Yeah, no IRQ_NONE at the end of i915_driver_irq_handler now. So MSI is
busted, either in the card, the
On Thu, 3 May 2012 14:54:22 -0700
Jesse Barnes jbar...@virtuousgeek.org wrote:
On Thu, 03 May 2012 23:16:02 +0200
Jiri Slaby jsl...@suse.cz wrote:
On 05/03/2012 11:15 PM, Daniel Vetter wrote:
Shot in the dark, let's disable msi a bit. Can you try the below patch?
Yeah, no IRQ_NONE
On Tue, Apr 10, 2012 at 01:34:11PM -0700, Jesse Barnes wrote:
> On Tue, 10 Apr 2012 22:32:12 +0200
> Daniel Vetter wrote:
>
> > On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri Slaby wrote:
> > > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> > > SERR- > >
> > > I tried 3.2 and
On Wed, 11 Apr 2012 08:29:22 +0200
Michel D?nzer wrote:
> On Die, 2012-04-10 at 11:34 -0700, Jesse Barnes wrote:
> > On Tue, 10 Apr 2012 20:11:29 +0200
> > Jiri Slaby wrote:
> >
> > > On 04/10/2012 06:26 PM, Jesse Barnes wrote:
> > > > So port hotplug is always reporting that port C has a
On Die, 2012-04-10 at 11:34 -0700, Jesse Barnes wrote:
> On Tue, 10 Apr 2012 20:11:29 +0200
> Jiri Slaby wrote:
>
> > On 04/10/2012 06:26 PM, Jesse Barnes wrote:
> > > So port hotplug is always reporting that port C has a hotplug
> > > interrupt though... If you write 0x3 back to it does the
On Die, 2012-04-10 at 11:34 -0700, Jesse Barnes wrote:
On Tue, 10 Apr 2012 20:11:29 +0200
Jiri Slaby jsl...@suse.cz wrote:
On 04/10/2012 06:26 PM, Jesse Barnes wrote:
So port hotplug is always reporting that port C has a hotplug
interrupt though... If you write 0x3 back to it does
On Tue, Apr 10, 2012 at 01:34:11PM -0700, Jesse Barnes wrote:
On Tue, 10 Apr 2012 22:32:12 +0200
Daniel Vetter dan...@ffwll.ch wrote:
On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri Slaby wrote:
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort-
TAbort- MAbort- SERR- PERR-
On Wed, 11 Apr 2012 08:29:22 +0200
Michel Dänzer mic...@daenzer.net wrote:
On Die, 2012-04-10 at 11:34 -0700, Jesse Barnes wrote:
On Tue, 10 Apr 2012 20:11:29 +0200
Jiri Slaby jsl...@suse.cz wrote:
On 04/10/2012 06:26 PM, Jesse Barnes wrote:
So port hotplug is always reporting
On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri Slaby wrote:
> On 04/10/2012 08:34 PM, Jesse Barnes wrote:
> > On Tue, 10 Apr 2012 20:11:29 +0200 Jiri Slaby
> > wrote:
> >
> >> On 04/10/2012 06:26 PM, Jesse Barnes wrote:
> >>> So port hotplug is always reporting that port C has a hotplug
> >>>
On 04/10/2012 08:34 PM, Jesse Barnes wrote:
> On Tue, 10 Apr 2012 20:11:29 +0200 Jiri Slaby
> wrote:
>
>> On 04/10/2012 06:26 PM, Jesse Barnes wrote:
>>> So port hotplug is always reporting that port C has a hotplug
>>> interrupt though... If you write 0x3 back to it does the
>>> interrupt
On 04/10/2012 06:26 PM, Jesse Barnes wrote:
> So port hotplug is always reporting that port C has a hotplug
> interrupt though... If you write 0x3 back to it does the interrupt
> stop?
I'm not sure I got it right. This doesn't help:
--- a/drivers/gpu/drm/i915/i915_irq.c
+++
On Tue, Apr 10, 2012 at 10:52:06AM +0200, Jiri Slaby wrote:
> On 04/06/2012 11:31 PM, Jiri Slaby wrote:
> > On 03/30/2012 02:24 PM, Chris Wilson wrote:
> >> On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby wrote:
> >>> On 03/30/2012 12:45 PM, Chris Wilson wrote:
> On Fri, 30 Mar 2012 11:59:28
On Tue, 10 Apr 2012 22:32:12 +0200
Daniel Vetter wrote:
> On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri Slaby wrote:
> > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> > SERR- >
> > I tried 3.2 and 3.3. Although the spurious interrupts were always
> > there, they occurred
On 04/10/2012 10:58 AM, Daniel Vetter wrote:
> On Tue, Apr 10, 2012 at 10:47:49AM +0200, Jiri Slaby wrote:
>> On 04/09/2012 07:11 PM, Jesse Barnes wrote:
>>> On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson
>>> wrote:
>>>
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby
wrote:
> I
On Tue, 10 Apr 2012 20:11:29 +0200
Jiri Slaby wrote:
> On 04/10/2012 06:26 PM, Jesse Barnes wrote:
> > So port hotplug is always reporting that port C has a hotplug
> > interrupt though... If you write 0x3 back to it does the interrupt
> > stop?
>
> I'm not sure I got it right. This doesn't
On Tue, Apr 10, 2012 at 10:47:49AM +0200, Jiri Slaby wrote:
> On 04/09/2012 07:11 PM, Jesse Barnes wrote:
> > On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson
> > wrote:
> >
> >> On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby
> >> wrote:
> >>> I don't know what to dump more, because iir is
On 04/06/2012 11:31 PM, Jiri Slaby wrote:
> On 03/30/2012 02:24 PM, Chris Wilson wrote:
>> On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby wrote:
>>> On 03/30/2012 12:45 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby wrote:
> I don't know what to dump more,
On Fri, Apr 6, 2012 at 23:31, Jiri Slaby wrote:
>> That was introduced in 05eff845a28499762075d3a72e238a31f4d2407c to close
>> a race where the pipestat triggered an interrupt after we processed the
>> secondary registers and before reseting the primary.
>>
>> But the basic premise that we should
On 04/09/2012 07:11 PM, Jesse Barnes wrote:
> On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson
> wrote:
>
>> On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby
>> wrote:
>>> I don't know what to dump more, because iir is obviously zero
>>> too. What other sources of interrupts are on the (G33) chip?
On 04/07/2012 12:40 AM, Thomas Gleixner wrote:
> On Fri, 6 Apr 2012, Jiri Slaby wrote:
>> It very looks like the generic IRQ handling code is broken. Like it
>> frees/corrupts irq_desc and ...
>
> OMG, your problem analyzing skills are amazing.
Hehe, no I did *no* analysis. I stand here as a bug
On Tue, 10 Apr 2012 10:47:49 +0200
Jiri Slaby wrote:
> On 04/09/2012 07:11 PM, Jesse Barnes wrote:
> > On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson
> > wrote:
> >
> >> On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby
> >> wrote:
> >>> I don't know what to dump more, because iir is obviously
On 04/07/2012 12:40 AM, Thomas Gleixner wrote:
On Fri, 6 Apr 2012, Jiri Slaby wrote:
It very looks like the generic IRQ handling code is broken. Like it
frees/corrupts irq_desc and ...
OMG, your problem analyzing skills are amazing.
Hehe, no I did *no* analysis. I stand here as a bug
On 04/09/2012 07:11 PM, Jesse Barnes wrote:
On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson
ch...@chris-wilson.co.uk wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz
wrote:
I don't know what to dump more, because iir is obviously zero
too. What other sources of
On Fri, Apr 6, 2012 at 23:31, Jiri Slaby jsl...@suse.cz wrote:
That was introduced in 05eff845a28499762075d3a72e238a31f4d2407c to close
a race where the pipestat triggered an interrupt after we processed the
secondary registers and before reseting the primary.
But the basic premise that we
On 04/06/2012 11:31 PM, Jiri Slaby wrote:
On 03/30/2012 02:24 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby jsl...@suse.cz wrote:
On 03/30/2012 12:45 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz wrote:
I don't know what to dump
On Tue, Apr 10, 2012 at 10:47:49AM +0200, Jiri Slaby wrote:
On 04/09/2012 07:11 PM, Jesse Barnes wrote:
On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson
ch...@chris-wilson.co.uk wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz
wrote:
I don't know what to dump more,
On 04/10/2012 10:58 AM, Daniel Vetter wrote:
On Tue, Apr 10, 2012 at 10:47:49AM +0200, Jiri Slaby wrote:
On 04/09/2012 07:11 PM, Jesse Barnes wrote:
On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson
ch...@chris-wilson.co.uk wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz
On Tue, 10 Apr 2012 10:47:49 +0200
Jiri Slaby jsl...@suse.cz wrote:
On 04/09/2012 07:11 PM, Jesse Barnes wrote:
On Fri, 30 Mar 2012 11:45:43 +0100 Chris Wilson
ch...@chris-wilson.co.uk wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz
wrote:
I don't know what to
On 04/10/2012 06:26 PM, Jesse Barnes wrote:
So port hotplug is always reporting that port C has a hotplug
interrupt though... If you write 0x3 back to it does the interrupt
stop?
I'm not sure I got it right. This doesn't help:
--- a/drivers/gpu/drm/i915/i915_irq.c
+++
On Tue, 10 Apr 2012 20:11:29 +0200
Jiri Slaby jsl...@suse.cz wrote:
On 04/10/2012 06:26 PM, Jesse Barnes wrote:
So port hotplug is always reporting that port C has a hotplug
interrupt though... If you write 0x3 back to it does the interrupt
stop?
I'm not sure I got it right. This
On 04/10/2012 08:34 PM, Jesse Barnes wrote:
On Tue, 10 Apr 2012 20:11:29 +0200 Jiri Slaby jsl...@suse.cz
wrote:
On 04/10/2012 06:26 PM, Jesse Barnes wrote:
So port hotplug is always reporting that port C has a hotplug
interrupt though... If you write 0x3 back to it does the
interrupt
On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri Slaby wrote:
On 04/10/2012 08:34 PM, Jesse Barnes wrote:
On Tue, 10 Apr 2012 20:11:29 +0200 Jiri Slaby jsl...@suse.cz
wrote:
On 04/10/2012 06:26 PM, Jesse Barnes wrote:
So port hotplug is always reporting that port C has a hotplug
On Tue, 10 Apr 2012 22:32:12 +0200
Daniel Vetter dan...@ffwll.ch wrote:
On Tue, Apr 10, 2012 at 09:52:40PM +0200, Jiri Slaby wrote:
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort-
TAbort- MAbort- SERR- PERR- INTx-
I tried 3.2 and 3.3. Although the spurious interrupts were
On Tue, Apr 10, 2012 at 10:52:06AM +0200, Jiri Slaby wrote:
On 04/06/2012 11:31 PM, Jiri Slaby wrote:
On 03/30/2012 02:24 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby jsl...@suse.cz wrote:
On 03/30/2012 12:45 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 11:59:28
>> You know what? suspend calls free_irq() via i915_drm_freeze() ->
>> drm_irq_uninstall() and the resume code calls request_irq() again.
>> free_irq() removes the action and request_irq installs it fresh.
>
> Yeah this is a known issue with the DRM code, I thought Dave had a
> fix queued a long
On Sat, 7 Apr 2012 00:40:28 +0200 (CEST)
Thomas Gleixner wrote:
> You know what? suspend calls free_irq() via i915_drm_freeze() ->
> drm_irq_uninstall() and the resume code calls request_irq() again.
> free_irq() removes the action and request_irq installs it fresh.
Yeah this is a known issue
On Fri, 30 Mar 2012 11:45:43 +0100
Chris Wilson wrote:
> On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby wrote:
> > I don't know what to dump more, because iir is obviously zero too. What
> > other sources of interrupts are on the (G33) chip?
>
> IIR is the master interrupt, with chained
On Fri, 30 Mar 2012 11:45:43 +0100
Chris Wilson ch...@chris-wilson.co.uk wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz wrote:
I don't know what to dump more, because iir is obviously zero too. What
other sources of interrupts are on the (G33) chip?
IIR is the master
On Sat, 7 Apr 2012 00:40:28 +0200 (CEST)
Thomas Gleixner t...@linutronix.de wrote:
You know what? suspend calls free_irq() via i915_drm_freeze() -
drm_irq_uninstall() and the resume code calls request_irq() again.
free_irq() removes the action and request_irq installs it fresh.
Yeah this is a
You know what? suspend calls free_irq() via i915_drm_freeze() -
drm_irq_uninstall() and the resume code calls request_irq() again.
free_irq() removes the action and request_irq installs it fresh.
Yeah this is a known issue with the DRM code, I thought Dave had a
fix queued a long time ago
On Fri, 6 Apr 2012, Jiri Slaby wrote:
> On 03/30/2012 02:24 PM, Chris Wilson wrote:
> > On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby wrote:
> >> On 03/30/2012 12:45 PM, Chris Wilson wrote:
> >>> On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby wrote:
> I don't know what to dump more,
On 03/30/2012 02:24 PM, Chris Wilson wrote:
> On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby wrote:
>> On 03/30/2012 12:45 PM, Chris Wilson wrote:
>>> On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby wrote:
I don't know what to dump more, because iir is obviously zero too. What
other
On Fri, 6 Apr 2012, Jiri Slaby wrote:
On 03/30/2012 02:24 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby jsl...@suse.cz wrote:
On 03/30/2012 12:45 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz wrote:
I don't know what to
On 03/30/2012 02:24 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby jsl...@suse.cz wrote:
On 03/30/2012 12:45 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz wrote:
I don't know what to dump more, because iir is obviously zero too.
On 03/30/2012 12:45 PM, Chris Wilson wrote:
> On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby wrote:
>> I don't know what to dump more, because iir is obviously zero too. What
>> other sources of interrupts are on the (G33) chip?
>
> IIR is the master interrupt, with chained secondary interrupt
On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby wrote:
> On 03/30/2012 12:45 PM, Chris Wilson wrote:
> > On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby wrote:
> >> I don't know what to dump more, because iir is obviously zero too. What
> >> other sources of interrupts are on the (G33) chip?
> >
On 03/27/2012 10:42 AM, Jiri Slaby wrote:
> On 03/27/2012 10:40 AM, Jiri Slaby wrote:
>> Hi,
>>
>> I'm getting spurious interrupts leading to disabling the interrupt:
>> 42:19168532471662 PCI-MSI-edge i915 at pci::00:02.0
>>
>> The message:
>> irq 42: nobody cared (try booting
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby wrote:
> I don't know what to dump more, because iir is obviously zero too. What
> other sources of interrupts are on the (G33) chip?
IIR is the master interrupt, with chained secondary interrupt statuses.
If IIR is 0, the interrupt wasn't raised by
On 03/27/2012 10:42 AM, Jiri Slaby wrote:
On 03/27/2012 10:40 AM, Jiri Slaby wrote:
Hi,
I'm getting spurious interrupts leading to disabling the interrupt:
42:19168532471662 PCI-MSI-edge i915@pci::00:02.0
The message:
irq 42: nobody cared (try booting with the irqpoll
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz wrote:
I don't know what to dump more, because iir is obviously zero too. What
other sources of interrupts are on the (G33) chip?
IIR is the master interrupt, with chained secondary interrupt statuses.
If IIR is 0, the interrupt
On 03/30/2012 12:45 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz wrote:
I don't know what to dump more, because iir is obviously zero too. What
other sources of interrupts are on the (G33) chip?
IIR is the master interrupt, with chained secondary
On Fri, 30 Mar 2012 14:11:47 +0200, Jiri Slaby jsl...@suse.cz wrote:
On 03/30/2012 12:45 PM, Chris Wilson wrote:
On Fri, 30 Mar 2012 11:59:28 +0200, Jiri Slaby jsl...@suse.cz wrote:
I don't know what to dump more, because iir is obviously zero too. What
other sources of interrupts are on
On 03/27/2012 10:57 AM, Daniel Vetter wrote:
> And please mind the guy with bad memory and tell us which chip you have
> again?
Where's that? In xorg.log:
https://bugs.freedesktop.org/attachment.cgi?id=58771
?
(II) intel(0): Integrated Graphics Chipset: Intel(R) G33
(--) intel(0): Chipset: "G33"
On Tue, Mar 27, 2012 at 10:40:03AM +0200, Jiri Slaby wrote:
> Hi,
>
> I'm getting spurious interrupts leading to disabling the interrupt:
> 42:19168532471662 PCI-MSI-edge i915 at pci::00:02.0
>
> The message:
> irq 42: nobody cared (try booting with the "irqpoll" option)
>
On 03/27/2012 10:40 AM, Jiri Slaby wrote:
> Hi,
>
> I'm getting spurious interrupts leading to disabling the interrupt:
> 42:19168532471662 PCI-MSI-edge i915 at pci::00:02.0
>
> The message:
> irq 42: nobody cared (try booting with the "irqpoll" option)
> Pid: 20716, comm:
Hi,
I'm getting spurious interrupts leading to disabling the interrupt:
42:19168532471662 PCI-MSI-edge i915 at pci::00:02.0
The message:
irq 42: nobody cared (try booting with the "irqpoll" option)
Pid: 20716, comm: virtuoso-t Not tainted 3.3.0-next-20120326_64+ #1673
It is
Hi,
I'm getting spurious interrupts leading to disabling the interrupt:
42:19168532471662 PCI-MSI-edge i915@pci::00:02.0
The message:
irq 42: nobody cared (try booting with the irqpoll option)
Pid: 20716, comm: virtuoso-t Not tainted 3.3.0-next-20120326_64+ #1673
It is not
On 03/27/2012 10:40 AM, Jiri Slaby wrote:
Hi,
I'm getting spurious interrupts leading to disabling the interrupt:
42:19168532471662 PCI-MSI-edge i915@pci::00:02.0
The message:
irq 42: nobody cared (try booting with the irqpoll option)
Pid: 20716, comm: virtuoso-t Not
On Tue, Mar 27, 2012 at 10:40:03AM +0200, Jiri Slaby wrote:
Hi,
I'm getting spurious interrupts leading to disabling the interrupt:
42:19168532471662 PCI-MSI-edge i915@pci::00:02.0
The message:
irq 42: nobody cared (try booting with the irqpoll option)
Pid: 20716,
On 03/27/2012 10:57 AM, Daniel Vetter wrote:
And please mind the guy with bad memory and tell us which chip you have
again?
Where's that? In xorg.log:
https://bugs.freedesktop.org/attachment.cgi?id=58771
?
(II) intel(0): Integrated Graphics Chipset: Intel(R) G33
(--) intel(0): Chipset: G33
68 matches
Mail list logo
