ASRock M3A UCC - FreeBSD - 2014 archive
back to main FreeBSD page for this machine.
2014 archive.
2014-12-24: slice 2 - rebooted the machine because of the interrupt storm.
2014-12-23: slice 2 - another interrupt storm detected:
Dec 23 09:30:55 kg-fil kernel: interrupt storm detected on "irq22:"; throttling interrupt source Dec 23 09:31:26 kg-fil last message repeated 31 times Dec 23 09:33:27 kg-fil last message repeated 121 times Dec 23 09:43:28 kg-fil last message repeated 601 times
nothing more.
2014-08-31: slice 2 - rebooted the machine because of the interrupt storm.
2014-08-30: slice 2 - another interrupt storm detected:
Aug 30 22:53:06 kg-fil kernel: interrupt storm detected on "irq22:"; throttling interrupt source Aug 30 22:53:37 kg-fil last message repeated 31 times Aug 30 22:55:38 kg-fil last message repeated 120 times
nothing more.
2014-08-06: slice 2 - rebooted the machine because of the interrupt storm.
2014-08-05: slice 2 - another interrupt storm detected:
Aug 5 08:15:56 kg-fil kernel: interrupt storm detected on "irq22:"; throttling interrupt source Aug 5 08:16:27 kg-fil last message repeated 31 times Aug 5 08:18:28 kg-fil last message repeated 121 times
nothing more.
2014-07-15: slice 2 - rebooted the machine because of the interrupt storm.
2014-07-14: slice 2 - another interrupt storm detected:
Jul 14 11:34:17 kg-fil kernel: interrupt storm detected on "irq22:"; throttling interrupt source Jul 14 11:34:48 kg-fil last message repeated 31 times Jul 14 11:36:49 kg-fil last message repeated 121 times
nothing more.
2014-07-11: slice 2 - reboot due to a power failure (local circuit breaker tripped) earlier in the day. Nothing more.
2014-07-04: slice 2 - do a vmstat -i before rebooting the machine:
root@kg-fil# vmstat -i interrupt total rate irq9: acpi0 1 0 irq14: ata0 121554 0 irq16: pcm0 ohci0 12 0 irq17: ohci1 ohci3 2 0 irq18: ohci2 ohci4 2 0 irq22: em0 atapci0 15640792522 32488 cpu0: timer 962659200 1999 Total 16603573293 34487
Ok, so the network card and the PCI controller is on irq22. reboot machine.
2014-07-03: slice 2 - another interrupt storm detected:
Jul 3 21:52:31 kg-fil kernel: interrupt storm detected on "irq22:"; throttling interrupt source Jul 3 21:53:02 kg-fil last message repeated 30 times Jul 3 21:55:03 kg-fil last message repeated 121 times Jul 3 22:05:04 kg-fil last message repeated 601 times
perhaps I need to reboot the machine again.
2014-06-28: slice 2 - network connectivity restored with the PCI adapter. From /var/log/messages:
Jun 28 20:10:58 kg-fil kernel: em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 0xd800-0xd83f mem 0xfebe0000-0xfebfffff,0xfebc0000-0xfebdffff irq 22 at device 7.0 on pci2 Jun 28 20:10:58 kg-fil kernel: em0: Ethernet address: 90:e2:ba:5c:3b:f6
good.
2014-06-28: slice 2 - testing the Intel Pro/1000CT PCIe Desktop Adapter 1000BaseT, Inc Low Profile Bracket, bulk network adapter. The adapter shows up as em0, and appears to work nicely. Under FreeBSD 6.4-stable:
root@kg-fil# uname -a FreeBSD kg-fil.kg4.no 6.4-STABLE FreeBSD 6.4-STABLE #0: Sat Aug 13 17:30:21 CEST 2011 root@kg-fil.kg4.no:/usr/obj/usr/src/sys/FIL62 amd64
from dmesg output: - it just says "no driver attached", so it doesn't work here. slice 1 - testing with FreeBSD 6.2-stable:
root@kg-fil# uname -a FreeBSD kg-fil.kg4.no 6.2-STABLE FreeBSD 6.2-STABLE #20: Mon Mar 12 23:04:49 CET 2007 root@kg-fil.kg4.no:/usr/obj/usr/src/sys/FIL60 amd64
from dmesg output: - it just says "no driver attached", so it doesn't work here. slice 3 - testing with FreeBSD 7.4-stable:
root@kg-fil# uname -a FreeBSD kg-fil.kg4.no 7.4-STABLE FreeBSD 7.4-STABLE #1: Sat Aug 27 16:32:02 CEST 2011 root@kg-fil.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
from dmesg output:
em0: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0xd800-0xd81f mem 0xfebe0000-0xfebfffff,0xfeb00000-0xfeb7ffff,0xfebdc000-0xfebdffff irq 16 at device 0.0 on pci2 em0: Using MSIX interrupts with 3 vectors em0: [ITHREAD] em0: [ITHREAD] em0: [ITHREAD] em0: Ethernet address: 68:05:ca:28:a2:e1
slice 4 - testing with FreeBSD 8.2-stable:
root@kg-fil# uname -a FreeBSD kg-fil.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #0: Sat Aug 27 21:00:17 CEST 2011 root@kg-fil.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
from dmesg output:
em0: <Intel(R) PRO/1000 Network Connection 7.2.3> port 0xd800-0xd81f mem 0xfebe0000-0xfebfffff,0xfeb00000-0xfeb7ffff,0xfebdc000-0xfebdffff irq 16 at device 0.0 on pci2 em0: Using MSIX interrupts with 3 vectors em0: [ITHREAD] em0: [ITHREAD] em0: [ITHREAD] em0: Ethernet address: 68:05:ca:28:a2:e1
That's all.
2014-06-28: slice 2 - testing the Intel Pro/1000GT PCI Desktop Adapter 1000BaseT, bulk network adapter. The adapter shows up as em0, and appears to work nicely. This under FreeBSD 6.4-stable:
root@kg-fil# uname -a FreeBSD kg-fil.kg4.no 6.4-STABLE FreeBSD 6.4-STABLE #0: Sat Aug 13 17:30:21 CEST 2011 root@kg-fil.kg4.no:/usr/obj/usr/src/sys/FIL62 amd64
from dmesg output:
em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 0xd800-0xd83f mem 0xfebe0000-0xfebfffff,0xfebc0000-0xfebdffff irq 22 at device 7.0 on pci2 em0: Ethernet address: 90:e2:ba:5c:3b:f6
slice 1 - testing with FreeBSD 6.2-stable:
root@kg-fil# uname -a FreeBSD kg-fil.kg4.no 6.2-STABLE FreeBSD 6.2-STABLE #20: Mon Mar 12 23:04:49 CET 2007 root@kg-fil.kg4.no:/usr/obj/usr/src/sys/FIL60 amd64
from dmesg output:
em0: <Intel(R) PRO/1000 Network Connection Version - 6.2.9> port 0xd800-0xd83f mem 0xfebe0000-0xfebfffff,0xfebc0000-0xfebdffff irq 22 at device 7.0 on pci2 em0: Ethernet address: 90:e2:ba:5c:3b:f6
slice 3 - testing with FreeBSD 7.4-stable:
root@kg-fil# uname -a FreeBSD kg-fil.kg4.no 7.4-STABLE FreeBSD 7.4-STABLE #1: Sat Aug 27 16:32:02 CEST 2011 root@kg-fil.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
from dmesg output:
em0: <Intel(R) PRO/1000 Legacy Network Connection 1.0.3> port 0xd800-0xd83f mem 0xfebe0000-0xfebfffff,0xfebc0000-0xfebdffff irq 22 at device 7.0 on pci2 em0: [FILTER] em0: Ethernet address: 90:e2:ba:5c:3b:f6
slice 4 - testing with FreeBSD 8.2-stable:
root@kg-fil# uname -a FreeBSD kg-fil.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #0: Sat Aug 27 21:00:17 CEST 2011 root@kg-fil.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
from dmesg output:
em0: <Intel(R) PRO/1000 Legacy Network Connection 1.0.3> port 0xd800-0xd83f mem 0xfebe0000-0xfebfffff,0xfebc0000-0xfebdffff irq 22 at device 7.0 on pci2 em0: [FILTER] em0: Ethernet address: 90:e2:ba:5c:3b:f6
That's all.
2014-04-08: slice2 - another interrupt storm detected:
Apr 8 12:20:05 kg-fil kernel: interrupt storm detected on "irq22:"; throttling interrupt source Apr 8 12:20:36 kg-fil last message repeated 31 times Apr 8 12:22:37 kg-fil last message repeated 121 times
reboot again.
2014-03-13: slice 2 - testing tv_grab_no_gfeed after the move to Sweden (see this thread - in Norwegian). Getting some errors:
removing existing program: tvnorge.no Castle 2014-03-18T00:25:00 - 2014-03-18T01:25:00 inserting new program : tvnorge.no Castle Tue Mar 18 00:25:00 2014 - Tue Mar 18 01:25:00 2014 2014-03-13 20:37:36.541 DB Error (person insert): Query was: INSERT INTO people (name) VALUES ('<actors> <actor>Seamus Dever</actor> <actor>Susan Sullivan</actor> <actor>Molly C. Quinn</actor> <actor>Jon Huertas</actor> <actor>Stana Katic</actor> <actor>Nathan Fillion</actor> </actors>'); Driver error was [2/1582]: QMYSQL3: Unable to execute query Database error was: Duplicate entry '<actors> <actor>Seamus Dever</actor> <act' for key 'name' Error inserting person removing existing program: tvnorge.no CSI: Miami 2014-03-18T01:25:00 - 2014-03-18T02:20:00 inserting new program : tvnorge.no CSI: Miami Tue Mar 18 01:25:00 2014 - Tue Mar 18 02:20:00 2014
most likely because I'm using a (very) old MythTV version.
2014-03-01: slice2 - another interrupt storm detected:
Feb 27 05:02:55 kg-fil kernel: interrupt storm detected on "irq22:"; throttling interrupt source Feb 27 05:03:26 kg-fil last message repeated 31 times Feb 27 05:05:27 kg-fil last message repeated 121 times Feb 27 05:15:28 kg-fil last message repeated 599 times
reboot again.
2014-01-11: slice 2 - interrupt storm again:
Jan 11 03:28:09 kg-fil kernel: interrupt storm detected on "irq22:"; throttling interrupt source Jan 11 03:28:39 kg-fil last message repeated 29 times Jan 11 03:30:39 kg-fil last message repeated 120 times
As always, reboot the machine.