[Bug 588643] Re: Lockup with stacktrace (native_smp_send_reschedule)

2010-06-04 Thread Jean-Louis Dupond
Got a totally other result today ... Seems like its more a hardware issue then Kernel issue. We can close it with 'Invalid' ? :) ** Attachment added: dmesg http://launchpadlibrarian.net/49653852/dmesg -- Lockup with stacktrace (native_smp_send_reschedule)

[Bug 588643] Re: Lockup with stacktrace (native_smp_send_reschedule)

2010-06-04 Thread Jean-Louis Dupond
Sadly it seems the hardware/bios that is f00bar .. :( ** Changed in: linux (Ubuntu) Status: Triaged = Invalid -- Lockup with stacktrace (native_smp_send_reschedule) https://bugs.launchpad.net/bugs/588643 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 588643] Re: Lockup with stacktrace (native_smp_send_reschedule)

2010-06-02 Thread Jean-Louis Dupond
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/49546058/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/49546059/AplayDevices.txt ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/49546060/ArecordDevices.txt

[Bug 588643] Re: Lockup with stacktrace (native_smp_send_reschedule)

2010-06-02 Thread Jean-Louis Dupond
Oh btw, I have this issue from the day I replaced my CPU from a AMD Athlon 3800+ (single core) to a Phenom 2 945. -- Lockup with stacktrace (native_smp_send_reschedule) https://bugs.launchpad.net/bugs/588643 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 588643] Re: Lockup with stacktrace (native_smp_send_reschedule)

2010-06-02 Thread Jeremy Foshee
Hi Jean-Louis, If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the

[Bug 588643] Re: Lockup with stacktrace (native_smp_send_reschedule)

2010-06-02 Thread Jean-Louis Dupond
** Tags removed: needs-upstream-testing -- Lockup with stacktrace (native_smp_send_reschedule) https://bugs.launchpad.net/bugs/588643 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 588643] Re: Lockup with stacktrace (native_smp_send_reschedule)

2010-06-02 Thread Jean-Louis Dupond
Seems like I have the same issue on 2.6.35-999-generic #201006021335. Will try to make a screenshot of the error it gives on the screen! -- Lockup with stacktrace (native_smp_send_reschedule) https://bugs.launchpad.net/bugs/588643 You received this bug notification because you are a member of

[Bug 588643] Re: Lockup with stacktrace (native_smp_send_reschedule)

2010-06-02 Thread Jean-Louis Dupond
Was able to get a full trace using the daily kernel. The time it took to hit the bug was MUCH longer ** Attachment added: dmesglog http://launchpadlibrarian.net/49572407/dmesglog -- Lockup with stacktrace (native_smp_send_reschedule) https://bugs.launchpad.net/bugs/588643 You received this

[Bug 588643] Re: Lockup with stacktrace (native_smp_send_reschedule)

2010-06-02 Thread Jeremy Foshee
** Changed in: linux (Ubuntu) Status: Incomplete = Triaged ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: kernel-uncat -- Lockup with stacktrace (native_smp_send_reschedule) https://bugs.launchpad.net/bugs/588643 You received this bug notification because