From: Andrew Lunn <andrew@lunn.ch>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: Mikael Pettersson <mikpelinux@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Andrew Lunn <andrew@lunn.ch>,
linux-ide@vger.kernel.org
Subject: Re: [REGRESSION] 3.14-rc2 boot failure on Kirkwood (qnap ts-119p+)
Date: Sun, 16 Feb 2014 21:29:57 +0100 [thread overview]
Message-ID: <20140216202957.GC26583@lunn.ch> (raw)
In-Reply-To: <20140216143735.GA8680@localhost>
On Sun, Feb 16, 2014 at 11:45:20AM -0300, Ezequiel Garcia wrote:
> Hi Mikael,
>
> On Sun, Feb 16, 2014 at 12:00:37PM +0100, Mikael Pettersson wrote:
> > My Kirkwood box worked fine with the 3.13 kernel, but with 3.14-rc2
> > boot always fails due to a kernel NULL dereference in __clk_put.
> >
> > This is a non-DT kernel, with:
> >
> > CONFIG_ARCH_KIRKWOOD=y
> > CONFIG_KIRKWOOD_LEGACY=y
> > CONFIG_MACH_TS219=y
> > # CONFIG_ARCH_KIRKWOOD_DT is not set
> >
>
> Thanks for the report. I thought this issue was already fixed, but I
> cannot find it on either the mailing lists or linux-next.
>
> So, in case it hasn't been fixed here's an untested fix for you to test.
> Please try this patch and let us know.
>
> Your SATA won't work but if the patch is OK the kernel wont't blow away.
>
> Andrew? Do we support the new phy requirement in non-DT platforms?
Hi Ezequiel
I consider Non-DT kirkwood now pretty much near death. Probably with
3.16 it will of gone altogether. So i did not plan for Non-DT to
support SATA phy. I did however want it to at least boot, so i broke
something here :-(
I will take a look at your fix and what we can expect in the next -rc.
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [REGRESSION] 3.14-rc2 boot failure on Kirkwood (qnap ts-119p+)
Date: Sun, 16 Feb 2014 21:29:57 +0100 [thread overview]
Message-ID: <20140216202957.GC26583@lunn.ch> (raw)
In-Reply-To: <20140216143735.GA8680@localhost>
On Sun, Feb 16, 2014 at 11:45:20AM -0300, Ezequiel Garcia wrote:
> Hi Mikael,
>
> On Sun, Feb 16, 2014 at 12:00:37PM +0100, Mikael Pettersson wrote:
> > My Kirkwood box worked fine with the 3.13 kernel, but with 3.14-rc2
> > boot always fails due to a kernel NULL dereference in __clk_put.
> >
> > This is a non-DT kernel, with:
> >
> > CONFIG_ARCH_KIRKWOOD=y
> > CONFIG_KIRKWOOD_LEGACY=y
> > CONFIG_MACH_TS219=y
> > # CONFIG_ARCH_KIRKWOOD_DT is not set
> >
>
> Thanks for the report. I thought this issue was already fixed, but I
> cannot find it on either the mailing lists or linux-next.
>
> So, in case it hasn't been fixed here's an untested fix for you to test.
> Please try this patch and let us know.
>
> Your SATA won't work but if the patch is OK the kernel wont't blow away.
>
> Andrew? Do we support the new phy requirement in non-DT platforms?
Hi Ezequiel
I consider Non-DT kirkwood now pretty much near death. Probably with
3.16 it will of gone altogether. So i did not plan for Non-DT to
support SATA phy. I did however want it to at least boot, so i broke
something here :-(
I will take a look at your fix and what we can expect in the next -rc.
Andrew
next prev parent reply other threads:[~2014-02-16 20:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 11:00 [REGRESSION] 3.14-rc2 boot failure on Kirkwood (qnap ts-119p+) Mikael Pettersson
2014-02-16 14:45 ` Ezequiel Garcia
2014-02-16 14:45 ` Ezequiel Garcia
2014-02-16 15:10 ` Mikael Pettersson
2014-02-16 15:10 ` Mikael Pettersson
2014-02-16 15:28 ` Ezequiel Garcia
2014-02-16 15:28 ` Ezequiel Garcia
2014-02-16 16:48 ` Mikael Pettersson
2014-02-16 16:48 ` Mikael Pettersson
2014-02-16 20:29 ` Andrew Lunn [this message]
2014-02-16 20:29 ` Andrew Lunn
2014-02-16 21:17 ` Ezequiel Garcia
2014-02-16 21:17 ` Ezequiel Garcia
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=20140216202957.GC26583@lunn.ch \
--to=andrew@lunn.ch \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=mikpelinux@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.