• Status Closed
  • Percent Complete
  • Task Type Bugs
  • Category Music playback
  • Assigned To
  • Operating System
  • Severity Low
  • Priority Very Low
  • Reported Version Release 1.3
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by Anonymous Submitter - 2002-09-30
Last edited by bagder - 2002-10-11

FS#325 - CPUAdrEr at 0f00079a during playback

Archos Jukebox Recorder 10
Built-in firmware 1.27b
Rockbox 1.3

Selected a playlist, used » to skip the first albums
worth of MP3's, and then allowed it to play. On about
the 4th track, I received an:
at 0f00079A
error. I shutdown and restarted, attempted the same
sequence, but it worked fine the second time.


Closed by  bagder
2002-10-11 06:26
Reason for closing:  Fixed
Anonymous Submitter commented on 2002-10-02 23:56

Well, this is getting downright annoying. This error appears
every 15-60 minutes while playing on my Recorder. Is
anyone else having this problem?


I've actually seen this on my Recorder 15 a couple times. I
only got it to do it twice, both times in the same folder of
MP3s. Hasn't happened since, though.


Project Manager
zagor commented on 2002-10-03 08:17

Does this happen with the daily builds too, or just 1.3?

It happened those two times on 1.3. I did get it to do it once
on the daily build (10/1 I believe), but I'm using 10/1 now and
it's been fine.


I just got it again. This time the error looked like:

at 0F00084A

This is on a recorder 15 with 9/30 version.

Project Manager

Just double checking, are you absolutely sure that you typed the error
message correctly? And are you absolutely sure that you ran the 9/30
daily build?

What did you do when that last crash happened?
Battery status?

The latest crash is not the same that you had in
the original report. This looks like a serious bug…

Project Manager

I have found and fixed a bug in the mpeg code (the bitswapping) that could
cause CPUAddr errors. Please try the latest daily build and see if the
crashes are gone.

I double checked the version, and it was definitely the 9/30
build. I also made sure to get the memory address correct in
the error. I'm not sure about the battery status, but I did have
the adapter plugged in and have the "drain and charge" option
turned on, so the battery could have been low at the time. If I
see it again, I'll check that. Is there any other data I should
collect to help you debug?

Project Manager

Yes, you should try the daily build that arrives at october
9, or one of the current bleeding edge builds. This problem
is believed to have been fixed in CVS.

Anonymous Submitter commented on 2002-10-09 19:16

The October 9 build seems to have solved this problem for

Thanks Linus.



Available keyboard shortcuts


Task Details

Task Editing