Hello, Jeremy.
You wrote 19 января 2011 г., 0:46:54:
> CC'ing Jack Vogel of Intel, as this looks like it could be something the
> em(4) driver might be tickling. I do see it in the stack trace shortly
> before the crash. In the interim, can you please provide output from the
> following command:
> # pciconf -lbcv
> And include only the entries relevant to your emX devices.
em0@pci0:0:25:0: class=0x020000 card=0x82681043 chip=0x10bd8086 rev=0x02
hdr=0x00
vendor = 'Intel Corporation'
device = 'Intel 82566DM Gigabit Ethernet Adapter (82566DM)'
class = network
subclass = ethernet
bar [10] = type Memory, range 32, base 0xfea40000, size 131072, enabled
bar [14] = type Memory, range 32, base 0xfea79000, size 4096, enabled
bar [18] = type I/O Port, range 32, base 0xdc00, size 32, enabled
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit
cap 09[e0] = vendor (length 6) Intel cap 2 version 0
It is on-board LAN on Q35-based MoBo (ASUS P5E-VM DO)
> As for the "the server refuses to auto-reboot": that may be a separate
> problem. You might try toggling the hw.acpi.disable_on_reboot and
> hw.acpi.handle_reboot sysctls (check what values they have on your
> system first) to see if there's any improvement.
Both are zero. BTW, manual reboots (reboot && shutdown -r now) and
shutdowns (shutdown -p now) works perfectly Ok.
--
// Black Lion AKA Lev Serebryakov <[email protected]>
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[email protected]"
