From grg@koch2.pikenet.ru  Tue Mar 28 09:32:12 2000
Return-Path: <grg@koch2.pikenet.ru>
Received: from koch2.pikenet.ru (koch2.pikenet.ru [194.135.17.184])
	by hub.freebsd.org (Postfix) with ESMTP id 4659D37C01B
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 28 Mar 2000 09:31:57 -0800 (PST)
	(envelope-from grg@koch2.pikenet.ru)
Received: (from grg@localhost)
	by koch2.pikenet.ru (8.9.3/8.9.2) id VAA01315;
	Tue, 28 Mar 2000 21:31:57 +0400 (MSD)
	(envelope-from grg)
Message-Id: <200003281731.VAA01315@koch2.pikenet.ru>
Date: Tue, 28 Mar 2000 21:31:57 +0400 (MSD)
From: grg@philol.msu.ru
Sender: grg@koch2.pikenet.ru
Reply-To: grg@philol.msu.ru
To: FreeBSD-gnats-submit@freebsd.org
Subject: 3.4 to 4.0 upgrade: ATAPI drivers damage the filesystem
X-Send-Pr-Version: 3.2

>Number:         17643
>Category:       kern
>Synopsis:       3.4 to 4.0 upgrade: ATAPI drivers damage the filesystem
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    sos
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 28 09:40:01 PST 2000
>Closed-Date:    Tue Nov 14 00:19:28 PST 2000
>Last-Modified:  Tue Nov 14 00:21:04 PST 2000
>Originator:     Grigoriy Strokin
>Release:        FreeBSD 3.4-STABLE i386
>Organization:
Moscow University
>Environment:

>Description:

 I have CVSuped the 4.0-STABLE sources on Mar 20.
 I have upgraded one 3.4-STABLE machine without any problems,
 and today wanted to upgrade another.
 I've made buildworld, buildkernel, installkernel.

 During the boot I've seen:

 Mar 28 17:48:56 koch2 /kernel: ata0: at 0x1f0 irq 14 on atapci0
 Mar 28 17:48:56 koch2 /kernel: ata0: at 0x1f0 irq 14 on atapci0
 Mar 28 17:49:07 koch2 /kernel: ed0: <Longshine LCS-8634P Ethernet Card
 Mar 28 17:49:07 koch2 /kernel: > at port 0x240-0x25f iomem 0xc0000-0xc003f irq 11 on isa0
 Mar 28 17:49:07 koch2 /kernel: ed0: supplying EUI64: 08:00:00:ff:fe:00:10:37
 Mar 28 17:49:07 koch2 /kernel: ed0: address 08:00:00:00:10:37, type NE2000 (16 bit) 
 ...
 Mar 28 17:49:07 koch2 /kernel: ed0: starting DAD for fe80:0001::0a00:00ff:fe00:1037
 Mar 28 17:49:07 koch2 /kernel: ed0: DAD complete for fe80:0001::0a00:00ff:fe00:1037 - no duplicates found
 Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
 Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
 Mar 28 17:49:07 koch2 /kernel: ad0: WRITE command timeout - resetting
 Mar 28 17:49:07 koch2 /kernel: ata0: resetting devices .. done
 Mar 28 17:49:11 koch2 /kernel: ed0: device timeout
 Mar 28 17:49:26 koch2 last message repeated 2 times
 Mar 28 17:49:48 koch2 /kernel: ad0: WRITE command timeout - resetting
 Mar 28 17:49:48 koch2 /kernel: ata0: resetting devices .. done
 Mar 28 17:50:23 koch2 /kernel: ed0: device timeout

Two strange thing here: ed0 timeout and ad0 timeout.

The booting process continued. 

Despite that fact that ed0 was detected,
"ifconfig ed0" gave "interface does not exist"
(also, note the 'ed0 device timeout' messages above)

Then I shut down the machine
and turned it off and on again, just in case there were
real minor problem with hardware.

Second boot:

fsck says about /usr "UNEXPECTED INCONSISTENCY, RUN FSCK MANUALLY".

After running fsck -y several times quite a few files
have been either deleted or moved to lost+found.
/usr/local and my home directory disappeared.

Then I rebooted again in order to turn 'UDMA' off in BIOS.

And again I've seen 'ad0: WRITE command timeout - resetting'
messages, and again /usr became damaged, which resulted
in loss of many other files and directories. About
2/3 of /usr is lost.

I restored parts of /usr and now this machine is again
on 3.4, without any hardware problems neither with 
HDD nor network card.

>How-To-Repeat:


>Fix:

I think I don't know where to look for source of the problem.


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->sos 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Wed Mar 29 03:02:52 PST 2000 
Responsible-Changed-Why:  
Over to the ata maintainer. 

From: Grigoriy Strokin <grg@philol.msu.ru>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/17643: 3.4 to 4.0 upgrade: ATAPI drivers damage the filesystem
Date: Wed, 29 Mar 2000 18:19:20 +0400

 I want to add that I use the chipset
 detected as 
 
    pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0
 
 
 Several other users wrote to freebsd-stable mail-list
 about the same problem with this chipset.
 
 -- 
 === Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
 === contact info: http://isabase.philol.msu.ru/~grg/     ===
 

From: Grigoriy Strokin <grg@philol.msu.ru>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: kern/17643: 3.4 to 4.0 upgrade: ATAPI drivers damage the filesystem
Date: Sat, 22 Apr 2000 18:37:17 +0400

 Further details:
 
 When I use sysctl -w hw.atamodes=pio,pio,pio,pio, 
 I live with 4.0 quite happily, but sometimes see
 a strange FreeBSD behaviour:
    1) sometimes, after a clean shutdown, 
       there is a message
         WARNING: / was not properly dismounted
    2) sometimes, just after the message 
       'mounting root from ufs:/dev/ad0s3a'
       I see '/sbin/iu4yefbkljhf: not found,
       'iu4yefbkljhf' is varying random string.
       The system doesn't go multi-user in such cases.
       Then I turn the machine off and on again,
       and the system boots fine
    I suppose that some nasty things happen to happen
    just after the kernel is booted and
    before sysctl -w hw.atamodes=pio,pio,pio,pio
    from /etc/rc is executed, and also
    during the system shutdown.
 
    They happen seldom, but they do.
 
 
 
 -- 
 === Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
 === contact info: http://isabase.philol.msu.ru/~grg/     ===
 
State-Changed-From-To: open->closed 
State-Changed-By: sos 
State-Changed-When: Tue Nov 14 00:19:28 PST 2000 
State-Changed-Why:  

Problems with the VIA 586 chipset should be fixed in 4.2 and later. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=17643 
>Unformatted:
