From: Meelis Roos <mroos@linux.ee>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: printks messed up in 3.6-rc2+git
Date: Sun, 19 Aug 2012 10:30:57 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1208191026340.18296@math.ut.ee> (raw)
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
--
Meelis Roos (mroos@linux.ee)
next reply other threads:[~2012-08-19 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 7:30 Meelis Roos [this message]
2012-08-19 9:47 ` printks messed up in 3.6-rc2+git Ming Lei
2012-08-19 9:49 ` Markus Trippelsdorf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.SOC.1.00.1208191026340.18296@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox