newbury at mandamus
Jul 17, 2012, 1:03 PM
Views: 194
Permalink
|
|
Re: Ticket #10911: another backend deadlock
|
|
On 07/16/2012 02:10 PM, MythTV wrote:
> #10911: another backend deadlock
> ----------------------------------------+----------------------------
> Reporter: brian@… | Owner:
> Type: Bug Report - Hang/Deadlock | Status: new
> Priority: minor | Milestone: unknown
> Component: MythTV - General | Version: 0.25-fixes
> Severity: medium | Resolution:
> Keywords: | Ticket locked: 0
> ----------------------------------------+----------------------------
>
> Comment (by gigem):
>
> Geoff, it sound like you are experiencing a new problem. Please get the
> exact version and a backtrace and then open a new ticket. We're pretty
> sure the problem as originally reported for this ticket is fixed.
OK I am really stumped here. I have a sneaky suspicion that something is
wrong with my install. KDE is doing some weird things, such as I cannot
maximize windows parked on the panel. I cannot atm be sure of where the
problem lies. Here's the latest news.
I took a copy of a July 2 or so git clone (v0.26-pre-757-ge2a0efd) which
runs perfectly here, home and compiled that. It barfs there (on fedora
17 w 3.4.4.3.) I am running F16 w 3.4.0-0.rc5.git2.1.fc18 here at work.
Trolling through the logs, I saw one funny message in dmesg.
(Significant? No idea.) Then mythtv-setup could not find the dvb adapter
although I could azap tune it, and cat from it cleanly both before and
after attempting setup. And the compile was done after a reboot: I was
testing the tuners first.
Then mythtv-setup borked with the 'empty' error. After that the frontend
does the same thing but only as soon as I enter 'Upcoming Recordings'
and the system attempts to populate the screen: that particular mysql
query triggers it. Note that that does NOT happen on the desktop here
and the other database-data populated screens throughout myth work fine,
as does the status page. The tuners appear there too. Also at home I
cannot schedule recordings. Here, works fine.
So again, I pulled a git clone late last night. when I built that brand
spanking new git v0.26-pre-899-g1316335, it crashed severely on frontend
startup ( see new-error which is something else I think).
So I think there is more than the mysql communication error going
on.(BTW, mysql was completely unaffected and I could use the console
without difficulty throughout my testing.)
So I am thinking that I have some other error going on.
I am going to re-install fedora and I may just go for an rpm install
from atrpms in order to get this up and running again (Yes the database
will be a bitch! Worst case, I hand delete some columns from a couple of
tables to get back to 1295 or whatever.)
So, no backtraces at the moment, although I would appreciate any
pointers on how anyone thinks I should trace this.
Run gdb against both the backend and the frontend?
Should I also try that against mysqld??
Geoff
|
dmesg-error
Re: Ticket #10911: another backend deadlock