Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 11
Registered: ‎05-20-2008

ERROR FOUND IN SUPPORTSHOW

Hi , I found this errors in my supportshow switch Silkworm24000 fabos 5.3.1 , this could cause panic in my SAN ,

that mean its errors.

hda: status timeout: status=0xd0 { Busy }
Soft reset done!
hda: no DRQ after issuing WRITE
ide0: reset timed-out, status=0x80
hda: status timeout: status=0x80 { Busy }
Soft reset done!
cmd: pagebuf_daemon 1
cmd: pagebuf_daemon 1
cmd: swapper 1
cmd: swapper 1
cmd: swapper 1
cmd: swapper 1
cmd: pagebuf_daemon 1
cmd: pagebuf_daemon 1
cmd: swapper 1
cmd: kupdated 1
hda: drive not ready for command
ide0: reset timed-out, status=0x80
end_request: I/O error, dev 03:01 (hda), sector 74944
end_request: I/O error, dev 03:01 (hda), sector 74952
end_request: I/O error, dev 03:01 (hda), sector 75216
end_request: I/O error, dev 03:01 (hda), sector 75224
end_request: I/O error, dev 03:01 (hda), sector 75232
end_request: I/O error, dev 03:01 (hda), sector 75240
end_request: I/O error, dev 03:01 (hda), sector 112828


I/O error in filesystem ("ide0(3,1)") meta-data dev 0x30<2>Watchdog Exception: current process c01e9080, r1=c01ea9e0
Oops: Watchdog exception, sig: 0
NIP: C0112624 XER: 20000000 LR: C0118680 SP: C01EA9E0 REGS: c01e5f30 TRAP: 1020    Not tainted
MSR: 00021030 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = c01e9080 'swapper' Last syscall: 120
last math 00000000 last altivec 00000000
PLB0: bear= 0x00200000 acr=   0xbb000000 besr=  0x00000000

GPR00: 00000002 C01EA9E0 C01E9080 00000000 00000005 00000030 C01EAB20 C02B0000
GPR08: C0210000 00000005 00000BA0 FDFEC300 01AE395E 10095730 00000000 00000000
GPR16: 00000000 FFFA274D 00000000 C02B0000 C02B41F0 00000005 C02B0000 00000010
GPR24: 00000048 00000039 C02B0F19 C0210000 00001974 000F4033 C02B0F18 C02C0404
Call backtrace:
C01186E4 C0014C2C C0014CC4 C0014DE4 C0015140 C0015034 C0100624
C00EE2E8 C00D4DE8 C00F06B4 C00F0980 C011B04C C0124FBC C012A17C
C0126BD4 C0126FBC C0127328 C001EB8C C001A51C C001A3DC C001A01C
C00055F0 C000388C C0024DD0 C0004FA0 C0004FC8 C0001310 C02995A4
C000025C

>>NIP; c0112624 <serial_in+0x38/0x40 >    <=====
Trace; c01186e4 <serial_console_write+0xd8/0x210 >
Trace; c0014c2c <__call_console_drivers+0x60/0x80 >
Trace; c0014cc4 <_call_console_drivers+0x78/0x8c >
Trace; c0014de4 <call_console_drivers+0x10c/0x14c >
Trace; c0015140 <release_console_sem+0x64/0xe0 >
Trace; c0015034 <printk+0x19c/0x1c0 >
Trace; c0100624 <cmn_err+0xa8/0xbc >
Trace; c00ee2e8 <xfs_ioerror_alert+0x74/0x88 >
Trace; c00d4de8 <xlog_iodone+0x4c/0xe0 >
Trace; c00f06b4 <pagebuf_iodone+0x70/0xdc >
Trace; c00f0980 <_end_pagebuf_page_io+0x160/0x174 >
Trace; c011b04c <end_that_request_first+0x7c/0xf4 >
Trace; c0124fbc <ide_end_request+0x78/0xc4 >
Trace; c012a17c <default_end_request+0x10/0x20 >
Trace; c0126bd4 <start_request+0x234/0x260 >
Trace; c0126fbc <ide_do_request+0x328/0x378 >
Trace; c0127328 <ide_timer_expiry+0x1e4/0x200 >
Trace; c001eb8c <timer_bh+0x300/0x458 >
Trace; c001a51c <bh_action+0x3c/0x8c >
Trace; c001a3dc <tasklet_hi_action+0xa0/0xe0 >
Trace; c001a01c <do_softirq+0x88/0x100 >
Trace; c00055f0 <timer_interrupt+0x234/0x24c >
Trace; c000388c <ret_from_intercept+0x0/0x8 >
Trace; c0024dd0 <check_pgt_cache+0x20/0x30 >
Trace; c0004fa0 <idled+0x58/0x70 >
Trace; c0004fc8 <cpu_idle+0x10/0x24 >
Trace; c0001310 <rest_init+0x30/0x40 >
Trace; c02995a4 <start_kernel+0x168/0x17c >
Trace; c000025c <skpinv+0x1f0/0x22c >

PD Start
Section "MTRACER" not found.
pdex failed on /mnt/core_files/panic/core.pd1102375161 for MTRACER \(0\)

External Moderator
Posts: 4,780
Registered: ‎02-23-2004

Re: ERROR FOUND IN SUPPORTSHOW

All Release Notes beetwen 5.3.0 and the latest 5.3.2b don't report any Closed Defect with Supportshow.

I think this impact is caused by hardware Problem, such a Defective CF or Control Processor.

If you have a Active Maintenance Contract send the supportshow file to Brocade. 

TechHelp24

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.