All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Stratos Psomadakis <psomas@gentoo.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Chris Wright <chrisw@sous-sol.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	David Woodhouse <David.Woodhouse@intel.com>,
	kernel@gentoo.org
Subject: Re: -stable commit 87cc4d1e (bisected) causes system freeze
Date: Wed, 13 Jul 2011 14:42:50 -0700	[thread overview]
Message-ID: <20110713214250.GW15844@sequoia.sous-sol.org> (raw)
In-Reply-To: <4E1DF736.9020908@gentoo.org>

* Stratos Psomadakis (psomas@gentoo.org) 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@sous-sol.org>
> >> 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).

      reply	other threads:[~2011-07-13 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 14:28 intel-iommu: Dont cache iova above 32bit - network copy freezes system Marcus Becker
2011-07-13 18:55 ` -stable commit 87cc4d1e (bisected) causes system freeze Stratos Psomadakis
2011-07-13 19:51   ` Stratos Psomadakis
2011-07-13 21:42     ` Chris Wright [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110713214250.GW15844@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=David.Woodhouse@intel.com \
    --cc=gregkh@suse.de \
    --cc=kernel@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psomas@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.