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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120819094942.GA251@x4>
Date:	Sun, 19 Aug 2012 11:49:42 +0200
From:	Markus Trippelsdorf <markus@...ppelsdorf.de>
To:	Meelis Roos <mroos@...ux.ee>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: printks messed up in 3.6-rc2+git

On 2012.08.19 at 10:30 +0300, Meelis Roos wrote:
> 1. Lots of broken HPET messages scattered in PCI prontks like this:
> pcieport 0000:00:0c.0: Force enabled HPET at 0x%lx
> irq 40 for MSI/MSI-X
> pcieport 0000:00:0d.0: Force enabled HPET at 0x%lx
> irq 41 for MSI/MSI-X
> pcieport 0000:00:0e.0: Force enabled HPET at 0x%lx
> irq 42 for MSI/MSI-X
> pcieport 0000:00:0f.0: Force enabled HPET at 0x%lx
> irq 43 for MSI/MSI-X
> 
> 2. Lots of \0x10 in different printk lines, like this:
> 
> pci 0000:00:05.0: \x010Enabling HT MSI Mapping
> pci 0000:00:05.1: \x010Enabling HT MSI Mapping
> pci 0000:00:05.2: \x010Enabling HT MSI Mapping
> pci 0000:00:06.0: \x010Enabling HT MSI Mapping
> pci 0000:00:06.1: \x010Enabling HT MSI Mapping
> pci 0000:00:08.0: \x010Enabling HT MSI Mapping
> pci 0000:00:09.0: \x010Enabling HT MSI Mapping
> pci 0000:00:0c.0: \x010Enabling HT MSI Mapping
> pci 0000:00:0d.0: \x010Enabling HT MSI Mapping
> pci 0000:00:0e.0: \x010Enabling HT MSI Mapping
> pci 0000:00:0f.0: \x010Enabling HT MSI Mapping
> and this:
> usb 2-8: \x010new low-speed USB device number 5 using ohci_hcd
> usb 2-8: \x010New USB device found, idVendor=0592, idProduct=0002
> usb 2-8: \x010New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 2-8: %s: Can't disable non-U1 or U2 state.
> 
> 3. Many more %s and runtogether lines:
> 
> sata_nv 0000:00:05.1: %s: ino %lu, used %d with only %d reserved data blocksUsing SWNCQ mode

Yes.
Fix is already queued up:
http://git.kernel.org/?p=linux/kernel/git/gregkh/driver-core.git;a=commitdiff;h=ebdc82899ec5ed35af1c79ed6a4eeda69dad9b90

-- 
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ