** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/348694
Title:
Jaunty will not boot on Dell Optiplex 760 unless hpet=disable
To manag
The bug task for the somerville project has been removed by an automated
script. This bug has been cloned on that project and is available here:
https://bugs.launchpad.net/bugs/1305936
** No longer affects: somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: somerville
Status: New => Fix Released
** No longer affects: dell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/348694
Title:
Jaunty will not boot on Dell Optiplex 760 unless
** Changed in: dell
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
Jaunty will not boot on Dell Optiplex 760 unless hpet=disable
https://bugs.launchpad.net/bugs/348694
You received this bug notification because you are a member of Ubuntu
Bugs, w
Good news! Dell has released an updated BIOS that remedies the problem.
Rev A03 for the Dell Optiplex 760 can be found at:
http://ftp.us.dell.com/bios/O760-A03.EXE
I have updated my test system to this revision, and confirmed that HPET
interrupts now correctly reach the Linux kernel with C stat
Luis:
It was under Intrepid that I first noticed clock problems myself.
In fact, the Intrepid LiveCD has an old enough version of the kernel
that you may see what I call, "Infinite spew," where the HPET code prints a
kernel oops on every clock tick.
I read a lot of deltas on kernel.org dealing
I have an Optiplex 760 with Intrepid installed.
I did notice a slower that usual boot up in this computer but i didn't pay much
attention until I tried the Jaunty CD, and thats how I found this bug report.
With Intrepid, sometimes, and only sometimes, I had to hit the keyboard
during boot for the
Fabián:
Also make sure that the BIOS setting, "C States Control" under "Performance" is
set in the BIOS.
This setting is not enabled by default unless you go for an Energy Star Custom
Factory Integration.
As Mario said, the option is only available for higher end processors.
--
Jaunty will not
Fabián:
Double check what CPU you have in the system. It needs to be one of the
higher end CPUs to be able to reproduce this. Also, with the higher end
CPU, you will have a BIOS option for it.
Fabián Rodríguez wrote:
> I've just received an Optiplex 760 and Jaunty Beta DVD ISO image runs
> just
I've just received an Optiplex 760 and Jaunty Beta DVD ISO image runs
just fine without any special kernel options. BIOS is A02 too.
--
Jaunty will not boot on Dell Optiplex 760 unless hpet=disable
https://bugs.launchpad.net/bugs/348694
You received this bug notification because you are a member
Someone suggested out of band that I open a kernel.org bugzilla.
By way of preparation for doing that, I searched the existing bugzilla
for "ACPI CPU C3 interrupt" and turned up additional insight:
In BZ 10409
http://bugzilla.kernel.org/show_bug.cgi?id=10409
it was suggested leaving HPET enabled
It was suggested to me out of band to look at the output of powertop.
So I enabled C States in the BIOS and got Jaunty running again (hitting
the power switch 30-some times and the Ctrl key on the keyboard 500-some
times to create interrupts to get it to where I could run powertop.
powertop showe
Here is more information on the C States from the Dell Senior Tech:
C3 Deep Sleep
Stops all CPU internal and external clocks
Pentium II and above, but not on Core 2 Duo E4000 and E6000;
AMD Turion 64
http://www.hardwaresecrets.com/article/611/4
C4 Deeper Sleep
Reduces CPU voltage
Pentium M
Thanks for the details, Mario.
Apparently my CPU has the C States thing, but yours does not, but the
clue as to who does and who does not isn't obvious. The Dell Tech is
going to follow up to find out.
So anybody wanting to reproduce my problem will need a fancier CPU than
yours, but it isn't ye
Hi William:
It looks like it does claim to have EST:
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 15
model name: Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz
stepping: 13
cpu MHz: 2400.000
cache size: 2048 KB
physical id: 0
siblings:
I have a Core 2 Duo E8400 CPU.
The Dell Senior Tech said that the C States are available with CPU chips
that have the "EIST" (for Enhanced Intel Speedstep Technology) processor
option. He'd like to know which CPU he has to re-confirm that the
option isn't present for your CPU.
According to some
Hi William:
Did the technician mention at all whether this option is only available
in certain CPU configurations? I'm looking at a 760 w/ BIOS A02 right
now, and don't see any such option under Performance (or anywhere else
for that matter).
I see:
* Multi Core Support
* Intel SpeedStep
* Limit
With the help of a senior Tech at Dell, the relevant BIOS bit has been
identified:
Under "Performance", the bit "C States Control" determines whether or
not there will be a problem. If the additional processor sleep states
are enabled by turning this option on, the HPET clock breaks.
I have Dell
Actually, I was the one who cut open the box.
I also checked with the MIT folk who received the hardware from Dell.
The settings are as they came from the factory.
My current theory is that there are two defaults: "High Performance"
defaults that are set at the factory before the system ships out
Hi William:
This is possible, but it's also possible that MIT made some changes to
the BIOS settings too before providing you the machine.
Towards your Dell Factory changing a setting:
Try toggling AHCI->ATA. If these systems were shipped with Windows,
it's quite possible that setting gets flipp
The prospect of, flip a bios bit, boot CD, repeat for all bits seems
rather daunting.
On the assumption that it was an Intrepid post-install nastiness with some
software MIT integrated, I used biosdecode, dmidecode, dumpCmos and dumpSmbios
to take
a snapshot of as much BIOS state as I could, and
Hi William:
I'd recommend going through and just flipping different settings in the
BIOS to find the one that is causing the problems. One we know which
one is doing it, we should be able to in the short term document it, and
in the long term fix what's breaking from it.
William Cattey wrote:
>
WOW!
I was skeptical that "Load BIOS Defaults" was going to make any
difference, but INDEED, Jaunty started right up.
The image is the most recent one posted to cdimage.ubuntu.com/daily-live/current
which is dated 24-Mar-2009, filename, "jaunty-desktop-i386.iso"
QUESTION: Any suggestions on how
When's the last jaunty image you've ran? Can you check whether it works
with Load BIOS Defaults (so as to rule out a post install configuration
related item)
--
Jaunty will not boot on Dell Optiplex 760 unless hpet=disable
https://bugs.launchpad.net/bugs/348694
You received this bug notification
I have one of these new Dells as well; same problems here. I don't see
a way to make Intrepid usable without disabling acpi completely.
(...and losing a CPU.)
To answer a question above: a lot of the ICH10 support is fairly new.
I'm not convinced that the real problem isn't in Dell's firmware.
Although Intrepid still runs through the HPET code path, setting
hpet=disable is the smallest scope change to get Jaunty working.
** Summary changed:
- Jaunty will not boot on Dell Optiplex 760 unless acpi=off
+ Jaunty will not boot on Dell Optiplex 760 unless hpet=disable
--
Jaunty will not bo
26 matches
Mail list logo
