Opened 10 years ago
Closed 7 years ago
#11953 closed bug (no change required)
[ipro1000] driver resets, and becomes unusable
Reported by: | jessicah | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Network/ipro1000 | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Section of syslog where the driver gets into a messed up state prior to rebooting:
KERN: low resource address space: normal -> note KERN: low resource address space: note -> normal KERN: bfs: bfs_read_link:1531: Invalid Argument KERN: [ipro1000] (em) Watchdog timeout -- resetting KERN: [ipro1000] (em) Queue(0) tdh = 308, hw tdt = 315 KERN: [ipro1000] (em) TX(0) desc avail = 1017,Next TX to Clean = 308 KERN: [ipro1000] (em) Link is Down KERN: /dev/net/ipro1000/0: media change, media 0x20 quality 1000 speed 1000000000 KERN: [ipro1000] (em) Link is up 1000 Mbps Full Duplex KERN: /dev/net/ipro1000/0: media change, media 0x900030 quality 1000 speed 1000000000 DAEMON 'DHCP': /dev/net/ipro1000/0: Send DHCP_REQUEST for 10.20.30.18 to 255.255.255.255:67 DAEMON 'DHCP': /dev/net/ipro1000/0: Timeout shift: 8 secs (try 1) DAEMON 'DHCP': /dev/net/ipro1000/0: Send DHCP_REQUEST for 10.20.30.18 to 255.255.255.255:67 DAEMON 'DHCP': /dev/net/ipro1000/0: Timeout shift: 16 secs (try 2) DAEMON 'DHCP': /dev/net/ipro1000/0: Send DHCP_REQUEST for 10.20.30.18 to 255.255.255.255:67 KERN: [ipro1000] (em) Watchdog timeout -- resetting KERN: [ipro1000] (em) Queue(0) tdh = 0, hw tdt = 3 KERN: [ipro1000] (em) TX(0) desc avail = 1021,Next TX to Clean = 0 KERN: [ipro1000] (em) Link is Down KERN: /dev/net/ipro1000/0: media change, media 0x20 quality 1000 speed 1000000000 KERN: [ipro1000] (em) Link is up 1000 Mbps Full Duplex KERN: /dev/net/ipro1000/0: media change, media 0x900030 quality 1000 speed 1000000000 DAEMON 'DHCP': /dev/net/ipro1000/0: Timeout shift: 32 secs (try 3) DAEMON 'DHCP': /dev/net/ipro1000/0: Send DHCP_REQUEST for 10.20.30.18 to 255.255.255.255:67 KERN: bfs: bfs_open_dir:1644: Not a directory KERN: [ipro1000] (em) Watchdog timeout -- resetting KERN: [ipro1000] (em) Queue(0) tdh = 0, hw tdt = 11 KERN: [ipro1000] (em) TX(0) desc avail = 1013,Next TX to Clean = 0 KERN: [ipro1000] (em) Link is Down KERN: /dev/net/ipro1000/0: media change, media 0x20 quality 1000 speed 1000000000 KERN: [ipro1000] (em) Link is up 1000 Mbps Full Duplex KERN: /dev/net/ipro1000/0: media change, media 0x900030 quality 1000 speed 1000000000 KERN: low resource address space: normal -> note DAEMON 'DHCP': /dev/net/ipro1000/0: Timeout shift: 64 secs (try 4) DAEMON 'DHCP': /dev/net/ipro1000/0: Send DHCP_REQUEST for 10.20.30.18 to 255.255.255.255:67 KERN: [ipro1000] (em) Watchdog timeout -- resetting KERN: [ipro1000] (em) Queue(0) tdh = 0, hw tdt = 12 KERN: [ipro1000] (em) TX(0) desc avail = 1012,Next TX to Clean = 0 KERN: [ipro1000] (em) Link is Down KERN: /dev/net/ipro1000/0: media change, media 0x20 quality 1000 speed 1000000000 KERN: [ipro1000] (em) Link is up 1000 Mbps Full Duplex KERN: /dev/net/ipro1000/0: media change, media 0x900030 quality 1000 speed 1000000000 KERN: low resource address space: note -> normal AUTH 'sshd'[727]: error: setsockopt IPV6_V6ONLY: Operation not supported AUTH 'sshd'[727]: Server listening on :: port 22. AUTH 'sshd'[727]: Server listening on 0.0.0.0 port 22. AUTH 'sshd'[727]: error: Couldn't create pid file "/packages/openssh-6.6p1-1/.self/var/run/sshd.pid": No such file or directory
listdev output:
device Serial bus controller (SMBus) [c|5|0] vendor 8086: Intel Corporation device 1e22: 7 Series/C210 Series Chipset Family SMBus Controller device Mass storage controller (SATA controller, AHCI 1.0) [1|6|1] vendor 8086: Intel Corporation device 1e02: 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] device Bridge (ISA bridge) [6|1|0] vendor 8086: Intel Corporation device 1e4a: H77 Express Chipset LPC Controller device Serial bus controller (USB controller, EHCI) [c|3|20] vendor 8086: Intel Corporation device 1e26: 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 device Serial bus controller (FireWire (IEEE 1394), OHCI) [c|0|10] vendor 1106: VIA Technologies, Inc. device 3403: VT6315 Series Firewire Controller device Bridge (PCI bridge, Normal decode) [6|4|0] vendor 8086: Intel Corporation device 1e1e: 7 Series/C210 Series Chipset Family PCI Express Root Port 8 device Bridge (PCI bridge, Normal decode) [6|4|0] vendor 8086: Intel Corporation device 1e10: 7 Series/C210 Series Chipset Family PCI Express Root Port 1 device Multimedia controller (Audio device) [4|3|0] vendor 8086: Intel Corporation device 1e20: 7 Series/C210 Series Chipset Family High Definition Audio Controller device Serial bus controller (USB controller, EHCI) [c|3|20] vendor 8086: Intel Corporation device 1e2d: 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 device Network controller (Ethernet controller) [2|0|0] vendor 8086: Intel Corporation device 1503: 82579V Gigabit Network Connection device Communication controller [7|80|0] vendor 8086: Intel Corporation device 1e3a: 7 Series/C210 Series Chipset Family MEI Controller #1 device Serial bus controller (USB controller, XHCI) [c|3|30] vendor 8086: Intel Corporation device 1e31: 7 Series/C210 Series Chipset Family USB xHCI Host Controller device Display controller (VGA compatible controller, VGA controller) [3|0|0] vendor 8086: Intel Corporation device 0162: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller device Bridge (Host bridge) [6|0|0] vendor 8086: Intel Corporation device 0150: Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller
Change History (3)
comment:1 by , 10 years ago
comment:2 by , 8 years ago
The same symptoms, although directly after boot, were seen in KVM and hrev50755 solves them.
Note:
See TracTickets
for help on using tickets.
Could be interrupt related.