On 06/01/2010 14:56, Daniel Bolgheroni wrote:
(I don't know what's happening but my message isn't getting the mailing
list. Third try.)
Hi,
Your messages are reaching the list. However, the date/time of your
computer is incorrectly set:
for ; Tue, 5 Jan 2010 08:56:52 -0700 (MST)
Date: Wed,
(I don't know what's happening but my message isn't getting the mailing
list. Third try.)
Hi,
running -current, I'm having what it is not a problem at all, but at
least a very, very annoying behaviour.
I'm getting a lot of console messages with "bge0: watchdo
Hi,
running -current, I'm having what it is not a problem at all, but at
least an annoying behaviour.
I'm getting a lot of console messages with "bge0: watchdog timeout --
resetting". It's annonying because everytime the nic resets, the
machine locks ~1 min or mo
quot; rev 1.10/8.02 addr 2
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
wsdisplay0: screen 6 added (80x25bf, vt100 emulation)
wsdisplay0: screen 7 added (80x25bf, vt100 emulation)
wsdisplay0: screen 8 added (80x25bf, vt100 emulation)
wsdisplay0: screen 9 added (80x50bf, vt100 emulation)
bge0: watchdog timeout -- resetting
Salut,
On Wed, Aug 29, 2007 at 02:23:04PM -0700, Tom Bombadil wrote:
> So, basically all we can do is just avoid the 5704s, right?
Well, I can't tell you for 100% if it is that bug or a simple driver
problems. It's just the symptoms which I know very well from prior
experiences with 5704/5705 bas
> The 5704 has a particularly crappy DMA controller. This might be the usual
> problems of the bge hardware. Not only does it support only one DMA transfer
> in parallel, it also jams for some times, and if it has a particularly bad
> day, it jams the bus, too.
>
> There might be a description on
Salut,
On Wed, Aug 29, 2007 at 11:09:34AM -0700, Tom Bombadil wrote:
> I'm getting a few "bge0: watchdog timeout -- resetting" errors on
4.1-stable
>
> The box becomes unresponsive for a minute or so, and then comes back to
> life.
>
> bge0 at pci3 dev 0 functi
Greetings...
I'm getting a few "bge0: watchdog timeout -- resetting" errors on 4.1-stable
The box becomes unresponsive for a minute or so, and then comes back to
life.
Any hints?
Thanks,
g.
# dmesg
OpenBSD 4.1-stable (GENERIC.MP) #0: Mon Aug 27 11:04:17 UTC 2007
[EMAIL PROT
Karl Kopp wrote:
She just hung again - I reverted to the orig /bsd file and rebooted
You may or may not already have done that and it may not be of any help
what so ever to you.
But on my IBM 326e I had the same problem with the bge0 where my server
just freeze and nothing on the screen, et
She just hung again - I reverted to the orig /bsd file and rebooted
# dmesg
OpenBSD 3.9-current (GENERIC) #500: Sun Apr 9 01:37:11 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC
Will let you know how I go...
On 6/9/06, Brad <[EMAIL PROTECTED]> wrote:
Please try a UP ker
MP = yes
# dmesg
OpenBSD 3.9-current (GENERIC.MP) #770: Sun Apr 9 01:47:42 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1073274880 (1048120K)
avail mem = 908345344 (887056K)
using 22937 buffers containing 107536384 bytes (105016K) of memory
mainbus0 (root)
Hi! We recently moved from a Cisco based router to OpenBSD and have
been wrapped. The only issue is that recently, every 2 days or so, the
OBSD 3.9 router stops moving packets and has to be rebooted. The
system is an dual AMD 64 with
The console reports "bge0: Watchdog timeout"
T
12 matches
Mail list logo
