Messages in this thread | | | Date | Sun, 3 Aug 2003 17:47:55 -0400 | From | Diffie <> | Subject | Re: Badness in device_release at drivers/base/core.c:84 |
| |
On Sat, Aug 02, 2003 at 07:07:37PM -0700, Andrew Morton wrote: > Diffie <diffie@blazebox.homeip.net> wrote: > > > > After applaying the above patch and testing it still oopses the kernel. > > > > I noticed same patch in today's mm3 which i compiled and use right now. > > > > When using cat /proc/scsi/aic7xxx/0 i get segmentation fault and oops > > which i'll attach to this email. > > > > ... > > > > EIP is at aic7xxx_proc_info+0xc28/0xc80 > > This is crashing in a different place. Probably the same bug, showing up > later on. > > I don't know if anyone is maintaining aic7xxx_old in 2.7. It looks like it > was subject to some random untested change a couple of months back. > > >
Hi Andrew,
I think this bug is due to me using the aic7xxx_old code ver 5.x.x.
Under kernel 2.4.21 the aic7xxx (new) is ver 6.2.8 and it works great with Adaptec AHA-2940U2W controller i have.
On 2.6.0-test2-mm3 (tried Linus test1,test2,mm1 and mm2) the NEW aic7xxx uses ver 6.2.35 and will not scan my IBM drive even though it initializes the correct SCSI ID,LUN etc...
I would like to contact and report this issue to the aic7xxx maintaner and perhaps get it resolved.Where would be the best place to report this kind of problem?
I have taken few screen captures which are available at: http://www.blazebox.homeip.net:81/diffie/images/2.6.0-test2/ and show the aic7xxx (new) failure.
Regards,
Paul B.
[unhandled content-type:application/pgp-signature] | |