From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Tanaka Takahisa <mc74hc00@gmail.com>
Cc: Joseph Salisbury <josephtsalisbury@gmail.com>,
Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Kernel Team <kernel-team@lists.ubuntu.com>
Subject: Re: [v3.8 Regression] watchdog: sp5100_tco: Add SB8x0 chipset support
Date: Thu, 21 Feb 2013 19:04:39 -0500 [thread overview]
Message-ID: <5126B617.6010405@canonical.com> (raw)
In-Reply-To: <CAHh0gOgiSjTYvEzim-7+yEhU74c5PVV=2ScTnaJ15SPY=y-WqA@mail.gmail.com>
On 02/18/2013 12:14 PM, Tanaka Takahisa wrote:
> Hi Joseph,
>
> Thanks a lot for your help.
>
>> The bug report tested a kernel with the patches. However, he reports the kernel panic still occurs[0].
> I understood. I guess this problem conflicts with the watchdog MMIO
> address (*) written in SB700 chipset and other resource. So, I made a
> patch which gets rid of the code considered to cause the problem. If
> this patch is applied, although the SP5100 and SB7x0 chipsets can't
> use watchdog function any longer, I'm sure attached patch resolve the
> problem. The SB800 or later chipsets can be used as before.
> (*)This address is obtained from allocate_resource() function.
>
> I'm sorry to trouble you, but Would you confirm whether attached patch
> solves a problem?
> If there is no problem in this patch, I will submit this patch to a
> linux-watchdog community.
This patch did resolve the issue. The bug reporter states the panic no
longer happens and the system boots. Thanks so much for your assistance.
>
>
>> I've requested a digital image or screen capture of the panic. Is
>> there any additional debug information you thing would be helpful?
> I'm interested in the I/O resource of PC in which the problem has
> occurred, So, I want the result of 'cat /proc/iomem'. When 'cat
> /proc/iomem' is performed, I don't care about whether sp5100_tco
> driver is loaded.
The I/O data can be seen at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1116835/+attachment/3540738/+files/iomem.txt
>
>
> Thanks in advance.
> Takahisa
next prev parent reply other threads:[~2013-02-22 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 16:07 [v3.8 Regression] watchdog: sp5100_tco: Add SB8x0 chipset support Joseph Salisbury
2013-02-15 7:32 ` Wim Van Sebroeck
2013-02-15 14:54 ` Joseph Salisbury
2013-02-17 9:44 ` Tanaka Takahisa
2013-02-18 3:13 ` Joseph Salisbury
2013-02-18 7:26 ` Joseph Salisbury
2013-02-18 17:14 ` Tanaka Takahisa
2013-02-22 0:04 ` Joseph Salisbury [this message]
2013-02-23 6:14 ` Tanaka Takahisa
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=5126B617.6010405@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=josephtsalisbury@gmail.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mc74hc00@gmail.com \
--cc=wim@iguana.be \
/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).