linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: francesco foresti <frafore@tiscali.it>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.20-1 not working on ibook g4 (BUG/Oops)
Date: Tue, 06 Mar 2007 01:18:14 +0000	[thread overview]
Message-ID: <1173143894.3461.240.camel@pmac.infradead.org> (raw)
In-Reply-To: <200703051414.15802.frafore@tiscali.it>

On Mon, 2007-03-05 at 14:13 +0100, francesco foresti wrote:
> Hi,
> i'm having problems trying to use 2.6.20-1 (taken from kernel.org, not 
> patched) on my ibook g4 (debian testing/unstable): 
> i'm getting two errors while trying to boot up, and i can only report the 
> second one because the other slips offscreen before i can see what's going 
> on. However, this is what i have been able to hand-copy:
>  
> kernel BUG at mm/slab.c:610!
> Oops: Exception in kernel mode, sig: 5 [#2]
> 
> Modules linked in: snd_aoa_codec_tas snd_aoa_fabric_layout snd_aoa 
> snd_aoa_i2sbus snd_pcm_oss snd_mixer_oss snd_pcm appletouch
> snd_timer snd_page_alloc snd soundcore snd_aoa_soundbus uninorth_agp agpgart 
> eth1394 evdev ext3 jbd mbcache dm_mirror dm_snapshot
> dm_mod usbhid ff_memless ide_cd cdrom ide_disk sungem sungem_phy ohci1394 
> ieee1394 ehci_hcd ohci_hcd usbcore i2c_powermac
> NIP: C007B5A4 LR: C007B740 CTR: 00000000
> REGS: effc7e50 TRAP: 0700  Not tainted  (2.6.20.1-powerpc)
> MSR: 00021032 <ME,IR,DR>  CR: 42000048 XER: 00000000
> TASK effc0bf0[3] 'events/0' THREAD: effc6000
> GPR00: 00000001 EFFC7F00 EFFC0BF0 EFFEE6E0 C0B1E008 00000000 00000000 00000000
> GPR08: C1D093Bc 00004000 FFFFFFF4 C031E000 00000000 00000000 00000000 00000000
> GPR16: 00000000 00000000 00000000 00000000 00000000 00000000 0164B230 41400000
> GPR24: 00000000 00311000 EFFF6920 00000018 00000000 00000000 C1C96A10 EFFEE6E0
> NIP [C007b5a4] free_block+0x5c/0x160
> LR [C007B740] drain_array+0x98/0xd8
> Call Trace:
> [EFFC7F00] [00000001] 0x1 (unreliable)
> [EFFC7F20] [C007B740] drain_array+0x98/0xd8
> [EFFC7F40] [C007CE0C] cache_reap+0x40/0x128
> [EFFC7F50] [C003E2C8] run_workqueue+0xb4/0x15c
> [EFFC7F70] [C003EB10] worker_thread+0x124/0x15c
> [EFFC7FC0] [C00423FC] kthread+0xc4/0x100
> [EFFC7FF0] [C0013998] kernel_thread+0x44/0x60
> Instruction dump:
> 3d20c02e 81692688 3d254000 5529c9f4 7c09582e 7c895a14 70094000 41a20008
> 8084000c 80040000 5400cffe <0f000000> 80e4001c 5789103a 3c000010

I've been seeing very similar behaviour with 2.6.20 on all pmac32
hardware. I haven't yet tried hard to reproduce on non-pmac.

-- 
dwmw2

       reply	other threads:[~2007-03-06  1:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703051414.15802.frafore@tiscali.it>
2007-03-06  1:18 ` David Woodhouse [this message]
2007-03-06  1:53   ` PROBLEM: 2.6.20-1 not working on ibook g4 (BUG/Oops) Paul Collins
2007-03-06 10:35     ` David Woodhouse
2007-03-07  4:53       ` Paul Collins
2007-03-07 11:04         ` Benjamin Herrenschmidt
     [not found]           ` <a8e1da0703121849y202b7e3clb39afca72731762d@mail.gmail.com>
2007-03-13  1:54             ` Fwd: " young dave
     [not found]             ` <1173769125.24454.58.camel@localhost.localdomain>
2007-03-15  1:27               ` young dave

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=1173143894.3461.240.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=frafore@tiscali.it \
    --cc=linux-kernel@vger.kernel.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).