From: Andreas Schwab <schwab@suse.de>
To: linux-arm-kernel@lists.infradead.org
Subject: BUG: scheduling while atomic: swapper/1/0/0xffff0000
Date: Thu, 23 Jun 2022 14:55:08 +0200 [thread overview]
Message-ID: <mvmwnd7o7yr.fsf@suse.de> (raw)
I'm getting a lot of these messages on a panda board:
[ 572.187805] BUG: scheduling while atomic: swapper/1/0/0xffff0000
[ 572.187835] Modules linked in: af_packet snd_soc_dmic snd_soc_omap_hdmi snd_soc_omap_abe_twl6040 snd_soc_twl6040 omap_remoteproc smsc smsc95xx usbnet omap_ocp2scp mii ti_soc_thermal bq27xxx_battery_hdq bq27xxx_battery rfkill omap_hdq wire twl6030_gpadc industrialio omap_rng snd_soc_omap_mcbsp snd_soc_omap_mcpdm snd_soc_ti_sdma snd_soc_core snd_compress qrtr ac97_bus snd_pcm_dmaengine snd_pcm snd_timer snd soundcore leds_gpio efi_pstore cpufreq_dt uio_pdrv_genirq uio nls_iso8859_1 nls_cp437 vfat fat fuse efivarfs ip_tables x_tables ext4 mbcache jbd2 mmc_block clk_twl6040 gpio_twl6040 omapdrm ti_abb_regulator omap_sham omap_aes_driver omap4_keypad omap_mailbox omap2430 ohci_platform ohci_hcd pbias_regulator phy_twl6030_usb ehci_omap phy_omap_usb2 ehci_hcd musb_hdrc omap_dma udc_core phy_omap_control omap_des omap_hsmmc crypto_engine usbcore mmc_core omap_crypto libdes spi_omap2_mcspi usb_common pwm_twl_led twl6030_regulator pwm_twl ti_tfp410 display_connector omap_wdt
[ 572.188537] drm_kms_helper phy_generic syscopyarea sysfillrect ti_tpd12s015 gpio_keys fb_sys_fops ledtrig_heartbeat sg dm_multipath dm_mod dax scsi_dh_rdac scsi_dh_emc scsi_dh_alua
[ 572.188659] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G W 5.18.4-1-default #1 openSUSE Tumbleweed 89a11705cdd7557b347c90566dc52d3793f62b0a
[ 572.188690] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2022.04 04/01/2022
[ 572.188720] Backtrace:
[ 572.188720] dump_backtrace from show_stack+0x20/0x24
[ 572.188842] r7:ef4675b8 r6:c29e3700 r5:60000153 r4:c1544714
[ 572.188842] show_stack from dump_stack_lvl+0x48/0x54
[ 572.188903] dump_stack_lvl from dump_stack+0x18/0x1c
[ 572.188964] r5:00000000 r4:00000000
[ 572.188964] dump_stack from __schedule_bug+0x74/0x84
[ 572.189025] __schedule_bug from __schedule+0xea0/0x1308
[ 572.189086] r5:00000000 r4:ef468bc0
[ 572.189086] __schedule from schedule_idle+0x2c/0x70
[ 572.189147] r10:c1e0b0f0 r9:c1e0b114 r8:c1e163d0 r7:ef4675b8 r6:c1e0b090 r5:00000001
[ 572.189178] r4:c29e3700
[ 572.189178] schedule_idle from do_idle+0x1a4/0x2c8
[ 572.189239] r5:00000001 r4:c29e3700
[ 572.189270] do_idle from cpu_startup_entry+0x28/0x2c
[ 572.189331] r10:00000000 r9:411fc092 r8:8020406a r7:c204c6b4 r6:c29e3700 r5:00000001
[ 572.189331] r4:00000099
[ 572.189331] cpu_startup_entry from secondary_start_kernel+0x190/0x224
[ 572.189392] secondary_start_kernel from 0x80301ea0
[ 572.189453] r7:c204c6b4 r6:10c0387d r5:00000055 r4:829cc06a
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-06-23 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 12:55 Andreas Schwab [this message]
2022-06-23 13:27 ` BUG: scheduling while atomic: swapper/1/0/0xffff0000 Russell King (Oracle)
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=mvmwnd7o7yr.fsf@suse.de \
--to=schwab@suse.de \
--cc=linux-arm-kernel@lists.infradead.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 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.