Re: [2.6.13-rc6-git13/sparc64]: Slab corruption (possible stack or buffer-cache corruption)

From: Tomasz Kłoczko (kloczek_at_rudy.mif.pg.gda.pl)
Date: 09/13/05

  • Next message: Christoph Hellwig: "Re: [ANNOUNCE 0/2] Serial Attached SCSI (SAS) support for the Linux kernel" 
    Date:	Tue, 13 Sep 2005 12:12:22 +0200 (CEST)
To: "David S. Miller" <davem@davemloft.net>

    On Mon, 12 Sep 2005, David S. Miller wrote:

    > From: Tomasz Kłoczko <kloczek@rudy.mif.pg.gda.pl>
    > Date: Mon, 12 Sep 2005 16:37:04 +0200 (CEST)
    >
    >> On first it looks like stack or buffer-cache corruption.
    >>
    >> Slab corruption: (Not tainted) start=fffff8005d9be708, len=808
    >> Redzone: 0x5a2cf071/0x5a2cf071.
    >> Last user: [destroy_inode+100/144](destroy_inode+0x64/0x90)
    >> Call Trace:
    >> [00000000004759f4] free_block+0x160/0x1b4
    >> [0000000000475bb8] cache_flusharray+0x98/0x128
    >> [0000000000475704] kmem_cache_free+0x68/0x94
    >> [00000000004a56c4] destroy_inode+0x64/0x90
    >
    > One way for destroy_inode() to be called twice on the same
    > inode would be if atomic_dec_and_test() was buggy in some way.
    > I think it might be on sparc64.
    >
    > Therefore, would you mind giving this patch a test?

    I will. Thanks.

    Dave I have next thing.
    In kernel 2.6.13-rc6-git13 I observe relative very intensive emmiting some
    kernel messages. From yesterday logs:

    # grep "^Sep 12" /var/log/messages | grep kernel: | uniq | cut -d " " -f 6- | sort | uniq -c | sort -n | tail -n 2
         509 svc: bad direction 268435456, dropping request
         653 eth0: Happy Meal out of receive descriptors, packet dropped.

    As you see one of this two messagess occures avarange one time per ~two
    minutes.
    Second looks like some error in sunhme.c. eth0 it is:

    0001:00:01.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal (rev 01)

    kloczek 

    -- 
-----------------------------------------------------------
*Ludzie nie mają problemów, tylko sobie sami je stwarzają*
-----------------------------------------------------------
Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.pl*
-
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: Christoph Hellwig: "Re: [ANNOUNCE 0/2] Serial Attached SCSI (SAS) support for the Linux kernel"

    Relevant Pages

    • Re: Kernel 2.6.9 Multiple Page Allocation Failures (Part 2)
      ... > This should be harmless as Andrew said - it would be helpful if you could ... still swapping a bit but no kernel messages on this, ... No, sorry to give you this impression, 2.6.7 is just what some of my collegues ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Kernel 2.6.9 Multiple Page Allocation Failures
      ... > Adam Radford from this list and i would like to see it run stable for about a ... > still swapping a bit but no kernel messages on this, ... We will have more information on the free areas state when the allocation ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: unsafe printk
      ... So one day root is using grep on ... Sanitizing kernel messages would be good start, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [patch] __block_write_full_page bug
      ... >> It seems that more than one request would be submitted for a given bh ... the bug is that end_buffer_async_write first does ... Or did you mean *how* is it being run twice? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.7-mm3 [broken serial console and Kernel BUG on dual Opteron]
      ... On Monday 28 of June 2004 09:19, Andrew Morton wrote: ... attached log) while tty0 gets only kernel messages ("normally" it worked in ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)