From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <10b109140706040026k65c5377auecdd583673409f1d@mail.gmail.com> Date: Mon, 4 Jun 2007 09:26:34 +0200 From: "Antonin Vecera" To: 9fans@cse.psu.edu MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_29096_15025812.1180941994106" Subject: [9fans] fossil crash after installation Topicbox-Message-UUID: 77c8053a-ead2-11e9-9d60-3106f5b1d025 ------=_Part_29096_15025812.1180941994106 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello all, I have installed Plan 9 from CD on some older PC. But after a while (from a few minutes to 10 minutes) the system stalled and on the screen I could see: fossil: diskWriteRaw failed: /dev/sdD0/fossil: 0x00004509: date=Thu Jan 1 21:29:00 EST 1970 part=data addr=17673: i/o error fossil(#S/sdD0/fossil)...version...boot: mount /: corrupted meta data panic: boot process died: unknown I had to format the harddisk and made new installation. Several times but no success. A few minutes after installation when I started configuration of system files the OS panics... PC is small booksize PC - Lightbook - from www.lex.com.tw CPU VIA Eden 500MHz chipset VIA PLE133 (VT8601A + VT82C686B) LAN 3x 10/100Base-T, RJ-45, Realtek 8100B I disabled in BIOS all USB, COM, LPT, audio and left only disk controller + 1 LAN I have no idea what else. Does anybody know? (I tried to install MS-Windows and it was OK) Antonin ------=_Part_29096_15025812.1180941994106 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello all,

I have installed Plan 9 from CD on some older PC. But after a while (from a few minutes to 10 minutes) the system stalled and on the screen I could see:

     fossil: diskWriteRaw failed: /dev/sdD0/fossil: 0x00004509: date=Thu Jan  1 21:29:00 EST 1970 part=data addr=17673: i/o error

     fossil(#S/sdD0/fossil)...version...boot: mount /: corrupted meta data
     panic: boot process died: unknown

I had to format the harddisk and made new installation.
Several times but no success. A few minutes after installation when I started configuration of system files the OS panics...

PC is small booksize PC - Lightbook - from www.lex.com.tw
CPU VIA Eden 500MHz
chipset VIA PLE133 (VT8601A + VT82C686B)
LAN 3x 10/100Base-T, RJ-45, Realtek 8100B

I disabled in BIOS all USB, COM, LPT, audio and left only disk controller + 1 LAN
I have no idea what else.

Does anybody know?

(I tried to install MS-Windows and it was OK)


Antonin ------=_Part_29096_15025812.1180941994106-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: "Steve Simon" Date: Mon, 4 Jun 2007 08:35:26 +0100 To: 9fans@cse.psu.edu Subject: Re: [9fans] fossil crash after installation In-Reply-To: <10b109140706040026k65c5377auecdd583673409f1d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 77d32ab4-ead2-11e9-9d60-3106f5b1d025 > A few minutes after installation when I > started configuration of system files the OS panics... It sounds to me like plan9 doesn't know about the quirks of your IDE controller, even though it obviously thinks it does. You could try turning off disk i/o DMA just in case that helps, DMA seems to be the quirkest area in the IDE interface. echo 'dma off' > /dev/sd00/ctl Unfortunately this will have a significant performance hit but if it works reliably then you could start looking at the datasheets for your chipset to try to bugfix it. -Steve From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] fossil crash after installation From: Charles Forsyth Date: Mon, 4 Jun 2007 08:59:56 +0100 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 77d7ca7e-ead2-11e9-9d60-3106f5b1d025 > DMA seems to be the quirkest area in the IDE interface. you must remember that dma is remarkable technology newly devised for the PC platform, and it has been understandably hard to get it just right. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4663C9BD.5060505@conducive.org> Date: Mon, 4 Jun 2007 04:13:49 -0400 From: W B Hacker User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] fossil crash after installation References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 77dbfec8-ead2-11e9-9d60-3106f5b1d025 Charles Forsyth wrote: >> DMA seems to be the quirkest area in the IDE interface. > > you must remember that dma is remarkable technology > newly devised for the PC platform, and it has been understandably > hard to get it just right. > > Surely you jest? Bill Godbout's 'Disk One' FDD controller had it on S-100, and it was nowhere near 'new' even then. Nor dual-ported memory. Both available on the GA-SPC12 IIRC. BIOS and driver code is what seems to be forever 'hard to get right'. Smothers Brothers rules seem to apply: "If you borrow it, break it!" Bill From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] fossil crash after installation From: Charles Forsyth Date: Mon, 4 Jun 2007 09:27:48 +0100 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 77dfd480-ead2-11e9-9d60-3106f5b1d025 > you must remember that dma is remarkable technology > newly devised for the PC platform, and it has been understandably > hard to get it just right. obviously i refer to the hardware interfaces. if it weren't new and difficult, IDE/ATA/SATA (... get this right yet!) drive interfaces would all be the same and all work, wouldn't they? there can't be any other possible explanation. it's not like VGA where all the interfaces are simple and the same ... just a moment ... oh, no! that's all different and differently buggy as well. i wonder how to sack an entire industry. (have you seen USB-to-Go?) From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] fossil crash after installation From: Charles Forsyth Date: Mon, 4 Jun 2007 09:55:43 +0100 In-Reply-To: <4663C9BD.5060505@conducive.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 77e3a6f0-ead2-11e9-9d60-3106f5b1d025 > Surely you jest? evidently. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <10b109140706040155l74f05576o46c24c4663d824b8@mail.gmail.com> Date: Mon, 4 Jun 2007 10:55:57 +0200 From: "Antonin Vecera" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] fossil crash after installation In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_30026_6649543.1180947357939" References: <10b109140706040026k65c5377auecdd583673409f1d@mail.gmail.com> Topicbox-Message-UUID: 77e970d0-ead2-11e9-9d60-3106f5b1d025 ------=_Part_30026_6649543.1180947357939 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/4/07, Steve Simon wrote: > > > You could try turning off disk i/o DMA just in case that helps, > DMA seems to be the quirkest area in the IDE interface. > > echo 'dma off' > /dev/sd00/ctl > Do you think it is enough to disable DMA in BIOS? Or is it necessary to disable it in Plan 9? Should I care what is set in PIO mode? Antonin ------=_Part_30026_6649543.1180947357939 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 6/4/07, Steve Simon <steve@quintile.net > wrote:

You could try turning off disk i/o DMA just in case that helps,
DMA seems to be the quirkest area in the IDE interface.

        echo 'dma off' > /dev/sd00/ctl


Do you think it is enough to disable DMA in BIOS?
Or is it necessary to disable it in Plan 9?
Should I care what is set in PIO mode?

Antonin
------=_Part_30026_6649543.1180947357939-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4663D422.9000301@conducive.org> Date: Mon, 4 Jun 2007 04:58:10 -0400 From: W B Hacker User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] fossil crash after installation References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 77f0176e-ead2-11e9-9d60-3106f5b1d025 Charles Forsyth wrote: >> you must remember that dma is remarkable technology >> newly devised for the PC platform, and it has been understandably >> hard to get it just right. > > obviously i refer to the hardware interfaces. > if it weren't new and difficult, IDE/ATA/SATA (... get this right yet!) drive > interfaces would all be the same and all work, wouldn't they? > there can't be any other possible explanation. > it's not like VGA where all the interfaces are simple and the same ... > just a moment ... oh, no! that's all different and differently buggy as well. > i wonder how to sack an entire industry. > T'was once both simpler and more obvious wherein the limitations were to be found. Software - or more specifically, 'firmware' - not hardware. At least once designers got their collective arms well and truly around clock distribution, gate-delay, and timing issues in general - most of which were in the 'long ago solved' category once legacy ISA-bus stuff - IDE in particular - moved into a ~bridge' chipset. Unfortunately, today's 'solution' to marginal silicon or PCB implementations seems to be to program around it with bespoke BIOS / driver kludges that may satisfy one OS but not another. > (have you seen USB-to-Go?) > > Not sure I want to... ;-) Bill From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <10b109140706040232q4a660daera1e8161433e65c0e@mail.gmail.com> Date: Mon, 4 Jun 2007 11:32:44 +0200 From: "Antonin Vecera" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] fossil crash after installation In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_30374_27133723.1180949564087" References: <10b109140706040026k65c5377auecdd583673409f1d@mail.gmail.com> Topicbox-Message-UUID: 7810f0c4-ead2-11e9-9d60-3106f5b1d025 ------=_Part_30374_27133723.1180949564087 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/4/07, Steve Simon wrote: > > > echo 'dma off' > /dev/sd00/ctl > > Where is the best place to disable DMA ? This command can be used in termrc (or cpurc) after kernel is loaded. But isn't it late? Antonin ------=_Part_30374_27133723.1180949564087 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/4/07, Steve Simon <steve@quintile.net> wrote:

        echo 'dma off' > /dev/sd00/ctl


Where is the best place to disable DMA ?
This command can be used in termrc (or cpurc) after kernel is loaded. But isn't it late?

Antonin
------=_Part_30374_27133723.1180949564087-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: erik quanstrom Date: Mon, 4 Jun 2007 07:45:18 -0400 To: 9fans@cse.psu.edu Subject: Re: [9fans] fossil crash after installation In-Reply-To: <10b109140706040232q4a660daera1e8161433e65c0e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 7819d586-ead2-11e9-9d60-3106f5b1d025 > Where is the best place to disable DMA ? > This command can be used in termrc (or cpurc) after kernel is loaded. But > isn't it late? > > Antonin dma is left as bios left it. c.f. /sys/src/9/pc/sdata.c:/^atadmamode so disabling dma in bios should do the trick. you can verify this with ; /cat /dev/sdC0/ctl | grep config config 427A capabilities 2F00 dma 00550040 dmactl 00000000 rwm 16 rwmctl 0 lba48always off the number following dmactl will be non-zero if dma is on. - erik From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] fossil crash after installation From: "Russ Cox" Date: Mon, 4 Jun 2007 11:10:29 -0400 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20070604150702.3ABCD1E8C26@holo.morphisms.net> Topicbox-Message-UUID: 78220396-ead2-11e9-9d60-3106f5b1d025 > dma is left as bios left it. c.f. /sys/src/9/pc/sdata.c:/^atadmamode > so disabling dma in bios should do the trick. you can verify this > with > > ; /cat /dev/sdC0/ctl | grep config > config 427A capabilities 2F00 dma 00550040 dmactl 00000000 rwm 16 rwmctl 0 lba48always off > > the number following dmactl will be non-zero if dma is on. not true; dma is left off unless explicitly enabled with echo dma on >/dev/sdC0/ctl that has on occasion been put in termrc but i don't see it there now. dma does get enabled in the termrc used for installation, but i don't believe it stays enabled in the base system unless you modify your termrc yourself. what is true is that the specific dma mode used when dma is enabled is whatever got set up by the bios. but whether or not to use dma at all is a separate question and not one that plan 9 defers to the bios for. russ