New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 896738 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
pgangishetty@chromium.org
█ ravisadineni@chromium.org
ka...@chromium.org
briannorris@chromium.org
sontis@chromium.org
█ dmitrygr@chromium.org
tbroch@chromium.org
diand...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

hana, veyron_mighty: repeatedly fails to suspend due to mmc2:0001

Project Member Reported by matthewjoseph@google.com, Oct 18 
Google Chrome:    71.0.3578.13 (Official Build) dev (32-bit)
Platform:         11151.6.0 (Official Build) dev-channel veyron_mighty
FW Version:       Google_Veyron_Mighty.6588.197.0
Customization ID: HAIER

What steps will reproduce the problem?
(1) Recover device and sign in
(2) Leave device idle and connected to AC power
(3) Attempt to wake the device after some time
(4) Observe device boot & dev screen displayed

What is the expected result?
Device should successfully enter the suspend state

What happens instead?
Device is rebooting after failing to suspend

From eventlog
0 | 2018-10-16 08:37:22 | Log area cleared | 4096
1 | 2018-10-16 08:37:22 | System boot | 0
2 | 2018-10-16 08:37:22 | Chrome OS Developer Mode
3 | 2018-10-18 08:47:28 | Sleep
4 | 2018-10-18 08:47:36 | Wake
5 | 2018-10-18 08:47:46 | Sleep
6 | 2018-10-18 08:47:53 | Wake
7 | 2018-10-18 08:48:03 | Sleep
8 | 2018-10-18 08:48:10 | Wake
9 | 2018-10-18 08:48:19 | Sleep
10 | 2018-10-18 08:48:26 | Wake
11 | 2018-10-18 08:48:36 | Sleep
12 | 2018-10-18 08:48:43 | Wake
13 | 2018-10-18 08:48:52 | Sleep
14 | 2018-10-18 08:48:59 | Wake
15 | 2018-10-18 08:49:09 | Sleep
16 | 2018-10-18 08:49:16 | Wake
17 | 2018-10-18 08:49:25 | Sleep
18 | 2018-10-18 08:49:32 | Wake
19 | 2018-10-18 08:49:42 | Sleep
20 | 2018-10-18 08:49:49 | Wake
21 | 2018-10-18 08:49:58 | Sleep
22 | 2018-10-18 08:50:05 | Wake
23 | 2018-10-18 08:50:15 | Sleep
24 | 2018-10-18 08:50:22 | Wake
25 | 2018-10-16 08:54:00 | System boot | 0
26 | 2018-10-16 08:54:00 | Chrome OS Developer Mode


from powerd.PREVIOUS

[1018/154948:INFO:daemon.cc(636)] powerd_suspend returned 3
[1018/154948:INFO:main.cc(247)] Launching "/usr/bin/powerd_setuid_helper --action=mosys_eventlog --mosys_eventlog_code=0xa8"
[1018/154948:WARNING:suspender.cc(554)] Suspend attempt #9 canceled due to wake event
[1018/154958:INFO:suspender.cc(457)] Starting suspend
[1018/154958:INFO:main.cc(266)] Running "/usr/bin/powerd_setuid_helper --action=mosys_eventlog --mosys_eventlog_code=0xa7"
[1018/154959:INFO:main.cc(266)] Running "/usr/bin/powerd_setuid_helper --action=suspend"
[1018/155004:ERROR:main.cc(272)] Command failed with exit status 3
[1018/155004:INFO:daemon.cc(636)] powerd_suspend returned 3
[1018/155004:INFO:main.cc(247)] Launching "/usr/bin/powerd_setuid_helper --action=mosys_eventlog --mosys_eventlog_code=0xa8"
[1018/155004:WARNING:suspender.cc(554)] Suspend attempt #10 canceled due to wake event
[1018/155014:INFO:suspender.cc(457)] Starting suspend
[1018/155014:INFO:main.cc(266)] Running "/usr/bin/powerd_setuid_helper --action=mosys_eventlog --mosys_eventlog_code=0xa7"
[1018/155015:INFO:main.cc(266)] Running "/usr/bin/powerd_setuid_helper --action=suspend"
[1018/155021:ERROR:main.cc(272)] Command failed with exit status 3
[1018/155021:INFO:daemon.cc(636)] powerd_suspend returned 3
[1018/155021:INFO:main.cc(247)] Launching "/usr/bin/powerd_setuid_helper --action=mosys_eventlog --mosys_eventlog_code=0xa8"
[1018/155021:ERROR:suspender.cc(546)] Unsuccessfully attempted to suspend 11 times; shutting down
[1018/155021:INFO:daemon.cc(1191)] Shutting down, reason: suspend-failed
[1018/155021:INFO:main.cc(247)] Launching "/usr/bin/powerd_setuid_helper --action=shut_down --shutdown_reason=suspend-failed"

Comment 2 Deleted

Comment 3 by matthewjoseph@google.com, Oct 18 

Unable to reproduce on M70 Beta 11021.51.0 using the same device

Comment 4 by derat@chromium.org, Oct 19

Cc: ravisadineni@chromium.org tbroch@chromium.org
Summary: veyron_might repeatedly fails to suspend due to mmc2:0001 (was: [veyron_mighty] Device fails to suspend, reboots instead)
2018-10-18T15:49:10.074803+00:00 NOTICE powerd_suspend[10043]: Finalizing suspend
2018-10-18T15:49:10.080015+00:00 INFO kernel: [  704.028372] PM: suspend entry 2018-10-18 15:49:10.079707650 UTC
2018-10-18T15:49:15.241669+00:00 INFO kernel: [  704.028397] PM: Syncing filesystems ... done.
2018-10-18T15:49:15.241747+00:00 DEBUG kernel: [  704.078932] PM: Preparing system for mem sleep
2018-10-18T15:49:15.241896+00:00 NOTICE kernel: [  704.080983] Freezing user space processes ... (elapsed 0.003 seconds) done.
2018-10-18T15:49:15.241904+00:00 NOTICE kernel: [  704.084462] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done.
2018-10-18T15:49:15.241909+00:00 DEBUG kernel: [  704.086600] PM: Entering mem sleep
2018-10-18T15:49:15.241913+00:00 INFO kernel: [  704.087293] calling  rfkill1+ @ 10046, parent: phy0, cb: rfkill_suspend
2018-10-18T15:49:15.241916+00:00 INFO kernel: [  704.087311] call rfkill1+ returned 0 after 1 usecs
2018-10-18T15:49:15.241925+00:00 INFO kernel: [  704.087342] calling  rfkill0+ @ 10046, parent: hci0, cb: rfkill_suspend
2018-10-18T15:49:15.241930+00:00 INFO kernel: [  704.087354] call rfkill0+ returned 0 after 0 usecs
2018-10-18T15:49:15.241934+00:00 INFO kernel: [  704.087427] calling  phy0+ @ 127, parent: mmc2:0001:1, cb: wiphy_suspend [cfg80211]
2018-10-18T15:49:15.241944+00:00 INFO kernel: [  704.087444] calling  regulatory.0+ @ 10046, parent: platform, cb: platform_pm_suspend
2018-10-18T15:49:15.241948+00:00 INFO kernel: [  704.087448] call regulatory.0+ returned 0 after 0 usecs
2018-10-18T15:49:15.241964+00:00 INFO kernel: [  704.087475] calling  mmc2:0001:3+ @ 10046, parent: mmc2:0001, cb: pm_no_operation
2018-10-18T15:49:15.241969+00:00 INFO kernel: [  704.087481] call phy0+ returned 0 after 15 usecs
2018-10-18T15:49:15.241972+00:00 INFO kernel: [  704.087494] call mmc2:0001:3+ returned 0 after 0 usecs
2018-10-18T15:49:15.241975+00:00 INFO kernel: [  704.087508] calling  mmc2:0001:2+ @ 10046, parent: mmc2:0001, cb: pm_no_operation
2018-10-18T15:49:15.241981+00:00 INFO kernel: [  704.087520] call mmc2:0001:2+ returned 0 after 0 usecs
2018-10-18T15:49:15.241994+00:00 INFO kernel: [  704.087537] calling  mmc2:0001:1+ @ 10046, parent: mmc2:0001, cb: pm_no_operation
2018-10-18T15:49:15.242002+00:00 INFO kernel: [  704.087549] call mmc2:0001:1+ returned 0 after 0 usecs
2018-10-18T15:49:15.242013+00:00 INFO kernel: [  704.087569] calling  mmc2:0001+ @ 10046, parent: mmc2, cb: mmc_bus_suspend
2018-10-18T15:49:15.242020+00:00 ERR kernel: [  709.188613] Bluetooth: btmrvl_main.c:btmrvl_enable_hs() Host sleep enable command failed
2018-10-18T15:49:15.242024+00:00 ERR kernel: [  709.188634] Bluetooth: btmrvl_sdio.c:btmrvl_sdio_suspend() HS not actived, suspend failed!
2018-10-18T15:49:15.242028+00:00 ERR kernel: [  709.188665] dpm_run_callback(): mmc_bus_suspend+0x0/0x58 returns -16
2018-10-18T15:49:15.242031+00:00 INFO kernel: [  709.188678] call mmc2:0001+ returned -16 after 4981539 usecs
2018-10-18T15:49:15.242035+00:00 ERR kernel: [  709.188721] PM: Device mmc2:0001 failed to suspend: error -16
2018-10-18T15:49:15.242039+00:00 ERR kernel: [  709.188736] PM: Some devices failed to suspend, or early wake event detected
2018-10-18T15:49:15.242042+00:00 INFO kernel: [  709.188767] calling  mmc2:0001:1+ @ 10046, parent: mmc2:0001, cb: pm_no_operation
2018-10-18T15:49:15.242046+00:00 INFO kernel: [  709.188779] call mmc2:0001:1+ returned 0 after 0 usecs
2018-10-18T15:49:15.242055+00:00 INFO kernel: [  709.188823] calling  phy0+ @ 127, parent: mmc2:0001:1, cb: wiphy_resume [cfg80211]
2018-10-18T15:49:15.242060+00:00 INFO kernel: [  709.188856] call phy0+ returned 0 after 20 usecs
2018-10-18T15:49:15.242063+00:00 INFO kernel: [  709.188875] calling  mmc2:0001:2+ @ 10046, parent: mmc2:0001, cb: pm_no_operation
2018-10-18T15:49:15.242067+00:00 INFO kernel: [  709.188888] call mmc2:0001:2+ returned 0 after 0 usecs
2018-10-18T15:49:15.242074+00:00 INFO kernel: [  709.188900] calling  mmc2:0001:3+ @ 10046, parent: mmc2:0001, cb: pm_no_operation
2018-10-18T15:49:15.242082+00:00 INFO kernel: [  709.188911] call mmc2:0001:3+ returned 0 after 0 usecs
2018-10-18T15:49:15.242086+00:00 INFO kernel: [  709.188929] calling  regulatory.0+ @ 10046, parent: platform, cb: platform_pm_resume
2018-10-18T15:49:15.242099+00:00 INFO kernel: [  709.188941] call regulatory.0+ returned 0 after 0 usecs
2018-10-18T15:49:15.242103+00:00 INFO kernel: [  709.188963] calling  rfkill0+ @ 10046, parent: hci0, cb: rfkill_resume
2018-10-18T15:49:15.242107+00:00 INFO kernel: [  709.188977] call rfkill0+ returned 0 after 3 usecs
2018-10-18T15:49:15.242111+00:00 INFO kernel: [  709.188990] calling  rfkill1+ @ 10046, parent: phy0, cb: rfkill_resume
2018-10-18T15:49:15.242114+00:00 INFO kernel: [  709.189002] call rfkill1+ returned 0 after 1 usecs
2018-10-18T15:49:15.242118+00:00 INFO kernel: [  709.189031] PM: resume of devices complete after 0.279 msecs
2018-10-18T15:49:15.242121+00:00 DEBUG kernel: [  709.189733] PM: Finishing wakeup.
2018-10-18T15:49:15.250531+00:00 NOTICE kernel: [  709.189740] Restarting tasks ... done.
2018-10-18T15:49:15.250582+00:00 INFO kernel: [  709.193281] PM: suspend exit 2018-10-18 15:49:15.244620902 UTC
2018-10-18T15:49:15.261780+00:00 NOTICE powerd_suspend[10049]: Warning: Device or resource busy on write to /sys/power/state
2018-10-18T15:49:15.264460+00:00 NOTICE powerd_suspend[10050]: --- begin /sys/kernel/debug/suspend_stats ---
2018-10-18T15:49:15.276992+00:00 NOTICE powerd_suspend[10054]: success: 0
2018-10-18T15:49:15.277687+00:00 NOTICE powerd_suspend[10054]: fail: 7
2018-10-18T15:49:15.278089+00:00 NOTICE powerd_suspend[10054]: failed_freeze: 0
2018-10-18T15:49:15.278483+00:00 NOTICE powerd_suspend[10054]: failed_prepare: 0
2018-10-18T15:49:15.278864+00:00 NOTICE powerd_suspend[10054]: failed_suspend: 7
2018-10-18T15:49:15.279255+00:00 NOTICE powerd_suspend[10054]: failed_suspend_late: 0
2018-10-18T15:49:15.279663+00:00 NOTICE powerd_suspend[10054]: failed_suspend_noirq: 0
2018-10-18T15:49:15.280203+00:00 NOTICE powerd_suspend[10054]: failed_resume: 0
2018-10-18T15:49:15.280682+00:00 NOTICE powerd_suspend[10054]: failed_resume_early: 0
2018-10-18T15:49:15.281074+00:00 NOTICE powerd_suspend[10054]: failed_resume_noirq: 0
2018-10-18T15:49:15.281463+00:00 NOTICE powerd_suspend[10054]: failures:
2018-10-18T15:49:15.281812+00:00 NOTICE powerd_suspend[10054]:   last_failed_dev: mmc2:0001
2018-10-18T15:49:15.282189+00:00 NOTICE powerd_suspend[10054]:    mmc2:0001
2018-10-18T15:49:15.282564+00:00 NOTICE powerd_suspend[10054]:   last_failed_errno: -16
2018-10-18T15:49:15.282968+00:00 NOTICE powerd_suspend[10054]:    -16
2018-10-18T15:49:15.283317+00:00 NOTICE powerd_suspend[10054]:   last_failed_step: suspend
2018-10-18T15:49:15.283693+00:00 NOTICE powerd_suspend[10054]:    suspend
2018-10-18T15:49:15.286778+00:00 NOTICE powerd_suspend[10055]: --- end /sys/kernel/debug/suspend_stats ---

Comment 5 by derat@chromium.org, Oct 19

Summary: veyron_mighty repeatedly fails to suspend due to mmc2:0001 (was: veyron_might repeatedly fails to suspend due to mmc2:0001)

Comment 6 by tbroch@google.com, Oct 19

Cc: briannorris@chromium.org
+Brian. I believe this is marvel wifi.

Quick glance at 

https://crosland.corp.google.com/log/11021.51.0..11151.6.0

didn't see anything itneresting under 3.14 kernel or linux-firmware

Comment 7 by briannorris@chromium.org, Oct 19 

That would be Marvell Bluetooth, not Wifi:

2018-10-18T15:49:15.242020+00:00 ERR kernel: [  709.188613] Bluetooth: btmrvl_main.c:btmrvl_enable_hs() Host sleep enable command failed
2018-10-18T15:49:15.242024+00:00 ERR kernel: [  709.188634] Bluetooth: btmrvl_sdio.c:btmrvl_sdio_suspend() HS not actived, suspend failed!
2018-10-18T15:49:15.242028+00:00 ERR kernel: [  709.188665] dpm_run_callback(): mmc_bus_suspend+0x0/0x58 returns -16

Comment 8 by briannorris@chromium.org, Oct 19

Cc: diand...@chromium.org
I've never really debugged an SDIO device before, but in one of those logs, after the next reboot we continue to see BT issues, like this:

2018-10-18T08:54:49.483075-07:00 ERR kernel: [   46.487896] Bluetooth: btmrvl_sdio.c:btmrvl_sdio_card_to_host() readsb failed: -110

I'm not sure if that's just a symptom of an already-dying SDIO device, or if that's an issue with the SDIO bus itself.

Comment 9 by tbroch@google.com, Oct 19

Cc: dmitrygr@chromium.org
+Dmitry as well as I did see BT related fixes in crosland ... although none seemed targeted at this device.

Comment 10 by dianders@google.com, Oct 19 

Is this just a single device that's failing, or is it all veyron devices?  Presumably it wouldn't be just veyron_mighty since there shouldn't be anything super different there.


In one of the logs I see a reset of Marvell at bootup:

2018-10-18T08:54:48.853073-07:00 INFO kernel: [   45.855792] binder: 4053:4063 refcount change on invalid ref 59
2018-10-18T08:54:49.013080-07:00 INFO kernel: [   46.009193] Bluetooth: hci_core.c:skip_conditional_cmd()   COND LE cmd (0x200c) is already 0 (chg 0), skip transition to 0
2018-10-18T08:54:49.013104-07:00 INFO kernel: [   46.009218] Bluetooth: hci_core.c:skip_conditional_cmd()   COND call queue_work.
2018-10-18T08:54:49.483075-07:00 ERR kernel: [   46.487896] Bluetooth: btmrvl_sdio.c:btmrvl_sdio_card_to_host() readsb failed: -110
2018-10-18T08:54:50.409216-07:00 ERR arc-oemcrypto[1652]: BootstrapMojoConnection(...): Domain=arc-oemcrypto, Code=dev_mode, Message=OEMCrypto disabled in dev mode
2018-10-18T08:54:50.613163-07:00 INFO kernel: [   47.608367] arcbr0: port 1(veth_android) entered forwarding state
2018-10-18T08:54:51.583087-07:00 WARNING kernel: [   48.585204] audit_printk_skb: 6 callbacks suppressed
2018-10-18T08:54:51.583113-07:00 NOTICE kernel: [   48.585216] audit: type=1400 audit(1539878091.570:466): avc:  denied  { dac_read_search } for  pid=2499 comm="main" capability=2  scontext=u:r:zygote:s0 tcontext=u:r:zygote:s0 tclass=capability permissive=0
2018-10-18T08:54:52.485514-07:00 ERR dhcpcd[2520]: mlan0: dhcp if_readrawpacket: Network is down
2018-10-18T08:54:52.485650-07:00 ERR shill[1171]: [ERROR:arp_client.cc(118)] Socket recvfrom failed: Network is down
2018-10-18T08:54:52.486178-07:00 ERR wpa_supplicant[600]: nl80211: Failed to open /proc/sys/net/ipv4/conf/mlan0/drop_unicast_in_l2_multicast: No such file or directory
2018-10-18T08:54:52.486193-07:00 ERR wpa_supplicant[600]: nl80211: Failed to set IPv4 unicast in multicast filter
2018-10-18T08:54:52.493146-07:00 INFO kernel: [   49.488386] mwifiex_sdio mmc2:0001:1: Firmware wakeup failed
2018-10-18T08:54:52.493179-07:00 WARNING kernel: [   49.488414] ------------[ cut here ]------------
2018-10-18T08:54:52.493185-07:00 WARNING kernel: [   49.488447] WARNING: CPU: 3 PID: 0 at ../../../../../tmp/portage/sys-kernel/chromeos-kernel-3_14-3.14-r2074/work/chromeos-kernel-3_14-3.14/drivers/net/wireless-3.8/mwifiex/sdio.c:2137 mwifiex_sdio_card_reset+0x34/0x70 [mwifiex_sdio]()
2018-10-18T08:54:52.493190-07:00 NOTICE kernel: [   49.488484] Modules linked in: xt_TCPMSS ip6table_mangle ip6table_raw veth esp6 ah6 xfrm6_mode_tunnel xfrm6_mode_transport xfrm4_mode_tunnel xfrm4_mode_transport nf_nat_tftp nf_conntrack_tftp nf_nat_ftp nf_conntrack_ftp ip6t_REJECT ip6t_ipv6header i2c_dev rfcomm cmac uinput uvcvideo videobuf2_vmalloc snd_seq_dummy zram bridge btmrvl_sdio mwifiex_sdio btmrvl iio_trig_sysfs mwifiex bluetooth stp llc cros_ec_accel kfifo_buf ipt_MASQUERADE xt_mark fuse cfg80211 ip6table_filter ip6_tables snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device joydev
2018-10-18T08:54:52.493195-07:00 NOTICE kernel: [   49.488729] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.14.0 #1
2018-10-18T08:54:52.493198-07:00 NOTICE kernel: [   49.488767] [<c020e51c>] (unwind_backtrace) from [<c020a90c>] (show_stack+0x20/0x24)
2018-10-18T08:54:52.493201-07:00 NOTICE kernel: [   49.488796] [<c020a90c>] (show_stack) from [<c081bbc4>] (dump_stack+0x7c/0xc0)
2018-10-18T08:54:52.493205-07:00 NOTICE kernel: [   49.488819] [<c081bbc4>] (dump_stack) from [<c0223abc>] (warn_slowpath_common+0x7c/0xa0)
2018-10-18T08:54:52.493209-07:00 NOTICE kernel: [   49.488842] [<c0223abc>] (warn_slowpath_common) from [<c0223be4>] (warn_slowpath_null+0x2c/0x34)
2018-10-18T08:54:52.493217-07:00 NOTICE kernel: [   49.488871] [<c0223be4>] (warn_slowpath_null) from [<bf27c64c>] (mwifiex_sdio_card_reset+0x34/0x70 [mwifiex_sdio])
2018-10-18T08:54:52.493221-07:00 NOTICE kernel: [   49.488924] [<bf27c64c>] (mwifiex_sdio_card_reset [mwifiex_sdio]) from [<bf22ef20>] (wakeup_timer_fn+0x5c/0x64 [mwifiex])
2018-10-18T08:54:52.493225-07:00 NOTICE kernel: [   49.488966] [<bf22ef20>] (wakeup_timer_fn [mwifiex]) from [<c0230acc>] (call_timer_fn+0xa4/0x17c)
2018-10-18T08:54:52.493228-07:00 NOTICE kernel: [   49.488989] [<c0230acc>] (call_timer_fn) from [<c023141c>] (run_timer_softirq+0x25c/0x2ac)
2018-10-18T08:54:52.493232-07:00 NOTICE kernel: [   49.489015] [<c023141c>] (run_timer_softirq) from [<c0229050>] (__do_softirq+0x16c/0x33c)
2018-10-18T08:54:52.493235-07:00 NOTICE kernel: [   49.489038] [<c0229050>] (__do_softirq) from [<c02294c0>] (irq_exit+0x94/0xf0)
2018-10-18T08:54:52.493239-07:00 NOTICE kernel: [   49.489060] [<c02294c0>] (irq_exit) from [<c02747a0>] (__handle_domain_irq+0x90/0xb0)
2018-10-18T08:54:52.493242-07:00 NOTICE kernel: [   49.489082] [<c02747a0>] (__handle_domain_irq) from [<c0200390>] (gic_handle_irq+0x48/0x6c)
2018-10-18T08:54:52.493247-07:00 NOTICE kernel: [   49.489103] [<c0200390>] (gic_handle_irq) from [<c020b500>] (__irq_svc+0x40/0x70)
2018-10-18T08:54:52.493251-07:00 NOTICE kernel: [   49.489120] Exception stack(0xee12df00 to 0xee12df48)
2018-10-18T08:54:52.493254-07:00 NOTICE kernel: [   49.489137] df00: ee12df48 0000000b 853ce74b 0000000b 00000000 ee7cc288 850eb88a 0000000b
2018-10-18T08:54:52.493258-07:00 NOTICE kernel: [   49.489154] df20: c103ed78 00000000 c103ed78 ee12df7c 00000008 ee12df48 c0281fe4 c066c33c
2018-10-18T08:54:52.493262-07:00 NOTICE kernel: [   49.489168] df40: 900f0113 ffffffff
2018-10-18T08:54:52.493265-07:00 NOTICE kernel: [   49.489182] [<c020b500>] (__irq_svc) from [<c066c33c>] (cpuidle_enter_state+0x60/0xe8)
2018-10-18T08:54:52.493268-07:00 NOTICE kernel: [   49.489202] [<c066c33c>] (cpuidle_enter_state) from [<c066c540>] (cpuidle_idle_call+0x17c/0x270)
2018-10-18T08:54:52.493271-07:00 NOTICE kernel: [   49.489222] [<c066c540>] (cpuidle_idle_call) from [<c02072f0>] (arch_cpu_idle+0x18/0x48)
2018-10-18T08:54:52.493276-07:00 NOTICE kernel: [   49.489252] [<c02072f0>] (arch_cpu_idle) from [<c02743d4>] (cpu_startup_entry+0x1c4/0x23c)
2018-10-18T08:54:52.493280-07:00 NOTICE kernel: [   49.489275] [<c02743d4>] (cpu_startup_entry) from [<c020c7c0>] (secondary_start_kernel+0x14c/0x174)
2018-10-18T08:54:52.493284-07:00 NOTICE kernel: [   49.489301] [<c020c7c0>] (secondary_start_kernel) from [<00200444>] (0x200444)
2018-10-18T08:54:52.493287-07:00 WARNING kernel: [   49.489317] ---[ end trace a9fcc48229538e91 ]---
2018-10-18T08:54:52.493291-07:00 ERR kernel: [   49.489393] mwifiex_sdio: Resetting card...
2018-10-18T08:54:52.493294-07:00 INFO kernel: [   49.489965] mwifiex_sdio mmc2:0001:1: PREP_CMD: card is removed

---

I don't think Marvell resets are exactly foolproof so I could sorta believe that things are left in a wonky state.

Comment 11 by briannorris@chromium.org, Oct 19 

Marvell Wifi reset/recovery is certainly super-not-great. But even there, the first thing that went wrong was the Bluetooth:

2018-10-18T08:54:49.483075-07:00 ERR kernel: [   46.487896] Bluetooth: btmrvl_sdio.c:btmrvl_sdio_card_to_host() readsb failed: -110

I've also seen one "side's" death cause the whole thing to go down and never recover.

Not sure if that really helps anything.

Comment 12 by matthewjoseph@chromium.org, Oct 29

Summary: hana, veyron_mighty: repeatedly fails to suspend due to mmc2:0001 (was: veyron_mighty repeatedly fails to suspend due to mmc2:0001)
Observing this issue with hana on R71-11151.16.0

Device was left idle with no peripherals attached.  Returned to the device after some time and it booted to the dev screen.

[1029/163159:INFO:suspender.cc(457)] Starting suspend
[1029/163159:INFO:main.cc(266)] Running "/usr/bin/powerd_setuid_helper --action=mosys_eventlog --mosys_eventlog_code=0xa7"
[1029/163200:INFO:main.cc(266)] Running "/usr/bin/powerd_setuid_helper --action=suspend"
[1029/163205:ERROR:main.cc(272)] Command failed with exit status 3
[1029/163205:INFO:daemon.cc(636)] powerd_suspend returned 3
[1029/163205:INFO:main.cc(247)] Launching "/usr/bin/powerd_setuid_helper --action=mosys_eventlog --mosys_eventlog_code=0xa8"
[1029/163205:ERROR:suspender.cc(546)] Unsuccessfully attempted to suspend 11 times; shutting down
[1029/163205:INFO:daemon.cc(1191)] Shutting down, reason: suspend-failed
[1029/163205:INFO:main.cc(247)] Launching "/usr/bin/powerd_setuid_helper --action=shut_down --shutdown_reason=suspend-failed"

Logs here: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/896738
►

Sign in to add a comment