http://bugzilla.kernel.org/show_bug.cgi?id=13065





--- Comment #2 from Rafael Varela Pet <rafael.var...@gmail.com>  2009-04-13 
16:50:26 ---
Thank you for yor support

As I said in my initial report, I've already tested it in single-user mode, so
there's almost any process running.

Anyway, I've used the command "lsof /proc/acpi/events" to be sure that anybody
was using /proc/acpi/event, and it didn't show anything, as expected.

While trying this, I tried a slight variation on the test:

After enabling silent mode, instead of pushing the "Enter" key several times, I
waited for a while. Nothing happened, so it seemed that it wasn't going to
crash. 

I entered the "sync" command and it crashed again, but this time it didn't
reboot and i could see some kernel messages which said something like this:

  CPU0: Machine Check Exception

  RIP !INEXACT!  10: <ffffffff80429e0e> (_spin_lock ....

  TSC 1e6962ba7c
  This is not a software problem!
  Run through mcelog --ascii to decode and ....

  HARDWARE ERROR
  CPU1: Machine Check Exception:

  TSC 1e6962becc

  Kernel panic - not syncing: Machine check


As you can see it says that is not a software problem, but this is a dual-boot
machine and it does not crash while running Windows XP.

Also, it does not crash while waiting in the GRUB bootloader menu (and I cannot
activate silent mode either)

I'll install mcelog to give you the information suggested by the kernel
messages

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to