On Thu, 25 Dec 2008 01:06:06 -0700
Grant Grundler <grundler@xxxxxxxxxxxxxxxx> wrote:
> [ 1589.466507] Badness at fs/buffer.c:1186
>
> Technically, this isn't a panic. This is a "WARN_ON".
> I didn't see any panic's after that either.
Yes sorry. The system is still usable after the WARN_ON occurs. So no
panic.
Because of this, wouldn't it be a good idea to commit Kyle's patch ?
To me it seems better to have a running system with failure messages
being log rather than an ugly and barely understandable HPMC.
> The file system warning us that the sata disk it was
> talking failed an IO.
>
> However, this is likely to be some other issue with the SATA
> controller. Can you post more details about the config?
> o "lspci -v"
> o hdparm -i /dev/sd<X>
Here it is :
01:04.0 Mass storage controller: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 02)
Subsystem: Silicon Image, Inc. SiI 3112 SATALink Controller
Flags: bus master, 66MHz, medium devsel, latency 240, IRQ 21
I/O ports at 12400 [size=8]
I/O ports at 12300 [size=4]
I/O ports at 12200 [size=8]
I/O ports at 12100 [size=4]
I/O ports at 12000 [size=16]
Memory at fb807000 (32-bit, non-prefetchable) [size=512]
Expansion ROM at fb880000 [disabled] [size=512K]
Capabilities: [60] Power Management version 2
Kernel modules: sata_sil
/dev/sdc:
Model=WDC WD5000AAKS-00TMA0 , FwRev=12.01C01, SerialNo= WD-WMAPW1390228
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=?0?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 udma6
AdvancedPM=no WriteCache=disabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
I'd like to add that I've been using the exact same card and hard drive on one of my x86 box for month without any issue.
Also I've reproduce the problem again and this time I've had this message right before the "end_request" line :
[ 163.039983] timer_interrupt(CPU 0): delayed! cycles EB5EE1E6 rem 36AE6 next/now 706F7328/5BCE550E
Anything else I can do/provide to troubleshoot this ?
Cheers,
Guy
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
