All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: Oops in tun: bisected to  Limit amount of queued packets per device
Date: Thu, 9 Apr 2009 12:39:14 +0200	[thread overview]
Message-ID: <200904091239.14630.borntraeger@de.ibm.com> (raw)
In-Reply-To: <20090409093817.GA5760@gondor.apana.org.au>

Am Thursday 09 April 2009 11:38:17 schrieb Herbert Xu:
> On Thu, Apr 09, 2009 at 09:52:01AM +0200, Christian Borntraeger wrote:
> > with my kvm test scenario on s390 I get the following oops:
> > Unable to handle kernel pointer dereference at virtual kernel address
> > 0000000400000000 Oops: 003b [#1] SMP
> > Modules linked in: kvm dm_multipath sunrpc qeth_l2 dm_mod qeth ccwgroup
> > CPU: 0 Not tainted 2.6.29-kvm-06607-ga317a1e-dirty #8
> > Process kuli (pid: 14827, task: 00000000b3df8138, ksp: 00000000b4703a98)
> > Krnl PSW : 0404e00180000000 0000000000171278
> > (__lock_acquire+0x3d4/0x191c)
>
> This is weird.  It looks like it's dying on the wake_up_interruptible_sync
> in tun_sock_write_space.  However, I can't see how that can cause this.
>
> Were you in the middle of removing the tun module?
>
> Cheers,

No, I was booting up a guest and the guest sent its first packet (arp). I 
forgot to mention, that the tap device is persistent and attached to a 
bridge. Does that give a clue?

Christian

  reply	other threads:[~2009-04-09 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09  7:52 Oops in tun: bisected to Limit amount of queued packets per device Christian Borntraeger
2009-04-09  9:38 ` Herbert Xu
2009-04-09 10:39   ` Christian Borntraeger [this message]
2009-04-15 14:30     ` Andreas Schwab
2009-04-22 20:34   ` Andreas Schwab
2009-04-23  0:17     ` Herbert Xu
2009-04-23 10:08       ` Andreas Schwab

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=200904091239.14630.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.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.