Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Kurt Fitzner <kfitzner@excelcia.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Infinite error message from SDC driver on install
Date: Tue, 12 Jul 2005 20:12:48 -0600	[thread overview]
Message-ID: <42D478A0.9040608@excelcia.org> (raw)
In-Reply-To: <20050711195440.GD2170@roadwarrior.mcmartin.ca>

Kyle McMartin wrote:
> On Sat, Jul 09, 2005 at 03:50:04PM -0600, Kurt Fitzner wrote:
> 
>>"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
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

      parent reply	other threads:[~2005-07-13  2:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09  0:16 [parisc-linux] Infinite error message from SDC driver on install Kurt Fitzner
2005-07-09 21:50 ` Kurt Fitzner
2005-07-11 19:50   ` Scott Edwards
2005-07-11 19:54   ` Kyle McMartin
2005-07-12  6:16     ` Joel Soete
2005-07-12 12:02       ` Kyle McMartin
2005-07-12 17:07         ` Joel Soete
2005-07-13  2:12     ` Kurt Fitzner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42D478A0.9040608@excelcia.org \
    --to=kfitzner@excelcia.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox