9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9load hangs in floppygetfspart dosinit
Date: Mon, 16 Feb 2004 01:34:26 +0100	[thread overview]
Message-ID: <200402160034.i1G0YQM26212@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 13 Feb 2004 18:35:08 -0800." <71506c31124588928cf24315b400d591@collyer.net>

short version:
after plugging usb keyboard via different slot (usb port), it works.

Axel.

long version::

To sum up from my previous post, 9load got stuck in timedsleep
after I changed the agp video card.

> It sounds somewhat like problems I had a long time ago; perhaps your
> fs kernel it out of date?  Check that the last line of trapinit(),
> /sys/src/fs/pc/trap.c:192 in my copy, is:
>
> 	fpinit();

I don't even make it to the fs kernel, I'm already hanging in 9load.
My copy of /sys/src/boot/pc/trap.c is up to date with sources;
however, comparing that with sys/src/fs/pc/trap.c I do see some
differences.

i tried to integrate those differences, but failed to solve the problem
(the resulting 9load was able to boot a kernel on another machine)


Then, I tried 'shuffling' and disabling hardware,
with more success!!!
`plain' 9load works, except when a usb keyboard is attached to usb2
(disconnecting the usb keyboard, or connecting to a (sufficiently)
 different usb port is sufficient to make 9load work again.
 plugging it back into the original port makes it fail again)

why 9load stopped working when I changed agp card I don't know,
I suppose because interrupts moved, don't know the 'original'
irq assignment.

Some details in case anyone is interested:

The motherboard is a shuttle ak32vn (via kt266a + vt8235)
when keyboard is on usb2 (irq 10) 9load gets stuck

term% cat /dev/irqalloc
          3           0 debugpt
          7           0 mathemu
          8           0 doublefault
          9           0 mathover
         14           0 fault386
         15           0 unexpected
         16           0 matherror
         32           0 clock
         33           1 kbd
         35           3 usb1
         36           4 COM1
         38           6 floppy
         39           7 lpt
         42          10 usb2
         43          11 usb0
         43          11 ether0
         44          12 kbdaux
         46          14 sdC (ata)
         47          15 sdD (ata)
term% pci
0.0.0:	06.00.00 1106/3099   0
0.1.0:	06.04.00 1106/b099   0
0.10.0:	04.80.00 1131/7134  10 0:ef000000 1024
0.12.0:	02.00.00 10b7/9001  11 0:0000d001 64
0.16.0:	0c.03.00 1106/3038  11 4:0000d401 32
0.16.1:	0c.03.00 1106/3038   3 4:0000d801 32
0.16.2:	0c.03.00 1106/3038  10 4:0000dc01 32
0.16.3:	0c.03.20 1106/3104   5 0:ef001000 256
0.17.0:	06.01.00 1106/3177   0
0.17.1:	01.01.8a 1106/0571 255 4:0000e001 16
0.17.5:	04.01.00 1106/3059  10 0:0000e401 256
1.0.0:	03.00.00 10de/0110  11 0:ec000000 16777216 1:e0000008 134217728
term%


Axel. - glad that it works now


      reply	other threads:[~2004-02-16  0:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 23:07 Axel Belinfante
2004-02-14  0:43 ` Axel Belinfante
2004-02-14  2:35   ` Geoff Collyer
2004-02-16  0:34     ` Axel Belinfante [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=200402160034.i1G0YQM26212@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /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).