YDL 3.0 Crashes 800 MHz Titaniam Laptop
John Howland
yellowdog-general@lists.terrasoftsolutions.com
Sun Jun 22 06:33:01 2003
On Fri, 20 Jun 2003, John Howland wrote:
> On Fri, 20 Jun 2003, John Howland wrote:
>
> > I have a G4 Titanium laptop which repeatededly crashes
> > while running YDL 3.0. The machine runs the Apple diagonistics
> > and seems to run OSX in reliable fashion. Does anyone else
> > have this experience?
>
> This is one of the kinds of failures I have seen:
>
> Hello,
> does this (see following between snip/snap) during startup of the first CD:
>
> ------------snip--------------
> Oops: Kernel access of bad area, sig. 11
> NIP: C01E5670 XER: 20000000 LR: C01E64A0 SP: C0273BC0 REGS: c0273d10
> TRAP: 0300 Not tainted
> MSR: 00009032 EF: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 20000000, DSISR: 40000000
> TASK=c0272000[11] 'loader' last syscall: 3
> last math c0272000 last activec 00000000
> ....
> ----------snap----------------
>
> mean, my machine (NewWorld iMac) has a hardware problem? Like RAM?
> (I tried all the install CD images I found up to the latest, May 30th)
>
> Best Regards and Have a nice day,
> Igor
>
> >
> > I have installed everything and found that
> > pwrctl and pwrctl-local in /etc/power were not executable.
> > Various pmud features were not available until file modes
> > were changed. I found that by default pmud runs the
> > processor at 667 MHz rather than 800 MHz even when running
> > on AC power. I introduced the code:
> >
> > case "$2" in
> > ac)
> > $logger -p daemon.info -t pwrctl-local "setting cpu speed 800000 MHz"
> > echo -n "800000:800000:performance" > /proc/cpufreq
> > ;;
> > battery)
> > $logger -p daemon.info -t pwrctl-local "setting cpu speed 667000 MHz"
> > echo -n "667000:667000:powersave" > /proc/cpufreq
> > ;;
> > esac
> >
> > in pwrctl-local to run faster when on AC. I cannot trace the kernel
> > crashes to this change as the machine crashes when pwrctl and
> > pwrctl-local and pmud are disabled.
> >
> > I have compiled kernels but have been unable to achieve the same
> > kernel features as YDL 3.0 and the kernels I've built also
> > crash the machine. The crashes are easiest to produce by compiling
> > a kernel, but sometimes come when the machine is not being used.
> >
> > I would appreciate any input or suggestions before I send the
> > machine back to Apple (for the second time) for repairs.
> >
Now one has responded yet to my query. Most failures leave no logged
messages. Here is one from /var/log/messages
Jun 9 16:57:39 Amalthea kernel: Oops: kernel access of bad area, sig: 11
Jun 9 16:57:39 Amalthea kernel: NIP: C002BD20 XER: 20000000 LR: C0029FD4 SP: D96A5DA0 REGS: d96a5cf0 TRAP: 0300 Tainted: GF
Jun 9 16:57:39 Amalthea kernel: MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
Jun 9 16:57:39 Amalthea kernel: DAR: 000000FD, DSISR: 40000000
Jun 9 16:57:39 Amalthea kernel: TASK = d96a4000[1122] 'fam' Last syscall: 142
Jun 9 16:57:39 Amalthea kernel: last math d96a4000 last altivec 00000000
Jun 9 16:57:39 Amalthea kernel: GPR00: C0029FD4 D96A5DA0 D96A4000 00000000 000000FD 0FCD0000 0000C000 C02C0000
Jun 9 16:57:39 Amalthea kernel: GPR08: DC36C4E8 00000001 00000000 DA965740 00000000 1003BEAC 00000000 00000000
Jun 9 16:57:39 Amalthea kernel: GPR16: 00000000 00000000 00000000 00000000 00009032 196A5F40 0FCD0000 00000000
Jun 9 16:57:39 Amalthea kernel: GPR24: 0FCDC000 100D0000 000000FD DC36C4C0 0000C000 0FCDC000 000000FD 000000FD
Jun 9 16:57:39 Amalthea kernel: Call backtrace:
Jun 9 16:57:39 Amalthea kernel: 00000000 C0029FD4 C002D5CC C00172D8 C001C6C4 C00231D0 C00064C8
Jun 9 16:57:39 Amalthea kernel: 1000FCA8 10013B38 100170CC 0FD1904C 00000000
Jun 9 16:57:39 Amalthea kernel: Oops: kernel access of bad area, sig: 11
Jun 9 16:57:39 Amalthea kernel: NIP: C004C800 XER: 00000000 LR: C004C778 SP: DEBE5E30 REGS: debe5d80 TRAP: 0300 Tainted: GF
Jun 9 16:57:39 Amalthea kernel: MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
Jun 9 16:57:39 Amalthea kernel: DAR: 00000008, DSISR: 40000000
Jun 9 16:57:39 Amalthea kernel: TASK = debe4000[632] 'pbbuttonsd' Last syscall: 5
Jun 9 16:57:39 Amalthea kernel: last math d8ba2000 last altivec 00000000
Jun 9 16:57:39 Amalthea kernel: GPR00: 00000000 DEBE5E30 DEBE4000 00000000 DFFFC1A0 00000004 DEF52A3F 00000009
Jun 9 16:57:39 Amalthea kernel: GPR08: DFFFC1A0 DFFE60C8 00006FFF DFFE60C8 0FFC96E8 100217E8 00000000 00000000
Jun 9 16:57:39 Amalthea kernel: GPR16: 00000000 00000000 00000000 00000000 00009032 1EBE5F40 00000000 C0006494
Jun 9 16:57:39 Amalthea kernel: GPR24: C0006200 00000004 00000001 DEBE5ED8 DFFFE360 FFFFFFFE CBAD9006 00000000
Jun 9 16:57:39 Amalthea kernel: Call backtrace:
Jun 9 16:57:39 Amalthea kernel: C004C7A4 C004CD64 C004CF78 C004D4FC C003F0B8 C003F48C C000625C
Jun 9 16:57:39 Amalthea kernel: 0FFCA4F4 0FEE5230 0FEE529C 100030B4 10002D8C 10001EC8 100022CC
Jun 9 16:57:39 Amalthea kernel: 100012E8 0FE9904C 00000000
Jun 9 16:57:40 Amalthea kernel: Oops: kernel access of bad area, sig: 11
Jun 9 16:57:40 Amalthea kernel: NIP: C004C800 XER: 00000000 LR: C004C778 SP: DDC59E30 REGS: ddc59d80 TRAP: 0300 Tainted: GF
Jun 9 16:57:40 Amalthea kernel: MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
Jun 9 16:57:40 Amalthea kernel: DAR: 00000008, DSISR: 40000000
Jun 9 16:57:40 Amalthea kernel: TASK = ddc58000[734] 'sendmail' Last syscall: 5
Jun 9 16:57:40 Amalthea kernel: last math ddc58000 last altivec 00000000
Jun 9 16:57:40 Amalthea kernel: GPR00: 00000000 DDC59E30 DDC58000 00000000 DFFFC1A0 00000004 DEF52A3F 00000006
Jun 9 16:57:40 Amalthea kernel: GPR08: DFFFC1A0 DFFE60C8 00006FFF DFFE60C8 100D8308 100C3944 100E0000 100C0000
Jun 9 16:57:40 Amalthea kernel: GPR16: 7FFFD558 00000000 00000000 00000000 00009032 1DC59F40 00000000 C0006494
Jun 9 16:57:40 Amalthea kernel: GPR24: C0006200 00000004 00000001 DDC59ED8 DFFFE360 FFFFFFFE CB745006 00000000
Jun 9 16:57:40 Amalthea kernel: Call backtrace:
Jun 9 16:57:40 Amalthea kernel: C004C7A4 C004CD64 C004CF78 C004D4FC C003F0B8 C003F48C C000625C
Jun 9 16:57:40 Amalthea kernel: 00000000 1007E5F0 10012B74 10012C90 10012E8C 10017334 10007F4C
Jun 9 16:57:40 Amalthea kernel: 0FAB804C 00000000
Jun 9 16:59:50 Amalthea syslogd 1.4.1: restart.
Anyone have any ideas as to whether this is a hardware problem?
I have now verified that the failures occur in OS X as well.
> >
>
>
--
_______________________________________________________________
John E. Howland url: http://www.cs.trinity.edu/~jhowland/
Computer Science email: jhowland@ariel.cs.trinity.edu
Trinity University voice: (210) 999-7364
One Trinity Place fax: (210) 999-7477
San Antonio, Texas 78212-7200