mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: linux-kernel@vger.kernel.org, mathieu@newview.com
Cc: andre@linux-ide.org, dalecki@evision-ventures.com
Subject: Re: 2.4.19-pre9, IDE on Sparc, Big Disks
Date: Thu, 30 May 2002 02:09:53 +0200 (MEST)	[thread overview]
Message-ID: <UTC200205300009.g4U09ri18210.aeb@smtp.cwi.nl> (raw)

    I just pulled a copy of Marcello's tree from bk and compiled it on my sparc
    (that's a sun ultra 5). Everything went well but the IDE.
    I have a large ide disk connected to this guy (around 120GB if memory
    serves) and it used to work properly in the 2.4.17 era.
    Now when I boot, I got this:

    hdc: -612473816857182208 sectors

Well, clearly your bug is here.
This number is F7800E4F00000000 hex.
On the other hand, your disk has 240121728 sectors, which is 0E4FF780 hex.

So, someone assumed somewhere that the world is little-endian
with long the same size as int.

Precisely what happened is easiest to trace with the identify data in hand.
For example, maybe the sparc code still has to be extended to fix the
order of lba_capacity48 or so (in ide_fix_driveid).

Andries


[So, if you cannot find the culprit yourself, please give the identify data.
On some old kernel, the real, clean, identify data, as read directly from
the disk; not the stuff modified by the kernel. Maybe "cat /proc/ide/hdc/identify"
or so works.]

BTW, this fixing in-place of the driveid is a very bad idea.
Nobody should ever touch driveid. It is a read-only variable.

             reply	other threads:[~2002-05-30  0:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-30  0:09 Andries.Brouwer [this message]
2002-05-30  0:48 ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2002-05-30 12:29 Bartlomiej Zolnierkiewicz
2002-05-30 12:17 ` David S. Miller
2002-05-31  7:53 ` Andre Hedrick
2002-05-29 21:24 Mathieu Chouquet-Stringer
2002-05-30  1:59 ` David S. Miller
2002-05-30  2:42   ` Mathieu Chouquet-Stringer

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=UTC200205300009.g4U09ri18210.aeb@smtp.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=andre@linux-ide.org \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu@newview.com \
    /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

all inboxes | Powered by JetHome®