Timing error with kernel

Bug #37553 reported by Dean Loros
This bug report is a duplicate of:  Bug #29420: Strange clock behaviour on powerpc-smp. Edit Remove
12
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Medium
Unassigned

Bug Description

Time/date will randomly go from current time/date to a time/date in the future or past--will cause most apps to crash randomly or start randomly (xscreensaver--gnomescreensaver will start repeatedly within a matter of minutes) Dial up will "time-out" within seconds--seems to be a timing issue between the two processors--single processor kernel acts normally with all else the same.

Tags: linux
Revision history for this message
DiegoCG (diegocg) wrote :

What hardware is this?

Revision history for this message
Dean Loros (autocrosser) wrote : Re: [Bug 37553] Re: Timing error with kernel

Dual MMD 1.25 G4 with 2g of Apple stock memory--480G's drivespace in two
internal & two external firewire--ATI 9600PRO modified for G4
operation---Apple Pro keyboard & Logitech Trackball. Bought new during
first quarter of 2003. Only other non-Apple is a Belkin 5 port USB pci card.

DiegoCG wrote:
> What hardware is this?
>
>

Revision history for this message
Dean Loros (autocrosser) wrote :

Last Kernel that worked was 15-11. -12 onward has had this error.

DiegoCG wrote:
> What hardware is this?
>
>

Revision history for this message
Dean Loros (autocrosser) wrote :

As before--Dual Mirror-Door 1.25-mostly stock with 2G ram--Problem is still there with "new" kernel updated on 5/18 (-23 SMP)--Any ideas? Or is there a way I could regress to the -11 SMP kernel so I could use both processors? (do not have a copy of the -11 kernel after I reinstalled my system in early April)

Revision history for this message
robT (rob-terhaar) wrote :

under -23-PowerPC-SMP i see the same clock problem.

see also:
bug #44040

Revision history for this message
Dean Loros (autocrosser) wrote :

"New" kernel update on 5/23/2006 has the same problems--no change. Is there anything I can send to help correct this problem?

Revision history for this message
jbauman (jonas-abgensets) wrote :

I have the same machine with the same problem. I looked through the smp kernel config file and noticed that the CONFIG_IRQ_ALL_CPUS option is set to y, which means interrupts are distributed across all cpus. I seem to remember in the back of my mind that some dual processor Power Macs had a problem with this and it needed to be set to route interrupts to the first cpu only. Another thing I noticed is that the nvram is not accessible with the smp kernel, CONFIG_NVRAM is set to m in the config and when I try to load the nvram module it fails. I did a quick google search on the error message and found this: http://patchwork.ozlabs.org/linuxppc/patch?id=5419
which seems to indicate that the nvram module should be compiled into the kernel instead of as a separate module. Perhaps someone can re-compile the kernel with these options corrected and see if it fixes the problem?

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.