* need fusion driver guide
@ 2009-01-06 21:45 Sam Ravnborg
2009-01-06 21:50 ` James Bottomley
0 siblings, 1 reply; 5+ messages in thread
From: Sam Ravnborg @ 2009-01-06 21:45 UTC (permalink / raw)
To: LKML, linux linux, linux-scsi
[I forward this mail on request of Tina as her
mails to lkml are lost somehow. /Sam ]
Hi ,
I am new in scsi fusion driver code.
i got some error in fusion driver. But i do not understand how fusion and
scsi are working in kernel.
can anyone please let me know wher i can get much info about this.
Thanks
Tina
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: need fusion driver guide
2009-01-06 21:45 need fusion driver guide Sam Ravnborg
@ 2009-01-06 21:50 ` James Bottomley
[not found] ` <e7b7bf130901062002ke59c0dkd7ca0ed73352066f@mail.gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: James Bottomley @ 2009-01-06 21:50 UTC (permalink / raw)
To: Sam Ravnborg; +Cc: LKML, linux linux, linux-scsi
On Tue, 2009-01-06 at 22:45 +0100, Sam Ravnborg wrote:
> [I forward this mail on request of Tina as her
> mails to lkml are lost somehow. /Sam ]
Best guess would be non plain text (i.e. having html components). vger
is pretty keen on eating those as part of its spam filtering.
> I am new in scsi fusion driver code.
> i got some error in fusion driver. But i do not understand how fusion and
> scsi are working in kernel.
> can anyone please let me know wher i can get much info about this.
The best docs we have is the source. LSI can provide the reference
manuals under NDA.
James
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: need fusion driver guide
[not found] ` <e7b7bf130901062002ke59c0dkd7ca0ed73352066f@mail.gmail.com>
@ 2009-01-07 4:21 ` James Bottomley
2009-01-07 5:24 ` linux linux
0 siblings, 1 reply; 5+ messages in thread
From: James Bottomley @ 2009-01-07 4:21 UTC (permalink / raw)
To: linux linux; +Cc: Sam Ravnborg, LKML, linux-scsi
You still need to turn off html email attachments, otherwise your
messages won't be accepted by the mailing lists. It will be an option
like recipient wants text/plain only or something.
On Wed, 2009-01-07 at 09:32 +0530, linux linux wrote:
> Hi,
>
> Sam many thanks for ur help.
>
> Hi James,
>
> I am getting some error on for fusion device driver.
> The error message look like this
>
>
> 2F240F4C226078: 19/12/2008 EST 04:42:45, mptscsih: ioc1: >>
> Attempting task abort! (sc=e40df080)
> 2F240F6E8C2E00: 19/12/2008 EST 04:42:45, mptbase: ioc1:
> IOCStatus(0x0048): SCSI Task Terminated
> 2F240F6E905A98: 19/12/2008 EST 04:42:45, mptscsih: ioc1: >>
> Attempting task abort! (sc=f7e23680)
>
> 2F24117BDA2438: 19/12/2008 EST 04:42:50, mptscsih: ioc1: >>
> Attempting bus reset! (sc=e40df080)
>
> After then the server has been rebooted.
>
> I can see the code is written inside /drivers/message/fussion/
> mptscsih.c
> The responsible function is
> mptscsih_host_reset()
> i am very new in SCSI fusion device driver. read some help guide from
> google but still i do not understand when the mptscsih_host_reset() is
> called by kernel. I normal situation i am not able to see this message
> in kernel log.
> Can any one help me to understand when these type of kernel message
> are comming, is it foe SCSI hardware problem ?
> when mptscsih_host_reset() will be executed?
It looks like a standard error handling escalation sequence. Why is
very hard to tell without the entire kernel log. Why there wasn't a
recovery is also not clear.
> Only one time i show this message in my kernel log, is there any way
> to reproduce this message manually?
>
> where i get much info regarding this issue and SCSI fusion kernel
> driver except kernel code itself?
>
> I am writting this after reading help doc from
> http://www.lsi.com/insight_center/tech_trends/advanced_architectures/fusionmpt/index.html
>
> But still i am very few knowledge to solve it.
>
> waiting for your help.
There's not much else I can do. If you post the entire kernel log, the
fusion people hang out on this list and might see something that
indicates what the problem is.
James
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: need fusion driver guide
2009-01-07 4:21 ` James Bottomley
@ 2009-01-07 5:24 ` linux linux
2009-01-12 16:13 ` linux linux
0 siblings, 1 reply; 5+ messages in thread
From: linux linux @ 2009-01-07 5:24 UTC (permalink / raw)
To: James Bottomley; +Cc: Sam Ravnborg, LKML, linux-scsi
[-- Attachment #1: Type: text/plain, Size: 2602 bytes --]
Hi James,.
Now it should be received by all...
Many many thanks for the help.
I am sending the kernel log.
On Wed, Jan 7, 2009 at 9:51 AM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>
> You still need to turn off html email attachments, otherwise your
> messages won't be accepted by the mailing lists. It will be an option
> like recipient wants text/plain only or something.
>
> On Wed, 2009-01-07 at 09:32 +0530, linux linux wrote:
> > Hi,
> >
> > Sam many thanks for ur help.
> >
> > Hi James,
> >
> > I am getting some error on for fusion device driver.
> > The error message look like this
> >
> >
> > 2F240F4C226078: 19/12/2008 EST 04:42:45, mptscsih: ioc1: >>
> > Attempting task abort! (sc=e40df080)
> > 2F240F6E8C2E00: 19/12/2008 EST 04:42:45, mptbase: ioc1:
> > IOCStatus(0x0048): SCSI Task Terminated
> > 2F240F6E905A98: 19/12/2008 EST 04:42:45, mptscsih: ioc1: >>
> > Attempting task abort! (sc=f7e23680)
> >
> > 2F24117BDA2438: 19/12/2008 EST 04:42:50, mptscsih: ioc1: >>
> > Attempting bus reset! (sc=e40df080)
> >
> > After then the server has been rebooted.
> >
> > I can see the code is written inside /drivers/message/fussion/
> > mptscsih.c
> > The responsible function is
> > mptscsih_host_reset()
> > i am very new in SCSI fusion device driver. read some help guide from
> > google but still i do not understand when the mptscsih_host_reset() is
> > called by kernel. I normal situation i am not able to see this message
> > in kernel log.
> > Can any one help me to understand when these type of kernel message
> > are comming, is it foe SCSI hardware problem ?
> > when mptscsih_host_reset() will be executed?
>
> It looks like a standard error handling escalation sequence. Why is
> very hard to tell without the entire kernel log. Why there wasn't a
> recovery is also not clear.
>
Pls let me know when this kind of error handler is happened?
is it for SCSI hard ware failure?
> > Only one time i show this message in my kernel log, is there any way
> > to reproduce this message manually?
> >
> > where i get much info regarding this issue and SCSI fusion kernel
> > driver except kernel code itself?
> >
> > I am writting this after reading help doc from
> > http://www.lsi.com/insight_center/tech_trends/advanced_architectures/fusionmpt/index.html
> >
> > But still i am very few knowledge to solve it.
> >
> > waiting for your help.
>
> There's not much else I can do. If you post the entire kernel log, the
> fusion people hang out on this list and might see something that
> indicates what the problem is.
>
> James
>
>
[-- Attachment #2: kernel-log.txt --]
[-- Type: text/plain, Size: 15067 bytes --]
2F208F0FE68D48: 19/12/2008 EST 04:10:34, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F2091ADF0D244: 19/12/2008 EST 04:10:40, printk: 737 messages suppressed.
2F2091AE01533C: 19/12/2008 EST 04:10:40, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F2093E42737B4: 19/12/2008 EST 04:10:44, printk: 60 messages suppressed.
2F2093E4414034: 19/12/2008 EST 04:10:44, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F209624B6C4B0: 19/12/2008 EST 04:10:49, printk: 78 messages suppressed.
2F209624BBEFC0: 19/12/2008 EST 04:10:49, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F20985B9DFFDC: 19/12/2008 EST 04:10:54, printk: 82 messages suppressed.
2F20985BA31D64: 19/12/2008 EST 04:10:54, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F209BD0698814: 19/12/2008 EST 04:11:01, printk: 299 messages suppressed.
2F209BD074E5A0: 19/12/2008 EST 04:11:01, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F209D24C4FF48: 19/12/2008 EST 04:11:04, printk: 52 messages suppressed.
2F209D24CC65EC: 19/12/2008 EST 04:11:04, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F209F4DEB39C0: 19/12/2008 EST 04:11:09, printk: 78 messages suppressed.
2F209F4DF6DFB4: 19/12/2008 EST 04:11:09, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F20A1A4EB7DA2: 19/12/2008 EST 04:11:14, printk: 62 messages suppressed.
2F20A1A5031CBE: 19/12/2008 EST 04:11:14, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F210BF8DE0658: 19/12/2008 EST 04:15:03, mounting FS type nfs on
/export_monitor/tftpboot_retry
2F210BF8E769AC: 19/12/2008 EST 04:15:03, nfs warning: mount version older
than kernel
2F210C3E7F4102: 19/12/2008 EST 04:15:04, unmounting
/export_monitor/tftpboot_retry
2F212B900C68F4: 19/12/2008 EST 04:16:11, procmon_ForceProcessRestart:
procmon.c(505): PROCMON running init_program /etc/init.d/sysconfigspyd
restart &
2F212B9E9C0818: 19/12/2008 EST 04:16:11, telinit called by pid 25272,
cmdline /sbin/telinitq
2F212BA0F73AE2: 19/12/2008 EST 04:16:11, 25272 (/sbin/telinit q ) called by
2F212BA391D06E: 19/12/2008 EST 04:16:11, 25238 (/bin/sh
/etc/init.d/sysconfigspyd restart ) called by
2F212BA3A10C32: 19/12/2008 EST 04:16:11, 1 (init)
2F212BBB1BF9E0: 19/12/2008 EST 04:16:11, telinit called by pid 25322,
cmdline /sbin/telinitq
2F212BBCF08DAC: 19/12/2008 EST 04:16:11, 25322 (/sbin/telinit q ) called by
2F212BBEDE50A4: 19/12/2008 EST 04:16:11, 25238 (/bin/sh
/etc/init.d/sysconfigspyd restart ) called by
2F212BBEEAA9E4: 19/12/2008 EST 04:16:11, 1 (init)
2F219717D77D32: 19/12/2008 EST 04:20:03, mounting FS type nfs on
/export_monitor/tftpboot_retry
2F219717E16562: 19/12/2008 EST 04:20:03, nfs warning: mount version older
than kernel
2F21974930017E: 19/12/2008 EST 04:20:03, unmounting
/export_monitor/tftpboot_retry
2F21A7BE6DF116: 19/12/2008 EST 04:20:39, printk: 27 messages suppressed.
2F21A7BE71D61A: 19/12/2008 EST 04:20:39, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F21A7BE9313EA: 19/12/2008 EST 04:20:39, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F21A7BEA7E096: 19/12/2008 EST 04:20:39, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F21A7BEC5CEFA: 19/12/2008 EST 04:20:39, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F21A7BED3852A: 19/12/2008 EST 04:20:39, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F21A7BEF364A2: 19/12/2008 EST 04:20:39, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F21A7BF01C6AA: 19/12/2008 EST 04:20:39, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F21A7BF1F69FA: 19/12/2008 EST 04:20:39, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F21A7BF323B2E: 19/12/2008 EST 04:20:39, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F21A7BF4F286A: 19/12/2008 EST 04:20:39, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F21AA26683C34: 19/12/2008 EST 04:20:44, printk: 717 messages suppressed.
2F21AA266DE2EC: 19/12/2008 EST 04:20:44, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F21ACCED5CFF4: 19/12/2008 EST 04:20:50, printk: 58 messages suppressed.
2F21ACCEDB05A4: 19/12/2008 EST 04:20:50, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F2226E6651E0C: 19/12/2008 EST 04:25:13, mounting FS type nfs on
/export_monitor/tftpboot_retry
2F2226E66E6170: 19/12/2008 EST 04:25:13, nfs warning: mount version older
than kernel
2F222717C1AEDA: 19/12/2008 EST 04:25:13, unmounting
/export_monitor/tftpboot_retry
2F22ADB5065EDA: 19/12/2008 EST 04:30:03, mounting FS type nfs on
/export_monitor/tftpboot_retry
2F22ADB50D8AB6: 19/12/2008 EST 04:30:03, nfs warning: mount version older
than kernel
2F22ADE97C0BE8: 19/12/2008 EST 04:30:04, unmounting
/export_monitor/tftpboot_retry
2F22C051D4D240: 19/12/2008 EST 04:30:43, printk: 62 messages suppressed.
2F22C051DC7290: 19/12/2008 EST 04:30:43, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F22C052045530: 19/12/2008 EST 04:30:43, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F22C052165984: 19/12/2008 EST 04:30:43, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F22C0523D40AC: 19/12/2008 EST 04:30:43, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F22C05250AE04: 19/12/2008 EST 04:30:43, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F22C052771F18: 19/12/2008 EST 04:30:43, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F22C0528896AC: 19/12/2008 EST 04:30:43, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F22C052ADA68C: 19/12/2008 EST 04:30:43, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F22C052C08364: 19/12/2008 EST 04:30:43, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F22C052E5E3E4: 19/12/2008 EST 04:30:43, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F22C46FBDD138: 19/12/2008 EST 04:30:52, printk: 712 messages suppressed.
2F22C46FC2D834: 19/12/2008 EST 04:30:52, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F22C5121D72B8: 19/12/2008 EST 04:30:53, printk: 5 messages suppressed.
2F22C51223D918: 19/12/2008 EST 04:30:53, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F22C7832C1810: 19/12/2008 EST 04:30:59, printk: 132 messages suppressed.
2F22C783327374: 19/12/2008 EST 04:30:59, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F22C9A9489D74: 19/12/2008 EST 04:31:03, printk: 98 messages suppressed.
2F22C9A950DDD4: 19/12/2008 EST 04:31:03, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F22CF8C370334: 19/12/2008 EST 04:31:16, printk: 344 messages suppressed.
2F22CF8C407DEC: 19/12/2008 EST 04:31:16, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F22CF8C6B2A14: 19/12/2008 EST 04:31:16, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F22D09C4465E4: 19/12/2008 EST 04:31:18, printk: 33 messages suppressed.
2F22D09C5ECE20: 19/12/2008 EST 04:31:18, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F22D2F2B75F2C: 19/12/2008 EST 04:31:23, printk: 134 messages suppressed.
2F22D2F2C146D8: 19/12/2008 EST 04:31:23, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F22D536A148A4: 19/12/2008 EST 04:31:28, printk: 90 messages suppressed.
2F22D536A7D998: 19/12/2008 EST 04:31:28, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F23391668B6CA: 19/12/2008 EST 04:35:03, mounting FS type nfs on
/export_monitor/tftpboot_retry
2F23391671CE56: 19/12/2008 EST 04:35:03, nfs warning: mount version older
than kernel
2F23393CD8FEE6: 19/12/2008 EST 04:35:04, unmounting
/export_monitor/tftpboot_retry
2F23C3FC940EE8: 19/12/2008 EST 04:40:03, mounting FS type nfs on
/export_monitor/tftpboot_retry
2F23C3FC9A06C8: 19/12/2008 EST 04:40:03, nfs warning: mount version older
than kernel
2F23C42D9CE5F8: 19/12/2008 EST 04:40:03, unmounting
/export_monitor/tftpboot_retry
2F23D952D43CB0: 19/12/2008 EST 04:40:49, printk: 16 messages suppressed.
2F23D952DA8B30: 19/12/2008 EST 04:40:49, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F23D952FC08DC: 19/12/2008 EST 04:40:49, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F23D9530E03C0: 19/12/2008 EST 04:40:49, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F23D9532BDDC8: 19/12/2008 EST 04:40:49, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F23D9533AA534: 19/12/2008 EST 04:40:49, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F23D9535760DC: 19/12/2008 EST 04:40:49, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F23D95368ACBC: 19/12/2008 EST 04:40:49, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F23D95386FB9C: 19/12/2008 EST 04:40:49, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F23D953958EA4: 19/12/2008 EST 04:40:49, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F23D953B31B94: 19/12/2008 EST 04:40:49, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F23DCEABF9A9C: 19/12/2008 EST 04:40:56, printk: 710 messages suppressed.
2F23DCEAC5036C: 19/12/2008 EST 04:40:56, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F23DE288918E0: 19/12/2008 EST 04:40:59, printk: 37 messages suppressed.
2F23DE288F926C: 19/12/2008 EST 04:40:59, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F23E061375DD4: 19/12/2008 EST 04:41:04, printk: 72 messages suppressed.
2F23E0613E8178: 19/12/2008 EST 04:41:04, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F23E4DB11D744: 19/12/2008 EST 04:41:13, printk: 338 messages suppressed.
2F23E4DB16EAA8: 19/12/2008 EST 04:41:13, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F23E51A344828: 19/12/2008 EST 04:41:14, printk: 4 messages suppressed.
2F23E51A4081A8: 19/12/2008 EST 04:41:14, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F23E740145B00: 19/12/2008 EST 04:41:19, printk: 104 messages suppressed.
2F23E7401BCBA8: 19/12/2008 EST 04:41:19, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F23E9AC484680: 19/12/2008 EST 04:41:24, printk: 202 messages suppressed.
2F23E9AC629270: 19/12/2008 EST 04:41:24, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F23EBF044C64A: 19/12/2008 EST 04:41:29, printk: 68 messages suppressed.
2F23EBF054744E: 19/12/2008 EST 04:41:29, sysmtc(24253) unable to deliver
event "MTC.00140017" to hwInvSystemInvM(22577), rx queue full
2F240F4C226078: 19/12/2008 EST 04:42:45, mptscsih: ioc1: >> Attempting task
abort! (sc=e40df080)
2F240F6E8C2E00: 19/12/2008 EST 04:42:45, mptbase: ioc1: IOCStatus(0x0048):
SCSI Task Terminated
2F240F6E905A98: 19/12/2008 EST 04:42:45, mptscsih: ioc1: >> Attempting task
abort! (sc=f7e23680)
2F24105C36E74C: 19/12/2008 EST 04:42:47, mptbase: Initiating ioc1 recovery
2F24117BDA2438: 19/12/2008 EST 04:42:50, mptscsih: ioc1: >> Attempting bus
reset! (sc=e40df080)
2F241240D3B8D8: 19/12/2008 EST 04:42:51, nfs: server base-unit1 not
responding, still trying
2F2413E3A894F8: 19/12/2008 EST 04:42:55, printk: 11 messages suppressed.
2F2413E3AC42AC: 19/12/2008 EST 04:42:55, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F2413E3B89754: 19/12/2008 EST 04:42:55, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F2413E3DC1260: 19/12/2008 EST 04:42:55, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F2413E3E6D38C: 19/12/2008 EST 04:42:55, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F2413F02F5210: 19/12/2008 EST 04:42:55, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F2413F03A0F68: 19/12/2008 EST 04:42:55, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F2413F06B418C: 19/12/2008 EST 04:42:55, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F2413F076E9B0: 19/12/2008 EST 04:42:55, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F24140CFDE420: 19/12/2008 EST 04:42:55, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F24140D08ED80: 19/12/2008 EST 04:42:55, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F24166A2CDA28: 19/12/2008 EST 04:43:00, printk: 67 messages suppressed.
2F24166A30A9B0: 19/12/2008 EST 04:43:00, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F2418884BF858: 19/12/2008 EST 04:43:05, printk: 72 messages suppressed.
2F2418884FB548: 19/12/2008 EST 04:43:05, sysmtc(24253) unable to deliver
event "MTC.00140016" to hwInvSystemInvM(22577), rx queue full
2F2428B06C6964: 19/12/2008 EST 04:43:40, mptscsih: ioc1: >> Attempting host
reset! (sc=e40df080)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: need fusion driver guide
2009-01-07 5:24 ` linux linux
@ 2009-01-12 16:13 ` linux linux
0 siblings, 0 replies; 5+ messages in thread
From: linux linux @ 2009-01-12 16:13 UTC (permalink / raw)
To: James Bottomley; +Cc: Sam Ravnborg, LKML, linux-scsi
HI James,
I got some idea about fusion driver from this link
http://bugzilla.kernel.org/show_bug.cgi?id=12195
And i found there is bug in fusion driver (kernel version 2.6.10) from this link
http://www.nabble.com/MPT-fusion-driver,-better-but-still-buggy-at-errors-handling-under-2.6-td1095505.html
On Wed, Jan 7, 2009 at 10:54 AM, linux linux <linux.tina@gmail.com> wrote:
> Hi James,.
> Now it should be received by all...
> Many many thanks for the help.
>
> I am sending the kernel log.
>
>
> On Wed, Jan 7, 2009 at 9:51 AM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
>>
>> You still need to turn off html email attachments, otherwise your
>> messages won't be accepted by the mailing lists. It will be an option
>> like recipient wants text/plain only or something.
>>
>> On Wed, 2009-01-07 at 09:32 +0530, linux linux wrote:
>> > Hi,
>> >
>> > Sam many thanks for ur help.
>> >
>> > Hi James,
>> >
>> > I am getting some error on for fusion device driver.
>> > The error message look like this
>> >
>> >
>> > 2F240F4C226078: 19/12/2008 EST 04:42:45, mptscsih: ioc1: >>
>> > Attempting task abort! (sc=e40df080)
>> > 2F240F6E8C2E00: 19/12/2008 EST 04:42:45, mptbase: ioc1:
>> > IOCStatus(0x0048): SCSI Task Terminated
>> > 2F240F6E905A98: 19/12/2008 EST 04:42:45, mptscsih: ioc1: >>
>> > Attempting task abort! (sc=f7e23680)
>> >
>> > 2F24117BDA2438: 19/12/2008 EST 04:42:50, mptscsih: ioc1: >>
>> > Attempting bus reset! (sc=e40df080)
>> >
>> > After then the server has been rebooted.
>> >
>> > I can see the code is written inside /drivers/message/fussion/
>> > mptscsih.c
>> > The responsible function is
>> > mptscsih_host_reset()
>> > i am very new in SCSI fusion device driver. read some help guide from
>> > google but still i do not understand when the mptscsih_host_reset() is
>> > called by kernel. I normal situation i am not able to see this message
>> > in kernel log.
>> > Can any one help me to understand when these type of kernel message
>> > are comming, is it foe SCSI hardware problem ?
>> > when mptscsih_host_reset() will be executed?
>>
>> It looks like a standard error handling escalation sequence. Why is
>> very hard to tell without the entire kernel log. Why there wasn't a
>> recovery is also not clear.
>>
yes its error handler sequence. But as describe into the above
link(http://www.nabble.com/MPT-fusion-driver,-better-but-still-buggy-at-errors-handling-under-2.6-td1095505.html)
that
2.6.xx xx <= 11, enters an infinit loop attempting to reset the SCSI
so the box gets unusable and requires a rough power cycle to recover.
So i think that is the reason to restart the server(after "Attempting host
reset! )as a power cycle is required to recover.
when next time server was booting i got some kernel messages on
recovery of SCSI. So recovery is done after reboot the server.
Still i do not know how to over come this bug fo infinite loop. If you
have any suggestion please let me know.
>
> Pls let me know when this kind of error handler is happened?
> is it for SCSI hard ware failure?
>
>> > Only one time i show this message in my kernel log, is there any way
>> > to reproduce this message manually?
>> >
>> > where i get much info regarding this issue and SCSI fusion kernel
>> > driver except kernel code itself?
>> >
>> > I am writting this after reading help doc from
>> > http://www.lsi.com/insight_center/tech_trends/advanced_architectures/fusionmpt/index.html
>> >
>> > But still i am very few knowledge to solve it.
>> >
>> > waiting for your help.
>>
>> There's not much else I can do. If you post the entire kernel log, the
>> fusion people hang out on this list and might see something that
>> indicates what the problem is.
>>
>> James
>>
>>
>
Thanks
Tina
http://teachmeembedded.blogspot.com/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-01-12 16:13 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-06 21:45 need fusion driver guide Sam Ravnborg
2009-01-06 21:50 ` James Bottomley
[not found] ` <e7b7bf130901062002ke59c0dkd7ca0ed73352066f@mail.gmail.com>
2009-01-07 4:21 ` James Bottomley
2009-01-07 5:24 ` linux linux
2009-01-12 16:13 ` linux linux
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox