Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Kirk Bresniker <kirkb@chrome.rose.hp.com>
To: willy@thepuffingroup.com (Matthew Wilcox)
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Minutes
Date: Fri, 14 Jan 2000 16:16:42 PST	[thread overview]
Message-ID: <200001150016.QAA16991@chrome.rose.hp.com> (raw)
In-Reply-To: <20000114172721.V11300@thepuffingroup.com>; from "Matthew Wilcox" at Jan 14, 100 5:27 pm

FYI --

| 4. Martin has cleaned up the serial and console code.  He will commit his
|    changes tomorrow after he's tested it.

In testing the 2.3 kernel on my D320/1 with an Access Port (AP) card as
the console, printk() appeared to be broken.  The mprint() statements in
the boot loader seem to function correctly, and the pdc_putc('.')  at
the end of realmode_setup() works, but the printk() at the start of
iodc_con_init() never outputs.  The chassis codes sent out in
realmode_setup() do appear properly on the AP console.

Now the interesting thing in a D-Class with an AP card installed is that
the RS-232 connector on the back of the machine is dis-connected from 
the LASI serial hardware and connected to the AP card hardware. Because
of this, regardless of what console path is stored on the machine, the 
AP card console is what is used, so that there will always be console
outptu. When I changed the stored path from the LASI RS-232 path to the 
AP card RS-232 path, the printk() succeeds. So, there must be something 
in printk() which is getting confused between what console is actually
in use and what console is the stored path.

That aside, the kernel appears to hang at the first __put_user() macro
called in unsigned long create_som_tables(). Executing a TOC after the
hang consitently gives IIA space/offset = 0x00000000 0x00046234.

KMB
--
+============================================================+
|       Kirk Bresniker    	(916) 748-2393		     |
|       8000 Foothills Blvd                                  |
|       Roseville, CA 95747-5649                             |
|       kirkb@rose.hp.com                                    |

  reply	other threads:[~2000-01-15  1:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-14 22:27 [parisc-linux] Minutes Matthew Wilcox
2000-01-15  0:16 ` Kirk Bresniker [this message]
2000-01-17 19:27   ` Matthew Wilcox
2000-01-19 16:40   ` Alex deVries
2000-01-22 12:33     ` [parisc-linux] Harware database down? Hannu Martikka
2000-01-24 21:36       ` dkennedy
2000-01-25  6:46         ` Hannu Martikka
2000-01-25 17:38         ` [parisc-linux] 715 problem Hannu Martikka
2000-01-25 19:22           ` willy
2000-01-25 18:37             ` Hannu Martikka
2000-01-25 18:41             ` Ross J. Reedstrom
2000-01-25 18:43             ` Martin K. Petersen

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=200001150016.QAA16991@chrome.rose.hp.com \
    --to=kirkb@chrome.rose.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=willy@thepuffingroup.com \
    /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