[9fans] new 9load panic

[9fans] new 9load panic

[Gabriel Diaz]

Hello

I pulled today and tryed a new 9load, and that's what i've got:

MBR...PBS1...Plan9 ....
ELCR: 0C28
apm: ax f000 cx f000 dx 0x40
bios0: drive 0x80...type 3
bios1: driver 0x81...type3
islba: drive f2: no dap extensions
sectread: bios failed to read 512 @....
biosread: failed to read 512....got -1
dev A0...
dev B0...
sectread:....
biosread:....
sectread:....
biosread:....
using: sdC0!9fat!plan9.ini
.FLAGS 10292 TRAP e ECODE 2 PC 8000176fa
AX acf08123 BX 80001a99 CX 800711d8 DX 0000003d
SI 00000000 DI 80001377 BP 80001250
CS 0010 DS 0008 ES 0008 FS 0008 GS 0008
CR0 80000011 CR2 acf08123 CR3 0000c000
panic: exception interrupt 14

is this related to the update done time ago about the same panic message?

thanks

gabi

Re: [9fans] new 9load panic

[ron minnich]

On 10/27/07, Gabriel Diaz <gabidiaz@gmail.com> wrote:
> Hello
>
> I pulled today and tryed a new 9load, and that's what i've got:
>
> MBR...PBS1...Plan9 ....
> ELCR: 0C28
> apm: ax f000 cx f000 dx 0x40
> bios0: drive 0x80...type 3
> bios1: driver 0x81...type3
> islba: drive f2: no dap extensions
> sectread: bios failed to read 512 @....
> biosread: failed to read 512....got -1
> dev A0...
> dev B0...
> sectread:....
> biosread:....
> sectread:....
> biosread:....
> using: sdC0!9fat!plan9.ini
> .FLAGS 10292 TRAP e ECODE 2 PC 8000176fa
> AX acf08123 BX 80001a99 CX 800711d8 DX 0000003d
> SI 00000000 DI 80001377 BP 80001250
> CS 0010 DS 0008 ES 0008 FS 0008 GS 0008
> CR0 80000011 CR2 acf08123 CR3 0000c000
> panic: exception interrupt 14
page fault IIRC? somebody want to correct me?
cr2 is at a weird address: acf08123

hmm. I gotta go but you're taking a page fault in 9load it seems? Any
chance your plan9.ini is messed up?

I keep telling people ... pbs should load a kernel, then we don't have
to debug BOTH 9load and a kernel :-)

ron

Re: [9fans] new 9load panic

[geoff]

The new 9load attempts to offer the bios as a boot device, primarily
for the benefit of usb devices.

It would be helpful to see the omitted parts of the boot messages.
Assuming that the PC printed is actually 800176fa, that's in the cis
(pcmcia) code.  Is this a laptop?

Does this machine have a SATA disk?  If so, does the BIOS have
settings to select AHCI or "compatibility" mode?  If so, what are they
set to?

Re: [9fans] new 9load panic

[Gabriel Diaz]

hello

it is a desktop pc, it has sata but not ahci, the bios is set up as
"enhaced mode" and "sata-only", and have two hard disks (one sata and
one ide) and one cdrom (ide). i can see sdC0 (ide disk), sdC1 (cdrom)
and sdE0 (sata disk).

i checked again the values and add the lines missing (the PC had a
typo, it is 800017bfa, sorry)

MBR...PBS1...Plan9 ....
ELCR: 0C28
apm: ax f000 cx f000 dx 0x40
bios0: drive 0x80, 120034123776 bytes, type 3
bios1: driver 0x81, 160041885696 bytes, type3
islba: drive f2: no dap extensions
sectread: bios failed to read 512 @....
biosread: failed to read 512....got -1
dev A0 poer 1F0 config 0C5a capabilities 2F00 mwdma 0007 udma 203F
LLBA sectors 234441648
dev B0 port 1F0 config 85C0 capabilities 0F00 mwdma 007 udm 101F
sectread: bios failed to read 512 @ off 0 from 80
biosread: failed to read 512 @ off 0 of 80, want 512 got -1
sectread: bios failed to read 512 @ off 1073741822 from 80
biosread: failed to read 512 @ off 549755812864 of 80, want 512 got -1
using: sdC0!9fat!plan9.ini
.FLAGS 10292 TRAP e ECODE 2 PC 800017bfa
AX acf08123 BX 80061a99 CX 800711d8 DX 0000003d
SI 00000000 DI 80001377 BP 80001250
CS 0010 DS 0008 ES 0008 FS 0008 GS 0008
CR0 80000011 CR2 acf08123 CR3 0000c000
panic: exception interrupt 14

thanks,

gabi


On 10/27/07, geoff@plan9.bell-labs.com <geoff@plan9.bell-labs.com> wrote:
> The new 9load attempts to offer the bios as a boot device, primarily
> for the benefit of usb devices.
>
> It would be helpful to see the omitted parts of the boot messages.
> Assuming that the PC printed is actually 800176fa, that's in the cis
> (pcmcia) code.  Is this a laptop?
>
> Does this machine have a SATA disk?  If so, does the BIOS have
> settings to select AHCI or "compatibility" mode?  If so, what are they
> set to?
>
>

Re: [9fans] new 9load panic

[Tim Wiess]

i also just got something similar while attempting to install
the new iso within qemu....

PS1...Plan 9 from Bell Labs
ELCR: 0A00
apm ax=f000 cx=f000 dx=f000 di=fff0 dbx=9e22 esi=-f0010
bios0: drive: 0x80: 10737418240 bytes, type 3
biosinit: sorry, only one bios drive; can't read last one
dev A0 port 1F0 config 0040 capabilities 0B00 mwdma 0007 udma 203F	LLBA sectors 20971520
dev A0 port 170 config 85C0 capabilities 0300 mwdma 0007 udma 203F
found partition sdD0!cdboot; 49952+1440
sectread: bios failed to read 512 @ off 1073741822 from 80
biosread: failed to read 512 @ off 549755812864 of 80, want 512 got -1
using sdD0!cdboot!plan9.ini
.FLAGS=286 TRAP=e ECODE=0 PC=3f
  AX 80017fdb  BX 80036900  CX 00000020  DX 80017f5c
  SI 00000000  DI 80017f66  BP 80001250
  CS 0010 DS 0008  ES 0008  FS 0008  GS 0008
  CR0 80000011 CR2 78512900 CR3 0000c000
panic: exception/interrupt 14


> it is a desktop pc, it has sata but not ahci, the bios is set up as
> "enhaced mode" and "sata-only", and have two hard disks (one sata and
> one ide) and one cdrom (ide). i can see sdC0 (ide disk), sdC1 (cdrom)
> and sdE0 (sata disk).
> 
> i checked again the values and add the lines missing (the PC had a
> typo, it is 800017bfa, sorry)
> 
> MBR...PBS1...Plan9 ....
> ELCR: 0C28
> apm: ax f000 cx f000 dx 0x40
> bios0: drive 0x80, 120034123776 bytes, type 3
> bios1: driver 0x81, 160041885696 bytes, type3
> islba: drive f2: no dap extensions
> sectread: bios failed to read 512 @....
> biosread: failed to read 512....got -1
> dev A0 poer 1F0 config 0C5a capabilities 2F00 mwdma 0007 udma 203F
> LLBA sectors 234441648
> dev B0 port 1F0 config 85C0 capabilities 0F00 mwdma 007 udm 101F
> sectread: bios failed to read 512 @ off 0 from 80
> biosread: failed to read 512 @ off 0 of 80, want 512 got -1
> sectread: bios failed to read 512 @ off 1073741822 from 80
> biosread: failed to read 512 @ off 549755812864 of 80, want 512 got -1
> using: sdC0!9fat!plan9.ini
> .FLAGS 10292 TRAP e ECODE 2 PC 800017bfa
> AX acf08123 BX 80061a99 CX 800711d8 DX 0000003d
> SI 00000000 DI 80001377 BP 80001250
> CS 0010 DS 0008 ES 0008 FS 0008 GS 0008
> CR0 80000011 CR2 acf08123 CR3 0000c000
> panic: exception interrupt 14

Re: [9fans] new 9load panic

[ron minnich]

On 10/27/07, Tim Wiess <tim@nop.cx> wrote:
> i also just got something similar while attempting to install
> the new iso within qemu....
>
> PS1...Plan 9 from Bell Labs
> ELCR: 0A00
> apm ax=f000 cx=f000 dx=f000 di=fff0 dbx=9e22 esi=-f0010
> bios0: drive: 0x80: 10737418240 bytes, type 3

280000000 So I assume it has found the CD, and the install is usually
this size IIRC.

> biosinit: sorry, only one bios drive; can't read last one

I assume this means there is only the CDROM on the channel? Thta would
be expected.

> dev A0 port 1F0 config 0040 capabilities 0B00 mwdma 0007 udma 203F      LLBA sectors 20971520

This translates to 280000000 bytes @ 512 bytes/sector.

> dev A0 port 170 config 85C0 capabilities 0300 mwdma 0007 udma 203F
> found partition sdD0!cdboot; 49952+1440
> sectread: bios failed to read 512 @ off 1073741822 from 80

oops. The read failed?

> biosread: failed to read 512 @ off 549755812864 of 80, want 512 got -1
^^^^^^^^^^^^^^^^^^^^^^^^^^^
I think it is safe to say your problem is here. The other report had
the same thing.
The first offset is 3FFFFFFE, the second is  7FFFFFFC00, which is interesting.


> using sdD0!cdboot!plan9.ini
> .FLAGS=286 TRAP=e ECODE=0 PC=3f
>   AX 80017fdb  BX 80036900  CX 00000020  DX 80017f5c
>   SI 00000000  DI 80017f66  BP 80001250
>   CS 0010 DS 0008  ES 0008  FS 0008  GS 0008
>   CR0 80000011 CR2 78512900 CR3 0000c000
> panic: exception/interrupt 14

This is a sideshow, I think. The reads failed and it's just running
with bogus data.

>From your more complete list:

> > sectread: bios failed to read 512 @ off 0 from 80
> > biosread: failed to read 512 @ off 0 of 80, want 512 got -1
> > sectread: bios failed to read 512 @ off 1073741822 from 80
> > biosread: failed to read 512 @ off 549755812864 of 80, want 512 got -1

not even the read @ 0 worked. You've got a problem with BIOS I/O. I
wonder what it is?

ron

Re: [9fans] new 9load panic

[geoff]

There are new 9load and friends on sources.  They complain less about
bios problems, and explicitly name the file being booted.  There are
two new plan9.ini options: "*nobiosload" to disable loading kernels
via bios0 or sdB0, and "*noahciload" to disable loading via AHCI
(native SATA).