It’s easy to bypass it with intel_iommu=off, that’s not an issue (though I lose virtualization and that is an issue, fortunately not a big one). What I’m interested in is where does one report bugs like this? I don’t exactly feel like writing to the LKML . Shall I fill a bug here in OpenSuse, or shall I let it drop as they probably know that already given that there was the Phoronix article?
I haven’t found a LKML post nor OpenSuse bug for this issue.
On 01/07/2012 12:36 PM, tmoravec wrote:
>
> What I’m interested in is where does one report bugs like
> this? I don’t exactly feel like writing to the LKML :).
As you point to an article that describes the bug, I would think that it is known upstream. What is the use of filing a bug after it is recognised as a bug?
But you could of course try to find out if there is a bugfile and what the status is at https://bugzilla.kernel.org/
Oh, I didn’t know about bugzilla.kernel.org. However it doesn’t work, it fails with a database error. Who knows for how long it doesn’t work, it has probably been some time, because Google fails to find any bugreport related to this problem too.
On 01/07/2012 08:16 AM, hcvv wrote:
>
> tmoravec;2427524 Wrote:
>> Oh, I didn’t know about bugzilla.kernel.org. However it doesn’t work, it
>> fails with a database error. Who knows for how long it doesn’t work, it
>> has probably been some time, because Google fails to find any bugreport
>> related to this problem too.
> Yes, it seems tthat the database is not running. But I doubt that
> structural. The website is too important for that.
>
> I do not know if Google searches there, after all you need to
> subscribe.