Bug 8069
Summary: | clock way to fast | ||
---|---|---|---|
Product: | Timers | Reporter: | Jethro Borsje (jborsje) |
Component: | Realtime Clock | Assignee: | john stultz (john.stultz) |
Status: | REJECTED INSUFFICIENT_DATA | ||
Severity: | high | CC: | acpi-bugzilla, bunk, protasnb |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.17-10mdv | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
A zip file of the requested output for 2.6.17-11mdv
A zip file of the requested output for 2.6.17-14mdv |
Description
Jethro Borsje
2007-02-23 02:47:31 UTC
does it get better with "acpi=off"? If I use "acpi=off" my NIC (Realtek RTL8139) does not work anymore. On Thu, 2007-03-08 at 00:18 -0800, bugme-daemon@bugzilla.kernel.org wrote: > ------- Additional Comments From jborsje@xs4all.nl 2007-03-08 00:18 ------- > If I use "acpi=off" my NIC (Realtek RTL8139) does not work anymore. Can you check the clock nevertheless ? tglx Yes "acpi=off" fixes the problem with the clock. Was there a version of the kernel that did not exhibit this behavior? Also are you running the latest version of your system's BIOS? For both the default and the "acpi=off" case, please attach the complete dmesg and paste the /proc/interrupts [quote]Was there a version of the kernel that did not exhibit this behavior?[/quote] Not that I know of. [quote]Also are you running the latest version of your system's BIOS?[/quote]I believe I am, I am not able to find a newer version. [quote]For both the default and the "acpi=off" case, please attach the complete dmesg and paste the /proc/interrupts[/quote] I will provide this information within the next few days. Jethro? I am so sorry, you are right, I still have to provide the information. I will start collecting it right away. Does this happen with a more recent kernel as well ? Created attachment 11662 [details]
A zip file of the requested output for 2.6.17-11mdv
This zip file contains the requested output. I apologize for taking so long.
Can you let me know if it helps? If you need any more information please do not
hesitate to ask.
==================================================================
NOTE: apic and lapic where always on
==================================================================
DEFAULT CASE:
- no extra boot options
- acpi = on
- nic works fine
- clock is too fast
==================================================================
ACPI=OFF CASE:
- no extra boot options
- acpi = off
- nic does not work
- clock works fine
- no GUI anymore when booting normally with this configuration (from
lilo.conf):
[quote]
default="linux"
boot=/dev/sda
map=/boot/map
keytable=/boot/us-intl.klt
menu-scheme=wb:bw:wb:bw
compact
prompt
nowarn
timeout=100
message=/boot/message
image=/boot/vmlinuz
label="linux"
root=/dev/sda6
initrd=/boot/initrd.img
append="resume=/dev/sda7 splash=silent acpi=ht"
vga=788
[/quote]
I managed to boot into the failsafe mode:
[quote]
image=/boot/vmlinuz
label="failsafe"
root=/dev/sda6
initrd=/boot/initrd.img
append="failsafe resume=/dev/sda7"
[/quote]
This placed me on the command line as root. I could then run "startx" (as
root). Which resulted in a proper KDE session. In this session the NIC was not
working.
==================================================================
WORKING CASE:
- extra boot options: "noapictimer irqpoll"
- acpi = on
- nic works fine
- clock works fine
I forgot to say I created the output with 2.6.17-11mdv. I now see that there is a kernel 2.6.17-14mdv available from the rpm sources. I will upgrade to this one and try it again. Created attachment 11670 [details]
A zip file of the requested output for 2.6.17-14mdv
Here is the requested output with kernel 2.6.17-14mdv.
==========================================
NOTE: apic and lapic are always on
==========================================
DEFAULT CASE:
- no extra boot options
- acpi=on
- nic works fine
- clock too fast
- USB did not work (it chrashed in 30 seconds)
==========================================
ACPI=OFF CASE:
- no extra boot options
- acpi=off
- nic does not work
- clock too fast
- I did not experience a USB crash
- I had the same GUI problems as with 2.6.17-10mdv
==========================================
WORKING CASE:
- extra boot options: "noapictimer irqpoll"
- acpi = on
- nic works fine
- clock works fine
==========================================
So overall the new kernel introduced a USB problem, and also made the clock
going to fast when booting with acpi=off. In 2.6.17-10mdv at least the clock
worked when booting with acpi=off (and I also did not experience the USB
problem).
Any progress with this so far? Jethro, how does this work with newer kernels? Thanks. No response |