On Fri, 2007-11-30 at 11:34 +0100, Anders Henke wrote: > Am 30.11.2007 schrieb FUJITA Tomonori: > > > > > According to the 2.6.23-rc1 short-form changelog, there is > > > > > one major edit on the dpt_i2o driver: > > > > > > > > > > FUJITA Tomonori > > > > > > > > > > [SCSI] dpt_i2o: convert to use the data buffer accessors > > > > > > > > > > Stephen Rothwell > > > > > dpt_i2o depends on virt_to_bus > > > > > > > > > > Fujita, would you please take a look at this? > > > > > > In between, I've ruled out that the static assignment isn't > source of the problem. And due to some manually made "make clean" which > didn't clean enough, I've also pointed out the wrong patch - sorry, > Fujita, definitely the right one which breaks my boxes is the dpt_i2o patch > from 2.6.23-rc2 to 2.6.23-rc3 (7 kb in Size) from Matthew Wilcox. > > commit 55d9fcf57ba5ec427544fca7abc335cf3da78160 > Author: Matthew Wilcox <matthew@xxxxxx> > Date: Mon Jul 30 15:19:18 2007 -0600 > > [SCSI] dpt_i2o: convert to SCSI hotplug model 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. Mike. - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
