From: Larry Finger <Larry.Finger@lwfinger.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>
Subject: Bug in 3.15-rc1: Scheduling while atomic splats filling log
Date: Thu, 17 Apr 2014 14:16:22 -0500 [thread overview]
Message-ID: <53502886.6020107@lwfinger.net> (raw)
On kernel 3.15-rc1, I get log entries for scheduling while atomic. These BUG
splats are repeated many times, and start early in the boot. I tried to bisect
this problem, but the bug does not always show on every boot, and I must have
had a faulty kernel boot without error. In any case, I ended up at a merge pull.
What I can definitively report is that a kernel generated from commit fd1df00 is
bad.
Fortunately, I have retained the kernels from the bisection onward, and I will
retry them to see if I reported any of them incorrectly. As far as I know, the
configuration was unchanged during the bisection.
The logged messages are as follows:
2014-04-16T10:51:25.205576-05:00 larrylap systemd[1]: Starting Name Service
Cache Daemon...
2014-04-16T10:51:25.197425-05:00 larrylap kernel: [ 27.176133] Call Trace:
2014-04-16T10:51:25.205599-05:00 larrylap kernel: [ 27.176139]
[<ffffffff81607386>] dump_stack+0x4e/0x71
2014-04-16T10:51:25.205605-05:00 larrylap kernel: [ 27.176144]
[<ffffffff816009e2>] __schedule_bug+0x5d/0x6d
2014-04-16T10:51:25.205615-05:00 larrylap kernel: [ 27.176149]
[<ffffffff8160a8d5>] __schedule+0x775/0x810
2014-04-16T10:51:25.205618-05:00 larrylap kernel: [ 27.176154]
[<ffffffff8160aa34>] schedule+0x24/0x70
2014-04-16T10:51:25.205620-05:00 larrylap kernel: [ 27.176159]
[<ffffffff8160adc1>] schedule_preempt_disabled+0x11/0x20
2014-04-16T10:51:25.205623-05:00 larrylap kernel: [ 27.176164]
[<ffffffff810941a3>] cpu_startup_entry+0x123/0x430
2014-04-16T10:51:25.205625-05:00 larrylap kernel: [ 27.176170]
[<ffffffff8102dcb3>] start_secondary+0x1d3/0x290
2014-04-16T10:51:25.205627-05:00 larrylap kernel: [ 27.176175]
[<ffffffff813aa118>] ? acpi_ps_parse_aml+0x186/0x476
2014-04-16T10:51:25.205629-05:00 larrylap kernel: [ 27.177033] BUG: scheduling
while atomic: swapper/1/0/0x00000004
2014-04-16T10:51:25.205638-05:00 larrylap kernel: [ 27.177037] no locks held
by swapper/1/0.
2014-04-16T10:51:25.205641-05:00 larrylap kernel: [ 27.177039] Modules linked
in: arc4 b43 mac80211 cfg80211 snd_hda_codec_generic snd_hda_intel snd_hda_co
ntroller snd_hda_codec snd_hwdep snd_pcm snd_seq powernow_k8 kvm_amd kvm rfkill
bcma snd_timer snd_seq_device snd r852 pcspkr ssb serio_raw sdhci_pci sm_comm
on sdhci nand forcedeth mmc_core sg mtd r592 nand_ids nand_bch memstick bch
nand_ecc sr_mod cdrom soundcore battery ac autofs4 nouveau ttm drm_kms_helper drm
i2c_algo_bit i2c_core thermal wmi video processor button thermal_sys hwmon
ata_generic pata_amd
next reply other threads:[~2014-04-17 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 19:16 Larry Finger [this message]
2014-04-20 5:37 ` Bug in 3.15-rc1: Scheduling while atomic splats filling log - bisected to commit 27f6c57 Larry Finger
[not found] ` <CA+55aFxsDvc=3j9TFgEV7W7f-PMRn2UfqStHPXDVqCRXyPXzEg@mail.gmail.com>
2014-04-20 18:27 ` Larry Finger
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=53502886.6020107@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox