linux-kernel - Re: [2.6.19-rc3-mm1] BUG at arch/i386/mm/pageattr.c:165

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200610302203.37570.ajwade@cpe001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com>
Date:	Mon, 30 Oct 2006 22:03:36 -0500
From:	Andrew James Wade <andrew.j.wade@...il.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	andrew.j.wade@...il.com, linux-kernel@...r.kernel.org,
	Andi Kleen <ak@...e.de>
Subject: Re: [2.6.19-rc3-mm1] BUG at arch/i386/mm/pageattr.c:165

On Monday 30 October 2006 21:04, Andrew Morton wrote:
> On Mon, 30 Oct 2006 20:26:24 -0500
> Andrew James Wade <andrew.j.wade@...il.com> wrote:
> 
> > I got the BUG below while booting. -rc2-mm2 worked fine, but with a
> > different .config. I'm going to try and narrow this down further.
> > 
> > cheers,
> > Andrew Wade
> > 
> > agpgart: Detected VIA KT266/KY266x/KT333 chipset
> > agpgart: unable to get minor: 175
> > agpgart: agp_frontend_initialize() failed.
> > ------------[ cut here ]------------
> > kernel BUG at arch/i386/mm/pageattr.c:165!
> > invalid opcode: 0000 [#1]
> > last sysfs file: 
> > CPU:    0
> > EIP:    0060:[<c010fdd7>]    Not tainted VLI
> > EFLAGS: 00010082   (2.6.19-rc3-mm1 #1)
> > EIP is at change_page_attr+0x167/0x234
> > eax: 1fc001e3   ebx: c1009c80   ecx: dfc20000   edx: c04e4dfc
> > esi: 1fc20000   edi: e0820000   ebp: 00000005   esp: dffc5e7c
> > ds: 007b   es: 007b   ss: 0068
> > Process swapper (pid: 1, ti=dffc4000 task=dffc3530 task.ti=dffc4000)
> > Stack: 00000011 c13f8400 00000010 00000292 c04e4dfc dfc20000 00000163 00000163 
> >        c13f8200 dfe66984 e0820000 00000005 c010fab8 c03ee740 c03ee740 dfe2334c 
> >        00000004 e080f000 c0289195 dfe2334c dfe2334c e080f000 c02881f6 fffffffb 
> > Call Trace:
> >  [<c010fab8>] iounmap+0xaa/0xdc
> >  [<00000004>] 0x4
> >  =======================
> > Code: 84 b7 00 00 00 eb d2 ff 43 0c eb 23 84 c0 78 1b 0b 74 24 1c 8b 54 24 10 89 32 8b 43 0c 85 c0 75 04 0f 0b eb fe 48 89 43 0c eb 04 <0f> 0b eb fe 8b 03 f6 c4 04 75 6c f6 05 0c 7c 45 c0 08 74 63 83 
> > EIP: [<c010fdd7>] change_page_attr+0x167/0x234 SS:ESP 0068:dffc5e7c
> >  <0>Kernel panic - not syncing: Attempted to kill init!
> 
> I'd be suspecting x86_64-mm-i386-clflush-size.patch and
> x86_64-mm-i386-cpa-clflush.patch.  Because x86_64-mm-cpa-clflush.patch made
> my x86_64 box instacrash in a similar manner, so I reverted that.
> 
> below is a ptch which reverts x86_64-mm-i386-clflush-size.patch and
> x86_64-mm-i386-cpa-clflush.patch.  Can you test it please?

Same crash I'm afraid.
However, I was too aggressive in trimming the kernel log: there are
some earlier errors:
Unable to create device for VGA+; errno = -17
...
Unable to create device for frame buffer device; errno = -17

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