In message [EMAIL PROTECTED], Iva Hesy writes:
OK, now, I get the result:
tag=RELENG_6 date=2005.07.30.22.00.00 works fine, tag=RELENG_6
date=2005.07.31.03.00.00 makes noise, many many ethernet frames can
be sniffered.
the cvsup log:
Updating collection src-all/cvs
Edit src/sys/dev/mlx/mlx_pci.c
My system:
---
FreeBSD ..org 5.4-STABLE FreeBSD 5.4-STABLE #0:
Mon Aug 15 19:06:46 EDT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
The problem:
I ran cvsup with no problems. But then I ran portsdb and I get these
warnings:
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-freebsd-
[EMAIL PROTECTED] On Behalf Of bob self
Sent: Thursday, August 18, 2005 08:05
To: freebsd-stable@freebsd.org
Subject: portsdb (Warning: Duplicate INDEX)
My system:
---
FreeBSD ..org 5.4-STABLE
You can try downloading a new index:
cd /usr/ports
make fetchindex
Then run portsdb again.
Cheers
Benjamin
signature.asc
Description: OpenPGP digital signature
On Thu, Aug 18, 2005 at 09:04:38AM -0400, bob self wrote:
My system:
---
FreeBSD ..org 5.4-STABLE FreeBSD 5.4-STABLE #0:
Mon Aug 15 19:06:46 EDT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
The problem:
I ran cvsup with no problems. But
At 11:25 PM 8/17/2005, Huang wen hui wrote:
hi,
I have DELL PE4600 server with acc driver , running 5.4 Release.
when system boot, got this message:
Mounting root from ufs:/dev/aacd0s1a
aac0: **Monitor** ID(0:02:0); Error Event [command:0x2a]
aac0: **Monitor** ID(0:02:0); Hardware Error
I'm still having problems with my onboard ethernet.
It usually runs for a day or two and then I see this
in the dmesg:
...
nve0: device timeout (63)
nve0: link state changed to DOWN
nve0: link state changed to UP
nve0: device timeout (63)
nve0: link state changed to DOWN
nve0: link state changed
alan bryan wrote:
I'm still having problems with my onboard ethernet.
It usually runs for a day or two and then I see this
in the dmesg:
...
nve0: device timeout (63)
nve0: link state changed to DOWN
nve0: link state changed to UP
nve0: device timeout (63)
nve0: link state changed to DOWN
Forgot to also add the details of the Ethernet as it's
being detected if that helps:
nve0: NVIDIA nForce MCP9 Networking Adapter port
0xb000-0xb007 mem 0xd810-0xd8100fff irq 5 at
device 10.0 on pci0
nve0: Ethernet address 00:30:1b:b8:86:dc
miibus0: MII bus on nve0
ukphy0: Generic IEEE 802.3u
--- Kövesdán Gábor [EMAIL PROTECTED]
wrote:
The nve driver has a lot of problems. You
experienced just device
timeouts, but other people - including me -
experiences system crashes.
As for me, I've had two kind of kernel panics, and
device timeouts too.
Cheers,
Gabor Kovesdan
Do you
alan bryan wrote:
--- Kövesdán Gábor [EMAIL PROTECTED]
wrote:
The nve driver has a lot of problems. You
experienced just device
timeouts, but other people - including me -
experiences system crashes.
As for me, I've had two kind of kernel panics, and
device timeouts too.
Cheers,
Gabor
Yes,
This appears to be a mistake on my part, please commit this patch.
Thanks for catching this!
On Thu, Aug 18, 2005 at 09:59:50AM +0100, Ian Dowse wrote:
In message [EMAIL PROTECTED], Iva Hesy writes:
OK, now, I get the result:
tag=RELENG_6 date=2005.07.30.22.00.00 works fine,
Or if you want, I will commit it.
On Thu, Aug 18, 2005 at 09:59:50AM +0100, Ian Dowse wrote:
In message [EMAIL PROTECTED], Iva Hesy writes:
OK, now, I get the result:
tag=RELENG_6 date=2005.07.30.22.00.00 works fine, tag=RELENG_6
date=2005.07.31.03.00.00 makes noise, many many ethernet frames
Thank you very much for the reaction (about a dozen user reported similar
problems the last month -but there seems no answer/solution)
From what I can tell from the full card dump state, the 39320 attempted
to send 77 transactions to your drive during a single connection. This
connection
--On Friday, August 19, 2005 12:20 AM +0200 Hutterer Robert
[EMAIL PROTECTED] wrote:
Thank you very much for the reaction (about a dozen user reported similar
problems the last month -but there seems no answer/solution)
From what I can tell from the full card dump state, the 39320 attempted
I had (about) the same problem at a linux server at my work last weekend.
But is was not repeatable for me.
Maybe it contains some info which helps you.
Log: http://ronald.klop.ws/~ronald/linux.scsi.txt
Ronald.
On Fri, 19 Aug 2005 00:20:41 +0200, Hutterer Robert
[EMAIL PROTECTED] wrote:
On Fri, 19 Aug 2005 01:29:03 +0200, Ronald Klop
[EMAIL PROTECTED] wrote:
I had (about) the same problem at a linux server at my work last
weekend. But is was not repeatable for me.
Maybe it contains some info which helps you.
Log: http://ronald.klop.ws/~ronald/linux.scsi.txt
Forgot to
On 8/18/05, Ian Dowse [EMAIL PROTECTED] wrote:
There appear to be some braces missed in that revision of bpf.c. Does
the following patch help?
Ian
Thank you very much, your patch works fine for me...
___
freebsd-stable@freebsd.org mailing list
Hi,
I am new to FreeBSD.
Please let me know the setup steps to update from 5.4RELEASE to 5.4RELEASEP1.
Thanks,
-
Start your day with Yahoo! - make it your home page
___
freebsd-stable@freebsd.org
Hi all,
It is an 5.4-STABLE running on i386, date is about Aug 10 4am UTC.
When I'm doing:
cat /var/log/maillog | ./log.pl
to do some log analysis, I panicked this system.
Here are some console log and kgdb output. I'll keeping this dump
for sometime, so if anyone wants any information, feel free
20 matches
Mail list logo