From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] new 9load report
Date: Thu, 8 Nov 2007 19:42:20 -0500 [thread overview]
Message-ID: <95441601ed581f7def5543865cd7ee67@quanstro.net> (raw)
In-Reply-To: <d1c554290711081443q3a0b9b87q1dbad2fafc80c3a1@mail.gmail.com>
> PBS1... Plan 9 from Bell Labs
> ELCR: 0C00
> Initial probe, to find plan9.ini... dev A0 port 1F0 config 85C0
> capabilities 0F00 mwdma 0407
> pcirouting 8086/27DF at pin 1 irq 10
> dev A0 port 18D0 config 045A capabilities 2F00 mwdma 0007 udma 203F
> LLBA sectors 117231408
> ahci0 port 0xd4544400: hba sss 0; ncs 31; coal 0; mports 3; led 1; clo 1; ems 0;
>
> intel 63[12]xesb: sata-I ports with 2 ports
> FLAGS=10282 TRAP=e ECODE=0 PC=8002a3a0
> AX f000ff6b BX 80039f64 CX f000ff53 DX 000003d5
> SI 80037e50 DI 00000002 BP 00000008
> CS 0010 DS 0008 ES 0008 FS 0008 GS 0008
> CR0 80000011 CR2 f000ff6b CR3 0000c000
> panic: exception/interrupt 14
>
> dmesg at http://mordor.tip9ug.jp/who/iru/dmesg.ein
> sorry any typos from the paper to the keyboard.
this is an excellent bug report. it's interesting that the
actual irq is 11, but the panic is for exception/interrupt 14.
are you sure the port (0xd4544400) is accurate? generally, bios
aligns bars a bit more.
if you can pxeboot this machine, would you be willing to try
/n/sources/contrib/quanstro/9pxeload9?
also, if you have a machine to compile on, if you could add
a debug to this loop from the 9load on sources:
/n/sources/plan9/sys/src/boot/pc/sdiahci.c:1584,1588
for(i = 0; i < n; i++)
if(ahciidle(c->drive[i]->port) == -1){
dprint("intel 63[12]xesb: port %d wedged; abort\n", i);
goto loop;
}
=>
for(i = 0; i < n; i++){
print("idle ahci %d\n", n);
if(ahciidle(c->drive[i]->port) == -1){
dprint("intel 63[12]xesb: port %d wedged; abort\n", i);
goto loop;
}
}
- erik
next prev parent reply other threads:[~2007-11-09 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 22:43 Iruata Souza
2007-11-09 0:42 ` erik quanstrom [this message]
2007-11-12 12:56 ` erik quanstrom
2008-02-04 2:23 ` erik quanstrom
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=95441601ed581f7def5543865cd7ee67@quanstro.net \
--to=quanstro@quanstro.net \
--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).