public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jens Axboe <axboe@suse.de>
Subject: Re: ide timer trbl ...
Date: Mon, 11 Mar 2002 20:53:58 +0100	[thread overview]
Message-ID: <3C8D0B56.7090505@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0202231238060.1449-100000@blue1.dev.mcafeelabs.com>

Davide Libenzi wrote:
> You guys probably already know but i'm still having problems with the ide
> timer in 2.5.5 :
> 
> hda: ide_set_handler: handler not null; old=c01c5e10, new=c01c5e10
> bug: kernel timer added twice at c01c7293.
> NFS: NFSv3 not supported.
> nfs warning: mount version older than kernel
> hda: ide_set_handler: handler not null; old=c01c5e10, new=c01c5e10
> bug: kernel timer added twice at c01c7293.

Hugh?

It would be helpfull if you could send me the System.map
corresponding to that, since this could make it clear
which particular timer function is involved.

lspci -v
hdparm -i /dev/hda

and so one are usefull as well of course.

I was already tempted to replace the above check by a BUG()...

Would you mind as well to just apply ide-clean-18 and ide-clean-19
on top of each other and recheck?



  parent reply	other threads:[~2002-03-11 19:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23 20:42 ide timer trbl Davide Libenzi
2002-02-24  4:48 ` Andre Hedrick
2002-03-11 19:53 ` Martin Dalecki [this message]
2002-03-11 20:15   ` Alan Cox
2002-03-11 20:12     ` Martin Dalecki
2002-03-11 20:31       ` Alan Cox
2002-03-12 14:21         ` Zwane Mwaikambo
2002-04-04 19:50           ` Mike Fedyk
2002-04-05  5:26             ` Andre Hedrick
2002-04-05 18:07               ` Mike Fedyk
2002-03-11 21:09   ` Davide Libenzi

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=3C8D0B56.7090505@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=axboe@suse.de \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@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