Hijack v223 is now out, with a fix for a kernel bug that has been causing many (if not all) of the player lockups people have been seeing. The bug is not specific to Hijack, but the fix is!

Y a H o o !

If anyone ever sees a player lockup with Hijack >= v223 installed, please don't hesitate to post it here or email me. We need to know if the fix really works for all lockups, or if there is yet another source of them.

Cheers

Next on the list: a cure for world drought/hunger, and peace in the middle-east.

Will the fix for world drought/hunger have vertical or horizontal menus? :P (sorry.. couldn't resist..)

yup mark mines still locking up.. looks like i have a pretty uniquie thing here.. either that or no one else can seem to match the problem.. i just find it kinda weird how hijack still works but the rest of the player dosnet.... its jsut weird becuase it never did this to me untill hijack v210 and above..

Okay, now, while it's "locked up", use a web browser (or ftp) to surf to the player, and dump out /proc/interrupts, and then dump it again (that's twice), and post both copies here.

Thanks

the ftp or http servers dont work while the player is locked only the menu via the player dose..

Hey Mark, I'm also having the same issues. Hijack continues to work but the player locks up. I left the visual on Flancedoor and let it run to see if it would lock and after a couple of hours, it has. As was posted above, the web and ftp servers do not function while the player is locked up.

Are you also running v223?

I'll add a menu screen to Hijack (v224?) to allow access to the /proc info without having to use http/ftp.

Cheers

Did either of you guys get the "jiffies" popup message on lockup here?

(it won't always appear, but it's helpful when it does).

my player locked up today for the first time...

hijack v223

jiffies message..

i forget the exact text...

something like "jiffies lockup ###"

where the ### was a steadily escalating number...

occured after two very quick short presses on the down button attempting to "down-down-down" while a file was playing...
--
sancho

Mark, my player locked too. In car, as soon as I turned the ignition on. I got the jiffies pop up message. Running 223.

Just noticed a "unstuck jiffies 44568" message (might have missed a previous lockup message as I've been away from the player a while watching TV)
MKIIa with 2.0b11, Hijack v223

/Michael

during ~0.75gig upload to player

stuck jiffies #####

see attached for interrupts... dumped the file thrice...
--
sancho

Okay, v223 didn't cure world hunger, and certainly didn't erase everyone's lockups. So..

Announcing Hijack v224, with yet another lockup bug fixed.

This version might be The One. But even if it isn't, the info I need to see will be put on the screen automatically when the bug occurs.

So, if you see a screen display beginning with BUG-n Jiffies=nnnn, then please write it all down and send it to me.

We are close, very close.

Thanks gang!

I've been posting my experiences in the thread in the General forum about this. I'm, off to bed now and I probably won't be able to try out any more updates until Sunday evening. Sorry .

Mark, I was running 223 and not getting any kind of jiffie message, just a lockup. I just updated to 224. I'll let you know what happens.

Already locked up under 224 >:(

No messages of any sort, just a hard lock. Hijack is still responding however. Unfortunately as before I can't FTP or HTTP in to get any information.

Ack! goto the Hijack menu and dump out "Vitals v2beta11" for me.

-ml

Jiffies: 105413
in: 32552 out: 105413
cr:e: 7q0676f mr:e: 7q08000
sr: 00000000

Run WITHOUT Hijack for a little while to see if you still get your player locking up. So far I don't think anyone has ever beenable to attribute player problems to a somewhat stable version of Hijack (I'm not counting these recent versions).

Are you sure your disk is ok? I can see your disk locking up and that could possibly kill everything including the player, yet leave Hijack (the kernel) running.

The other hang (the one Mark was trying to fix) locks up the entire interface (buttons & IR), but not the disks nor display.

Bruno

Ive never had anything happen to make me think the disk isn't okay. I'll reflash the player with b11 only and let it run for awhile and see what happens.

Yeah, but really we need that info from during a lockup.

Thanks!

Mark, the above information was when the player was locked up.

Ouch.

Okay, sorry about that. I just didn't see the "BUG" keyword on the first line, and the data (apart from the 'q' characters???) looks "good". So this particular lockup appears to be different from the "jiffies" problem. I think. Mmm..

I may have to add more data to that screen. Wonder whats going on in there..

-ml

We still suspect that it's a player thread priority/mutex/etc issue; problem is, we don't have the resources to look into it seriously at the moment. Everyone is fully committed on other projects.

Also, there's some new stuff on the horizon which when finished may well fix the problem, so there's a "wait for that & see" attitude about doing anything before then. We will fix the problem, but until then remember v2 is still in beta.

Hugo

Well, whatever it is, it stops the operating system timer interrupt dead in it's tracks.

I have found another race condition that could produce this bug (alsin in the reset_timer() code, way up top), but since I have been unable to reproduce anything here since beta3, testing is as hampered for me as for you folks.

Cheers