I've had a possible idea regarding the NFS issues.
I'm wondering if perhaps my NFS issues are related to the other email
thread I have going which is the xl0: watchdog timeouts etc.
I had not noticed this until last week because it's not often I copy
large files from one machine to another but
Matt Smith wrote:
Matt Smith wrote:
Jimmy Selgen wrote:
On Fri, 2003-11-21 at 21:29, Kris Kennaway wrote:
On Fri, Nov 21, 2003 at 09:22:49PM +0100, Jimmy Selgen wrote:
I saw this with some of sam's locking changes that (temporarily) broke
DUMMYNET. I see you're using ipfilter - it's possible th
Matt Smith wrote:
Jimmy Selgen wrote:
On Fri, 2003-11-21 at 21:29, Kris Kennaway wrote:
On Fri, Nov 21, 2003 at 09:22:49PM +0100, Jimmy Selgen wrote:
I saw this with some of sam's locking changes that (temporarily) broke
DUMMYNET. I see you're using ipfilter - it's possible that this
configurati
On Fri, Nov 21, 2003 at 11:40:37PM +0100, Jimmy Selgen wrote:
> The box in question is my workstation, so I guess i'm not passing that
> much traffic through ipfilter. Also, when I said that the NIC still
> worked, I might have mislead you a bit. I had about 5-10 timeouts while
> scp'ing the dmesg
Jimmy Selgen wrote:
On Fri, 2003-11-21 at 21:29, Kris Kennaway wrote:
On Fri, Nov 21, 2003 at 09:22:49PM +0100, Jimmy Selgen wrote:
I saw this with some of sam's locking changes that (temporarily) broke
DUMMYNET. I see you're using ipfilter - it's possible that this
configuration has not been wel
On Fri, 2003-11-21 at 21:29, Kris Kennaway wrote:
> On Fri, Nov 21, 2003 at 09:22:49PM +0100, Jimmy Selgen wrote:
> I saw this with some of sam's locking changes that (temporarily) broke
> DUMMYNET. I see you're using ipfilter - it's possible that this
> configuration has not been well-tested. Ar
.org/cgi/getmsg.cgi?fetch=608457+0+archive/2003/freebsd-current/20031109.freebsd-current)
> Strange thing is that this worked perfectly with FreeBSD-5.1-RELEASE.
>
> The NIC still works, just get "xl0: watchdog timeout" every now and
> then.
I saw this with some of sam's loc
that this worked perfectly with FreeBSD-5.1-RELEASE.
The NIC still works, just get "xl0: watchdog timeout" every now and
then.
I'm attaching a full dmesg in case you know what to look for.
The hardware is :
AMD Barton 2800
Asus A7V8X Deluxe
1024 mb. DDR333 Ram (PC2700 ?)
Promise
Subject: RE: xl0 watchdog timeout,
On Tue, 04 Nov 2003 12:23:19 -0500 (EST), John Baldwin wrote:
> Try disabling ACPI. ACPI is unable to route any of your PCI interrupts,
I tried disabling ACPI. It works fine. Thanks John.
> so all your PCI interrupts are hosed. You can try to talk wi
On 04-Nov-2003 Shin-ichi Yoshimoto wrote:
> Subject: RE: xl0 watchdog timeout,
> On Tue, 04 Nov 2003 10:39:44 -0500 (EST), John Baldwin wrote:
>> Can you please provide a full dmesg?
>
> yes.
Try disabling ACPI. ACPI is unable to route any of your PCI interrupts,
so all y
Subject: RE: xl0 watchdog timeout,
On Tue, 04 Nov 2003 10:39:44 -0500 (EST), John Baldwin wrote:
> Can you please provide a full dmesg?
yes.
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of
On 04-Nov-2003 Shin-ichi Yoshimoto wrote:
> After cvsup and make world, I could't use xl0 and kernel said "kernel:
> xl0: watchdog timeout".
>
># dmesg
> [snip]
> xl0: <3Com 3c920B-EMB Integrated Fast Etherlink XL> port 0xe400-0xe47f
> mem 0xea
&g
On Tue, 4 Nov 2003, Shin-ichi Yoshimoto wrote:
> After cvsup and make world, I could't use xl0 and kernel said "kernel:
> xl0: watchdog timeout".
>
> # dmesg
> [snip]
> xl0: <3Com 3c920B-EMB Integrated Fast Etherlink XL> port 0xe400-0xe47f
> mem 0xea
&g
After cvsup and make world, I could't use xl0 and kernel said "kernel:
xl0: watchdog timeout".
# dmesg
[snip]
xl0: <3Com 3c920B-EMB Integrated Fast Etherlink XL> port 0xe400-0xe47f
mem 0xea
02-0xea02007f irq 10 at device 18.0 on pci0
xl0: Ethernet address: 00:04:75:
On Fri, Oct 10, 2003 at 08:33:01PM -0700, Kris Kennaway wrote:
> Since upgrading to -CURRENT last night I have been getting a lot of
> watchdog timeouts on my xl0 device every time I put it under load:
>
> citusc17# grep "watchdog timeout" messages | wc -l
> 44
>
> Oct 10 02:30:48 citusc17
Since upgrading to -CURRENT last night I have been getting a lot of
watchdog timeouts on my xl0 device every time I put it under load:
citusc17# grep "watchdog timeout" messages | wc -l
44
Oct 10 02:30:48 citusc17 kernel: xl0: <3Com 3c905B-TX Fast Etherlink XL> port
0xdc00-0xdc7f mem 0xff0
bus, which is fine, since that is the one
@ that appears to cause the trouble.
@
@
@ > -Original Message-
@ > From: Anil Jangity [SMTP:[EMAIL PROTECTED]]
@ > Sent: Wednesday, April 04, 2001 4:08 AM
@ > To: [EMAIL PROTECTED]
@ > Cc: [EMAIL PROTECTED]
@ > Subject:Mo
phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
cardbus1: Detaching card: no cards to detach!
pccbb1: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
xl0: watchdog timeout
xl0: watchdog timeout
xl0: no carrier - transceiver cable problem?
HINTS:
hint.fdc.0.at="isa"
hint.f
In message <[EMAIL PROTECTED]> Pierre DAVID writes:
: If nobody is using NEWCARD because of such warning, I wonder
: when NEWCARD will be functionnal for joe user. Be aware that
: I already tried the same NEWCARD kernel from a Sony Vaio and
: another Dell.
Maybe. But also there are known issues
host, but
nothing is received by the NEWCARD machine, which is typical
of an IRQ problem.
>
> > - with a 3Com 3CCFE575BT-D (xl0) - which works like
> > a charm with a Sony Vaio - I get lot of:
> > xl0: watchdog timeout
> > and all communications are slo
x27;s odd.
> - with a 3Com 3CCFE575BT-D (xl0) - which works like
> a charm with a Sony Vaio - I get lot of:
> xl0: watchdog timeout
> and all communications are sloow.
I smell an IRQ conflict.
--
wca
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &qu
21 matches
Mail list logo
