From: Phil Nitschke <philn@avalon.com.au>
To: linuxppc-embedded@ozlabs.org
Subject: kernel oops in m41t00 rtc routines
Date: Fri, 03 Nov 2006 16:17:53 +1030 [thread overview]
Message-ID: <1162532873.4199.50.camel@lamorak.int.avalon.com.au> (raw)
Hi,
Some time ago we built a 2.6.17, then a 2.6.18 kernel for our 7448
PowerPC processor using source from kernel.org. However we've suffered
from the following problem whenever the m41t00 code is accessed:
kernel: Oops: kernel access of bad area, sig: 11 [#1]
kernel: NIP: C012DA14 LR: C010B944 CTR: 00000000
kernel: REGS: efd9dd50 TRAP: 0300 Not tainted (2.6.18-pmppc744x)
kernel: MSR: 00009032 <EE,ME,IR,DR> CR: 28002488 XER: 00000000
kernel: DAR: 00000004, DSISR: 40000000
kernel: TASK = efd720b0[55] 'hwclock' THREAD: efd9c000
kernel: GPR00: 00000000 EFD9DE00 EFD720B0 EFD9DE94 00000000 00000000 EFD9DEB4 0FF70500
kernel: GPR08: 40247009 00000000 00000001 EFD8D360 88002488 1001E7F8 00000000 7FF5E6D0
kernel: GPR16: 00000000 00000000 10010000 00000000 EFD9DE14 C0240000 00000000 00000000
kernel: GPR24: 00000000 C024400A 0006E919 40247009 FFFFFFF7 EFCFF960 EFD9DE94 EFD9DE09
kernel: NIP [C012DA14] m41t00_get_rtc_time+0x30/0x268
kernel: LR [C010B944] gen_rtc_ioctl+0xb8/0x338
kernel: Call Trace:
kernel: [EFD9DE00] [EFCFF960] 0xefcff960 (unreliable)
kernel: [EFD9DE70] [C010B944] gen_rtc_ioctl+0xb8/0x338
kernel: [EFD9DED0] [C00760D0] do_ioctl+0x80/0x84
kernel: [EFD9DEE0] [C0076160] vfs_ioctl+0x8c/0x418
kernel: [EFD9DF10] [C007652C] sys_ioctl+0x40/0x74
kernel: [EFD9DF40] [C0004460] ret_from_syscall+0x0/0x38
kernel: Instruction dump:
kernel: 7c0802a6 9421ff90 be810040 3ea0c024 39400001 3be10009 90010074 38000000
kernel: 81356718 3a810014 98010008 38000000 <a1690004> 39210008 b0010016 38000008
We have modified the kernel using a series of patches we've developed
here over time. However, other than adding marvell DMA support, the
patches mostly just create a 'platform' file for the PmPPC7448, which is
almost identical to arch/ppc/platforms/katana.c, so I'm guessing that
(a) the patches we're applying aren't the problem, and (b) the katana
board would suffer the same problem.
I also suspect the M41T00 RTC I2C Client Driver was re-written about the
time that we started seeing problems being introduced...
Has anyone else used recent kernels on these platforms?
Thanks for any suggestions you can offer,
--
Phil
reply other threads:[~2006-11-03 6:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1162532873.4199.50.camel@lamorak.int.avalon.com.au \
--to=philn@avalon.com.au \
--cc=Phil.Nitschke@avalon.com.au \
--cc=linuxppc-embedded@ozlabs.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