From: Andrew Morton <akpm@zip.com.au>
To: Martin Dalecki <dalecki@evision-ventures.com>,
Alexander Viro <viro@math.psu.edu>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: IDE hang, partition strangeness
Date: Thu, 01 Aug 2002 23:56:10 -0700 [thread overview]
Message-ID: <3D4A2D0A.8FEF9C2A@zip.com.au> (raw)
In-Reply-To: 3D4A205A.8EBFF53A@zip.com.au
Andrew Morton wrote:
>
> Seems that the partitioning code in 2.5.30 is sending illegal LBAs
> to the IDE driver, which responds by hanging the box:
I misread this backtrace:
> #0 __lock_page (page=0xc1994ff0) at /usr/src/25/include/asm/bitops.h:136
> #1 0xc012ca43 in lock_page (page=0xc3ff1960) at filemap.c:692
> #2 0xc012dba9 in read_cache_page (mapping=0xc2f6a144, index=20010815, filler=0xc01428c0 <blkdev_readpage>,
> data=0x0) at filemap.c:1756
> #3 0xc0162d16 in read_dev_sector (bdev=0xc2f0ef20, n=160086527, p=0xc3fd7d60) at check.c:539
> #4 0xc0166bae in read_lba (bdev=0xc2f0ef20, lba=160086528, buffer=0xc2f6d200 "", count=512) at efi.c:205
> #5 0xc0166ccf in alloc_read_gpt_header (bdev=0xc2f0ef20, lba=160086527) at efi.c:277
_this_ is the lba. 160086527. It is the very last sector on the disk.
block_read_full_page() has issued a read request for the 4k block
at index 20010815, which is LBA 160086520. So the device driver
is being asked to read exactly the final eight blocks on the device.
The partitioning code seems to be OK. There seems to be a problem
reading end-of-disk.
next prev parent reply other threads:[~2002-08-02 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 6:02 IDE hang, partition strangeness Andrew Morton
2002-08-02 6:56 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-02 10:15 Petr Vandrovec
2002-08-02 17:58 ` Andrew Morton
2002-08-03 23:35 ` Marcin Dalecki
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=3D4A2D0A.8FEF9C2A@zip.com.au \
--to=akpm@zip.com.au \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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