["Solved"] Strange error message send me back to TTY

Unia · 2011-08-17 15:06:04

Hello,

I was just doing my normal work, when I wanted to open Firefox. I clicked on the icon inside the DockbarX applet in AWN, and I got send straight to TTY1 with three of the same error messages waiting for me:

BUG: scheduling while atomic: X/865/0x00000002

Now I googled around a bit, but all it came up with were kernel this and thats, and that's way over my head. Could you explain me what this means and if it's something I have to solve?

Last edited by Unia (2011-08-29 15:51:39)

bernarcher · 2011-08-17 16:06:43

We need more detail to help you with this. At least which WM/DE you are using. And Firefox version.

Unia · 2011-08-17 16:59:28

Fully up to date system, with Compiz standalone and Firefox 6.0. Perhaps it has something to do with the recent kernel update to 3.0.2-1?

Unia · 2011-08-20 10:00:48

Just two minutes ago, when I wanted to open my email in Firefox from Pidgin, the whole system hung up. Nothing worked, couldn't get back to a TTY either - only a hard reboot worked.

Seems like it's related to Firefox.

Anyone?

Unia · 2011-08-20 19:52:33

Now my system hung again, again when opening Firefox (this time through a link in Skype).

Are there any error messages I can check?

fsckd · 2011-08-20 20:29:28

Try running from the command line and hopefully the message will be displayed in std{err,out}.

Unia · 2011-08-20 20:39:49

I've just installed Chromium so that I can check whether or not it's Firefox related.

Unia · 2011-08-22 10:41:32

Now I tried opening VLC's settings and my system hung again. I don't know if it is related though. Are there any logs I can check?

lolilolicon · 2011-08-22 10:53:08

You should look at kernel.log.

Unia · 2011-08-22 11:12:58

Acording to my post, the hang up took place around 12:41 (forum time is one hour behind). In kernel.log, there's nothing at that time though. Here's the log from before and after 12:41:

<snip>
Aug 22 11:45:54 localhost kernel: [   28.266552] EXT4-fs (sda1): re-mounted. Opts: commit=600
Aug 22 11:45:55 localhost kernel: [   29.165154] EXT4-fs (sda2): re-mounted. Opts: commit=600
Aug 22 11:46:38 localhost kernel: [   72.063557] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Aug 22 12:00:54 localhost kernel: [  926.560638] chromium-sandbo (3463): /proc/3461/oom_adj is deprecated, please use /proc/3461/oom_score_adj instead.
Aug 22 12:40:12 localhost kernel: [    0.000000] Initializing cgroup subsys cpuset
Aug 22 12:40:12 localhost kernel: [    0.000000] Initializing cgroup subsys cpu
Aug 22 12:40:12 localhost kernel: [    0.000000] Linux version 3.0-ARCH (tobias@T-POWA-LX) (gcc version 4.6.1 (GCC) ) #1 SMP PREEMPT Wed Aug 17 21:55:57 CEST 2011
Aug 22 12:40:12 localhost kernel: [    0.000000] Command line: root=/dev/sda1 resume=/dev/sda3 init=/sbin/e4rat-preload nomodeset vga=0x0323
Aug 22 12:40:12 localhost kernel: [    0.000000] BIOS-provided physical RAM map:
<snip>

AFAIK, the logs from 12:40 are starting from my reboot, so any errors should be placed right before these lines. I can't see anything, although I'm not exactly sure what I'm looking for. If you need the complete log from 11:45 just ask. It's pretty long though

Last edited by Unia (2011-08-22 11:13:32)

lolilolicon · 2011-08-22 11:36:06

You should look for:

BUG: scheduling while atomic: X/

in kernel.log. This line, enclosed with double quotes, will yield many threads from a google search.
dmesg.log may contain this error too.

From what I understand, this probably means a bug in some driver or the kernel.

Unia · 2011-08-22 11:43:39

Ah, I found that on August 17 - the day I created this thread. It's in more than once, and they all have messages about fglrx with them:

Aug 17 16:50:17 localhost kernel: [ 5248.084250] nautilus[14922]: segfault at b0 ip 00000000004861a4 sp 00007fff1b2c3370 error 4 in nautilus[400000+159000]
Aug 17 16:59:06 localhost kernel: [ 5775.598155] [fglrx] IRQ 45 Disabled
Aug 17 16:59:06 localhost kernel: [ 5775.598172] BUG: scheduling while atomic: X/865/0x00000002
Aug 17 16:59:06 localhost kernel: [ 5775.598173] Modules linked in: dm_mod fuse ipv6 cpufreq_ondemand uvcvideo videodev usbhid media v4l2_compat_ioctl32 hid joydev uas usb_storage keucr(C) arc4 snd_hda_codec_hdmi snd_hda_codec_realtek broadcom ath9k mac80211 ath9k_common ath9k_hw snd_hda_intel snd_hda_codec ath snd_hwdep snd_pcm cfg80211 snd_timer i2c_i801 tg3 intel_agp snd iTCO_wdt psmouse ehci_hcd vboxdrv acer_wmi sparse_keymap evdev sg pcspkr serio_raw i2c_core intel_ips libphy rfkill intel_gtt iTCO_vendor_support usbcore wmi soundcore mei(C) snd_page_alloc thermal battery ac video acpi_cpufreq freq_table processor mperf fglrx(P) button ext4 mbcache jbd2 crc16 sr_mod sd_mod cdrom ahci libahci libata scsi_mod
Aug 17 16:59:06 localhost kernel: [ 5775.598224] Pid: 865, comm: X Tainted: P         C  3.0-ARCH #1
Aug 17 16:59:06 localhost kernel: [ 5775.598226] Call Trace:
Aug 17 16:59:06 localhost kernel: [ 5775.598236]  [<ffffffff813e9ed3>] __schedule_bug+0x5f/0x64
Aug 17 16:59:06 localhost kernel: [ 5775.598241]  [<ffffffff813f0381>] schedule+0x831/0x9f0
Aug 17 16:59:06 localhost kernel: [ 5775.598280]  [<ffffffffa014e2e2>] ? firegl_trace+0x72/0x1e0 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598284]  [<ffffffff81045128>] ? __wake_up_common+0x58/0x90
Aug 17 16:59:06 localhost kernel: [ 5775.598308]  [<ffffffffa014e2e2>] ? firegl_trace+0x72/0x1e0 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598312]  [<ffffffff813f2eb7>] ? _raw_spin_unlock_irqrestore+0x37/0x40
Aug 17 16:59:06 localhost kernel: [ 5775.598315]  [<ffffffff81046e13>] ? __wake_up+0x53/0x70
Aug 17 16:59:06 localhost kernel: [ 5775.598317]  [<ffffffff813f2eb7>] ? _raw_spin_unlock_irqrestore+0x37/0x40
Aug 17 16:59:06 localhost kernel: [ 5775.598321]  [<ffffffff8107f470>] ? prepare_to_wait+0x60/0x90
Aug 17 16:59:06 localhost kernel: [ 5775.598338]  [<ffffffffa012355a>] KAS_Thread_WaitForFinish+0x8a/0xc0 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598341]  [<ffffffff8107f680>] ? abort_exclusive_wait+0xb0/0xb0
Aug 17 16:59:06 localhost kernel: [ 5775.598362]  [<ffffffffa013a567>] MCIL_WorkerThread+0x177/0x230 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598384]  [<ffffffffa013bc06>] ? MCIL_GetExecutionLevel+0x66/0x80 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598416]  [<ffffffffa01ee7a1>] ? PassiveRing_Cleanup+0x61/0xc0 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598444]  [<ffffffffa01fd3e8>] DispatchRing_Cleanup+0x48/0x70 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598447]  [<ffffffff81141933>] ? kfree+0x163/0x180
Aug 17 16:59:06 localhost kernel: [ 5775.598450]  [<ffffffff810bfee6>] ? free_irq+0x56/0xb0
Aug 17 16:59:06 localhost kernel: [ 5775.598481]  [<ffffffffa01edde0>] ? IRQMGR_FreeResources+0x20/0x60 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598504]  [<ffffffffa013cff5>] ? irqmgr_wrap_shutdown+0x125/0x180 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598522]  [<ffffffffa012ea06>] ? firegl_takedown+0x7d6/0x8a0 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598548]  [<ffffffffa0204202>] ? amdPcsEngine_InitDatabase+0x12/0x20 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598567]  [<ffffffffa012db15>] ? firegl_release+0x125/0x1c0 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598580]  [<ffffffffa011eee1>] ? ip_firegl_release+0x11/0x20 [fglrx]
Aug 17 16:59:06 localhost kernel: [ 5775.598584]  [<ffffffff811590fa>] ? fput+0xda/0x210
Aug 17 16:59:06 localhost kernel: [ 5775.598586]  [<ffffffff81155996>] ? filp_close+0x66/0x90
Aug 17 16:59:06 localhost kernel: [ 5775.598589]  [<ffffffff81060000>] ? put_files_struct+0xa0/0x110
Aug 17 16:59:06 localhost kernel: [ 5775.598591]  [<ffffffff81060132>] ? exit_files+0x52/0x60
Aug 17 16:59:06 localhost kernel: [ 5775.598593]  [<ffffffff8106063a>] ? do_exit+0x18a/0x8f0
Aug 17 16:59:06 localhost kernel: [ 5775.598595]  [<ffffffff810610f4>] ? do_group_exit+0x44/0xa0
Aug 17 16:59:06 localhost kernel: [ 5775.598598]  [<ffffffff81071fee>] ? get_signal_to_deliver+0x33e/0x510
Aug 17 16:59:06 localhost kernel: [ 5775.598601]  [<ffffffff8100b1af>] ? do_signal+0x6f/0x780
Aug 17 16:59:06 localhost kernel: [ 5775.598603]  [<ffffffff8106ffd7>] ? __set_task_blocked+0x37/0x80
Aug 17 16:59:06 localhost kernel: [ 5775.598605]  [<ffffffff81072362>] ? set_current_blocked+0x52/0x60
Aug 17 16:59:06 localhost kernel: [ 5775.598608]  [<ffffffff810723ba>] ? sigprocmask+0x4a/0x90
Aug 17 16:59:06 localhost kernel: [ 5775.598609]  [<ffffffff81071488>] ? do_tkill+0x88/0xa0
Aug 17 16:59:06 localhost kernel: [ 5775.598611]  [<ffffffff8106ffd7>] ? __set_task_blocked+0x37/0x80
Aug 17 16:59:06 localhost kernel: [ 5775.598613]  [<ffffffff8100b945>] ? do_notify_resume+0x65/0x80
Aug 17 16:59:06 localhost kernel: [ 5775.598615]  [<ffffffff810723ba>] ? sigprocmask+0x4a/0x90
Aug 17 16:59:06 localhost kernel: [ 5775.598618]  [<ffffffff813f4050>] ? int_signal+0x12/0x17

Need the others too? They look the same, but you might need them anyway.
EDIT: I didn't know if the first line with a nautilus segfault has anything to do with this, but I included it nonetheless.

Last edited by Unia (2011-08-22 11:46:57)

Unia · 2011-08-23 13:42:55

Asked for help at the ATi topic in Applications & Desktop Environments:
https://bbs.archlinux.org/viewtopic.php … 46#p980546

Unia · 2011-08-23 17:52:22

When opening VLC's preferences again, I had another system hang. I only experience these when opening Firefox (which I now replaced with Chromium) or VLC's preferences.
Upon reboot, I immediately checked the logs, but could only find this:

Aug 23 19:41:28 localhost kernel: [19407.904311] end_request: I/O error, dev sr0, sector 0
Aug 23 19:41:28 localhost kernel: [19407.904317] Buffer I/O error on device sr0, logical block 0

The system hang up actually took place at 19:47, but from that time there are only logs from booting process.

Unia · 2011-08-23 17:58:21

Just tried opening VLC's preferences again, and my system hung indeed.
The only entry before the new boot process from kernel.log:

Aug 23 19:48:10 localhost kernel: [   57.052255] chromium-sandbo (1246): /proc/1244/oom_adj is deprecated, please use /proc/1244/oom_score_adj instead.

Unia · 2011-08-23 20:49:02

I just downgraded to vlc 1.11.1-3 instead of 1.11.1-4, to see if that might help. So far I have been able to open its preferences window....

Unia · 2011-08-25 20:00:54

Downgrading VLC didn't help

lolilolicon · 2011-08-26 02:31:33

Well, my guess is it's a bug in your catalyst driver. Downgrading applications won't help. How about the open source driver xf86-video-ati?

Unia · 2011-08-26 18:44:05

lolilolicon wrote:

How about the open source driver xf86-video-ati?

Ooohh nooo Never am I going to try that monster again; it heats up my video card so bad I'm afraid it'll just eat it. According to Vi0L0, our Catalyst packager, it's a bug only AMD/ATI can solve (read here: https://bbs.archlinux.org/viewtopic.php … 6#p980546)

Fow now, the only workarounds I have found is switching applications: Chromium instead of Firefox and GNOME-mplayer instead of VLC. Haven't tested GNOME-mplayer that good yet, so I'm going to watch a movie tonight and see if it still crashes somehow.

Last edited by Unia (2011-08-26 18:44:23)

Unia · 2011-08-29 15:51:17

Well, I haven't experienced another hang up since I ditched Firefox for Chromium and VLC for GNOME-Mplayer. I guess we could consider this topic "solved" - untill I run into the issue again. I will make a new topic for that, might it happen. Thanks for the help all!

Unia · 2011-09-07 18:38:11

Today I tried Thunderbird. When I tried to start it, X crashed. Twice. I was able to start it succesfully a couple of times in between those two crashes though. When I checked, I saw that same error message as in my first post.

BUG: scheduling while atomic

Last edited by Unia (2011-09-07 18:38:25)

Arch Linux

#1 2011-08-17 15:06:04

["Solved"] Strange error message send me back to TTY

#2 2011-08-17 16:06:43

Re: ["Solved"] Strange error message send me back to TTY

#3 2011-08-17 16:59:28

Re: ["Solved"] Strange error message send me back to TTY

#4 2011-08-20 10:00:48

Re: ["Solved"] Strange error message send me back to TTY

#5 2011-08-20 19:52:33

Re: ["Solved"] Strange error message send me back to TTY

#6 2011-08-20 20:29:28

Re: ["Solved"] Strange error message send me back to TTY

#7 2011-08-20 20:39:49

Re: ["Solved"] Strange error message send me back to TTY

#8 2011-08-22 10:41:32

Re: ["Solved"] Strange error message send me back to TTY

#9 2011-08-22 10:53:08

Re: ["Solved"] Strange error message send me back to TTY

#10 2011-08-22 11:12:58

Re: ["Solved"] Strange error message send me back to TTY

#11 2011-08-22 11:36:06

Re: ["Solved"] Strange error message send me back to TTY

#12 2011-08-22 11:43:39

Re: ["Solved"] Strange error message send me back to TTY

#13 2011-08-23 13:42:55

Re: ["Solved"] Strange error message send me back to TTY

#14 2011-08-23 17:52:22

Re: ["Solved"] Strange error message send me back to TTY

#15 2011-08-23 17:58:21

Re: ["Solved"] Strange error message send me back to TTY

#16 2011-08-23 20:49:02

Re: ["Solved"] Strange error message send me back to TTY

#17 2011-08-25 20:00:54

Re: ["Solved"] Strange error message send me back to TTY

#18 2011-08-26 02:31:33

Re: ["Solved"] Strange error message send me back to TTY

#19 2011-08-26 18:44:05

Re: ["Solved"] Strange error message send me back to TTY

#20 2011-08-29 15:51:17

Re: ["Solved"] Strange error message send me back to TTY

#21 2011-09-07 18:38:11

Re: ["Solved"] Strange error message send me back to TTY

Board footer