* sym-2.1.18j Phase Change 6-7
@ 2005-03-12 18:40 Jackie Ferrera
2005-03-12 23:35 ` Mark Vitnell
0 siblings, 1 reply; 2+ messages in thread
From: Jackie Ferrera @ 2005-03-12 18:40 UTC (permalink / raw)
To: linux-scsi
I didn't find anyone else reporting this issue on linux-scsi. Actually,
i have only found some fedora core users experiencing the same problem
and reporting it (see
https://bugzilla.redhat.com/bugzilla/long_list.cgi?buglist=139949),
although the problem doesnt appear to be redhat-specific (i 've tried it
with slackware). Pardon me if this is a known bug, i am first-time
poster on this list.
I have been giving it a shot with vanilla kernel sources (straight from
kernel.org 2.6.9, 2.6.10, 2.6.11), and the error persists. 2.6.11.1 and
2.6.11.2 dont have any changes in SCSI that would affect the sym driver
in their tiny changelog, so i havent tried them yet.
The box is a dual i386, but i 've also been running non-SMP kernels for
my tests, producing the same results.
My controller shows up like this in `lspci -v`:
01:05.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010
Ultra3 SCSI Adapter (rev 01)
Flags: bus master, medium devsel, latency 72, IRQ 24
I/O ports at e400 [size=256]
Memory at febfe000 (64-bit, non-prefetchable) [size=1K]
Memory at febfa000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
When i run 2.6.9, 2.6.10 or 2.6.11, the sym kernel module produces
massive amounts of syslog traffic and logs. The message in syslog looks
like this:
kernel: sym0:0:0:phase change 6-7 11 2e37a784 resid=6.
As a temporary solution to overcome this and do my performance tests, i
just adjusted syslogd on that server not to log any kern messages from
syslog.conf.
Still, performance degrades on my 10K rpm harddrives at 3mb/sec.
In my humble opinion(i am not a kernel developer or expert), it appears
that some changes done in the code for scsi (API?) in the linux kernel
tree, were not correctly implemented in the sym driver.
The controller works fine with 2.6.8.1(vanilla). Anything later than
2.6.8.1 in my tests, was prone to these errors and the performance degrade.
Has anyone else experienced this issue? Are there any steps i can
take(hopefully a patch?) that would fix it?
thank you all,
Jackie.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: sym-2.1.18j Phase Change 6-7
2005-03-12 18:40 sym-2.1.18j Phase Change 6-7 Jackie Ferrera
@ 2005-03-12 23:35 ` Mark Vitnell
0 siblings, 0 replies; 2+ messages in thread
From: Mark Vitnell @ 2005-03-12 23:35 UTC (permalink / raw)
To: Jackie Ferrera; +Cc: linux-scsi
On 13/03/2005, at 5:40, Jackie Ferrera wrote:
> I didn't find anyone else reporting this issue on linux-scsi.
I reported this problem back on November 17, 2004, but got no
interest from the list.
> Actually, i have only found some fedora core users experiencing the
> same problem and reporting it (see
> https://bugzilla.redhat.com/bugzilla/long_list.cgi?buglist=139949),
> although the problem doesnt appear to be redhat-specific (i 've tried
> it with slackware). Pardon me if this is a known bug, i am first-time
> poster on this list.
> I have been giving it a shot with vanilla kernel sources (straight
> from kernel.org 2.6.9, 2.6.10, 2.6.11), and the error persists.
> 2.6.11.1 and 2.6.11.2 dont have any changes in SCSI that would affect
> the sym driver in their tiny changelog, so i havent tried them yet.
> The box is a dual i386, but i 've also been running non-SMP kernels
> for my tests, producing the same results.
>
> My controller shows up like this in `lspci -v`:
> 01:05.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010
> Ultra3 SCSI Adapter (rev 01)
> Flags: bus master, medium devsel, latency 72, IRQ 24
> I/O ports at e400 [size=256]
> Memory at febfe000 (64-bit, non-prefetchable) [size=1K]
> Memory at febfa000 (64-bit, non-prefetchable) [size=8K]
> Capabilities: [40] Power Management version 2
>
>
> When i run 2.6.9, 2.6.10 or 2.6.11, the sym kernel module produces
> massive amounts of syslog traffic and logs. The message in syslog
> looks like this:
>
> kernel: sym0:0:0:phase change 6-7 11 2e37a784 resid=6.
>
> As a temporary solution to overcome this and do my performance tests,
> i just adjusted syslogd on that server not to log any kern messages
> from syslog.conf.
>
> Still, performance degrades on my 10K rpm harddrives at 3mb/sec.
> In my humble opinion(i am not a kernel developer or expert), it
> appears that some changes done in the code for scsi (API?) in the
> linux kernel tree, were not correctly implemented in the sym driver.
The problems with the phase change errors seemed to have been fixed for
me when I patched the 2.6.10 kernel with the sym_2.1.18n patch released
by Mathew Wilcox on December 30. Though this was incorporated in the
2.6.11 kernel, so your issues may be different. All my tests were with
kernel.org sources without any distribution specific patches.
>
> The controller works fine with 2.6.8.1(vanilla). Anything later than
> 2.6.8.1 in my tests, was prone to these errors and the performance
> degrade.
>
> Has anyone else experienced this issue? Are there any steps i can
> take(hopefully a patch?) that would fix it?
>
Try patching 2.6.11.2 with sym2_2.2.0 released yesterday, perhaps?
Good luck
Mark Vitnell
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-03-12 23:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-03-12 18:40 sym-2.1.18j Phase Change 6-7 Jackie Ferrera
2005-03-12 23:35 ` Mark Vitnell
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.