linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Romain Francoise <romain@orebokech.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Christian Hesse <mail@earthworm.de>, linux-kernel@vger.kernel.org
Subject: Re: Thunar crashes kernel
Date: Sat, 18 Dec 2010 18:02:31 +0100	[thread overview]
Message-ID: <87y67nt3o8.fsf@elegiac.orebokech.com> (raw)
In-Reply-To: <1292646773.7406.19.camel@marge.simson.net> (Mike Galbraith's message of "Sat, 18 Dec 2010 05:32:53 +0100")

Mike Galbraith <efault@gmx.de> writes:

> Attached is a quilt tarball of what I've got plugged into 36.2
> here if you want to try it.

FWIW, I added fix_skip_clock_update.diff on top of what I was running
previously (2.6.36.2 + the two patches you posted previously and are
included in the tarball), and the WARN_ON_ONCE(test_tsk_need_resched(next));
triggers on two machines. It looks like this:

[ 2712.156085] ------------[ cut here ]------------
[ 2712.156097] WARNING: at /home/romain/tmp/linux/linux-2.6-2.6.36/debian/build/source_amd64_none/kernel/sched.c:3807 schedule+0x448/0x5f9()
[ 2712.156102] Hardware name:
[ 2712.156105] Modules linked in: authenc xfrm6_mode_tunnel xfrm4_mode_tunnel deflate zlib_deflate ctr twofish_generic twofish_x86_64 twofish_common camellia serpent blowfish cast5 des_generic xcbc rmd160 sha512_generic sha1_generic hmac crypto_null xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key ext4 jbd2 crc16 cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables coretemp acpi_cpufreq mperf loop sha256_generic aes_x86_64 aes_generic cbc dm_crypt dm_mod i915 ftdi_sio snd_hda_codec_realtek drm_kms_helper drm snd_hda_intel snd_hda_codec usbserial tpm_tis i2c_i801 tpm snd_pcsp i2c_algo_bit i2c_core rng_core tpm_bios snd_hwdep snd_pcm video psmouse parport_pc parport output snd_timer snd evdev soundcore serio_raw snd_page_alloc led_class processor button ext3 jbd mbcache raid1 md_mod sd_mod crc_t10dif ata_generic uhci_hcd thermal thermal_sys ata_piix ehci_hcd floppy r8169 usbcore mii libata scsi_mod nls_base [last unloaded: scsi_wait_scan]
[ 2712.156225] Pid: 2958, comm: tmux Not tainted 2.6.36-ore-amd64 #1
[ 2712.156229] Call Trace:
[ 2712.156236]  [<ffffffff8104487c>] ? warn_slowpath_common+0x78/0x8c
[ 2712.156242]  [<ffffffff8130e173>] ? schedule+0x448/0x5f9
[ 2712.156248]  [<ffffffff8130e719>] ? schedule_timeout+0xa0/0xd7
[ 2712.156254]  [<ffffffff81050c65>] ? process_timeout+0x0/0xb
[ 2712.156261]  [<ffffffff811192e6>] ? sys_epoll_wait+0x17f/0x267
[ 2712.156268]  [<ffffffff8103fab3>] ? default_wake_function+0x0/0xf
[ 2712.156274]  [<ffffffff81008a02>] ? system_call_fastpath+0x16/0x1b
[ 2712.156279] ---[ end trace 06ece612984887c2 ]---

On the other machine:

[ 6279.152199] Pid: 29865, comm: kworker/0:2 Tainted: P            2.6.36-ore-amd64 #1
[ 6279.152201] Call Trace:
[ 6279.152207]  [<ffffffff8104487c>] ? warn_slowpath_common+0x78/0x8c
[ 6279.152211]  [<ffffffff8130e173>] ? schedule+0x448/0x5f9
[ 6279.152215]  [<ffffffff8105a396>] ? worker_thread+0x23b/0x240
[ 6279.152218]  [<ffffffff8105a15b>] ? worker_thread+0x0/0x240
[ 6279.152221]  [<ffffffff8105a15b>] ? worker_thread+0x0/0x240
[ 6279.152225]  [<ffffffff8105d10c>] ? kthread+0x7a/0x82
[ 6279.152228]  [<ffffffff81009824>] ? kernel_thread_helper+0x4/0x10
[ 6279.152232]  [<ffffffff8105d092>] ? kthread+0x0/0x82
[ 6279.152234]  [<ffffffff81009820>] ? kernel_thread_helper+0x0/0x10
[ 6279.152237] ---[ end trace 5be61ee2b4fbcfdd ]---

  reply	other threads:[~2010-12-18 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17 23:55 Thunar crashes kernel Christian Hesse
2010-12-18  4:32 ` Mike Galbraith
2010-12-18 17:02   ` Romain Francoise [this message]
2010-12-18 18:13     ` Mike Galbraith
2010-12-20 14:36   ` Christian Hesse

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=87y67nt3o8.fsf@elegiac.orebokech.com \
    --to=romain@orebokech.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@earthworm.de \
    /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;
as well as URLs for NNTP newsgroup(s).