Hi,
Once again we cvsupped latest ATA code changes and nothing much
changed. Only after couple minutes of stress testing system will
freeze. Though error message is little different than before.
Tomppa
ad5: TIMEOUT - READ_DMA retrying (2 retries left)
ata2: resetting devices ..
ata2: reset t
Hi,
Current ATA code is still unusable unstable. We cvsupped latest
source yesterday and tried our standard stress test copy between two
vinum volumes. Once we even got 12 hour uptime but today it won't
take longer than couple minutes before system freezes. Situation is
even worse if we replace
Hi,
I'd like to give a try for this new code solving lost interrupts but
current code still doesn't find all my slave disks. Is there anything
what might help on this?
Tomppa
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinf
It seems Matteo Riondato wrote:
>
> It works perfectly and solves my problem.
> Thanks.
> Do you plan to commit it?
Already done :)
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
Il Mar, 2003-10-14 alle 15:09, Soren Schmidt ha scritto:
> It seems Matteo Riondato wrote:
> > After having update my -CURRENT box to yesterday afternoon (Central
> > Europe Time) sources, I can't get it to boot. It stops probing ata1:
> > GEOM: create disk ad0 dp=0xc4536a70
> >
> > I never had pr
From: Soren Schmidt <[EMAIL PROTECTED]>
Could you try this patch please:
Index: ata-queue.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-queue.c,v
retrieving revision 1.8
diff -u -r1.8 ata-queue.c
--- ata-queue.c 12 Oct 2003 12:38:03
Il Mar, 2003-10-14 alle 15:09, Soren Schmidt ha scritto:
> It seems Matteo Riondato wrote:
> >
> > I never had problem with ATAng before, so it is probably related to a
> > recent commit.
>
> Could you try this patch please:I
> Index: ata-queue.c
> ===
It seems Matteo Riondato wrote:
> After having update my -CURRENT box to yesterday afternoon (Central
> Europe Time) sources, I can't get it to boot. It stops probing ata1:
> GEOM: create disk ad0 dp=0xc4536a70
> ad0: 57259MB [116336/16/63] at ata0-master UDMA133
> GEOM: create disk ad1 dp=0xc4915
On Sat, 12 Feb 2000 20:57:44 +0100, Soren Schmidt writes:
> It seems Chris Radek wrote:
>
> > ad0: HARD READ ERROR blk# 0 status=51 error=04
> > ad0: reading primary partition table: error reading fsbn 0
>
> Try to disable the multi-sector stuff, that might be whats killing you..
>
> -Søren
I
It seems Chris Radek wrote:
>
> Hi,
>
> I have a group of Compaq LTE Elite 4/50CX laptops (486dx2/50, 24meg
> ram, two PCMCIA slots), on which I am attempting to install the
> 4.0 snapshot from 2209. Two of these machines report an IBM
> disk (this is `-v' transcribed by hand):
>
> ad0: A
It seems Thomas Veldhouse wrote:
>> Hmm, the WDC WD200BA disk does UDMA66 doesn't it ??
>> The VIA 82C686 has support for this, but its very "generous" in setting
>> it. Form the above I'd guess you dont have a 80lead cable on those
>> disks ?? What does the BIOS say about the disk modes on boot
On Fri, 17 Dec 1999, Soren Schmidt wrote:
>
> Hmm, the WDC WD200BA disk does UDMA66 doesn't it ??
> The VIA 82C686 has support for this, but its very "generous" in setting
> it. Form the above I'd guess you dont have a 80lead cable on those
> disks ?? What does the BIOS say about the disk mode
It seems Thomas T. Veldhouse wrote:
> I seem to be having a problem with the my Western Digital Caviar 6.4GB
> UDMA33
>
> ad0: ATA-4 disk at ata0 as master
> ad0: 19092MB (39102336 sectors), 38792 cyls, 16 heads, 63 S/T, 512 B/S
> ad0: 16 secs/int, 1 depth queue, UDMA33
> ad1: ATA-4 disk at at
On Wed, Dec 15, 1999 at 10:16:29PM +0100, D. Rock wrote:
> Hi,
>
> The ata driver tries to enable UDMA for my controller, but fails
> (this is no disk problem. The disks can do UDMA, as tested in
> another machine). Perhaps UDMA should be disabled for all
> VIA 82C586 chips:
I have two machines
It seems Andrew Gallatin wrote:
>
> Greg Childers writes:
> > Hello,
> >
> > Seems now is the time to raise problems with ATA, so here goes. I have used the
>ATA driver
> > since its introduction into -current without problem until recently. A kernel
>from October
> > 5 worked fine. No
Greg Childers writes:
> Hello,
>
> Seems now is the time to raise problems with ATA, so here goes. I have used the ATA
>driver
> since its introduction into -current without problem until recently. A kernel from
>October
> 5 worked fine. Now, it no longer works using ATA, but works f
Here's my fstab:
# DeviceMountpoint FStype Options DumpPass#
/dev/ad0s1b noneswapsw 0 0
/dev/ad1s1b noneswapsw 0 0
/dev/ad0s1a / ufs rw
Does your /etc/fstab have character devices listed or block devices ?
If it has character devices (aka raw devices), change them to block
(remove the 'r' at the front) e.g. change: "/dev/rad0s2a" to
"/dev/ad0s2a".
It seems to be only necessary for the root filesystem.
Some people (like me) chan
Hi,
With a bit of investigating, I've found the problem described in my previous email
quoted at
the end of this message started with the commits listed below. A kernel built using
sources just before these commits works fine, whereas a kernel build just after freezes
after the line
Mounting
19 matches
Mail list logo
