thr3ads.net - freebsd stable - dc0: watchdog timeout and nve0: device timeout [Jan 2006]

If this information is useful, please help other people find it:
Share via:

Anish Mistry

2006-Jan-31 00:12 UTC

dc0: watchdog timeout and nve0: device timeout

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
    root@kevin.united-ware.com:/usr/obj/usr/src/sys/KEVIN
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 2800+ (1808.26-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0xf4a  Stepping = 10
  
Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
  AMD Features=0xe0500800<SYSCALL,NX,MMX+,LM,3DNow+,3DNow>
real memory  = 535691264 (510 MB)
avail memory = 508751872 (485 MB)
ACPI APIC Table: <nVidia AWRDACPI>
ioapic0 <Version 1.1> irqs 0-23 on motherboardnfiguration
acpi0: <nVidia AWRDACPI> on motherboardal/share/config/kdm/kdmrc (from 
kde >= 2.  acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 2.3)
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0???????????????
agp0: <NVIDIA nForce3-250 AGP Controller> mem 0xf0000000-0xf7ffffff at 
device 0.0 on pci0                                    ?      ______
isab0: <PCI-ISA bridge> at device 1.0 on pci0    |  ____| __ ___  ___ 
isa0: <ISA bus> on isab0reeBSD!            ?     | |__ | '__/ _ \/ _ \
pci0: <serial bus, SMBus> at device 1.1 (no driver attached)  __/  __/
pci0: <serial bus, USB> at device 2.0 (no driver attached) |    |    |
pci0: <serial bus, USB> at device 2.1 (no driver attached)  \___|\___|
pci0: <serial bus, USB> at device 2.2 (no driver attached)____ _____
pci0: <bridge> at device 5.0 (no driver attached)|  _ \ / ____|  __ \
pcm0: <nVidia nForce3 250> port 0xf600-0xf6ff,0xfb00-0xfb7f mem 
0xfebfb000-0xfebfbfff irq 11 at device 6.0 on pci0 logging   ?     |  
_ < \___ \| |  | |
pcm0: <Avance Logic ALC655 AC97 Codec>     ?     | |_) |____) | |__| |
atapci0: <nVidia nForce3 Pro UDMA133 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf900-0xf90f at device 8.0 on 
pci0?     |____/|_____/|_____/
ata0: <ATA channel 0> on atapci0           ?
ata1: <ATA channel 1> on atapci0           ?
pcib1: <ACPI PCI-PCI bridge> at device 11.0 on pci0
pci1: <ACPI PCI bus> on pcib1r default     ?
pci1: <display, VGA> at device 0.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> at device 14.0 on pci0
pci2: <ACPI PCI bus> on pcib2
dc0: <LC82C115 PNIC II 10/100BaseTX> port 0xde00-0xdeff mem 
0xfeaff000-0xfeaff0ff irq 11 at device 3.0 on pci2
miibus0: <MII bus> on dc0
dcphy0: <Intel 21143 NWAY media interface> on miibus0
dcphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc0: Ethernet address: 00:a0:cc:37:02:bf
acpi_tz0: <Thermal Zone> on acpi0
nve0: <NVIDIA nForce MCP7 Networking Adapter> port 0xfc00-0xfc07 mem 
0xfebfc000-0xfebfcfff irq 10 at device 5.0 on pci0
nve0: Ethernet address 00:30:18:a4:37:7c
miibus1: <MII bus> on nve0
ciphy0: <Cicada CS8201 10/100/1000TX PHY> on miibus1
ciphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
nve0: Ethernet address: 00:30:18:a4:37:7c
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 
on acpi0
sio0: type 16550A, console
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0: <ECP parallel printer port> port 0x378-0x37f,0x778-0x77b irq 7 
drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <Parallel port bus> on ppc0
ppi0: <Parallel I/O> on ppbus0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcf7ff,0xd0000-0xd17ff on 
isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on 
isa0
Timecounter "TSC" frequency 1808256838 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 38162MB <WDC WD400BB-23FJA0 13.03G13> at ata0-master UDMA100
ad1: 32253MB <HDS728080PLAT20 PF2OA21B> at ata0-slave UDMA133
acd0: CDRW <BENQ CDRW 5232X/KPEY> at ata1-master UDMA33
cd0 at ata1 bus 0 target 0 lun 0
cd0: <BENQ CDRW 5232X KPEY> Removable CD-ROM SCSI-0 device 
cd0: 33.000MB/s transfers
cd0: cd present [1 x 2048 byte records]
-- 
Anish Mistry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060131/e99ed254/attachment.bin

Gleb Smirnoff

2006-Jan-31 00:32 UTC

head link

dc0: watchdog timeout and nve0: device timeout

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 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.

-- 
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE

Peter Pentchev

2006-Jan-31 03:27 UTC

head link

dc0: watchdog timeout and nve0: device timeout

On Tue, 31 Jan 2006 11:30:02 +0300, Gleb Smirnoff wrote:> 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 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 was disabled for some reason.

Warner, is there a reason for hiding the "Try to re-route interrupts"
code behind an apparently "ifdef 0" case?  Well, okay, most probably
there is a reason, since you've done it, but... it breaks my re0 card
and it also seems to break Anish's hardware :)

BTW, the commit message was not quite correct - rev. 1.302 was not
really merged, it's included in my patch here.  Also, rev. 1.305 of
pci.c seems to have more than just adding the PCI_FIND_EXTCAP method -
there are a couple of offset fixes that I also included in the patch
while trying to come as close to the -CURRENT code as possible; could
you check if they actually apply to -STABLE?

Anyway, here's a patch that fixes it for me, although most probably
the __PCI_REROUTE_INTERRUPT chunk should be sufficient.  Warner, if
you want more details, I could help with debugging this - on my
system, the re0 card definitely needs this rerouting.  I've posted
some verbose boot output with explanations at
http://people.FreeBSD.org/~roam/pcirouting/
The patch itself is also there in case it gets munged by the mail
swervers along the way.

Index: src/sys/dev/pci/pci.c
==================================================================RCS file:
/home/ncvs/src/sys/dev/pci/pci.c,v
retrieving revision 1.292.2.6
diff -u -r1.292.2.6 pci.c
--- src/sys/dev/pci/pci.c	30 Jan 2006 18:42:10 -0000	1.292.2.6
+++ src/sys/dev/pci/pci.c	31 Jan 2006 10:57:32 -0000
@@ -428,7 +428,7 @@
 		ptrptr = PCIR_CAP_PTR;
 		break;
 	case 2:
-		ptrptr = 0x14;
+		ptrptr = PCIR_CAP_PTR_2;
 		break;
 	default:
 		return;		/* no extended capabilities support */
@@ -447,10 +447,10 @@
 		}
 		/* Find the next entry */
 		ptr = nextptr;
-		nextptr = REG(ptr + 1, 1);
+		nextptr = REG(ptr + PCICAP_NEXTPTR, 1);

 		/* Process this entry */
-		switch (REG(ptr, 1)) {
+		switch (REG(ptr + PCICAP_ID, 1)) {
 		case PCIY_PMG:		/* PCI power management */
 			if (cfg->pp.pp_cap == 0) {
 				cfg->pp.pp_cap = REG(ptr + PCIR_POWER_CAP, 2);
@@ -1040,7 +1040,8 @@
 	}

 	if (cfg->intpin > 0 && PCI_INTERRUPT_VALID(cfg->intline)) {
-#ifdef __PCI_REROUTE_INTERRUPT
+#if defined(__ia64__) || defined(__i386__) || defined(__amd64__) || \
+		defined(__arm__) || defined(__alpha__)
 		/*
 		 * Try to re-route interrupts. Sometimes the BIOS or
 		 * firmware may leave bogus values in these registers.

Hope this helps!

G'luck,
Peter

-- 
Peter Pentchev	roam@ringlet.net    roam@cnsys.bg    roam@FreeBSD.org
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
"yields falsehood, when appended to its quotation." yields falsehood,
when appended to its quotation.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060131/8ac48147/attachment.bin

Daniel Eriksson

2006-Jan-31 04:18 UTC

head link

dc0: watchdog timeout and nve0: device timeout

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. The
only disks found are those hooked up to the on-board ATA controller.

Also, after rebooting the machine the BIOS on the Promise SATA card
fails to detect the disks. A power-toggle brings the disks back in BIOS,
and backing down to the old kernel brings them back in the OS.

/Daniel Eriksson

freebsd stable - Jan 2006 - dc0: watchdog timeout and nve0: device timeout

dc0: watchdog timeout and nve0: device timeout

dc0: watchdog timeout and nve0: device timeout

dc0: watchdog timeout and nve0: device timeout

dc0: watchdog timeout and nve0: device timeout