9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9pccpu: can't open /dev/sdXX/nvram
Date: Mon, 30 Jul 2012 10:46:51 -0400	[thread overview]
Message-ID: <4f1de3acaba511c0fa196f368d4be4b1@kw.quanstro.net> (raw)
In-Reply-To: <E4BAB05C-3D28-4E35-9074-70BFCA5F98DC@ar.aichi-u.ac.jp>

> pcirouting: ignoring south bridge PCI.0.0.0 10DE/07C0
> #l0: igbepcie: 1Gbps port 0xE4080000 irq 10: 6805ca00fbd2
> mpintrenable: out of choices eisa -1 isa 5 tbdf 0xc002000 irq 11
> intrenable: couldn't enable irq 11, tbdf 0xC002000 for usbohci
> mpintrenable: out of choices eisa -1 isa 5 tbdf 0xc002100 irq 5
> intrenable: couldn't enable irq 5, tbdf 0xC002100 for usbehci
> 3198M memory: 149M kernel data, 3048M user, 3673M swap
> usbinit...usbd...no usb disk...waiting for dhcp...

it sure looks to me like this is a usb interrupt problem.  i can't
tell from the output of your kernel if the mp table is just missing
or not.  i'm guessing that this mp table just doesn't have entries
for 1:1 mapped irqs.  my first guess (not tried myself) would be
to assume that irq 11 → GSI 11, which is usually ioapic 0, pin 11.
s/11/5 for the other usb port.

you might try adding fake irq entries to your mp table to match,
and see if that works.  :-).  usb is always level triggered.

> > authid: ehci 0xe0003000: polling

here's more confirmation of an irq problem.  i wonder if polling
isn't fully tested.

- erik



  reply	other threads:[~2012-07-30 14:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28  3:30 arisawa
2012-07-28  8:19 ` David du Colombier
2012-07-28 13:41   ` arisawa
2012-07-28 14:33     ` David du Colombier
2012-07-29  7:30       ` arisawa
2012-07-29  9:43         ` Richard Miller
2012-07-29 11:45           ` arisawa
2012-07-29 14:16             ` Richard Miller
2012-07-29 22:49               ` arisawa
2012-07-30  9:19                 ` arisawa
2012-07-30 14:46                   ` erik quanstrom [this message]
2012-07-30 20:45                     ` cinap_lenrek
2012-08-17  2:15                       ` arisawa
2012-08-17  3:27                         ` cinap_lenrek
2013-05-13 16:37                   ` Skip Tavakkolian
2013-05-13 21:32                     ` arisawa
2013-05-13 21:53                       ` Matthew Veety
2013-05-13 23:06                       ` erik quanstrom
2013-05-15  9:56                         ` arisawa
2013-05-15 20:56                           ` arisawa
2013-05-15 21:18                             ` erik quanstrom
2013-05-16  0:16                               ` arisawa
2013-05-16  1:25                                 ` erik quanstrom
2013-05-16 13:44                                 ` kernel panic
2013-05-17 12:36                                   ` arisawa

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=4f1de3acaba511c0fa196f368d4be4b1@kw.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).