Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
2012/6/16 Ben Hutchings <ben@decadent.org.uk>:
> On Fri, 2012-06-15 at 22:37 +0300, Martin-Éric Racine wrote:
>> Hi Jonathan,
>>
>> 2012/6/15 Jonathan Nieder <jrnieder@gmail.com>:
>> > Hi Martin-Éric,
>> >
>> > Martin-Éric Racine wrote:
>> >
>> >> I'm not sure if it's too early to report on kernel 3.4 or not, but
>> >> here it goes:
>> >
>> > Any package uploaded to the archive is open for bug reports. :)
>> >
>> > Could you send the full "oops" trace, starting at the first BUG line?
>> > (It should include the text "Not tainted".) Even better would be full
>> > "dmesg" output from booting and reproducing the bug.
>>
>> Here's the dmesg output at bootup, right after the first few oopses
>> have started to appear.
>
> The kernel is trying to free an inode and using an ACL pointer that
> should presumably be 0xffffffff (special value for ACL not in memory)
> but is instead 0xffffb4ff. This memory corruption could be a software
> bug (e.g. use after free) or a hardware fault.
>
> What was the last working kernel version on this system?
3.2.0-19 (or whatever 486 kernel is in Testing) is what's normally
running on this one.
Reply to: