From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Guido Guenther <agx@sigxcpu.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Oops on boot with 2.6.23-rc2-g2c9d365c
Date: Sun, 12 Aug 2007 16:05:36 -0500 [thread overview]
Message-ID: <1186952737.1576.48.camel@localhost.localdomain> (raw)
In-Reply-To: <20070811224241.GA9770@bogon.ms20.nix>
On Sun, 2007-08-12 at 00:42 +0200, Guido Guenther wrote:
> Hi,
> I'm seeing the following oops on a Powerbook 6,1 with
> 2.6.23-rc2-g2c9d365c (and also with earlier 2.6.23, 2.6.22 is fine) and
> am quiet clueless. Any ideas before ist start bisecting?
I think it's a bogus WARN_ON, just remove it.
Ben.
> -- Guido
>
> Registering PowerMac CPU frequency driver
> Low: 533 Mhz, High: 867 Mhz, Boot: 866 Mhz
> ------------[ cut here ]------------
> Badness at kernel/irq/resend.c:70
> NIP: c0050b2c LR: c0050b00 CTR: c0016738
> REGS: cff43c30 TRAP: 0700 Not tainted (2.6.23-rc2-g2c9d365c)
> MSR: 00021032 <ME,IR,DR> CR: 48002084 XER: 20000000
> TASK = cff41830[1] 'swapper' THREAD: cff42000
> GPR00: 00000001 cff43ce0 cff41830 00000178 0000002f 80000000 00000000 0000002f
> GPR08: 000186a0 c02a0000 4048002f 00000000 00082208 00000000 00000000 00000000
> GPR16: 00000000 00000000 00000000 00000000 00000000 41400000 01668460 00000000
> GPR24: c0273000 c02a0000 c02a0000 00000000 00000000 0000002f 00024008 c0279fb8
> NIP [c0050b2c] check_irq_resend+0x5c/0xc0
> LR [c0050b00] check_irq_resend+0x30/0xc0
> Call Trace:
> [cff43ce0] [c0050b00] check_irq_resend+0x30/0xc0 (unreliable)
> [cff43d00] [c0050658] enable_irq+0x84/0xa8
> [cff43d10] [c014ab54] pmu_resume+0x80/0xc4
> [cff43d20] [c00219d4] pmu_set_cpu_speed+0x19c/0x1b4
> [cff43db0] [c002157c] do_set_cpu_speed+0xb4/0x160
> [cff43dd0] [c002176c] pmac_cpufreq_target+0x48/0x6c
> [cff43df0] [c01719f8] __cpufreq_driver_target+0x38/0x50
> [cff43e00] [c017384c] cpufreq_governor_userspace+0x1c8/0x224
> [cff43e20] [c0171dd4] __cpufreq_governor+0x64/0xbc
> [cff43e40] [c01728bc] __cpufreq_set_policy+0x174/0x19c
> [cff43e60] [c01735b0] cpufreq_add_dev+0x258/0x2f8
> [cff43f20] [c013d9a4] sysdev_driver_register+0x78/0xe8
> [cff43f40] [c01732dc] cpufreq_register_driver+0xa4/0x120
> [cff43f50] [c025880c] pmac_cpufreq_setup+0x66c/0x688
> [cff43f80] [c024a1e4] kernel_init+0xc8/0x284
> [cff43ff0] [c001084c] kernel_thread+0x44/0x60
> Instruction dump:
> 4e800421 801f0000 3d20c005 57cb052a 39290eb8 2f0b0400 7f804800 419e0030
> 3d20c02a 80098508 7c000034 5400d97e <0f000000> 2f800000 41be0048 38000001
> io scheduler noop registered (default)
> io scheduler cfq registered
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
prev parent reply other threads:[~2007-08-12 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 22:42 Oops on boot with 2.6.23-rc2-g2c9d365c Guido Guenther
2007-08-12 21:05 ` Benjamin Herrenschmidt [this message]
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=1186952737.1576.48.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=agx@sigxcpu.org \
--cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).