Re: -stable commit 87cc4d1e (bisected) causes system freeze

From: Chris Wright
Date: Wed Jul 13 2011 - 17:43:14 EST


* Stratos Psomadakis (psomas@xxxxxxxxxx) wrote:
> On 13/07/2011 09:55 ÎÎ, Stratos Psomadakis wrote:
> > On 13/07/2011 05:28 ÎÎ, Marcus Becker wrote:
> >> Hi,
> >>
> >> With the upgrade to 2.6.39.2, I cannot copy more than ~1GB of data
> >> over the network before my input devices lock up.
> >> Example:
> >> use scp on tty1 to copy a folder or file larger than 3GB over my
> >> gigabit network and after ~1min the keyboard stops responding.
> >> use cp on tty1 with an nfs-3 share mounted over the same network and
> >> try to copy the same file, same happens
> >>
> >> I can hit ctrl+c for about 20-30 sec and eventually get an interrupt
> >> that stops the copying, then the input devices slowly gain control
> >> again. If I do the same on X, there is no chance to get in between and
> >> I have to use SysRq to reboot.
> >>
> >> In our bug report at https://bugs.gentoo.org/show_bug.cgi?id=373109
> >> We did a bisect between 2.6.39.1 and 2.6.39.2 and found the following
> >> patch is causing this problem:
> >>
> >> commit 87cc4d1e3e05af38c7c51323a3d86fe2572ab033
> >> Author: Chris Wright <chrisw@xxxxxxxxxxxx>
> >> Date: Sat May 28 13:15:04 2011 -0500
> >>
> >> intel-iommu: Dont cache iova above 32bit
> >>
> >> I will also attach dmesg, current kernel config, and my bisect log (I
> >> put a uname -a into the log after each bisect) plus git bisect log
> >>
> >> Please let me know if you need more information.
> >>
> >> Thanks,
> >>
> >> Marcus
> > CC'ed the people who signed-off the patch.
> >
> Bug #39312 [1] at b.k.o
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=39312

Thanks for the cc, looking into it. Would be useful to get details of
the boxes that are showing the issue (full dmesg from boot and lspci).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/