public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel GUILLET <Joel.Guillet@bull.net>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Preempt problems
Date: Wed, 05 Feb 2003 17:03:26 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805816@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805801@msgid-missing>

Hello,

I've just found a problem when using preemption patch with SMP on a
2.5.59 kernel. (with my version of the _raw_write_trylock() macro)

It seems, that the SCSI driver have some problems (at boot time):
As a result, sometimes, one of my partition (type ext3) can not be
mounted.
Here is the only related message in the log file :

Feb  5 17:54:13 zli22 kernel: scsi: Underflow detected - retrying command.


Sometimes, the partition is "half-mounted". I can only read one part of
the files. If I try to mount it again or to unmount it, I've got a message
saying that the device is busy.

		> mount /dev/sda4
		umount: /home: device is busy


It seems to me, that it is a deadlock. But it's not easy to identify it
because, it doesn't happen every time I boot the machine (about 1/2, with
my machines that have 2 cpus))

It could be a problem in the  "_raw_write_trylock()", but I have made some
tests, and it seems that the macro "returns" the good value.


---------------
> ... because the rw_lock value is composed with :
> - 1 bit for the write "flag" (the most significant bit of a _long_ value)

  Oh... I meant MSB of an _int_ value !

> - 31 bits for the read flags


Regards

---------
  Joel





  parent reply	other threads:[~2003-02-05 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 20:17 [Linux-ia64] Preempt problems Peter Chubb
2003-02-03 21:36 ` Stephane Eranian
2003-02-03 22:33 ` Peter Chubb
2003-02-03 23:43 ` David Mosberger
2003-02-05 17:03 ` Joel GUILLET [this message]
2003-02-14 20:05 ` Ray Bryant
2003-02-14 20:11 ` Stephane Eranian
2003-02-14 21:04 ` Ray Bryant

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=marc-linux-ia64-105590709805816@msgid-missing \
    --to=joel.guillet@bull.net \
    --cc=linux-ia64@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox