Infinite error message from SDC driver on install
I have just recently attempted to install Debian 3.1 on an old B132L. I have managed to get the install CD to boot, but the kernel is issuing an infinite stream of error messages from the SDC driver:
"HP SDC: Transaction add failed: transaction already queued?"
At first this was preventing the install CD from booting. I determined this was due to syslogd filling the ramdisk by logging the above message. I was able to get the install CD to boot into the installation by making the initial ramdisk size very large (64 meg). However, even this fills up withing a few minutes.
I'm not very familliar with the SDC - is there a way to prevent the above from occuring?
Thanks in advance,
Kurt Fitzner
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
I have found that if I switch to a serial console that after a variable (from 1 to 50) number of "Transaction add failed" error messages that a timeout error would occur and no further transaction errors will occur. This allows me to install Debian.
After installation if I continue to boot with a serial console then I can boot the Debian installation. If I try to boot with the standard graphics console, however, I have a new problem with the SDC driver. During boot when the SDC driver initializes, it issues the following message:
"HP SDC MLC: Registering the System Domain Controller's HIL MLC."
After the above message, the kernel hangs and booting is not possible.
I am at my wit's end with this one. I would really appreciate any insight that could be offered.
Regards,
Kurt Fitzner
p.s. In case it is relevant, machine specs are as follows:
HP 9000 B132L workstation
128 MB RAM
Seagate 4.3GB drive on fwscsi.6.0
Panasonic cdrom on sescsi.3.0
No EISA or PCI cards installed.
Quoted 15 lines · Kurt Fitzner
I have just recently attempted to install Debian 3.1 on an old B132L. I have managed to get the install CD to boot, but the kernel is issuing an infinite stream of error messages from the SDC driver:
"HP SDC: Transaction add failed: transaction already queued?"
At first this was preventing the install CD from booting. I determined this was due to syslogd filling the ramdisk by logging the above message. I was able to get the install CD to boot into the installation by making the initial ramdisk size very large (64 meg). However, even this fills up withing a few minutes.
I'm not very familliar with the SDC - is there a way to prevent the above from occuring?
Quoted 8 lines
Thanks in advance,
Kurt Fitzner
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
I also have a B132l workstation. I see about 200 lines of that message, and eventually it says timeout 52000ms (vague recolection) and it stops. I have noticed I'm unable to boot certian kernels.=20 I've had to boot from the cd, hop to a shell, mount the drive, and install the right kernel. All I recall is that it is the non smp 32bit 2.6 kernel. I was only able to use the same kernel that's used with the installer cd.
I've also reported this on
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D302238.
If it's related, you may want to add to my bug id. I'll try to get back to the list w/in the next day to provide more specifics. Ever since I was unable to use my pci scsi card combined with a mishap on my tape drive, I've kinda given up for a small season.
Good luck,
Scott
Quoted 22 lines · Kurt Fitzner
I have found that if I switch to a serial console that after a variable (from 1 to 50) number of "Transaction add failed" error messages that a timeout error would occur and no further transaction errors will occur. This allows me to install Debian.
=20
After installation if I continue to boot with a serial console then I can boot the Debian installation. If I try to boot with the standard graphics console, however, I have a new problem with the SDC driver. During boot when the SDC driver initializes, it issues the following message:
=20
"HP SDC MLC: Registering the System Domain Controller's HIL MLC." =20
After the above message, the kernel hangs and booting is not possible. =20
I am at my wit's end with this one. I would really appreciate any insight that could be offered.
=20
Regards,
=20
Kurt Fitzner
=20
Quoted 9 lines
p.s. In case it is relevant, machine specs are as follows:
HP 9000 B132L workstation
128 MB RAM
Seagate 4.3GB drive on fwscsi.6.0
Panasonic cdrom on sescsi.3.0
No EISA or PCI cards installed.
=20Quoted 1 line · Kurt Fitzner
I have just recently attempted to install Debian 3.1 on an old B132L. =
I
Quoted 1 line
Quoted 1 line
have managed to get the install CD to boot, but the kernel is issuing a=
n
Quoted 7 lines
Quoted 7 lines
infinite stream of error messages from the SDC driver:
"HP SDC: Transaction add failed: transaction already queued?"
At first this was preventing the install CD from booting. I determined this was due to syslogd filling the ramdisk by logging the above message. I was able to get the install CD to boot into the installatio=
n
Quoted 14 lines
Quoted 6 lines
by making the initial ramdisk size very large (64 meg). However, even this fills up withing a few minutes.
I'm not very familliar with the SDC - is there a way to prevent the above from occuring?
Quoted 8 lines
Thanks in advance,
Kurt Fitzner
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
Quoted 6 lines
=20
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
Quoted 2 lines · Kurt Fitzner
"HP SDC MLC: Registering the System Domain Controller's HIL MLC."
I don't suppose you could investigate further? (TOC the machine, lookup where it's hung, see the howto on parisc-linux.org).
All the d-i images tested fine on my B180, which is a fairly close match to your B132...
Cheers,
Signature · 5 lines
Kyle McMartin _______________________________________________ parisc-linux mailing list [email protected] http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
Hello Kyle,
Quoted 11 lines · Kurt Fitzner
Quoted 2 lines
"HP SDC MLC: Registering the System Domain Controller's HIL MLC."
I don't suppose you could investigate further? (TOC the machine, lookup where it's hung, see the howto on parisc-linux.org).
All the d-i images tested fine on my B180, which is a fairly close match to your B132...
mmm not exactely: there was actualy 2 b132 models i.e. B132L and B132L+ and <http://www.openpa.net/systems/b-class.html> rememmber me the major d= iff
imho:
[...]
Chipset
[...]
# B132L, B160L: NCR 53C720 16-bit Fast-wide high voltage differential (HV=
D)
SCSI-2
# B132L+, B180L+: Symbios Logic 53C875 16-bit Ultra-wide SCSI-2 controlle= r
Unfortunately, I couldn't test here because no B132L around.
Hth,
Joel
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
Quoted 3 lines · Joel Soete
# B132L, B160L: NCR 53C720 16-bit Fast-wide high voltage differential (HVD) SCSI-2
# B132L+, B180L+: Symbios Logic 53C875 16-bit Ultra-wide SCSI-2 controller
And this is utterly irrelevant because it's not involved in the problem.
Signature · 5 lines
Kyle McMartin _______________________________________________ parisc-linux mailing list [email protected] http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
Quoted 4 lines · Joel Soete
Quoted 1 line
# B132L, B160L: NCR 53C720 16-bit Fast-wide high voltage differential=
(HVD)
Quoted 2 lines
Quoted 2 lines
SCSI-2
# B132L+, B180L+: Symbios Logic 53C875 16-bit Ultra-wide SCSI-2 contr=
oller
Quoted 2 lines
And this is utterly irrelevant because it's not involved in the problem=
.
Quoted 1 line
Oops my bad I just noticed that there are some diff between those 2 model=
and don't care of messages.
As previously said I never had B132L so I couldn't verify if there was so= me
HIL port for this design.
(I would like to check on <http://www.parisc-linux.org/hardware/index.htm=
l>
but not available for the moment :_( )
Appologies,
Joel
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
Quoted 9 lines · Kyle McMartin
Quoted 1 line · Kurt Fitzner
"HP SDC MLC: Registering the System Domain Controller's HIL MLC."
I don't suppose you could investigate further? (TOC the machine, lookup where it's hung, see the howto on parisc-linux.org).
All the d-i images tested fine on my B180, which is a fairly close match to your B132...
I've done some more testing. My results are similar to what Scott posted. I've only taken the most cursory look at the relevant code in the kernel, so my report here is simply observation and my own interpretation.
When booting from the install CDs and the console is GRAPHICS(0), I find that I get the transaction add error ad infinitum:
"HP SDC: Transaction add failed: transaction already queued?"
In one out of every five boots (approximately), after a variable number of the transaction errors, there will be a timeout error. Once the timeout error occurs, no more transaction add errors occur. The number of transaction add errors that occur before this happens can be anywhere from three to several hundreds.
"HP SDC: Transaction add failed: transaction already queued?"
above repeated three to several hundred times
"HP SDC: read timeout (99999ms)"
I found quite by accident that if I am moving the mouse just as the kernel is booting up, there is a far better chance of getting the timeout error quickly and thus terminating the transaction error after just 3 or 4 lines.
If the console is set to serial_1, the transaction error almost always (9 out of 10 times) terminates after only 3 or 4 lines. I now believe that the two observations (mouse movement and serial console) are related. I believe the extra interrupt overhead from either the PS/2 or serial port is allowing the timeout to occur.
Regarding the problem with the kernel hanging, just as Scott indicated, this only occurs on SMP-enabled kernels on the B132L. Not being familliar with Debian prior to this install, it took me a while to figure out how to get the installer to allow me to select a different kernel (which is why I have so much info on the frequency of the issues on a per boot basis).
I have now compiled my own kernel without HIL or SDC support. This is quite nice simply because the HIL poling sucks a lot of CPU time (despite what the FAQ says, I could never get the CPU usage of ksoftirqd below 8% even when higher priority tasks were running at a -19 nice level).
I'll now spend some time in the kernel code to see how the transaction add errors are somehow resetting the read timeout.
Hope the observations help.
Kurt.
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux