-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Damian Gerow wrote:
Thus spake O. Hartmann ([EMAIL PROTECTED]) [22/05/06 20:23]:
: Is there a solution on its way? What is about the Berkeley native nfe-code?
As someone already pointed out, the fix is already in -CURRENT. A patch for
-STABLE
After updating to STABLE today I'm getting the following message with
my dc and nve NICs every few seconds. UP, AMD64. A kernel from last
Thursday was fine.
dc0: watchdog timeout
nve0: device timeout (4)
FreeBSD 6.0-STABLE #9: Mon Jan 30 20:21:17 UTC 2006
[EMAIL PROTECTED]:/usr/obj/usr
On Tue, Jan 31, 2006 at 03:08:03AM -0500, Anish Mistry wrote:
A After updating to STABLE today I'm getting the following message with
A my dc and nve NICs every few seconds. UP, AMD64. A kernel from last
A Thursday was fine.
A
A dc0: watchdog timeout
A nve0: device timeout (4)
Can you try
.
A
A dc0: watchdog timeout
A nve0: device timeout (4)
Can you try to backout the code in sys/dev/pci to Thursday? If this
doesn't help, you probably need to do a binary search in this small
timeframe.
I think I found the problem - the merge was not quite correct, and
the PCI interrupt rerouting
Here's sort of a me-too post:
After upgrading STABLE from about a week ago to sources from this
morning, all disks connected to PCI cards (Promise PDC20318 SATA150
controller + ITE IT8212F UDMA133 controller) fail to show up during
boot. The cards are properly identified, but no disks are found.
and nve NICs every few seconds. UP, AMD64. A kernel from last
: A Thursday was fine.
: A
: A dc0: watchdog timeout
: A nve0: device timeout (4)
:
: Can you try to backout the code in sys/dev/pci to Thursday? If this
: doesn't help, you probably need to do a binary search in this small
