Arch Linux

grndrush

Member

From: Hamilton, Ontario, Canada

Registered: 2003-12-28

Posts: 136

Website

Garbled/mangled log records

I've noticed this issue for some time now, as it typically occurs at a point in the boot process which, for several reasons, has been an 'interesting' point' in my boot process for some time. However, I'm going to be showing some logs soon, and this issue is rampant at one point where I'll be needing to provide a rational wha-happin?

Jan 22 07:58:22 rusty Freeing unused kernel memory: 252k freed
Jan 22 07:58:22 rusty scsi0 : pata_via
Jan 22 07:58:22 rusty scsi1 : pata_via
Jan 22 07:58:22 rusty ata1: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma 0x000000000001fc00 irq 14
Jan 22 07:58:22 rusty ata2: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma 0x000000000001fc08 irq 15
Jan 22 07:58:22 rusty ata1.00: ATA-7: WDC WD2500JB-00REA0, 20.00K20, max UDMA/100
Jan 22 07:58:22 rusty ata1.00: 488397168 sectors, multi 16: LBA48 
Jan 22 07:58:22 rusty ata1.00: configured for UDMA/100
Jan 22 07:58:22 rusty ata2.00: ATAPI: TOSHIBA DVD-ROM SD-R5112, 1034, max UDMA/33
Jan 22 07:58:22 rusty ata2.01: ATAPI: HL-DT-ST DVDRAM GSA-H10N, JL10, max UDMA/33
Jan 22 07:58:22 rusty ata2.00: configured for UDMA/33
Jan 22 07:58:22 rusty ata2.01: configured for UDMA/33
Jan 22 07:58:22 rusty scsi 0:0:0:0: Direct-Access     ATA      WDC WD2500JB-00R 20.0 PQ: 0 ANSI: 5
Jan 22 07:58:22 rusty scsi 1:0:0:0: CD-ROM            TOSHIBA  DVD-ROM SD-R5112 1034 PQ: 0 ANSI: 5
Jan 22 07:58:22 rusty scsi 1:0:1:0: CD-ROM            HL-DT-ST DVDRAM GSA-H10N  JL10 PQ: 0 ANSI: 5
Jan 22 07:58:22 rusty usbcore: registered new interface driver usbfs
Jan 22 07:58:22 rusty sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
Jan 22 07:58:22 rusty sd 0:0:0:0: [sda] Write Protect is off
Jan 22 07:58:22 rusty sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 22 07:58:22 rusty sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
Jan 22 07:58:22 rusty sd 0:0:0:0: [sda] Write Protect is off
Jan 22 07:58:22 rusty sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 22 07:58:22 rusty sda: sda1 sda2 sda3 sda4 <<6>usbcore: registered new interface driver hub
Jan 22 07:58:22 rusty sda5<6>usbcore: registered new device driver usb
Jan 22 07:58:22 rusty sda6ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
Jan 22 07:58:22 rusty ACPI: PCI Interrupt 0000:00:10.4[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
Jan 22 07:58:22 rusty sda7 >
Jan 22 07:58:22 rusty ehci_hcd 0000:00:10.4: EHCI Host Controller
Jan 22 07:58:22 rusty ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 1
Jan 22 07:58:22 rusty ehci_hcd 0000:00:10.4: debug port 1
Jan 22 07:58:22 rusty ehci_hcd 0000:00:10.4: irq 10, io mem 0xfebffc00
Jan 22 07:58:22 rusty USB Universal Host Controller Interface driver v3.0
Jan 22 07:58:22 rusty sd 0:0:0:0: [sda] Attached SCSI disk
Jan 22 07:58:22 rusty ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
Jan 22 07:58:22 rusty usb usb1: configuration #1 chosen from 1 choice

The top of this log excerpt is to provide reference as to where we are in the boot process. At this point, it appears (and has for a long time now) that while booting my machine is at this point attempting to  initialise both PCI(/SCSI) and USB buses simultaneously.

See the 1st log entry, just over 1/2-way down, beginning with "sda5<6>"? Yeah. The "<6>", specifically. Note that the line right above it - where ATA/SCS  is starting to enumerate the disk partitions on sda - but the line is apparently interrupted by a message from the also-initialising USB subsystem. Note how 5 consecutive log entries are mangled badly enough it's questionable whether a log parser could get back it.

This one's been around for a while...maybe an old-timer's laughing ATM?

Blue Skies...grndrush