sentry: memory corruption during suspend test |
||||
Issue descriptionKernel crashes during suspend test. For instance, in gs://chromeos-moblab-quanta/results/00:80:0f:11:41:25/df448a4e-df55-11e5-a99b-a01223b33c85/276-moblab/192.168.231.102/ [ 1885.586873] BUG: unable to handle kernel paging request at 0000000029db638a [ 1885.586887] IP: [<ffffffffaf1155f8>] __kmalloc_track_caller+0xc3/0x134 ... [ 1885.589082] [<ffffffffaf53aa69>] __alloc_skb+0x88/0x1c6 ... [ 1885.589111] [<ffffffffaf536594>] sock_alloc_send_pskb+0x1b2/0x254 ... [ 1885.589148] [<ffffffffaf532224>] sock_sendmsg+0x7d/0xb2 ... sendmsg is triggering the crash, the corruption can be in another driver.
,
Apr 19 2016
Another crashes at suspend related to memory corruption, in the block stack. gs://chromeos-moblab-quanta/results/00:80:0f:11:41:25/df448a4e-df55-11e5-a99b-a01223b33c85/305-moblab/192.168.231.102/ [35089.916685] HDMI HDA Codec ehdaudio0D2: HDMI: invalid ELD buf size -1 [35091.156839] asix 1-9:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 [35095.921664] HDMI HDA Codec ehdaudio0D2: HDMI: invalid ELD buf size -1 [35097.923655] HDMI HDA Codec ehdaudio0D2: HDMI: invalid ELD buf size -1 [35099.556370] last active wakeup source: 00:02 [35099.925644] HDMI HDA Codec ehdaudio0D2: HDMI: invalid ELD buf size -1 [35101.382287] BUG: Bad page state in process fio pfn:27387c [35101.382322] page:ffffea0009ce1f00 count:-1 mapcount:0 mapping: (null) index:0x0 [35101.382350] flags: 0x8000000000000000() ... [35101.382952] [<ffffffffa84df40b>] bad_page+0xe0/0xfe [35101.382976] [<ffffffffa84e1d6d>] get_page_from_freelist+0x412/0x59b .. [35101.383888] [<ffffffffa85546b7>] do_io_submit+0x2b6/0x37c
,
Apr 21 2016
FYR, I am tackling similar issue on chrome-os-partner:52363, and other corruption (various pattern) could be found in 52506 as well as 51073
,
May 17 2016
this should be able to relieve the memory corruption in network subsystem: https://chromium-review.googlesource.com/#/q/topic:skb_recv_datagram
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Apr 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by gwendal@chromium.org
, Apr 19 2016