From: Udo van den Heuvel <udovdh@xs4all.nl>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 3.14.1 BUG: scheduling while atomic: irq/20-serial/1299/0x00000202
Date: Sat, 31 May 2014 18:14:38 +0200 [thread overview]
Message-ID: <5389FFEE.7030901@xs4all.nl> (raw)
Hello,
After returning from holiday I found this in dmesg:
[1724773.295579] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[1725207.771256] BUG: scheduling while atomic: irq/20-serial/1299/0x00000202
[1725207.771260] Modules linked in: btrfs lzo_compress zlib_deflate bnep
bluetooth 6lowpan_iphc fuse edac_core cpufreq_userspace
nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_REJECT ipt_REJECT
nf_conntrack_ipv6 nf_defrag_ipv6 xt_tcpudp iptable_filter ipt_MASQUERADE
xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
nf_nat nf_conntrack ip6table_filter ip6_tables ip_tables x_tables eeprom
it87 hwmon_vid ext2 ppdev kvm_amd kvm microcode parport_serial
parport_pc snd_usb_audio snd_usbmidi_lib snd_hwdep k10temp snd_rawmidi
parport i2c_piix4 evdev pwc videobuf2_vmalloc videobuf2_memops
v4l2_common videobuf2_core cp210x videodev usbserial
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec
snd_seq snd_seq_device snd_pcm snd_timer snd acpi_cpufreq button nfsd
auth_rpcgss
[1725207.771314] binfmt_misc oid_registry nfs_acl lockd sunrpc autofs4
hid_generic usbhid ehci_pci ehci_hcd ohci_pci ohci_hcd radeon
cfbfillrect cfbimgblt cfbcopyarea i2c_algo_bit backlight fbcon bitblit
softcursor font sr_mod cdrom drm_kms_helper ttm xhci_hcd drm fb fbdev
[1725207.771336] CPU: 2 PID: 1299 Comm: irq/20-serial Not tainted 3.14.1 #2
[1725207.771338] Hardware name: Gigabyte Technology Co., Ltd. To be
filled by O.E.M./F2A85X-UP4, BIOS F5a 04/30/2013
[1725207.771340] 0000000000000000 000000003c9f116f ffffffff814dccf6
ffff88023ed11700
[1725207.771346] ffffffff814db539 ffffffff814dec5d 000000000000a000
ffff880235461010
[1725207.771350] ffff88008ec13fd8 ffff880235461010 0000000000000087
0000000000000087
[1725207.771353] Call Trace:
[1725207.771364] [<ffffffff814dccf6>] ? dump_stack+0x4a/0x75
[1725207.771371] [<ffffffff814db539>] ? __schedule_bug+0x3e/0x4b
[1725207.771374] [<ffffffff814dec5d>] ? __schedule+0x68d/0x8b0
[1725207.771379] [<ffffffff814df24f>] ? schedule_preempt_disabled+0xf/0x20
[1725207.771383] [<ffffffff814e09d4>] ? __mutex_lock_slowpath+0x124/0x200
[1725207.771387] [<ffffffff814e0abe>] ? mutex_lock+0xe/0x1d
[1725207.771392] [<ffffffff812e6019>] ? flush_to_ldisc+0x59/0x170
[1725207.771397] [<ffffffff812fa40c>] ? uart_insert_char+0x14c/0x180
[1725207.771400] [<ffffffff812fc24d>] ? serial8250_rx_chars+0xbd/0x1e0
[1725207.771404] [<ffffffff812fde57>] ?
serial8250_handle_irq.part.21+0x37/0x80
[1725207.771408] [<ffffffff812fd0da>] ? serial8250_interrupt+0x5a/0xd0
[1725207.771412] [<ffffffff810aa0e0>] ? irq_thread_fn+0x50/0x50
[1725207.771416] [<ffffffff810aa10c>] ? irq_forced_thread_fn+0x2c/0x70
[1725207.771419] [<ffffffff810aa3fb>] ? irq_thread+0x12b/0x160
[1725207.771422] [<ffffffff810aa220>] ? wake_threads_waitq+0x30/0x30
[1725207.771425] [<ffffffff810aa2d0>] ? irq_thread_dtor+0xb0/0xb0
[1725207.771429] [<ffffffff81084941>] ? kthread+0xd1/0xf0
[1725207.771432] [<ffffffff81084870>] ? kthread_create_on_node+0x1b0/0x1b0
[1725207.771435] [<ffffffff814e2abc>] ? ret_from_fork+0x7c/0xb0
[1725207.771438] [<ffffffff81084870>] ? kthread_create_on_node+0x1b0/0x1b0
[1728364.905013] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IRQ 20 is used by an add-in card with two serial ports:
[ 1.242174] 0000:03:06.0: ttyS1 at I/O 0xd050 (irq = 20, base_baud =
115200) is a 16550A
[ 1.262605] 0000:03:06.0: ttyS2 at I/O 0xd040 (irq = 20, base_baud =
115200) is a 16550A
What happened?
How to fix this?
Kind regards,
Udo
next reply other threads:[~2014-05-31 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 16:14 Udo van den Heuvel [this message]
2014-06-02 12:56 ` 3.14.1 BUG: scheduling while atomic: irq/20-serial/1299/0x00000202 Peter Hurley
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=5389FFEE.7030901@xs4all.nl \
--to=udovdh@xs4all.nl \
--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