Package: socklog Version: 2.1.0-8 Severity: minor I've noticed that socklog, particularly when run as ucspi application to parse /proc/kmsg, will occasionally fail to propertly decode & print a facility.priority string. For example:
2011-02-28_05:14:05.49083 kern.info: No AGP bridge found 2011-02-28_05:14:05.49087 kern.info: last_pfn = 0x1fffd max_arch_pfn = 0x400000000 2011-02-28_05:14:05.49090 <7>MTRR default type: write-back 2011-02-28_05:14:05.49095 kern.debug: MTRR fixed ranges enabled: 2011-02-28_05:14:05.49099 kern.debug: 00000-9FFFF write-back -or- 2011-02-28_05:52:02.48922 kern.debug: ACPI: Local APIC address 0xfee00000 2011-02-28_05:52:02.48924 kern.info: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) 2011-02-28_05:52:02.48926 <6>ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) 2011-02-28_05:52:02.48930 kern.info: IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23 2011-02-28_05:52:02.48932 kern.info: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) I haven't looked too hard at the frequency of the error, but it seems like it happens most reliably during system start up, and if it happens that it's likely to happen fairly consistently in the same spot during startup; maybe a buffer boundry issue or something? -- Jamie Heilman http://audible.transient.net/~jamie/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
