[Bug 334369] New: panic in interrupt context with fbcon causes "BUG: scheduling while atomic: swapper"
https://bugzilla.novell.com/show_bug.cgi?id=334369 Summary: panic in interrupt context with fbcon causes "BUG: scheduling while atomic: swapper" Product: openSUSE 10.3 Version: Final Platform: All OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: jeffm@novell.com QAContact: qa@suse.de Found By: Customer BUG: scheduling while atomic: beagled/ox10010000/4560 [<c02c362e>] __sched_text_start+0x5e/0x7c5 [<c011f2fc>] __cond_resched+0x18/0x29 [<c02c3dfb>] cond_resched+0x26/0x31 [<c0136c19>] down_read+0x08/0x17 [<c012eb07>] __blocking_notifier_call_chain+0x1q/0x47 [<c01ebc38>] bit_cursor+0x0/0x498 [<c012eb4b>] blocking_notifier_call_chain+0x17/0x1a [<c01eac73>] fbcon_blank+0x17/0x1e7 [<c022f2df>] lf+0x20/0x3d [<c0232fcb>] vt_console_print+0x0/0x226 [<c0123d45>] __call_console_drivers+0x4f/0x5b [<c012408e>] release_console_sem+0x186/0x19f [<c0123f06>] wake_up_klogd+0x33/0x35 [<c0158b7f>] fblockable_page_cache_readahead+0x4x/0x9f [<c012b904>] lock_timer_base+0x19/0x35 [<c012ba18>] __mod_timer+0x9a/0xa4 [<c0230b47>] do_unblank_screen+0xca/0x111 [<c01d17d0>] ust_spinlocks+0x14/0x24 [<c0123c0c>] panic+0x48/0xf8 [<dcf4cac1>] ahc_search_qinfifo+0x2b0/0x775 [aic7xxx] [<dcf4d98e>] ahc_freezedevq+0x7f/0x8f [aic7xxx] [<dcf4fbe5>] ahc_handle_seqint+0x1a1/0x23e0 [aic7xxx] [<c016fc81>] do_sync_read+0xc7/0x10a [<dcf0689c>] scsi_end_request+0xa1/0xab [scsi_mod] [<c01341b9>] autoremove_wake_function+0x0/0x33 [<dcf5aff0>] ahc_linux_isr+0x184/0x1b0 [aic7xxx] [<c014f2c7>] handle_IRQ_event+0x23/0x51 [<c01506c9>] handle_level_irq+0xb9/0xc8 [<c0107479>] do_IRQ+0x79/0x90 [<c0105e73>] common_interrupt+0x23/0x30 [<c02c0000>] unix_ioctl+0x75/0x95 The failure in aic7xxx is handled in bug 332048. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=334369#c1 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |reisenweber@web.de --- Comment #1 from Jeff Mahoney <jeffm@novell.com> 2007-10-23 11:36:55 MST --- Can you reproduce this with http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/i586... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=334369#c2 --- Comment #2 from joerg reisenweber <reisenweber@web.de> 2007-10-23 12:34:22 MST --- Please check #1 and #5 in other bug, note the three(!) completely different logs there. Also see difference (swapper ./. beagled) in description and first line of panic log here. NB: I may reproduce a "BUG: scheduling while atomic:", but i have no influence at all on which task is interrupted by this BUG. So i'm not sure i can help with checking fbcon. If so, please give me exact instruction how to proceed and what to check for (i don't like to do a 3. manual copy of a half screenfull of hex values by hand). Probably it's no issue to install the new kernel via yast. However i would very much appreciate some "rpm" lines to copy&paste to an xterm. Though i would prefer to rename some modules or vmlinuz and leave the whole rpmdb untouched. Especially i would not like to lose my actual kernel+modules setup, so an additional entry in grub menu.lst (or grub commands to boot) or at least exact instructions how to downgrade after test are welcome. This is a "mission critical" system, so i don't like to render it unusable and would have to install whole system again. i guess it would be best to copy vmlinux out of the *.rpm to some unique file in /boot and start with grub "kernel=..." ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=334369#c3 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|reisenweber@web.de | --- Comment #3 from Stephan Kulow <coolo@novell.com> 2007-11-26 09:40:29 MST --- info provided -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=334369 Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |jeffm@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=334369 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=334369#c4 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #4 from Jeff Mahoney <jeffm@novell.com> 2008-02-05 12:12:14 MST --- Hi Joerg, this one has kind of sat around for a while waiting for someone to take a look at it. I'll write up a patch I can use locally that will force a panic in interrupt context to create the appropriate oops. This isn't a SUSE-specific bug, so once I'm able to generate an Oops with the latest kernel, I'm just going to refile the bug upstream. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=334369 User auxsvr@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=334369#c5 --- Comment #5 from John McManaman <auxsvr@yahoo.com> 2008-12-02 08:10:00 MST --- Created an attachment (id=257293) --> (https://bugzilla.novell.com/attachment.cgi?id=257293) All 3 BUGs and a WARNING: at arch/x86/mm/ioremap.c Please check the attachment for more information. Using 2.6.27.7-3-default, I got this 3 times on an old P4 desktop: Dec 2 04:09:19 linux kernel: BUG: scheduling while atomic: swapper/0/0x10000100 Dec 2 04:09:19 linux kernel: Modules linked in: vboxdrv(N) iptable_raw xt_comment xt_policy ipt_ULOG ipt_TTL ipt_ttl ipt_REJECT ipt_REDIRECT ipt_recent ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat _pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntr ack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_con ntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG xt_multiport xt_MARK xt_mark xt_mac xt_limit xt_length xt_iprange xt_h elper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack _ipv4 nf_conntrack iptable_mangle nfnetlink tun iptable_filter ip_tables x_tables eeprom asb100(N) hwmon_vid radeon drm sidewinder snd_pcm_oss snd_mixer_oss snd_seq_midi snd_ Dec 2 04:09:19 linux kernel: emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_event snd_seq_midi_emul snd_seq edd af_packet bridge s tp microcode ipv6 ext3 jbd mbcache loop dm_mod fuse sr_mod cdrom ide_pci_generic piix ide_core ir_common videodev v4l1_compat compat_ioctl32 p pdev ata_generic v4l2_common snd_emu10k1 videobuf_dma_sg snd_intel8x0 videobuf_core snd_rawmidi tveeprom snd_seq_device tg3 snd_util_mem sg oh ci1394 via_rhine snd_ac97_codec emu10k1_gp snd_hwdep libphy cdc_ether ieee1394 ac97_bus usbnet ata_piix snd_pcm ahci floppy iTCO_wdt intel_agp shpchp snd_timer ns558 snd iTCO_vendor_support button agpgart pci_hotplug mii i2c_i801 pcspkr gameport parport_pc soundcore parport joydev sn d_page_alloc rtc_cmos i2c_core rtc_core rtc_lib usbhid hid ff_memless sd_mod crc_t10dif uhci_hcd ehci_hcd usbcore sata_promise libata scsi_mod dock reiserfs fan thermal processor thermal_sys hwmon [last unloaded: speedstep_lib] Dec 2 04:09:19 linux kernel: Supported: No Dec 2 04:09:19 linux kernel: Dec 2 04:09:19 linux kernel: Pid: 0, comm: swapper Tainted: G W (2.6.27.7-3-default #1) Dec 2 04:09:19 linux kernel: EIP: 0060:[<c01180cc>] EFLAGS: 00000286 CPU: 0 Dec 2 04:09:19 linux kernel: EIP is at native_safe_halt+0x2/0x3 Dec 2 04:09:19 linux kernel: EAX: c0540000 EBX: 00000020 ECX: 01377000 EDX: 00662492 Dec 2 04:09:19 linux kernel: ESI: c0591018 EDI: 00000000 EBP: 00a85007 ESP: c0541fd0 Dec 2 04:09:19 linux kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Dec 2 04:09:19 linux kernel: CR0: 8005003b CR2: a23b0004 CR3: 32309000 CR4: 000006d0 Dec 2 04:09:19 linux kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 Dec 2 04:09:19 linux kernel: DR6: ffff0ff0 DR7: 00000400 Dec 2 04:09:19 linux kernel: [<c010a9aa>] default_idle+0x3a/0x60 Dec 2 04:09:19 linux kernel: [<c0103d3f>] cpu_idle+0xeb/0x10c Dec 2 04:09:19 linux kernel: [<c054695b>] start_kernel+0x31a/0x31f Dec 2 04:09:19 linux kernel: ======================= -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=334369 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=334369#c6 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low --- Comment #6 from Jeff Mahoney <jeffm@novell.com> 2008-12-02 09:22:40 MST --- Thanks for the trace, but I'm afraid it's unrelated. There are lots of ways to get scheduling while atomic, and this isn't from the fbcon. This one is caused because the panic takes a spinlock and then the fbcon downs a mutex. Boom. I haven't done anything with it since it's quite involved and not that high a priority. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com