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
On Fri, Nov 21, 2003 at 09:22:49PM +0100, Jimmy Selgen wrote:
> Hi
>
> I'm getting some strange xl0 timeout messages on 5.1-CURRENT (synced
> today).
>
> I've searched the archives, and it seems that this problem is related to
> ACPI
> (http://docs.freebsd.org/cgi/getmsg.cgi?fetch=608457+0+archiv
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
> 02-0xea02007f irq 10 at device 18.0 on pci0
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
> 02-0xea02007f irq 10 at device 18.0 on pc
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
12 matches
Mail list logo
