This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
** Also affects: linux (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Karmic)
Status: New = Won't Fix
** Changed in: linux (Ubuntu Lucid)
Status: New = Won't
At this point I think two things should be tried and reported:
1. Does experimenting with the boot option described in the previous comment
lead to any success?
2. It might be interesting to see the results of a run of the firmware test
suite (without suspend and hibernate tests). This can be
Ok, I will try those as well. Sorry for the delay in getting
information collected, this week got kinda hectic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/217849
Title:
Hardy, Intrepid, Jaunty
I just want to repeat some observations I made over time here: I have
seen this on quite a few machines. Though solutions vary and I am not
sure there is a good automated way yet. The basic problem is that using
lower C-states has some effects on the timer tick sources normally used
(lapic and tsc
Please try the Maverick Live CD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/217849
Title:
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
--
ubuntu-bugs mailing list
On Wed, Dec 8, 2010 at 8:32 AM, Tim Gardner tim.gard...@canonical.com wrote:
Please try the Maverick Live CD.
I've upgraded to Maverick on this machine and I am pretty sure the
problem still exists. Is there reason to believe the LiveCD would
behave differently? I'll confirm that the problem
QuentinHartman - It would be helpful if we could get your machine
information attached. Please run 'apport-collect 217849' which will
upload a bunch of HW info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Mon, May 10, 2010 at 9:49 PM, Rami Autiomäki
rami.autiom...@gmail.com wrote:
I have JFL92 laptop. Until now I used kernel parameter clocksource=jiffies to
prevent machine pauses. This has a downside that processor is polling all the
time and consuming a lot of power.
I discovered that
I think this https://bugzilla.kernel.org/show_bug.cgi?id=12118 is same
kind of bug report in kernel bug tracker. This bug seems to concern
other laptops than Compal or Sager also.
** Bug watch added: Linux Kernel Bug Tracker #12118
http://bugzilla.kernel.org/show_bug.cgi?id=12118
--
Hardy,
I have JFL92 laptop. Until now I used kernel parameter clocksource=jiffies to
prevent machine pauses. This has a downside that processor is polling all the
time and consuming a lot of power.
I discovered that better alternative is to use pci=nomsi as kernel parameter.
This will also allow me to
This is very often a BIOS issue which cannot be solved (very often due
to missing chipset documentation) by Linux. My recommendation would be
to try acpi_skip_timer_override added to the kernel boot arguments.
This will cause Linux to try finding a working connection to the timer
(see below).
[
I'll give that a shot.
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
https://bugs.launchpad.net/bugs/217849
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The nominations may not be appropriate. Please investigate and fix as
appropriate.
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
https://bugs.launchpad.net/bugs/217849
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi Chris,
On Mon, Feb 08, 2010 at 06:38:10PM -, Chris Johnston wrote:
The nominations may not be appropriate. Please investigate and fix as
appropriate.
It's not necessary to follow up asking for investigations of these
nominations. This generates more noise than the nominations
** This bug has been marked a duplicate of bug 217815
Installation stalls randomly until a key is pressed
** This bug is no longer a duplicate of bug 217815
Installation stalls randomly until a key is pressed
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
This seemed to be troll attacked. There is no fix for that. We got a
work-around but I don't know how to detect and fix misrouted irq0
overriders, yet.
** Changed in: linux (Ubuntu)
Status: Fix Committed = Triaged
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Committed
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
https://bugs.launchpad.net/bugs/217849
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: linux (Ubuntu)
Assignee: 3n!Gma (wm3) = Stefan Bader (stefan-bader-canonical)
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
https://bugs.launchpad.net/bugs/217849
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: linux (Ubuntu)
Assignee: Stefan Bader (stefan-bader-canonical) = 3n!Gma (wm3)
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
https://bugs.launchpad.net/bugs/217849
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It looks useful. At least to understand better. It looks like the timer
interrupt is actually connected to pin 0 of the apic, not pin 2 as the override
tells the system. Sadly I messed up with the debug options, so the apic table
was not dumped (the right one is apic=debug). But even with what
Yes I am. When using the debug options in conjunction with the skip
argument, the dmesg will contain some information about the system
trying figure out the right routing for the timer interrupt. That might
be interesting to look at.
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
dmesg output. Hope it's useful!
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/28128836/dmesg.txt
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
https://bugs.launchpad.net/bugs/217849
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ok, So I am running the daily mainline from today, June 11, and the
problem still exists. After rebooting I had to recompile my Nvidia
drivers. During the compilation the progress stopped at 30% for about 3
minutes. Once that time passed and I was quite sure it wasn't just
thinking _real hard_, I
Hi Quentin, sorry for not getting back for that long. If you have some time it
would be great if you could verify tat hangs against the latest daily kernel
from https://wiki.ubuntu.com/KernelMainlineBuilds
We want to make sure this problem still exists upstream. That kernel can be
installed in
On Thu, Jun 4, 2009 at 5:59 AM, Stefan Bader
stefan.ba...@canonical.comwrote:
Hi Quentin, sorry for not getting back for that long. If you have some time
it would be great if you could verify tat hangs against the latest daily
kernel from https://wiki.ubuntu.com/KernelMainlineBuilds
We want
On Thu, May 7, 2009 at 5:52 PM, Justin Lloyd captll...@gmail.com
wrote:
I too have this issue on a Sager NP2092/Compal JFL92. I have found that
switching the hard drive controller to IDE mode seems to help. However
this is a less than ideal solution.
Yay! I'm not alone! Does switching to
I too have this issue on a Sager NP2092/Compal JFL92. I have found that
switching the hard drive controller to IDE mode seems to help. However
this is a less than ideal solution.
I would like to help resolve this issue if anyone has any suggestions of
what I could do to track down the cause.
Just modified the title of this bug to make it more accurate.
** Summary changed:
- Hardy 64-bit beta and nightly alternate installation stalls
+ Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
https://bugs.launchpad.net/bugs/217849
just found a BIOS update for this machine, upgraded to version 1.16.
doesn't seem to have made a difference. still getting hiccups that
have to be tickled away with kb / mouse input.
--
Hardy, Intrepid, Jaunty 64 hiccup on Sager notebook.
https://bugs.launchpad.net/bugs/217849
You received this
30 matches
Mail list logo
