All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Beamonte <dbeamonte@telnet-ri.es>
To: linuxppc-embedded@ozlabs.org
Subject: Interrupts get disabled on USB access on MPC8272
Date: Fri, 26 Sep 2008 17:36:09 +0200	[thread overview]
Message-ID: <48DD0169.7090709@telnet-ri.es> (raw)

Hi,

I'm trying to make USB driver work on my MPC8272 with kernel 2.6.21.

The driver detects properly the root hub (the embedded controller), but 
when it tries to communicate with a device, the system seems to hang.

I have debugged the kernel and what I can see is that, once the 
processor tries to send a buffer of the USB controller, interrupts get 
disabled. And so, there is no ethernet, serial port, or whatever way of 
communication to the processor. With my debugger I can see that the 
kernel keeps running and executing cpu_idle() and so on. Furtheremore, 
jiffies increase, but no other interrupts occur.

Has anyone experienced a problem like this?

It seems to happen when buffers try to access external memory. Can it be 
related to bus arbitration?

Regards,

David

             reply	other threads:[~2008-09-26 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26 15:36 David Beamonte [this message]
2008-09-26 16:31 ` Interrupts get disabled on USB access on MPC8272 Scott Wood

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=48DD0169.7090709@telnet-ri.es \
    --to=dbeamonte@telnet-ri.es \
    --cc=linuxppc-embedded@ozlabs.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.