hdc: lost interrupt

hdc: lost interrupt

[David F Barrera]

I am seeing a kernel message, "hdc: lost interrupt", when running LTP on 
the xen0 domain.  The first time I saw the 'kernel: hdc: lost interrupt' 
in /var/log/messages, I was running LTP on both xen0 and xenU domains.  
The xenU domain was totally hung at this point. Suspecting a setup 
error, I re-checked the installation and reran LTP on xen0 alone, 
without having anything running on xenU. Again, I saw the error. To rule 
out a hardware problem, I decided to run the same tests on a regular 
kernel from kernel.org (2.6.10) and on the RHEL 4 kernel from Red Hat, 
both of which ran without showing the error.  I don't know what to make 
of it.  I am not suspecting a hardware error since the message does not 
show up when running on non-xen kernels.

Setup
Platform: RHEL 4 Beta 3
Hw: IBM xSeries 200, with a 866Mhz Pentium III and 512MB RAM,
       IDE drive: 00:07.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)

The machine is not the most modern, but it has worked reliably.

Regards,

David Barrera


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

Re: hdc: lost interrupt

[Mike Kershaw]

On Fri, Jan 21, 2005 at 04:08:07PM -0600, David F Barrera wrote:
> I am seeing a kernel message, "hdc: lost interrupt", when running LTP on 
> the xen0 domain.  The first time I saw the 'kernel: hdc: lost interrupt' 
> in /var/log/messages, I was running LTP on both xen0 and xenU domains.  
> The xenU domain was totally hung at this point. Suspecting a setup 
> error, I re-checked the installation and reran LTP on xen0 alone, 
> without having anything running on xenU. Again, I saw the error. To rule 
> out a hardware problem, I decided to run the same tests on a regular 
> kernel from kernel.org (2.6.10) and on the RHEL 4 kernel from Red Hat, 
> both of which ran without showing the error.  I don't know what to make 
> of it.  I am not suspecting a hardware error since the message does not 
> show up when running on non-xen kernels.

This may be a false lead, but I saw this (and other significant IO-related 
weirdness) when I moved hardware around and forgot to enable kernel DMA support
for the IDE chipset.  Overall system performance tanked (obviously), I got
a large number of hdX: Lost interrupt warnings, and even some outright panics.

Turning on DMA in dom0's kernel config cleared it all up.

Might be worth investigating anyhow,

-m



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

RE: hdc: lost interrupt

[Ian Pratt]

> I'm not sure if it is xen related or not but when I put following in 
> /etc/exports
> 
>  	/       10.0.10.5/24(ro,sync,no_root_squash)
> 
> and then procedeed to use dom0 as nfs root server, it would 
> hung pretty 
> reliably with "dma timeout" errors, and require power-cycle. 
> the fix was 
> to replace "sync" with "async" as shown below.
> 
>  	/       10.0.10.5/24(ro,async,no_root_squash)
> 
> that was for xen 2.0.1 and 2.6.9

Weird. Could you try just running domain 0, then mounting localhost:/
somewhere. 

See if exercising the mount causes the same problem. It would then be
nice to repeat the experiment with a stock kernel.

BTW: exporting / is probably not such a great idea as it will allow
other domains to read your ssh host keys...

Ian


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

RE: hdc: lost interrupt

[Ian Pratt]

> I am seeing a kernel message, "hdc: lost interrupt", when 
> running LTP on 
> the xen0 domain.  The first time I saw the 'kernel: hdc: lost 
> interrupt' 
> in /var/log/messages, I was running LTP on both xen0 and xenU 
> domains.  

We've had one or two reports of interrupt related weirdness. We're
hoping (perhaps optimistically) that these might go away when the IOAPIC
configuration code gets moved out of Xen and into domain 0, getting
upgraded to 2.6 code in the process. 

Ian 


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

RE: hdc: lost interrupt

[Adam Sulmicki]

>> I am seeing a kernel message, "hdc: lost interrupt", when
>> running LTP on
>> the xen0 domain.  The first time I saw the 'kernel: hdc: lost
>> interrupt'
>> in /var/log/messages, I was running LTP on both xen0 and xenU
>> domains.
>
> We've had one or two reports of interrupt related weirdness. We're
> hoping (perhaps optimistically) that these might go away when the IOAPIC
> configuration code gets moved out of Xen and into domain 0, getting
> upgraded to 2.6 code in the process.

I'm not sure if it is xen related or not but when I put following in 
/etc/exports

 	/       10.0.10.5/24(ro,sync,no_root_squash)

and then procedeed to use dom0 as nfs root server, it would hung pretty 
reliably with "dma timeout" errors, and require power-cycle. the fix was 
to replace "sync" with "async" as shown below.

 	/       10.0.10.5/24(ro,async,no_root_squash)

that was for xen 2.0.1 and 2.6.9

FWIW.



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

Re: hdc: lost interrupt

[Natasha Jarymowycz]

> We've had one or two reports of interrupt related weirdness. We're
> hoping (perhaps optimistically) that these might go away when the IOAPIC
> configuration code gets moved out of Xen and into domain 0, getting
> upgraded to 2.6 code in the process.

I've started looking at the work involved to move the IOAPIC configuration  
code
to domain 0.  Is anyone actively working on this task right now?  Any  
information
you can share about the plan of attack?  I'd be happy to help with  
development,
testing, etc.

Natasha



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

Re: hdc: lost interrupt

[Derek J Witt]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 0 bytes --]



[-- Attachment #2: Type: MESSAGE/DELIVERY-STATUS, Size: 360 bytes --]

Reporting-MTA: dns; vger.kernel.org
Arrival-Date: Sun, 3 Mar 2002 00:03:12 -0500
Local-Spool-ID: S292385AbSCCFDM

Original-Recipient: rfc822;lknl@vger.kernel.org
Final-Recipient: RFC822;lknl@vger.kernel.org
Action: failed
Status: 5.1.1 (User does not exist)
Last-Attempt-Date: Sun, 3 Mar 2002 00:03:29 -0500
Diagnostic-Code: x-local; 550 (User does not exist)

[-- Attachment #3: Type: MESSAGE/RFC822, Size: 3107 bytes --]

Received: from konza.flinthills.com ([64.39.200.1]:28131 "EHLO
	konza.flinthills.com") by vger.kernel.org with ESMTP
	id <S292385AbSCCFDM>; Sun, 3 Mar 2002 00:03:12 -0500
Received: from saiya-jin.flinthills.com (mail@saiya-jin.flinthills.com [64.39.192.211])
	by konza.flinthills.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g2353BCc026343
	for <lknl@vger.kernel.org>; Sat, 2 Mar 2002 23:03:11 -0600 (CST)
Received: from localhost ([127.0.0.1] ident=cappicard)
	by saiya-jin.flinthills.com with esmtp (Exim 3.34 #1 (Debian))
	id 16hO88-0001Ld-00
	for <lknl@vger.kernel.org>; Sat, 02 Mar 2002 23:01:52 -0600
Date: Sat, 2 Mar 2002 23:01:52 -0600 (CST)
From: Derek J Witt <djw@flinthills.com>
X-X-Sender: cappicard@saiya-jin.flinthills.com
Reply-To: Derek J Witt <djw@flinthills.com>
To: lknl@vger.kernel.org
Subject: Re: hdc: lost interrupt
Message-ID: <Pine.LNX.4.44.0203022235100.4998-100000@saiya-jin.flinthills.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I just solved my lost interrupt problems. I just moved my Caviar hard
drive from secondary master to primary slave. and I've not received any
lost interupt errors. But I may just recompile my kernel without apic. I
also have an SMP-capable controller that is also used for the sensor. But,
I know I don't need an apic for the sensor to run.

(I wonder if the apic is throwing off my LM80's readings. That's a
different matter.)

>
>> yeah, I am. My celeron 500 PPGA has APIC. Oh, could the apic causing
>> interrupt timing problems?
>
>yes, that's the point.  windows doesn't use the local apic,
>so a lot of bioses don't configure it properly.  note that it
>offers only fairly obscure benefits (nmi oopser, perf-counter events);
>in particular, the local apic is probably *slower* than normal pic.
>
>
>
>
>
>> On Sat, 2002-03-02 at 10:16, Mark Hahn wrote:
>> > > losing IDE interrupts.  I tried disabling multimode in makeconfig but to
>> >
>> > are you using the local apic?
>> >
>> > here are the set settings I use on my via-based machines (which are all stable):
>> > CONFIG_IDE=y
>> > CONFIG_BLK_DEV_IDE=y
>> > CONFIG_BLK_DEV_IDEDISK=y
>> > CONFIG_IDEDISK_MULTI_MODE=y
>> > CONFIG_BLK_DEV_IDECD=y
>> > CONFIG_BLK_DEV_IDEPCI=y
>> > CONFIG_IDEPCI_SHARE_IRQ=y
>> > CONFIG_BLK_DEV_IDEDMA_PCI=y
>> > CONFIG_BLK_DEV_ADMA=y
>> > CONFIG_IDEDMA_PCI_AUTO=y
>> > CONFIG_BLK_DEV_IDEDMA=y
>> > CONFIG_BLK_DEV_VIA82CXXX=y
>> > CONFIG_IDEDMA_AUTO=y
>> > CONFIG_BLK_DEV_IDE_MODES=y
>> >
>> > > Has anyone else with a Via chipset been able to boot into 2.5.x without having these interrupt problems? Any suggestions will be helpful.
>> >
>> > I confess I haven't ventured to use 2.5 on any machines.
>> >
>> >
>>
>
>--
>operator may differ from spokesperson.	            hahn@coffee.mcmaster.ca
>                                              http://java.mcmaster.ca/~hahn


**  Derek J Witt                                              **
*   Email: mailto:djw@flinthills.com                           *
*   Home Page: http://www.flinthills.com/~djw/                 *
*** "...and on the eighth day, God met Bill Gates." - Unknown **


From: Derek J Witt <djw@flinthills.com>
To: lknl@vger.kernel.org
Subject: Re: hdc: lost interrupt
Date: Sat, 2 Mar 2002 23:01:52 -0600 (CST)
Message-ID: <Pine.LNX.4.44.0203022235100.4998-100000@saiya-jin.flinthills.com>

I just solved my lost interrupt problems. I just moved my Caviar hard
drive from secondary master to primary slave. and I've not received any
lost interupt errors. But I may just recompile my kernel without apic. I
also have an SMP-capable controller that is also used for the sensor. But,
I know I don't need an apic for the sensor to run.

(I wonder if the apic is throwing off my LM80's readings. That's a
different matter.)

>
>> yeah, I am. My celeron 500 PPGA has APIC. Oh, could the apic causing
>> interrupt timing problems?
>
>yes, that's the point.  windows doesn't use the local apic,
>so a lot of bioses don't configure it properly.  note that it
>offers only fairly obscure benefits (nmi oopser, perf-counter events);
>in particular, the local apic is probably *slower* than normal pic.
>
>
>
>
>
>> On Sat, 2002-03-02 at 10:16, Mark Hahn wrote:
>> > > losing IDE interrupts.  I tried disabling multimode in makeconfig but to
>> >
>> > are you using the local apic?
>> >
>> > here are the set settings I use on my via-based machines (which are all stable):
>> > CONFIG_IDE=y
>> > CONFIG_BLK_DEV_IDE=y
>> > CONFIG_BLK_DEV_IDEDISK=y
>> > CONFIG_IDEDISK_MULTI_MODE=y
>> > CONFIG_BLK_DEV_IDECD=y
>> > CONFIG_BLK_DEV_IDEPCI=y
>> > CONFIG_IDEPCI_SHARE_IRQ=y
>> > CONFIG_BLK_DEV_IDEDMA_PCI=y
>> > CONFIG_BLK_DEV_ADMA=y
>> > CONFIG_IDEDMA_PCI_AUTO=y
>> > CONFIG_BLK_DEV_IDEDMA=y
>> > CONFIG_BLK_DEV_VIA82CXXX=y
>> > CONFIG_IDEDMA_AUTO=y
>> > CONFIG_BLK_DEV_IDE_MODES=y
>> >
>> > > Has anyone else with a Via chipset been able to boot into 2.5.x without having these interrupt problems? Any suggestions will be helpful.
>> >
>> > I confess I haven't ventured to use 2.5 on any machines.
>> >
>> >
>>
>
>--
>operator may differ from spokesperson.	            hahn@coffee.mcmaster.ca
>                                              http://java.mcmaster.ca/~hahn


**  Derek J Witt                                              **
*   Email: mailto:djw@flinthills.com                           *
*   Home Page: http://www.flinthills.com/~djw/                 *
*** "...and on the eighth day, God met Bill Gates." - Unknown **

Re: hdc: lost interrupt

[Derek J Witt]

[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]

Yeah, I do have APIC enabled. I'm using the local APIC and the IO-apic. 
My Celeron PPGA 500 does have an apic. Could the apic be causing the
interrupt timing problems?  Sorry about the double post.


On Sat, 2002-03-02 at 12:06, Derek J Witt wrote:
> yeah, I am. My celeron 500 PPGA has APIC. Oh, could the apic causing
> interrupt timing problems?
> 
> 
> On Sat, 2002-03-02 at 10:16, Mark Hahn wrote:
> > > losing IDE interrupts.  I tried disabling multimode in makeconfig but to
> > 
> > are you using the local apic?
> > 
> > here are the set settings I use on my via-based machines (which are all stable):
> > CONFIG_IDE=y
> > CONFIG_BLK_DEV_IDE=y
> > CONFIG_BLK_DEV_IDEDISK=y
> > CONFIG_IDEDISK_MULTI_MODE=y
> > CONFIG_BLK_DEV_IDECD=y
> > CONFIG_BLK_DEV_IDEPCI=y
> > CONFIG_IDEPCI_SHARE_IRQ=y
> > CONFIG_BLK_DEV_IDEDMA_PCI=y
> > CONFIG_BLK_DEV_ADMA=y
> > CONFIG_IDEDMA_PCI_AUTO=y
> > CONFIG_BLK_DEV_IDEDMA=y
> > CONFIG_BLK_DEV_VIA82CXXX=y
> > CONFIG_IDEDMA_AUTO=y
> > CONFIG_BLK_DEV_IDE_MODES=y
> > 
> > > Has anyone else with a Via chipset been able to boot into 2.5.x without having these interrupt problems? Any suggestions will be helpful.
> > 
> > I confess I haven't ventured to use 2.5 on any machines.
> > 
> > 
> -- 
> **  Derek J Witt                                              **
> *   Email: mailto:djw@flinthills.com                           *
> *   Home Page: http://www.flinthills.com/~djw/                 *
> *** "...and on the eighth day, God met Bill Gates." - Unknown **
-- 
**  Derek J Witt                                              **
*   Email: mailto:djw@flinthills.com                           *
*   Home Page: http://www.flinthills.com/~djw/                 *
*** "...and on the eighth day, God met Bill Gates." - Unknown **

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

hdc: lost interrupt

[Derek J Witt]

[-- Attachment #1: Type: text/plain, Size: 5261 bytes --]

Good evening, all. I've been trying to get 2.5.x to boot up without
losing IDE interrupts.  I tried disabling multimode in makeconfig but to
no avail.

My IDE controller and chipset are as follows (via dmesg):

ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
    ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA

...

Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
    ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALL SE6.4A, ATA DISK drive
hdb: ATAPI CD-ROM DRIVE 40X MAXIMUM, ATAPI CD/DVD-ROM drive
hdc: WDC AC36400L, ATA DISK drive
hdd: CRW6206A, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 12594960 sectors (6449 MB) w/80KiB Cache, CHS=784/255/63, UDMA(33)
hdc: 12594960 sectors (6449 MB) w/256KiB Cache, CHS=13328/15/63,
UDMA(33)

And /proc/pci reports my chipset as such: 

  Bus  0, device   0, function  0:
    Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev 196).
      Master Capable.  Latency=8.  
      Prefetchable 32 bit memory at 0xd0000000 [0xd7ffffff].
  Bus  0, device   1, function  0:
    PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (rev 0).
      Master Capable.  No bursts.  Min Gnt=12.
  Bus  0, device   7, function  0:
    ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 64).
  Bus  0, device   7, function  1:
    IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 6).
      Master Capable.  Latency=32.  
      I/O at 0xe000 [0xe00f].

And I have the following IDE kernel setup for 2.5.6-pre1+xfs:

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set
# CONFIG_BLK_DEV_IDEDISK_IBM is not set
# CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set
# CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set
# CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set
# CONFIG_BLK_DEV_IDEDISK_WD is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
# CONFIG_BLK_DEV_TIVO is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=y
CONFIG_IDE_TASK_IOCTL=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
# CONFIG_IDEDMA_PCI_AUTO is not set
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_IDEDMA_TIMEOUT is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_AEC62XX_TUNING is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_AMD74XX_OVERRIDE is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_PIIX_TUNING is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC_ADMA is not set
# CONFIG_BLK_DEV_PDC202XX is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_PDC202XX_FORCE is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
# CONFIG_IDEDMA_AUTO is not set
CONFIG_IDEDMA_IVB=y
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y
# CONFIG_BLK_DEV_ATARAID is not set
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set

Has anyone else with a Via chipset been able to boot into 2.5.x without having these interrupt problems? Any suggestions will be helpful.

Thanks.
                                   
-- 
**  Derek J Witt                                              **
*   Email: mailto:djw@flinthills.com                           *
*   Home Page: http://www.flinthills.com/~djw/                 *
*** "...and on the eighth day, God met Bill Gates." - Unknown **

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]