Solaris 10 - bunch of drivers, or devfsadm ran for no reason?
Yesterday a bunch of syslog entries showed up, out of nowhere, no one was logged in, no cron jobs running at that time, the system was not rebooted:
Apr 5 17:27:16 jackson bge: [ID 801725 kern.info] NOTICE: bge2: ddi_intr_get_su
pported_types() returned: 1
Apr 5 17:27:16 jackson bge: [ID 801725 kern.info] NOTICE: bge2: Using Legacy in
terrupt type
Apr 5 17:27:16 jackson bge: [ID 801725 kern.info] NOTICE: bge2: bge_add_legacy_
intrs
Apr 5 17:27:17 jackson mac: [ID 543131 kern.info] NOTICE: bge2/0 registered
Apr 5 17:27:17 jackson bge: [ID 801725 kern.info] NOTICE: bge3: ddi_intr_get_su
pported_types() returned: 1
Apr 5 17:27:17 jackson bge: [ID 801725 kern.info] NOTICE: bge3: Using Legacy in
terrupt type
Apr 5 17:27:17 jackson bge: [ID 801725 kern.info] NOTICE: bge3: bge_add_legacy_
intrs
Apr 5 17:27:18 jackson mac: [ID 543131 kern.info] NOTICE: bge3/0 registered
Apr 5 17:27:18 jackson scsi: [ID 365881 kern.info] /pci@1c,600000/scsi@2,1 (glm
1):
Apr 5 17:27:18 jackson glm1 supports power management.
Apr 5 17:27:18 jackson scsi: [ID 365881 kern.info] /pci@1c,600000/scsi@2,1 (glm
1):
Apr 5 17:27:18 jackson Rev. 0 Symbios 53c1010-33/66 found.
Apr 5 17:27:18 jackson pcisch: [ID 370704 kern.info] PCI-device: scsi@2,1, glm1
Apr 5 17:27:18 jackson genunix: [ID 936769 kern.info] glm1 is /pci@1c,600000/sc
si@2,1
Apr 5 17:27:39 jackson ebus: [ID 521012 kern.info] su1 at ebus0: offset 0,2e8
Apr 5 17:27:39 jackson genunix: [ID 936769 kern.info] su1 is /pci@1e,600000/isa
@7/serial@0,2e8
Apr 5 17:27:39 jackson pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Apr 5 17:27:39 jackson genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap
@0
Apr 5 17:27:39 jackson pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Apr 5 17:27:39 jackson genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ra
mdisk@1024
Apr 5 17:27:39 jackson pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Apr 5 17:27:39 jackson genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlo
ck@0
Apr 5 17:27:39 jackson pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Apr 5 17:27:39 jackson genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lock
stat@0
Apr 5 17:27:39 jackson pseudo: [ID 129642 kern.info] pseudo-device: vol0
Apr 5 17:27:39 jackson genunix: [ID 936769 kern.info] vol0 is /pseudo/vol@0
[etc]
This is a Solaris 10 host. Does something wake up periodically and do a "devfsadm" or something? A few minutes later in.mpathd chimed in:
Apr 5 17:32:13 jackson in.mpathd[125]: [ID 585766 daemon.error] Cannot meet req
uested failure detection time of 10000 ms on (inet bge0) new failure detection t
ime for group "bge" is 37394 ms
Apr 5 17:33:13 jackson in.mpathd[125]: [ID 302819 daemon.error] Improved failur
e detection time 18697 ms on (inet bge0) for group "bge"
Apr 5 17:33:13 jackson in.mpathd[125]: [ID 302819 daemon.error] Improved failur
e detection time 10000 ms on (inet bge1) for group "bge"
Apr 5 17:34:13 jackson in.mpathd[125]: [ID 585766 daemon.error] Cannot meet req
uested failure detection time of 10000 ms on (inet bge0) new failure detection t
ime for group "bge" is 36204 ms
Apr 5 17:35:13 jackson in.mpathd[125]: [ID 302819 daemon.error] Improved failur
e detection time 18102 ms on (inet bge0) for group "bge"
Apr 5 17:35:13 jackson in.mpathd[125]: [ID 302819 daemon.error] Improved failur
e detection time 10000 ms on (inet bge1) for group "bge"
That could have been caused by a network glitch as the LAN this host is on is relatively unstable. Could there be a relationship to the previous kernel syslog entries?
Just curious more than anything else . . .
