| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <481D9DCC.7040000@garzik.org> Date: Sun, 04 May 2008 07:28:12 -0400 From: Jeff Garzik <jeff@...zik.org> To: LKML <linux-kernel@...r.kernel.org> CC: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de> Subject: k8-bus_64.c(?) spams dmesg in 2.6.26-rc1 Even at KERN_DEBUG, the following dmesg output is both overly excessive (overall spew) and overly terse (each line is singularly uninformative to anyone but code's author): node 0 link 0: mmio [fa700000, fa8fffff] node 1 link 0: mmio [fa900000, fa9fffff] bus: 00 to node: 00 bus: 01 to node: 00 bus: 02 to node: 00 bus: 03 to node: 00 bus: 04 to node: 00 bus: 05 to node: 00 bus: 06 to node: 00 bus: 07 to node: 00 bus: 08 to node: 00 bus: 09 to node: 00 bus: 0a to node: 00 bus: 0b to node: 00 bus: 0c to node: 00 bus: 0d to node: 00 bus: 0e to node: 00 bus: 0f to node: 00 bus: 10 to node: 00 [... SPAM SPAM SPAM, let us count to 0xff, shall we? ...] bus: fd to node: 01 bus: fe to node: 01 bus: ff to node: 01 bus: [00,3f] on node 0 link 0 bus: 00 index 0 io port: [2000, dfff] View attachment "lspci.viper" of type "text/plain" (2589 bytes) View attachment "dmesg.viper" of type "text/plain" (31856 bytes) View attachment "config.viper" of type "text/plain" (43300 bytes)
Powered by blists - more mailing lists