Description
Danny Schneider
2005-04-13 02:47:03 UTC
Kernel: Have there been fixes put in for this driver since 2.6.11-r3 that would resolve this problem? Hi, in my particular case, i have some servers around that have that controller but don't have anything attached to it (we use the compaq array). besides that, i can boot the livecd 2005.0 with no problem. can you please provide come more info like lspci and lsmod after booting the livecd? my lspci follow's: livecd root # lspci 0000:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 02) 0000:00:06.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 14) 0000:00:06.1 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 14) 0000:00:07.0 Network controller: Compaq Computer Corporation Netelligent Integrated 10/100 TX UTP (rev 10) 0000:00:08.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC] (rev 7a) 0000:00:09.0 System peripheral: Compaq Computer Corporation Advanced System Management Controller 0000:00:0f.0 PCI bridge: IBM IBM27-82351 (rev 07) 0000:00:10.0 PCI bridge: Intel Corporation 21154 PCI-to-PCI Bridge 0000:00:14.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) 0000:00:14.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 0000:00:14.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) 0000:00:14.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) 0000:01:00.0 Unknown mass storage controller: Compaq Computer Corporation Smart-2/P RAID Controller (rev 03) 0000:02:04.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) 0000:02:05.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) can you please post also a link to a page with someone with the same or very similar problem? thx Created attachment 56342 [details]
dmesg Output of my system when booted with systemrescuecd with kernel 2.4 - thisone works very fine exept with my USB Stick, but no problem with the SCSI Subsystem. It seems to use the old ncr53c8xx
I will also try to get an dmesg output from the failing 2.6 kernel as ist seems
to boot the system compleatly after several reset loops of scsi bus. to get to
the login you have to wait several minutes and as far as I see, the SCSI does
not work when booted. As I still have other problems to solve it my take a few
days... sorry
Created attachment 56668 [details]
DMESG of booted system
I have found out, that the System continues to boot after several minutes. So I
was able to log an and store the dmesg output. the output of lsmod nevertheless
is empty and also /proc/modules
Created attachment 56670 [details]
Output of List of my scsi drives found in the /proc tree
additional to the last dmesg output
Created attachment 56671 [details]
List of PCI devices found under the /proc tree
Created attachment 56681 [details, diff]
testing.patch
please test this patch. this is some little changes that i found on LKML. to
patch the kernel go to /usr/src/linux, and make:
patch -p0 < <path_to_testing.patch>
Looks like a kernel issue and not a release issue. I'm leaving release on CC so we can make sure to test this next time around. Is this a dual-processor machine? Since we've been having trouble on sparc with SMP systems with 2.6 kernels with machines that use sym53c8xx in some form. Kernel team: i have a quad xeon sleeping beside me, and also got a couple symbios cards around, i can give it a spin if you didn't get an answer yet. Gustavo: If you could try and reproduce this, it would be much appreciated. I have tested the patch - I can not see any change im my system behavior...sorry the problem still exists Oh, and my computer is a single processor one. I also have mailed the Problem to Gerard Roudier <groudier@free.fr> and Matthew Wilcox <matthew@wil.cx> - which seem to be the authors of the sym53c8xx V2 driver... I also have searched the net a second time: It seems that there are several nearly identical bug reports at red hat, debian and the kernel buglist. To me it seems that al lot of people have the same problem. Most say, that kernel 2.4 and other os's work fine, kernel 2.6 does not! So I really think it is not a hardware problem as these people use different computers, different scsi-cards and so on... To the maintainers: Please mark this problem as very urgent! PS: Is it possible to get gentoo 2005 working with a 2.4 kernel also? Created attachment 58551 [details]
PDF which I have mailed to the maintainers of the driver
Problem description which I have send to the maintainers of the sym53c8xx V2
driver...
Created attachment 58552 [details]
seems that the upload with the former attachment faild - so this is the second try
none
Created attachment 58554 [details, diff]
testing2.patch
Ok, now can u please try this patch? don't apply the other, just this one. If
this doesn't solve the problem, i'll the closing this as this will be an
upstream problem (it already is but i'm trying to avoid closing this)
See comment #14 By the way, if you sent the PDF to the maintainer, I suggest you resend it as a 80col plain text email. It may go ignored otherwise. I have tested Patch 2. Unable to report positive effects or any at all. Bug still not resolved. As soon as posible I will dismount my harddrive dev/sdb and try if the module loads when this drive is not connected with the computer might take 1-2 weeks... sorry I have found some time and disconected the harddrive which is accessed by the /dev/sdb name physicaly from my computer. When doing this the system boots without problems - or better with no problems concerned with this bug, as lsmod still has no output and I think there migth be a problem with the proc filesystem in my kernel - probably a configuration problem. So the problem is still unfixed - kernel 2.4 works, 2.6 not. This is still very unsatisfying and being the only os not accessing this harddrive makes it hard for me to thust linux 2.6 to be as stable and reliable as for example Windows 2000. If it supports scsi ist should at laeast support all harddiscs, CD and DVD drives without hassle. I migth have found a workaround with removing my good old ibm harddisc, but so I only cure the symptom and not the cause for the disease. In that case its an upstream bug. Please test vanilla-sources-2.6.12 and file a bug with the relevent info at http://bugzilla.kernel.org Just noticed this patch: http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/jejb/scsi-for-linus-2.6.git;a=commitdiff_plain;h=53222b906903fd861dc24ebccfa07ee125941313;hp=7c00ffa314bf0fb0e23858bbebad33b48b6abbb9 You might want to try it first, although I'm not sure it will make any difference... |