From: Miquel van Smoorenburg <miquels@cistron.nl>
To: Anders Henke <anders.henke@1und1.de>
Cc: FUJITA Tomonori <tomof@acm.org>,
matthew@wil.cx, jack@ucw.cz, fujita.tomonori@lab.ntt.co.jp,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
miquels@cistron.nl
Subject: Re: broken dpt_i2o in 2.6.23 (was: ext2_check_page: bad entry in directory) (fwd)
Date: Tue, 11 Dec 2007 22:53:03 +0100 [thread overview]
Message-ID: <1197409983.6288.9.camel@localhost.localdomain> (raw)
In-Reply-To: <1197384034.19679.13.camel@n2o.xs4all.nl>
On Tue, 2007-12-11 at 15:40 +0100, Miquel van Smoorenburg wrote:
> I just noticed the same bug when I tried to update a 2.6.18 server to
> 2.6.23.9 .. also tried 2.6.24-rc4. The symptom I'm seeing is that init
> segfaults, or can't be found .. anyway, driver/fs errors.
>
> In the kernel config, under "processor type and features", I disabled
> "64GB memory" support (changed to 4GB) and I also disabled "64 bit
> Memory and IO resources" and the problem went away. Do you by any chance
> happen to have those features enabled ?
>
> The dpt_i2o driver is not 64-bit clean, it happens to work with
> PAE/64-bit dma in earlier kernels but that might be by chance. Perhaps
> the different initialization ordering exposes the problem.
>
> I got the 64-bit dpt_i2o driver from Adaptec some time ago, and I have
> added 64-bit support to the 2.6.23.1 dpt_i2o driver based on that
> driver. I intended to submit it for 2.6.25 or so ... if I have some time
> later today or tomorrow I'll try that next to see if that makes a
> difference.
I just recompiled 2.6.23.9 with the 64 bit patch for dpt_i2o and now it
boots just fine.
The patch is here:
http://www.miquels.cistron.nl/linux/dpt_i2o-64bit-2.6.23.patch
It's not the final version - it needs a few cleanups before it can be
submitted, but perhaps you can test if it also works for you.
Mike.
next prev parent reply other threads:[~2007-12-11 21:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 13:03 broken dpt_i2o in 2.6.23 (was: ext2_check_page: bad entry in directory) (fwd) Jan Kara
2007-11-29 14:55 ` FUJITA Tomonori
2007-11-29 16:45 ` Anders Henke
2007-11-29 17:04 ` Matthew Wilcox
2007-11-30 13:27 ` Anders Henke
2007-11-29 17:09 ` FUJITA Tomonori
2007-11-30 10:34 ` Anders Henke
2007-12-11 14:40 ` Miquel van Smoorenburg
2007-12-11 16:07 ` broken dpt_i2o in 2.6.23 (was: ext2_check_page: bad entry indirectory) (fwd) Salyzyn, Mark
2007-12-11 16:07 ` Salyzyn, Mark
2007-12-11 21:53 ` Miquel van Smoorenburg [this message]
2007-12-12 13:25 ` Salyzyn, Mark
2007-12-12 13:25 ` Salyzyn, Mark
-- strict thread matches above, loose matches on Subject: below --
2007-12-12 10:58 broken dpt_i2o in 2.6.23 (was: ext2 check page: bad entry in directory) (fwd) Anders Henke
2007-12-12 11:38 ` Andrew Morton
2007-12-12 11:38 ` Andrew Morton
2007-12-12 13:07 ` Miquel van Smoorenburg
2007-12-12 13:43 ` Anders Henke
2007-12-12 19:16 ` Andrew Morton
2007-12-12 19:54 ` James Bottomley
2007-12-12 14:17 ` Anders Henke
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=1197409983.6288.9.camel@localhost.localdomain \
--to=miquels@cistron.nl \
--cc=anders.henke@1und1.de \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jack@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=tomof@acm.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.