Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1292012

RE: ARM64/KVM: Bad page state in process iperf

Show key headers only | View raw

> -----Original Message-----
> From: Christoffer Dall [mailto:christoffer.dall@linaro.org]
> Sent: Tuesday, December 15, 2015 2:59 PM
> To: Bhushan Bharat-R65777 <Bharat.Bhushan@freescale.com>
> Cc: kvmarm@lists.cs.columbia.edu; kvm@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; linux-kernel@vger.kernel.org
> Subject: Re: ARM64/KVM: Bad page state in process iperf
> 
> On Tue, Dec 15, 2015 at 03:46:03AM +0000, Bhushan Bharat wrote:
> >
> > Hi All,
> >
> > I am running "iperf" in KVM guest on ARM64 machine and observing below
> crash.
> 
> Which host/guest kernel version is this?

We are using Linux-v4.1 for both host (4K page size) and guest (64K page size).

> 
> Which hardware?

This is observed on Freescale LS2085 hardware based on A57 (8 CPUs).

Thanks
-Bharat

> 
> -Christoffer
> 
> >
> > =============================
> > $iperf -c 3.3.3.3 -P 4 -t 0 -i 5 -w 90k
> > ------------------------------------------------------------
> > Client connecting to 3.3.3.3, TCP port 5001 TCP window size:  180
> > KByte (WARNING: requested 90.0 KByte)
> > ------------------------------------------------------------
> > [  3] local 3.3.3.1 port 51131 connected with 3.3.3.3 port 5001 [  6]
> > local 3.3.3.1 port 51134 connected with 3.3.3.3 port 5001 [  5] local
> > 3.3.3.1 port 51133 connected with 3.3.3.3 port 5001 [  4] local
> > 3.3.3.1 port 51132 connected with 3.3.3.3 port 5001
> > [   53.088567] random: nonblocking pool is initialized
> > [ ID] Interval       Transfer     Bandwidth
> > [  3]  0.0- 5.0 sec   638 MBytes  1.07 Gbits/sec
> > [  4] 35.0-40.0 sec  1.66 GBytes  2.85 Gbits/sec [  5] 40.0-45.0 sec
> > 1.11 GBytes  1.90 Gbits/sec [  4] 40.0-45.0 sec  1.16 GBytes  1.99
> > Gbits/sec
> > [   98.895207] BUG: Bad page state in process iperf  pfn:0a584
> > [   98.896164] page:ffff780000296100 count:-1 mapcount:0 mapping:
> (null) index:0x0
> > [   98.897436] flags: 0x0()
> > [   98.897885] page dumped because: nonzero _count
> > [   98.898640] Modules linked in:
> > [   98.899178] CPU: 0 PID: 1639 Comm: iperf Not tainted 4.1.8-00461-
> ge5431ad #141
> > [   98.900302] Hardware name: linux,dummy-virt (DT)
> > [   98.901014] Call trace:
> > [   98.901406] [<ffff800000096cac>] dump_backtrace+0x0/0x12c
> > [   98.902522] [<ffff800000096de8>] show_stack+0x10/0x1c
> > [   98.903441] [<ffff800000678dc8>] dump_stack+0x8c/0xdc
> > [   98.904202] [<ffff800000145480>] bad_page+0xc4/0x114
> > [   98.904945] [<ffff8000001487a4>] get_page_from_freelist+0x590/0x63c
> > [   98.905871] [<ffff80000014893c>] __alloc_pages_nodemask+0xec/0x794
> > [   98.906791] [<ffff80000059fc80>] skb_page_frag_refill+0x70/0xa8
> > [   98.907678] [<ffff80000059fcd8>] sk_page_frag_refill+0x20/0xd0
> > [   98.908550] [<ffff8000005edc04>] tcp_sendmsg+0x1f8/0x9a8
> > [   98.909368] [<ffff80000061419c>] inet_sendmsg+0x5c/0xd0
> > [   98.910178] [<ffff80000059bb44>] sock_sendmsg+0x14/0x58
> > [   98.911027] [<ffff80000059bbec>] sock_write_iter+0x64/0xbc
> > [   98.912119] [<ffff80000019b5b8>] __vfs_write+0xac/0x10c
> > [   98.913126] [<ffff80000019bcb8>] vfs_write+0x90/0x1a0
> > [   98.913963] [<ffff80000019c53c>] SyS_write+0x40/0xa0
> >
> > -----------
> > _______________________________________________
> > kvmarm mailing list
> > kvmarm@lists.cs.columbia.edu
> > https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

ARM64/KVM: Bad page state in process iperf   Bhushan Bharat <Bharat.Bhushan@freescale.com> - 2015-12-15 04:50 +0100
  Re: ARM64/KVM: Bad page state in process iperf Christoffer Dall <christoffer.dall@linaro.org> - 2015-12-15 10:30 +0100
    RE: ARM64/KVM: Bad page state in process iperf Bhushan Bharat <Bharat.Bhushan@freescale.com> - 2015-12-15 11:10 +0100
  Re: ARM64/KVM: Bad page state in process iperf Marc Zyngier <marc.zyngier@arm.com> - 2015-12-15 10:40 +0100
    RE: ARM64/KVM: Bad page state in process iperf Bhushan Bharat <Bharat.Bhushan@freescale.com> - 2015-12-15 11:00 +0100
      Re: ARM64/KVM: Bad page state in process iperf Marc Zyngier <marc.zyngier@arm.com> - 2015-12-15 11:20 +0100
        RE: ARM64/KVM: Bad page state in process iperf Bhushan Bharat <Bharat.Bhushan@freescale.com> - 2015-12-15 12:00 +0100
          Re: ARM64/KVM: Bad page state in process iperf Marc Zyngier <marc.zyngier@arm.com> - 2015-12-15 12:20 +0100
            RE: ARM64/KVM: Bad page state in process iperf Bhushan Bharat <Bharat.Bhushan@freescale.com> - 2015-12-15 12:50 +0100

csiph-web