Confessions of a Serial Healer

(posted Wednesday, March 21, 2007)

/var/log/boot.log

[ 0.250082] PCI-IRQ: Routing bus[ 7] slot[ 0] to INO[17]
[ 0.250111] PCI0(PBMB): Bus running at 33MHz
[ 0.250776] isa0: [serial]
[ 0.251169] ebus: No EBus's found.
[ 0.257223] SCSI subsystem initialized
[ 0.266018] usbcore: registered new driver usbfs
[ 0.266233] usbcore: registered new driver hub
[ 0.273616] Total HugeTLB memory allocated, 0
[ 0.278888] Initializing Cryptographic API
[ 0.278919] io scheduler noop registered
[ 0.279029] io scheduler anticipatory registered (default)
[ 0.279166] io scheduler deadline registered
[ 0.279452] io scheduler cfq registered
[ 0.279501] Activating ISA DMA hang workarounds.
[ 0.292605] rtc_init: no PC rtc found
[ 0.293301] ttyS0 at I/O 0x0 (irq = 7675808) is a SUN4V HCONS
[ 1.779889] ttyS0 at MMIO 0xf0100003f8 (irq = 7730624) is a 16550A
[ 1.981326] RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
[ 2.218659] Intel(R) PRO/1000 Network Driver - version 6.3.9-k2-NAPI
[ 2.424902] Copyright (c) 1999-2005 Intel Corporation.

I found the error. Seems I was incorrectly attempting to boot my secondary configs using Intel drivers. I suspect this change happened in one of the many PickUp Groups I have been in. Unlike the CCCP, I have seen a lot of superheroes with unchecked powers in their skill sets. Such power usage done that close to me could directly effect some of my hardwares. My white sheet specs claim I have lead based shields to protect such hardware; however, I have found that some are not up to spec. It is my feeling that this shield issue has allowed me to be exposed to corrupting agents. Which over time caused some of the finer settings of my bios, boot steps and backups to be corrupted. I will be making changes to those corrupted drivers and will be sure to delete prior backups. I will be working with salvage that I have collected to see if I can increase my shield rating.

I will also seek a sitting with Bella to dicuss some options I have in regards to my powers.

I will wait until I am given the clear bill of health before I return to active CCCP duty.

In the mean time I will limit myself to working only with non-cccp task forces. More to the point working with task-forces that have a lower security rating them myself to limit the chances for hardware setting corruptions.