[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <40a4ed591003110534k1ab9c343r35ac45f64476bdc6@mail.gmail.com>
Date: Thu, 11 Mar 2010 14:34:22 +0100
From: Zeno Davatz <zdavatz@...il.com>
To: linux-kernel@...r.kernel.org
Subject: kmemleak: 17 new suspected memory leaks
This may or may not be connected to the ata-timeout issue but it is in
the same place in my dmesg:
kmemleak: 17 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
See attached file for all of the 17 issues.
Let me know if you need any other information.
kmemleak: 17 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
ata1: clearing spurious IRQ
ata1: lost interrupt (Status 0x50)
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:9d:24:68/00:00:00:00:00/ea tag 0 dma 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1.00: configured for UDMA/133
ata1.00: device reported invalid CHS sector 0
ata1: EH complete
ata1: clearing spurious IRQ
ata1: lost interrupt (Status 0x50)
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:08:3d:7f:10/00:00:00:00:00/e5 tag 0 dma 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1.00: configured for UDMA/133
ata1.00: device reported invalid CHS sector 0
ata1: EH complete
Best
Zeno
Download attachment "kmemleak" of type "application/octet-stream" (15159 bytes)
Powered by blists - more mailing lists