[MB Premium Twin HD] System occasionally fails to boot properly. Recordings missed.

[birdman]

My MB Twin has failed to boot up properly from Deep Standby to start a recording.

It did this last week on 071 (IIRC) and I sent off the crash log then. I also re-imaged (and restored settings - since they usually work).

It had the same issue again tonight (this time with 073) and I've again mailed the crash log off to [email protected] (both of them with some info in an attached text file).

Do I also need to report this here, or is the mailing sufficient (I've never had any acknowledgement form such crash log mailings)?

 

[judge]

Do I also need to report this here, or is the mailing sufficient (I've never had any acknowledgement form such crash log mailings)?

Uploading them here as an attachment might get faster replys as not everyone logs onto the email server.
Doesn't mean you'll get a faster solution, just puts more eyes on the issue...

 

[birdman]

Doesn't mean you'll get a faster solution, just puts more eyes on the issue...

Thanks. That's all I was expecting.

Minor problem, in that I've deleted last this weeks' log already, but I do have a copy of the cc'ed mailing from tonight. So I'll attach that. AFAIK the register dump was at the same point (just after the resolution: line) and looks similar (numerical values may well have changed..)

 

[judge]

Looks like a kernel panic.
Best to get your other issues sorted first to reduce the chances of a kernel panic happening.

 

[Joe_90]

Anything in /var/log/dmesg of interest?

 

[birdman]

Looks like a kernel panic.
Best to get your other issues sorted first to reduce the chances of a kernel panic happening.

I don't have any other issues to sort out.

 

[birdman]

Anything in /var/log/dmesg of interest?

I don't know. I didn't look today. If it happens again I'll try to remember.

One other thing. When it gets to this state the Remote Control is inactive. But I can login to it. A reboot from the command line fails, though. It does close the network, but it never actually shuts down the whole system. So I've had to power it off/on with the rocker switch on the back.

 

[birdman]

Looks like a kernel panic.

The box continues to run, so It might be an OOPS but not a PANIC(?).
I've seen Linux systems stop from a panic (had to take a camera in to work to get the screen dump, as there is no other way to keep a record. Worked too - found out the problem an hour later, and a workaround about 5 mins later).
But I've also seen processes get stuck because of a kernel issue - these dumped things into the syslog files, so I'll need to have a closer look next () time it happens. That didn't stop the system rebooting, though.

 

[birdman]

It's just happened again (with Apollo 088).

The messages log file finished with an entry (actually two) from init that the gui was respawning too quickly so was suspended for 5 mins.

I did take a tar copy of log in /var, but that was an error as I now just have a copy of a symlink log -> volatile/log

Had to reflash to get it started this time.