Re: kernel BUG at mm/page_alloc.c:796 (2.6.7-mm7)

[Jens Axboe]

On Fri, Jul 09 2004, Jens Axboe wrote:
> On Fri, Jul 09 2004, Jürg Billeter wrote:
> > Just built and installed 2.6.7-mm7 and on startup I get the following
> > BUG message. config and lspci output to be found below. 2.6.7-mm6 didn't
> > have this problem on my computer. I can provide more information if
> > requested. Please CC me on reply.
> > 
> > kernel BUG at mm/page_alloc.c:796!
> > invalid operand: 0000 [#1]
> > PREEMPT
> > Modules linked in: ds pcmcia_core freq_table nfs lockd sunrpc ohci_hcd
> > e100 snd_intel8x0 snd_ac97_codec snd_pcm snd_timer snd_page_alloc
> > snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore ehci_hcd
> > uhci_hcd ipt_REJECT ipt_LOG ipt_MASQUERADE ip_nat_irc ip_nat_ftp
> > iptable_nat
> > ipt_state ip_conntrack_irc ip_conntrack_ftp ip_conntrack iptable_filter
> > ip_tables ext3 jbd mbcache
> > CPU:    0
> > EIP:    0060:[<c0135581>]    Not tainted VLI
> > EFLAGS: 00010256   (2.6.7-mm7-upkg1)
> > EIP is at __free_pages+0x31/0x40
> > eax: 00000000   ebx: f7faf2c0   ecx: c16e3d00   edx: 00000000
> > esi: f7fb2900   edi: f7fb28c0   ebp: 00000001   esp: f799fd70
> > ds: 007b   es: 007b   ss: 0068
> > Process hald (pid: 2748, threadinfo=f799e000 task=f7891190)
> > Stack: c015276d fffffff2 f7c02a64 00000000 f799fe18 f7c02a64 c0246a5a
> > f799fea4
> >        00007425 c0249dbe 00000020 f7fb2900 f7feda80 f7c1097c 00000246
> > 00000000
> >        00000020 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > Call Trace:
> >  [<c015276d>] bio_uncopy_user+0x5d/0x90
> >  [<c0246a5a>] blk_rq_unmap_user+0x3a/0x40
> >  [<c0249dbe>] sg_io+0x23e/0x290
> >  [<c024a260>] scsi_cmd_ioctl+0x1e0/0x390
> 
> You're not using 2.6.7-mm7 virgin, it has no BUG() at that line. Care to
> fill in what code is around line 796 in mm/page_alloc.c?

Nevermind, I gather it's put_page_testzero(). Hmm double free, I'll take
a look.

-- 
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/