From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: v3.5-rc1 ARM PXA possible regression
Date: Mon, 4 Jun 2012 16:05:31 +0200 [thread overview]
Message-ID: <20120604140531.GA7486@lunn.ch> (raw)
Hi Paul
I've got the same problem on my kirkwood based QNAP NAS box.
I bisected it, and the problem patch for me is:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=7ff9554bb578ba02166071d2d487b7fc7d860d62
printk: convert byte-buffer to variable-length record buffer
I've not looked further, so i've no idea why this is causing problems.
Andrew
next reply other threads:[~2012-06-04 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 14:05 Andrew Lunn [this message]
2012-06-04 14:15 ` v3.5-rc1 ARM PXA possible regression Arnaud Patard (Rtp)
2012-06-04 15:23 ` Paul Parsons
2012-06-04 19:32 ` Simon Baatz
-- strict thread matches above, loose matches on Subject: below --
2012-06-04 12:35 Paul Parsons
2012-06-05 2:44 ` Eric Miao
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=20120604140531.GA7486@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).