From: Andreas Schwab <schwab@linux-m68k•org>
To: Herbert Xu <herbert@gondor•apana.org.au>
Cc: Christian Borntraeger <borntraeger@de•ibm.com>,
"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: Wed, 22 Apr 2009 22:34:32 +0200 [thread overview]
Message-ID: <m2ws9c2zs7.fsf@igel.home> (raw)
In-Reply-To: <20090409093817.GA5760@gondor.apana.org.au> (Herbert Xu's message of "Thu, 9 Apr 2009 17:38:17 +0800")
Herbert Xu <herbert@gondor•apana.org.au> writes:
> 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.
Any news on this? It is still badly broken in 2.6.30-rc3.
Andreas.
--
Andreas Schwab, schwab@linux-m68k•org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-04-22 20:34 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
2009-04-15 14:30 ` Andreas Schwab
2009-04-22 20:34 ` Andreas Schwab [this message]
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=m2ws9c2zs7.fsf@igel.home \
--to=schwab@linux-m68k$(echo .)org \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=davem@davemloft$(echo .)net \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox