All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jan Kara <jack@suse.cz>, Jeff Moyer <jmoyer@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
	Jens Axboe <jaxboe@fusionio.com>,
	mgalbraith@suse.com
Subject: Re: Deadlocks due to per-process plugging
Date: Mon, 16 Jul 2012 16:35:40 +0200	[thread overview]
Message-ID: <1342449340.7659.69.camel@marge.simpson.net> (raw)
In-Reply-To: <1342437873.7659.60.camel@marge.simpson.net>

On Mon, 2012-07-16 at 13:24 +0200, Mike Galbraith wrote:

> Box disagrees.
> 
> Waiting for device /dev/cciss/c0d0p6 to appear:  ok
> fsck from util-linux 2.19.1
> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/cciss/c0d0p6 
> SLES11: clean, 141001/305824 files, 1053733/1222940 blocks
> fsck succeeded. Mounting root device read-write.
> Mounting root /dev/cciss/c0d0p6
> mount -o rw,acl,user_xattr -t [   27.558934] jbd: disagrees about
> version of symbol rt_spin_trylock
> ext3 /dev/cciss/[   27.558938] jbd: Unknown symbol rt_spin_trylock (err
> -22)
> c0d0p6 /root
> [   27.558959] jbd: disagrees about version of symbol
> __rt_spin_lock_init
> [   27.558961] jbd: Unknown symbol __rt_spin_lock_init (err -22)
> [   27.558986] jbd: disagrees about version of symbol rt_spin_unlock
> [   27.558988] jbd: Unknown symbol rt_spin_unlock (err -22)
> [   27.558990] jbd: disagrees about version of symbol rt_spin_lock
> [   27.558992] jbd: Unknown symbol rt_spin_lock (err -22)
> [   27.559004] jbd: disagrees about version of symbol __rt_mutex_init
> [   27.559006] jbd: Unknown symbol __rt_mutex_init (err -22)
> modprobe: FATAL: Error inserting ext3
> (/lib/modules/3.0.35-rt56-rt/extra/ext3.ko): Invalid argument
> 
> mount: unknown filesystem type 'ext3'
> could not mount root filesystem -- exiting to /bin/sh
> $

Weird.  Make mrproper didn't help.  Whacking every trace that the damn
tree, kernel and modules ever existed did.  Box is grinding away at ext3
dbench testcase.  At 7 hours per run, it'll take a while.  This time
tomorrow box should still be happily grinding away.

-Mike


  reply	other threads:[~2012-07-16 15:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 13:37 Deadlocks due to per-process plugging Jan Kara
2012-07-11 16:05 ` Jeff Moyer
2012-07-11 20:16   ` Jan Kara
2012-07-11 22:12     ` Thomas Gleixner
2012-07-12  4:12       ` Mike Galbraith
2012-07-13 12:38       ` Jan Kara
2012-07-12  2:07     ` Mike Galbraith
2012-07-12 14:15     ` Thomas Gleixner
2012-07-13 12:33       ` Jan Kara
2012-07-13 14:25         ` Thomas Gleixner
2012-07-13 14:46           ` Jan Kara
2012-07-15  8:59             ` Thomas Gleixner
2012-07-15  9:14               ` Mike Galbraith
2012-07-15  9:51                 ` Thomas Gleixner
2012-07-16  2:22                 ` Mike Galbraith
2012-07-16  8:59                   ` Thomas Gleixner
2012-07-16  9:48                     ` Mike Galbraith
2012-07-16  9:59                       ` Thomas Gleixner
2012-07-16 10:13                         ` Mike Galbraith
2012-07-16 10:08                       ` Mike Galbraith
2012-07-16 10:19                         ` Thomas Gleixner
2012-07-16 10:30                           ` Mike Galbraith
2012-07-16 11:24                           ` Mike Galbraith
2012-07-16 14:35                             ` Mike Galbraith [this message]
2012-07-17 13:10                           ` Mike Galbraith
2012-07-18  4:44                             ` Mike Galbraith
2012-07-18  5:30                               ` Mike Galbraith
2012-07-21  7:47                                 ` Mike Galbraith
2012-07-22 18:43                                   ` Mike Galbraith
2012-07-23  9:46                                     ` Mike Galbraith
2012-07-14 11:00           ` Mike Galbraith
2012-07-14 11:06             ` Mike Galbraith
2012-07-15  7:14             ` Mike Galbraith

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=1342449340.7659.69.camel@marge.simpson.net \
    --to=efault@gmx.de \
    --cc=jack@suse.cz \
    --cc=jaxboe@fusionio.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgalbraith@suse.com \
    --cc=tglx@linutronix.de \
    --cc=tj@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 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.