Brad Miele wrote:
Hi,
Last week, i cvsupped two HP Proliant DL380 G4 machines to the most
recent stable, which replaced the bge driver from mid may with the one
committed on or around June 24. Since updating, my cards, Broadcom
BCM5704C have been throwing occasional watchdog timeout errors
Mike Tancsa wrote:
At 08:25 PM 08/08/2005, O. Hartmann wrote:
Hello.
My box is a FreeBSD 6.0-BETA2 driven ASUS A8N-SLI Deluxe based AMD64
boxed (see dmesg).
One of my SATA disks, the SAMSUNG SP2004C seems to show errors during
operation (and also showd under 5.4-RELEASE-p3).
Sometimes I
I am stuck on getting this graphics card working with stable.
Attached are xorg.conf and Xorg.log.0. The versions are:
# uname -a
FreeBSD rubicon.york.ac.uk 5.4-STABLE FreeBSD 5.4-STABLE #0: Mon Aug 8
16:18:46 BST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386
# pkg_info -Ia |
On Mon, 2005-Aug-08 14:25:35 -1000, Randy Bush wrote:
my error. i hacked /etc/make.conf between build and install.
so i can use ed to unhack it, but when i try to install again
--
Making hierarchy
On Tue, Aug 02, 2005 at 12:22:02AM +0200, Tijl Coosemans wrote:
A couple days ago I updated my system and was excited to see cpufreq
and powerd in 5-stable. Since then however I noticed that my laptop
temperature is about 5°C higher than with est and estctrl. I found that
cpufreq when setting
Dear Member,
Thank you for your interest in our offer. Unfortunately your inquiry
was not received. We are very interested in hearing from you. If you
would like to contact our Member Services Team, please go to www.netflip.com
and click the Contact Us link. We will respond
to your inquiry
I got the following while trying to rsync a large number of files over
the network to a firewire HD (FAT32 FS) on a 6.0-BETA1 system.
Aug 9 12:48:17 inchoate kernel: firewire0: split transaction timeout
dst=0xffc0 tl=0x36 state=3
Aug 9 12:48:17 inchoate kernel: sbp_orb_pointer_callback:
Hi,
I've experineced serious errors with the nve driver and I've seen quite
many people would like to use it, but they also experiences these error.
There are open PR's and unfortunately nobody has volunteered to fix this
issue, the PR's have the default Responsible field, nobody has changed
Tijl Coosemans wrote:
A couple days ago I updated my system and was excited to see cpufreq
and powerd in 5-stable. Since then however I noticed that my laptop
temperature is about 5°C higher than with est and estctrl. I found that
cpufreq when setting 200MHz for example set the absolute
Section Device
Identifier Card0
Driver ati
#VendorName ATI Technologies Inc
#BoardName Radeon X800PRO
#BusID PCI:5:0:0
EndSection
...
(--) Assigning device section with no busID to primary device
(WW) RADEON: No matching Device section for
Yann Golanski wrote:
Yes, it gives me the same error. The warning changes the PCI slot to
PCI:5:0:0...
Anyway, I used an older card. It works. *shrugs*
Odd.. I've got an X800SE and it works without problems; don't think
there's so much of a difference concerning the Xorg driver with the
two
On Sun, Aug 07, 2005 at 06:51:09PM +0200, Petr Holub wrote:
Hi all,
I've encoutnered the follwing kernel panic on 5.4-RELEASE-p6. However,
as the machine is production and not development one, I don't have
debugger analysis. The panic might *theoretically* be due to problems
accessing
On Wed, Aug 03, 2005 at 08:47:43AM -0400, Derrick Edwards wrote:
???Hi all,
I decided to try and help with testing 6-BETA1, after updating sources and
recompiling i get the following during boot up. I am tried booting without
hyperthreading enabled in the bios and I still get the same panic.
You need to follow the instructions in the chapter on kernel debugging
in the developers handbook in order for anyone to be able to begin
investigating this.
I though that - alas at the time of the panic, that machine didn't have
dump partition configured. :(( Anyway, I've configured that
On Tue, Aug 09, 2005 at 07:22:39PM +0200, Petr Holub wrote:
You need to follow the instructions in the chapter on kernel debugging
in the developers handbook in order for anyone to be able to begin
investigating this.
I though that - alas at the time of the panic, that machine didn't have
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jung-uk Kim
Sent: Monday, August 08, 2005 2:29 PM
To: freebsd-stable@FreeBSD.org
Cc: Josh Endries
Subject: Re: twa0 errors and system lockup on amd64
On Monday 08 August 2005 05:03 pm, Josh Endries
O. Hartmann wrote:
[ ... ]
One of my SATA disks, the SAMSUNG SP2004C seems to show errors during
operation (and also showd under 5.4-RELEASE-p3).
Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Other
Chuck Swiger wrote:
O. Hartmann wrote:
[ ... ]
One of my SATA disks, the SAMSUNG SP2004C seems to show errors
during operation (and also showd under 5.4-RELEASE-p3).
Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still
fwiw, we gave up and are cold installing 6
randy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Post your dmesg output from boot.
If the SATA controller has a SII chipset, you're in trouble.
Get that board out of there - or if its on the motherboard, get something
else in there and use it instead.
SII chipsets were ok in 4.x, but the newer ATA code broke badly with them.
I've had a PR
On 8/9/05, Kris Kennaway [EMAIL PROTECTED] wrote:
On Wed, Aug 03, 2005 at 08:47:43AM -0400, Derrick Edwards wrote:
???Hi all,
I decided to try and help with testing 6-BETA1, after updating sources and
recompiling i get the following during boot up. I am tried booting without
Karl Denninger wrote:
SII chipsets were ok in 4.x, but the newer ATA code broke badly with them.
I've had a PR open on this since February, and many others have reported
similar issues. The problems still exist in the 6.x-BETA releases I've
checked out, and are in some cases MORE severe (for me
On Tue, 2005-08-09 at 09:57 +0100, Yann Golanski wrote:
I am stuck on getting this graphics card working with stable.
I had the same problem with the standard server port. Replacing it with
the xorg-server-snap port solved it. Seems these cards are just to new
for the stable release ;)
23 matches
Mail list logo
