From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Dave Hansen <dave.hansen@intel.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Cc: kernel@gentoo.org, kvm@vger.kernel.org,
Gleb Natapov <gleb@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: 3.13 hangs when I tried to start a KVM at a 32 bit stable Gentoo
Date: Sat, 08 Feb 2014 09:30:27 +0100 [thread overview]
Message-ID: <52F5EB23.4060204@gmx.de> (raw)
In-Reply-To: <52E165B7.6020506@intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 01/23/2014 07:55 PM, Dave Hansen wrote:
> On 01/21/2014 08:38 AM, Toralf Förster wrote:
>> Jan 21 17:18:57 n22 kernel: INFO: rcu_sched self-detected stall on CPU { 2} (t=60001 jiffies g=18494 c=18493 q=183951)
>> Jan 21 17:18:57 n22 kernel: sending NMI to all CPUs:
>> Jan 21 17:18:57 n22 kernel: NMI backtrace for cpu 2
>> Jan 21 17:18:57 n22 kernel: CPU: 2 PID: 6779 Comm: qemu-system-x86 Not tainted 3.13.0 #3
>> Jan 21 17:18:57 n22 kernel: Hardware name: LENOVO 4180F65/4180F65, BIOS 83ET75WW (1.45 ) 05/10/2013
>> Jan 21 17:18:57 n22 kernel: task: e921c370 ti: e5f36000 task.ti: e5f36000
>
> I'm seeing a very similar hang with an ubuntu guest and a custom kernel.
> I'm on commit 0dc3fd0249a, and it's 100% reproducible every time I run KVM.
>
> Cc-ing a few more folks...
>
With 3.12.2 at the same 32 bit Gentoo Linux I experienced a similar thingin a complete different scenario: I umounted a loop-mounted file, on which I created and filled a btrfs file system before (/usr/portage FWIW - I'm a Gentoo user) and the systems becomes very slowly and /var/log/messages shows :
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: Error sending POWER_TABLE_CMD: time out after 2000ms.
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: Current CMD queue read_ptr 100 write_ptr 101
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: Loaded firmware version: 18.168.6.1
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | OK
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | uPc
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | branchlink1
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | branchlink2
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | interruptlink1
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | interruptlink2
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | data1
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | data2
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | line
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | beacon time
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | tsf low
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | time gp1
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | time gp2
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | time gp3
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | uCode version
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | hw version
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | board version
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | hcmd
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | isr0
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | isr1
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | isr2
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | isr3
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | isr4
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | isr_pref
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | wait_event
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | l2p_control
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | l2p_duration
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | l2p_mhvalid
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | l2p_addr_match
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | lmpm_pmg_sel
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | timestamp
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: 0x00000000 | flow_handler
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: Start IWL Event Log Dump: nothing in log
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: set power fail, ret = -110
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: iwl_trans_wait_tx_queue_empty bad state = 0
Feb 7 22:46:46 n22 kernel: ieee80211 phy0: Hardware restart was requested
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
Feb 7 22:46:46 n22 kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Feb 7 22:46:51 n22 kernel: iwlwifi 0000:03:00.0: Failed to load firmware chunk!
Feb 7 22:46:51 n22 kernel: iwlwifi 0000:03:00.0: Could not load the [0] uCode section
Feb 7 22:46:51 n22 kernel: iwlwifi 0000:03:00.0: Failed to start RT ucode: -110
Feb 7 22:46:51 n22 kernel: iwlwifi 0000:03:00.0: Unable to initialize device.
Feb 7 22:46:51 n22 kernel: iwlwifi 0000:03:00.0: Fw not loaded - dropping CMD: 18
Feb 7 22:46:51 n22 kernel: wlp3s0: HW problem - can not stop rx aggregation for 08:96:d7:05:f9:2a tid 0
Feb 7 22:46:51 n22 kernel: iwlwifi 0000:03:00.0: Fw not loaded - dropping CMD: 18
Feb 7 22:46:51 n22 kernel: wlp3s0: HW problem - can not stop rx aggregation for 08:96:d7:05:f9:2a tid 6
Feb 7 22:47:06 n22 dhcpcd[5978]: wlp3s0: carrier lost
Feb 7 22:47:06 n22 dhcpcd[5978]: wlp3s0: deleting route to 192.168.178.0/24
Feb 7 22:47:06 n22 dhcpcd[5978]: wlp3s0: deleting default route via 192.168.178.1
Feb 7 22:47:06 n22 kernel: iwlwifi 0000:03:00.0: iwl_trans_wait_tx_queue_empty bad state = 0
Feb 7 22:47:06 n22 kernel: cfg80211: Calling CRDA to update world regulatory domain
Feb 7 22:47:06 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:06 n22 wpa_cli: interface wlp3s0 DISCONNECTED
Feb 7 22:47:06 n22 wpa_cli: executing 'false /etc/init.d/net.wlp3s0 --quiet stop' failed
Feb 7 22:47:07 n22 kernel: cfg80211: World regulatory domain updated:
Feb 7 22:47:07 n22 kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 7 22:47:07 n22 kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 7 22:47:07 n22 kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 7 22:47:07 n22 kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Feb 7 22:47:07 n22 kernel: cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 7 22:47:07 n22 kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Feb 7 22:47:07 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:08 n22 ntpd[6263]: Deleting interface #3 wlp3s0, 192.168.178.21#123, interface stats: received=279, sent=281, dropped=0, active_time=12050 secs
Feb 7 22:47:08 n22 ntpd[6263]: 144.76.117.245 interface 192.168.178.21 -> (none)
Feb 7 22:47:08 n22 ntpd[6263]: 193.175.73.151 interface 192.168.178.21 -> (none)
Feb 7 22:47:08 n22 ntpd[6263]: 78.47.93.200 interface 192.168.178.21 -> (none)
Feb 7 22:47:08 n22 ntpd[6263]: 130.149.220.125 interface 192.168.178.21 -> (none)
Feb 7 22:47:08 n22 ntpd[6263]: peers refreshed
Feb 7 22:47:08 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:09 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:10 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:11 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:12 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:13 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:14 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:15 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:16 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:17 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:18 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:19 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:20 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:21 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:22 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:23 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:24 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:25 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:26 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Feb 7 22:47:27 n22 kernel: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
...
- --
MfG/Sincerely
Toralf Förster
pgp finger print:1A37 6F99 4A9D 026F 13E2 4DCF C4EA CDDE 0076 E94E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF0EAREIAAYFAlL16yIACgkQxOrN3gB26U6ZLAD4+xOsxbCxkoLLyZm10XESUBxh
3SK0iNuGjBEamGth3gD9GgeZoyK2dwfA5SJX/r6IwWVvwgwQ03frfqCRWQNe6BU=
=Eyi4
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-02-08 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 16:38 3.13 hangs when I tried to start a KVM at a 32 bit stable Gentoo Toralf Förster
2014-01-23 18:55 ` Dave Hansen
2014-01-23 19:33 ` Dave Hansen
2014-01-23 19:50 ` Toralf Förster
2014-01-24 12:36 ` Paolo Bonzini
2014-01-25 9:48 ` Toralf Förster
2014-01-26 10:40 ` Toralf Förster
2014-02-09 16:38 ` Toralf Förster
2014-02-08 8:30 ` Toralf Förster [this message]
2014-02-24 20:39 ` Toralf Förster
2014-02-23 18:59 ` Toralf Förster
-- strict thread matches above, loose matches on Subject: below --
2014-03-02 10:10 Toralf Förster
2014-03-29 9:46 ` Toralf Förster
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=52F5EB23.4060204@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=dave.hansen@intel.com \
--cc=gleb@kernel.org \
--cc=kernel@gentoo.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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.