From: Steve Ames [EMAIL PROTECTED]
Anyone tried going forward to 1.8?
Same result for me as with 1.7. I've just grabbed 1.6 and am rebuilding to
confirm that that's the last working version for me too.
Please DO NOT send me ANY email directly unless it's a privacy issue.
Reply-to
From: Rob MacGregor [EMAIL PROTECTED]
Same result for me as with 1.7. I've just grabbed 1.6 and am rebuilding to
confirm that that's the last working version for me too.
Backing out to 1.6 fixes the problem for me too...
Please DO NOT send me ANY email directly unless it's a privacy issue.
I've got a lock order reversal.
#uname -a
FreeBSD barleycoren.oikumene.gcd.org 5.1-CURRENT FreeBSD 5.1-CURRENT #1:
Tue Sep 23 21:37:42 JST 2003
[EMAIL PROTECTED]:/build/usr/src/sys/BARLEYCOREN i386
Oct 11 18:14:53 barleycoren kernel: 1st 0xc082f060 system map (system map)
@
I have a board Asus A7N8X...
I often receive the following error (I disabled DMA access now from
sysctl) Any ideas? or who should receive this information so that it might
be fixed. This same machine was working nicely with a previous version of
5.x-current
ad4: TIMEOUT_WRITE_DMA retrying (2
ad4: WARNING - WRITE_MUL write data underrun 81922048
ad4: TIMEOUT - WRITE_MUL retrying (2 retries left)
ata2: resetting devices ..
GEOM: destroy disk ad4 dp=0xc5b4b470
ad4: WARNING - removed from configuration
done
ata2-master: FAILURE - WRITE_MUL device lockup/removed
Now when I disabled the
It seems Dan Nelson wrote:
In the last episode (Oct 08), Robert Ferguson said:
I see this problem as well. I'm running on a T40, with a DVD/CDRW in
the ultrabay, and -CURRENT as of this morning. At boot, it hangs
immediately after
ad0: 35174MB IC25N040ATCS05-0 [71465/16/63] at
Hi all,
Quick question: Is there an official way of changing ATA modes on
boot/startup? I grepped my /etc/rc.d (5.1-R) for 'atacontrol' and did a
quick search of the archives, but both came up empty, so I'm guessing
there isn't.
I'm quite happy to write up an rc script for it, but I figured
It seems Johny Mattsson wrote:
Hi all,
Quick question: Is there an official way of changing ATA modes on
boot/startup? I grepped my /etc/rc.d (5.1-R) for 'atacontrol' and did a
quick search of the archives, but both came up empty, so I'm guessing
there isn't.
I'm quite happy to write
Soren Schmidt wrote:
You can control the ATA driver boot behavior in loader.conf with these:
hw.ata.atapi_dma=1
Doh. I can't believe I'd forgotten about that knob. Thanks for jogging
my memory - it worked like a charm! :)
Cheers,
/Johny
--
Johny Mattsson - System Designer ,-. ,-. ,-. There
-- Forwarded message --
Date: Mon, 13 Oct 2003 11:29:22 +0300 (WET)
From: Evren Yurtesen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: latest current problems... more
ad4: WARNING - WRITE_MUL write data underrun 81922048
ad4: TIMEOUT - WRITE_MUL retrying (2 retries left)
[ On Monday, October 13, Marius Strobl wrote: ]
And
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/57611
The latter is a bit more detailed and correct (it's not limited to ATAPI
burners). It also doesn't seem to be limited to cdrecord, the latest
ntpd also causes a panic when using
On Mon, Sep 15, 2003 at 02:16:47PM -0700, Nate Lawson wrote:
njl 2003/09/15 14:16:47 PDT
FreeBSD src repository
Modified files:
sys/dev/sound/pciich.c
Log:
Correctly reset ich[3-5] sound cards on resume. This fixes audio playback
after suspend/resume for me.
After installing a newly cvsupped freebsd 5.x-current
I started to receive the following message and had a few panics etc.
initiate_write_filepage: already started
Here is my dmesg output
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992,
Hi all,
dmesg doesn't show anything unusual but trying to mount disks known to be good
results in mount: /dev/fd0: Input/output error.
Also fdformat does not work. It shows me every sector bad.
Btw: How can I format a floppydisk in a USB-drive? fdformat /dev/da0 doesn't
work.
The USB-drive is
From: Soren Schmidt [EMAIL PROTECTED]
Date: Sat, 11 Oct 2003 21:08:30 +0200 (CEST)
Sender: [EMAIL PROTECTED]
It seems Antony T Curtis wrote:
Does your laptop have an Acer chipset? There are issues with them, I
have a similar problem on my fujitsu.
The Acer bug has been resolved,
From: Sam Leffler [EMAIL PROTECTED]
Date: Sun, 12 Oct 2003 11:56:53 -0700
Sender: [EMAIL PROTECTED]
On Sunday 12 October 2003 11:03 am, Andre Guibert de Bruet wrote:
On Sun, 12 Oct 2003, Josef Karthauser wrote:
On Sun, Oct 12, 2003 at 02:48:01PM +0200, Soren Schmidt wrote:
It seems
On Mon, 13 Oct 2003, Mark Santcroos wrote:
On Mon, Sep 15, 2003 at 02:16:47PM -0700, Nate Lawson wrote:
njl 2003/09/15 14:16:47 PDT
FreeBSD src repository
Modified files:
sys/dev/sound/pciich.c
Log:
Correctly reset ich[3-5] sound cards on resume. This
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Sun, 12 Oct 2003, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Nate Lawson [EMAIL PROTECTED] writes:
: I am very interested in our idle load characteristics. It seems
: most systems I've analyzed have an average idle interrupt rate of about
: 225 per second, dominated
On Sunday 12 October 2003 23:21, Jeff Roberson wrote:
I commited a fix that would have caused all of the jerky behaviors under
some load. I was not able to reproduce this problem with kde running
afterwards.
Thanks for the fix! However, the problem is still here for me (using rev.
1.58). I
On Mon, 13 Oct 2003, Arjan van Leeuwen wrote:
On Sunday 12 October 2003 23:21, Jeff Roberson wrote:
I commited a fix that would have caused all of the jerky behaviors under
some load. I was not able to reproduce this problem with kde running
afterwards.
Thanks for the fix! However, the
On Mon, Oct 13, 2003 at 09:47:45AM -0700, Nate Lawson wrote:
It looks like you are resetting the BARs on resume. If that's all that's
needed, I believe Warner was working on code to do this in the general
case.
Exactly, the thread[*] went on about pci power transitions in general. Warner
also
Backing out the most recent checkin to sys/dev/ata/ata-queue.c (i.e.
reverting to version 1.6) makes the problem go away.
I upgraded from an Oct 1 - Oct 12 kernel and saw the same hang.
Backing out r1.6 fixed it for me too.
Anyone tried going forward to 1.8?
I just tried 1.8, it
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how to make
/usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop
On Monday 13 October 2003 21:27, Jeff Roberson wrote:
On Mon, 13 Oct 2003, Arjan van Leeuwen wrote:
On Sunday 12 October 2003 23:21, Jeff Roberson wrote:
I commited a fix that would have caused all of the jerky behaviors
under some load. I was not able to reproduce this problem with kde
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports
On Tue, 14 Oct 2003, Arjan van Leeuwen wrote:
On Monday 13 October 2003 21:27, Jeff Roberson wrote:
On Mon, 13 Oct 2003, Arjan van Leeuwen wrote:
On Sunday 12 October 2003 23:21, Jeff Roberson wrote:
I commited a fix that would have caused all of the jerky behaviors
under some load.
On Mon, Oct 13, 2003 at 03:51:06PM -0700, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how to
Eric Anholt wrote:
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
On Mon, 2003-10-13 at 16:05, Peter Wemm wrote:
Eric Anholt wrote:
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds,
Peter == Peter Wemm [EMAIL PROTECTED] writes:
Peter David Gilbert wrote:
I don't really have a clue where to look for this fix as there
seems to be a serious amount of magic going into the divided
XFree86-4 port builds, but my XFree86-4-clients port fails saying:
make: don't know how to
Peter == Peter Wemm [EMAIL PROTECTED] writes:
Peter Eric Anholt wrote:
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: David Gilbert
wrote: I don't really have a clue where to look for this fix as
there seems to be a serious amount of magic going into the
divided XFree86-4 port builds,
On Mon, 2003-10-13 at 14:54, David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how to make
[ On Monday, October 13, Marius Strobl wrote: ]
And
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/57611
The latter is a bit more detailed and correct (it's not limited to ATAPI
burners). It also doesn't seem to be limited to cdrecord, the latest
ntpd also causes a panic when using
In message: [EMAIL PROTECTED]
Nate Lawson [EMAIL PROTECTED] writes:
: Given that, my biggest concern now is IO corruption. Are there any
: devices that have a low interrupt rate (or bus mastering rate) that cannot
: handle a few hundred us latency added to their handler startup? I'm
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Gang,
The rijndael code causes an unaligned reference prior to init(8). Sources
as of today. Please fix:
:
Timecounter ITC frequency 800025984 Hz quality 0
Timecounters tick every 10.000 msec
fatal kernel trap (cpu 0):
trap vector = 0x1e (Unaligned Reference)
cr.iip =
38 matches
Mail list logo
