All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathaniel J Villaume <Nathaniel.J.Villaume@domain.hid>
To: Jeroen Van den Keybus <jeroen.vandenkeybus@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Dual Xeon 2.6.13 SMP config problem
Date: Wed, 01 Feb 2006 20:02:05 -0800	[thread overview]
Message-ID: <23fcc723d285.23d28523fcc7@domain.hid> (raw)

Hi, 
It turns out that I had to upgrade the mkinitrd package. The one that comes with FC3 doesn't build the image correctly for SMP.  That said, I now can build and boot a vanilla 2.6.15 kernel, but when I try to boot the ipipe-patched kernel, I get the following error near the end of the boot-sequence: (  I thought it was an X-server problem it comes so late, but then I booted to init level 3, and I get the same thing)

hda: dma_timer_expiry  dma_status == 0x24
hda: dma: int recovery 
hda: lost interrupt

Then the kernel hangs. (Num Lock key doesn't make the lights blink.)

The configs have two differences: (seriously) 
1) The dates are different, 
2) ipipe is included in the failing kernel. 

I would like to know if there are any other tests I can do to isolate the cause of this failure. 

I appreciate any comments, 

Nate




             reply	other threads:[~2006-02-02  4:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  4:02 Nathaniel J Villaume [this message]
2006-02-02  8:04 ` [Xenomai-help] Dual Xeon 2.6.13 SMP config problem Philippe Gerum
2006-02-02 18:51   ` Nathaniel Villaume
2006-02-02 18:59     ` Philippe Gerum
     [not found] <200601251105.k0PB5uPK028509@domain.hid>
2006-01-25 19:10 ` [Xenomai-help] Dual Xeon, 2.6.10, adeos-r13 Nathaniel Villaume
2006-01-30 12:40   ` Jan Kiszka
2006-02-01  0:54     ` [Xenomai-help] Dual Xeon 2.6.13 SMP config problem Nathaniel Villaume
2006-02-01  7:30       ` Jeroen Van den Keybus

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=23fcc723d285.23d28523fcc7@domain.hid \
    --to=nathaniel.j.villaume@domain.hid \
    --cc=jeroen.vandenkeybus@domain.hid \
    --cc=xenomai@xenomai.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 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.