Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Dev

what's this dmesg output mean?

 

 

MythTV dev RSS feed   Index | Next | Previous | View Threaded


kirby at magnaspeed

Jan 14, 2006, 2:53 PM

Post #1 of 8 (1864 views)
Permalink
what's this dmesg output mean?

Running a Fusion5 Gold card, and an HD5000 card. Biostar MB with Nvidia
6200 PCIe card. Kernel 2.6.15-gentoo. Nvidia video version 8178 (and
yes, GL Vsync doesn't work.. I live with the occasional 'horizontal
seam'. Also, I'm running SVN 8605.

When watching LiveTv (perhaps watching recordings, I haven't checked
that yet), I get this output from 'dmesg':

Other than 'filling up' dmesg space with these messages, everything
works fine.... Is this a 'mythfrontend' problem? Or Nvidia?

Also, I posted a question asking for help with getting NTSC to work on
my Fusion5 card... I created a 'third' capture card with V4L... and it
looks promising, but mythtv-setup messages seem to indicate that this
'capture card' is still 'configured' as ATSC.... Any ideas here?


Trying to fix it up, but a reboot is needed
Bad page state at free_hot_cold_page (in process 'mythfrontend', page
ffff8100013dbdc8)
flags:0x0100000000000400 mapping:0000000000000000 mapcount:0 count:0
Backtrace:

Call Trace:<ffffffff8015bd64>{bad_page+113}
<ffffffff8015c5a5>{free_hot_cold_page+102}
<ffffffff8829eb3b>{:nvidia:nv_vm_free_pages+604}
<ffffffff88299b23>{:nvidia:nv_kern_vma_release+136}
<ffffffff8016afbb>{remove_vma+33} <ffffffff8016d0a7>{exit_mmap+205}
<ffffffff80135806>{mmput+35} <ffffffff8013a519>{do_exit+530}
<ffffffff8013afc6>{sys_exit_group+0}
<ffffffff8010f91a>{system_call+126}

Trying to fix it up, but a reboot is needed
Bad page state at free_hot_cold_page (in process 'mythfrontend', page
ffff810001579618)
flags:0x0100000000000400 mapping:0000000000000000 mapcount:0 count:0
Backtrace:

Call Trace:<ffffffff8015bd64>{bad_page+113}
<ffffffff8015c5a5>{free_hot_cold_page+102}
<ffffffff8829eb3b>{:nvidia:nv_vm_free_pages+604}
<ffffffff88299b23>{:nvidia:nv_kern_vma_release+136}
<ffffffff8016afbb>{remove_vma+33} <ffffffff8016d0a7>{exit_mmap+205}
<ffffffff80135806>{mmput+35} <ffffffff8013a519>{do_exit+530}
<ffffffff8013afc6>{sys_exit_group+0}
<ffffffff8010f91a>{system_call+126}

Trying to fix it up, but a reboot is needed
Bad page state at free_hot_cold_page (in process 'mythfrontend', page
ffff81000174b128)
flags:0x0100000000000400 mapping:0000000000000000 mapcount:0 count:0
Backtrace:

Call Trace:<ffffffff8015bd64>{bad_page+113}
<ffffffff8015c5a5>{free_hot_cold_page+102}
<ffffffff8829eb3b>{:nvidia:nv_vm_free_pages+604}
<ffffffff88299b23>{:nvidia:nv_kern_vma_release+136}
<ffffffff8016afbb>{remove_vma+33} <ffffffff8016d0a7>{exit_mmap+205}
<ffffffff80135806>{mmput+35} <ffffffff8013a519>{do_exit+530}
<ffffffff8013afc6>{sys_exit_group+0}
<ffffffff8010f91a>{system_call+126}


_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


mtdean at thirdcontact

Jan 14, 2006, 6:29 PM

Post #2 of 8 (1823 views)
Permalink
Re: what's this dmesg output mean? [In reply to]

Kirby Bakken wrote:
> Running a Fusion5 Gold card, and an HD5000 card. Biostar MB with Nvidia
> 6200 PCIe card. Kernel 2.6.15-gentoo. Nvidia video version 8178 (and
> yes, GL Vsync doesn't work.. I live with the occasional 'horizontal
> seam'. Also, I'm running SVN 8605.
>
> When watching LiveTv (perhaps watching recordings, I haven't checked
> that yet), I get this output from 'dmesg':
> ...
>
> Trying to fix it up, but a reboot is needed
> Bad page state at free_hot_cold_page (in process 'mythfrontend', page
> ffff8100013dbdc8)
> flags:0x0100000000000400 mapping:0000000000000000 mapcount:0 count:0
> Backtrace:
>
> Call Trace:<ffffffff8015bd64>{bad_page+113}
> <ffffffff8015c5a5>{free_hot_cold_page+102}
> <ffffffff8829eb3b>{:nvidia:nv_vm_free_pages+604}
> <ffffffff88299b23>{:nvidia:nv_kern_vma_release+136}
> <ffffffff8016afbb>{remove_vma+33} <ffffffff8016d0a7>{exit_mmap+205}
> <ffffffff80135806>{mmput+35} <ffffffff8013a519>{do_exit+530}
> <ffffffff8013afc6>{sys_exit_group+0}
> <ffffffff8010f91a>{system_call+126}
>
So, did you? ("Trying to fix it up, but a reboot is needed") Did
rebooting fix it?

Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


kirby at magnaspeed

Jan 14, 2006, 9:36 PM

Post #3 of 8 (1817 views)
Permalink
Re: what's this dmesg output mean? [In reply to]

Michael T. Dean wrote:

>Kirby Bakken wrote:
>
>
>>Running a Fusion5 Gold card, and an HD5000 card. Biostar MB with Nvidia
>>6200 PCIe card. Kernel 2.6.15-gentoo. Nvidia video version 8178 (and
>>yes, GL Vsync doesn't work.. I live with the occasional 'horizontal
>>seam'. Also, I'm running SVN 8605.
>>
>>When watching LiveTv (perhaps watching recordings, I haven't checked
>>that yet), I get this output from 'dmesg':
>>...
>>
>>Trying to fix it up, but a reboot is needed
>>Bad page state at free_hot_cold_page (in process 'mythfrontend', page
>>ffff8100013dbdc8)
>>flags:0x0100000000000400 mapping:0000000000000000 mapcount:0 count:0
>>Backtrace:
>>
>>Call Trace:<ffffffff8015bd64>{bad_page+113}
>><ffffffff8015c5a5>{free_hot_cold_page+102}
>> <ffffffff8829eb3b>{:nvidia:nv_vm_free_pages+604}
>><ffffffff88299b23>{:nvidia:nv_kern_vma_release+136}
>> <ffffffff8016afbb>{remove_vma+33} <ffffffff8016d0a7>{exit_mmap+205}
>> <ffffffff80135806>{mmput+35} <ffffffff8013a519>{do_exit+530}
>> <ffffffff8013afc6>{sys_exit_group+0}
>><ffffffff8010f91a>{system_call+126}
>>
>>
>>
>So, did you? ("Trying to fix it up, but a reboot is needed") Did
>rebooting fix it?
>
>Mike
>_______________________________________________
>mythtv-dev mailing list
>mythtv-dev[at]mythtv.org
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
>
>
Well, that's just it... there's really nothing 'noticeable' to fix
up... The mythfrontend still seems to be fine... It was only because I
was experimenting with my DVICO remote control and looking at dmesg that
I noticed all the 'errata' from this 'apparent' problem. I was hoping
someone in development might recognize what's happening and elaborate.
If nobody comes up with anything, I'll play around and see if I can
pinpoint what is causing all these 'warning/error' messages.
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


mtdean at thirdcontact

Jan 15, 2006, 5:28 AM

Post #4 of 8 (1800 views)
Permalink
Re: what's this dmesg output mean? [In reply to]

Kirby Bakken wrote:
> Michael T. Dean wrote:
>> Kirby Bakken wrote:
>>> Running a Fusion5 Gold card, and an HD5000 card. Biostar MB with Nvidia
>>> 6200 PCIe card. Kernel 2.6.15-gentoo. Nvidia video version 8178 (and
>>> yes, GL Vsync doesn't work.. I live with the occasional 'horizontal
>>> seam'. Also, I'm running SVN 8605.
>>>
>>> When watching LiveTv (perhaps watching recordings, I haven't checked
>>> that yet), I get this output from 'dmesg':
>>> ...
>>>
>>> Trying to fix it up, but a reboot is needed
>>> Bad page state at free_hot_cold_page (in process 'mythfrontend', page
>>> ffff8100013dbdc8)
>>> flags:0x0100000000000400 mapping:0000000000000000 mapcount:0 count:0
>>> Backtrace:
>>>
>>> Call Trace:<ffffffff8015bd64>{bad_page+113}
>>> <ffffffff8015c5a5>{free_hot_cold_page+102}
>>> <ffffffff8829eb3b>{:nvidia:nv_vm_free_pages+604}
>>> <ffffffff88299b23>{:nvidia:nv_kern_vma_release+136}
>>> <ffffffff8016afbb>{remove_vma+33} <ffffffff8016d0a7>{exit_mmap+205}
>>> <ffffffff80135806>{mmput+35} <ffffffff8013a519>{do_exit+530}
>>> <ffffffff8013afc6>{sys_exit_group+0}
>>> <ffffffff8010f91a>{system_call+126}
>> So, did you? ("Trying to fix it up, but a reboot is needed") Did
>> rebooting fix it?
>>
> Well, that's just it... there's really nothing 'noticeable' to fix
> up... The mythfrontend still seems to be fine... It was only because I
> was experimenting with my DVICO remote control and looking at dmesg that
> I noticed all the 'errata' from this 'apparent' problem. I was hoping
> someone in development might recognize what's happening and elaborate.
> If nobody comes up with anything, I'll play around and see if I can
> pinpoint what is causing all these 'warning/error' messages.
And the answer to my question is? Once again, in case you forgot, did
you reboot?

Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


kirby at magnaspeed

Jan 15, 2006, 7:10 AM

Post #5 of 8 (1809 views)
Permalink
Re: what's this dmesg output mean? [In reply to]

Michael T. Dean wrote:

>Kirby Bakken wrote:
>
>
>>Michael T. Dean wrote:
>>
>>
>>>Kirby Bakken wrote:
>>>
>>>
>>>>Running a Fusion5 Gold card, and an HD5000 card. Biostar MB with Nvidia
>>>>6200 PCIe card. Kernel 2.6.15-gentoo. Nvidia video version 8178 (and
>>>>yes, GL Vsync doesn't work.. I live with the occasional 'horizontal
>>>>seam'. Also, I'm running SVN 8605.
>>>>
>>>>When watching LiveTv (perhaps watching recordings, I haven't checked
>>>>that yet), I get this output from 'dmesg':
>>>>...
>>>>
>>>>Trying to fix it up, but a reboot is needed
>>>>Bad page state at free_hot_cold_page (in process 'mythfrontend', page
>>>>ffff8100013dbdc8)
>>>>flags:0x0100000000000400 mapping:0000000000000000 mapcount:0 count:0
>>>>Backtrace:
>>>>
>>>>Call Trace:<ffffffff8015bd64>{bad_page+113}
>>>><ffffffff8015c5a5>{free_hot_cold_page+102}
>>>> <ffffffff8829eb3b>{:nvidia:nv_vm_free_pages+604}
>>>><ffffffff88299b23>{:nvidia:nv_kern_vma_release+136}
>>>> <ffffffff8016afbb>{remove_vma+33} <ffffffff8016d0a7>{exit_mmap+205}
>>>> <ffffffff80135806>{mmput+35} <ffffffff8013a519>{do_exit+530}
>>>> <ffffffff8013afc6>{sys_exit_group+0}
>>>><ffffffff8010f91a>{system_call+126}
>>>>
>>>>
>>>So, did you? ("Trying to fix it up, but a reboot is needed") Did
>>>rebooting fix it?
>>>
>>>
>>>
>>Well, that's just it... there's really nothing 'noticeable' to fix
>>up... The mythfrontend still seems to be fine... It was only because I
>>was experimenting with my DVICO remote control and looking at dmesg that
>>I noticed all the 'errata' from this 'apparent' problem. I was hoping
>>someone in development might recognize what's happening and elaborate.
>>If nobody comes up with anything, I'll play around and see if I can
>>pinpoint what is causing all these 'warning/error' messages.
>>
>>
>And the answer to my question is? Once again, in case you forgot, did
>you reboot?
>
>Mike
>_______________________________________________
>mythtv-dev mailing list
>mythtv-dev[at]mythtv.org
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
>
>
Yes, I rebooted. And the messages in dmesg show up again. I'll try to
find out what 'action' causes these messages to start showing up. But
to retate, I reboot.. things work fine, I run the 'dmesg' command and
it prints out all those 'messages'... So I reboot, and again, all if
fine, but eventually, dmesg ends up showing those messages.
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


bjm at lvcm

Jan 15, 2006, 11:32 AM

Post #6 of 8 (1805 views)
Permalink
Re: what's this dmesg output mean? [In reply to]

Kirby Bakken wrote:
...
> I noticed all the 'errata' from this 'apparent' problem. I was hoping
> someone in development might recognize what's happening and elaborate.

That's a good idea. They're at linux.org .

> If nobody comes up with anything, I'll play around and see if I can
> pinpoint what is causing all these 'warning/error' messages.

Rollback to your previous working kernel until they fix this.

-- bjm
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


kirby at magnaspeed

Jan 15, 2006, 10:33 PM

Post #7 of 8 (1786 views)
Permalink
Re: what's this dmesg output mean? [In reply to]

Bruce Markey wrote:

>Kirby Bakken wrote:
>...
>
>
>>I noticed all the 'errata' from this 'apparent' problem. I was hoping
>>someone in development might recognize what's happening and elaborate.
>>
>>
>
>That's a good idea. They're at linux.org .
>
>
>
>>If nobody comes up with anything, I'll play around and see if I can
>>pinpoint what is causing all these 'warning/error' messages.
>>
>>
>
>Rollback to your previous working kernel until they fix this.
>
>-- bjm
>_______________________________________________
>mythtv-dev mailing list
>mythtv-dev[at]mythtv.org
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
>
>
This IS my 'previous working kernel'.... Its the only kernel that I
could get to work with my Fusion5 Gold card and HD5000 card, along with
audio (I had to manually patch the intenl8x0 code with the driver code
from RealTek... But you've given me a hint I can use to try and
find/fix the problem.
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


bjm at lvcm

Jan 16, 2006, 6:25 PM

Post #8 of 8 (1767 views)
Permalink
Re: what's this dmesg output mean? [In reply to]

Kirby Bakken wrote:
> Bruce Markey wrote:
...
>> Rollback to your previous working kernel until they fix this.
...
> This IS my 'previous working kernel'.... Its the only kernel that I

Maybe you need to look up the word 'previous' in a dictionary or
something. The kernel you are running is current. You should go
back to one before they horked virtual memory pages.

-- bjm
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

MythTV dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.