All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Villací­s Lasso" <a_villacis@palosanto.com>
To: Keith Packard <keithp@keithp.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Memory corruption starting in i915 code, in 3.2-rc5
Date: Tue, 13 Dec 2011 10:14:15 -0500	[thread overview]
Message-ID: <4EE76BC7.4070000@palosanto.com> (raw)
In-Reply-To: <86pqftivy8.fsf@sumi.keithp.com>

El 12/12/11 11:41, Keith Packard escribió:
> On Mon, 12 Dec 2011 09:51:19 -0500, Alex Villací­s Lasso<a_villacis@palosanto.com>  wrote:
>
>> Ran kernel with reverted patch for 6 hours without issues so far. Will
>> keep testing after work (issue happens with my home machine).
> Thanks much. Let me know if it's still stable this evening; I can send a
> revert along if you don't find any problems.
>
I just had a severe problem, but I am not sure if the patch (or its revert) is at fault.

I was running 3.2-rc5 at home, for an hour or so, when suddenly I could not launch any programs. I tried switching to the text console, but the login program restarted itself after typing "root", without waiting for the password. I then tried to reboot, 
but all of the installed kernels (even the stock Fedora ones) issued a kernel panic very early in the boot sequence, mentioning an attempt to kill init. By using a bootable USB stick, I could check the logs, which showed many segfaults at 
/lib64/ld-2.14.90.so . Even though running fsck -f on my / and /boot partitions (both ext4) showed no errors besides an unclean shutdown, the kernel panics on boot persisted. I eventually reinstalled the system from scratch, and kept my /home partition so 
that no important data was lost. I am still in the process of restoring my package list to the state before the crash.

Maybe the list corruption I experienced earlier was secondary damage, which now spread somewhere else and corrupted system files, but I do not have enough data to check this.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2011-12-13 15:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-11 18:36 Memory corruption starting in i915 code, in 3.2-rc5 Alex Villacís Lasso
2011-12-11 20:46 ` Keith Packard
2011-12-11 21:29   ` Alex Villacís Lasso
2011-12-12 14:51     ` Alex Villací­s Lasso
2011-12-12 16:41       ` Keith Packard
2011-12-13 15:14         ` Alex Villací­s Lasso [this message]
2011-12-13 18:14           ` Keith Packard
2011-12-13 18:26             ` Daniel Vetter
2011-12-16 19:22               ` Keith Packard
2011-12-16 22:04                 ` Ben Widawsky
2011-12-13 18:36             ` Daniel Vetter

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=4EE76BC7.4070000@palosanto.com \
    --to=a_villacis@palosanto.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.