Re: Badness in device_release at drivers/base/core.c:84

From: Diffie (diffie_at_blazebox.homeip.net)
Date: 08/03/03

  • Next message: bert hubert: "Re: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily" 
    Date:	Sun, 3 Aug 2003 17:47:55 -0400
To: Andrew Morton <akpm@osdl.org>

    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.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: bert hubert: "Re: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily"

    Relevant Pages

    • Re: BUG at mm/memory.c:1501 in 2.6.0-test5
      ... >Any module running inside the kernel can destroy anything. ... A simple bug in any ... You should send your report to the vendor. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.12-rc2-mm3
      ... > seems to be running Azareus. ... party PCI card, what video card are you using, can you reproduce the ... you are the only one to report that and none of the G5s here ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.15-rc1-mm2 unsusable on DELL Inspiron 8200, 2.6.15-rc1 works fine
      ... Many thanks for the report. ... Unfortunately your logging system is cutting out the most important info ... so don't worry if you can't track down the full Bad page state messages. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.10-mm2
      ... does this happen and when it doesn't) and will report it by then. ... /\ attachments and Software patents. ... send the line "unsubscribe linux-kernel" in ... More majordomo info at http://vger.kernel.org/majordomo-info.html ...
      (Linux-Kernel)
    • Re: journaled filesystems -- known instability; Was: XFS: inode with st_mode == 0
      ... Preferably on a hardware configuration ... I'm not interested in any report including binary drivers and to be ... I also don't care about XFS although Christoph may well do. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)