Your message dated Tue, 18 Jun 2013 21:25:24 +0200 with message-id <20130618192524.GA4794@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #607280, regarding linux-2.6: IOMMU read errors on nouveau (nv50) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 607280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607280 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: linux-2.6: IOMMU read errors on nouveau (nv50)
- From: Yves-Alexis Perez <corsac@debian.org>
- Date: Thu, 16 Dec 2010 16:43:56 +0100
- Message-id: <20101216154356.7017.52999.reportbug@hidalgo>
Package: linux-2.6 Version: 2.6.32-29 Severity: normal Hey, following my tries on intel_iommu, I found some errors on nvidia hardware, using nouveau driver. Basically, logs fill up with: [ 8120.811323] DRHD: handling fault status reg 2 [ 8120.811328] DMAR:[DMA Read] Request device [02:00.0] fault addr 0 [ 8120.811330] DMAR:[fault reason 06] PTE Read access is not set PCI device is the nvidia card: 02:00.0 VGA compatible controller: nVidia Corporation G86 [Quadro NVS 290] (rev a1) which is trying to read address 0. It doesn't seem to cause too much trouble, but it does fill up the log and it doesn't look really good. It'd be nice to have a fix for this, but sadly it's not as easy as #607095. Again, there's a fedora bug (https://bugzilla.redhat.com/show_bug.cgi?id=561267) which leads to the commit 4eb3033c but it doesn't really apply fine against 2.6.32, even with the whole nouveau backport in Debian kernels. Backporting the whole nv50_fb.c might be a little overkill (especially for Squeeze) though. Regards, -- Yves-Alexis -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-grsec-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: 604177-done@bugs.debian.org, 604438-done@bugs.debian.org, 605200-done@bugs.debian.org, 605204-done@bugs.debian.org, 607280-done@bugs.debian.org, 607439-done@bugs.debian.org
- Subject: Closing
- From: Moritz Mühlenhoff <jmm@inutil.org>
- Date: Tue, 18 Jun 2013 21:25:24 +0200
- Message-id: <20130618192524.GA4794@pisco.westfalen.local>
Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.0 / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to control@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz
--- End Message ---