=== Amaranth_ is now known as Amaranth
=== yofel_ is now known as yofel
=== kgnomelogger is now known as apachelogger
=== apachelogger is now known as fedoraloggr
=== fedoraloggr is now known as fedoralogger
=== fedoralogger is now known as phononlogger
[19:00] <alex_mayorga1> bryceh: you there?
[19:03] <alex_mayorga1> bug 696104 here
[19:03] <ubot4> Launchpad bug 696104 in xserver-xorg-video-nouveau (Ubuntu) "nvidia 320m locks up (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/696104
[19:04] <alex_mayorga1> I have ssh to the laptop locked out right here, what can I gather?
[19:29] <alex_mayorga1> no one?
[20:40] <pcjc2> alex_mayorga1: Sorry - no idea for Nouveau
[20:41] <pcjc2> Does the Nouveau driver expose anything under /sys/kernel/debug/dri/0 like the Intel one does?
[20:47] <alex_mayorga1> pcjc2: I do se these on /sys/kernel/debug/dri/0
[20:47] <alex_mayorga1> bufs     chipset  evict_vram  memory  queues         vbios.rom  vma
[20:47] <alex_mayorga1> channel  clients  gem_names   name    ttm_page_pool  vm
[20:48] <pcjc2> bufs, "gem_names" "ttm_page_pool", "vm" "might" be interesting
[20:48] <pcjc2> pastebin if they are big?
[20:48] <pcjc2> TBH, I don't know what I'm looking for though
[20:48] <alex_mayorga1> anyway yo attach them to the bug report from a ssh console?
[20:49] <pcjc2> not that my LP foo can manage, sorry
[20:49] <alex_mayorga1> pcjc2: OK, thanks anyway
[20:51] <pcjc2> you can email additions to bug reports
[20:51] <pcjc2> but it has been a long time since I used a terminal based email client ;)
[20:52] <pcjc2> Also, you can access launchpad through a terminal based web-browser, such as "w3m"
[20:54] <tjaalton> just copy the contents locally, and attach to the bug later
[20:55]  * pcjc2 missed that rather obvious suggestion ;)
[20:56] <tjaalton> hehe :)
[20:57] <pcjc2> Bryce about?
[20:58] <tjaalton> it's sunday, so probably having quality time off work :)
[21:08] <Amaranth> tjaalton: probably flying
[21:59] <alex_mayorga1> pcjc2: there's also a /sys/kernel/debug/dri/64 folder shall I copy that one too?
[21:59] <pcjc2> I don't think that is as useful
[22:00] <pcjc2> tjaalton: quality time -> disallowed ;)
[22:00] <alex_mayorga1> pcjc2: sorry on the slow response, had to go deal with real life :)
[22:00] <pcjc2> I'm working on something too... _very_ slowly writing a robot for managing bugs using launchpad APi
[22:02] <alex_mayorga1> pcjc2: sounds like fun
[22:03] <alex_mayorga1> pcjc2: is that a public project
[22:03] <pcjc2> bogged down in database design at the moment
[22:03] <pcjc2> Not currently, but it can be. Nothing fancy mind.. just a hook to retrieve "Closes-bug: lp-12345" messages from git commits and make comments / status updates on bugs
[22:04] <pcjc2> The tricky bit is that to ensure it works reliably (around LP downtime etc..), I need to have the git hook stuff work into a queue (a sqilte database), and then prod the robot - which will also be run periodically from a cron job
[22:05] <pcjc2> The tricky bit is the DB design, and deciding just what to do for reverted commits, forced updates etc..
[22:07] <alex_mayorga1> pcjc2: I see
[22:09] <alex_mayorga1> OK I've copied the contents of both dri/0 and dri/64 anything else?
[22:10] <alex_mayorga1> funny enough the lock up stays even when the laptop suspends itself and I resume it :)
[22:18] <pcjc2> Not sure
[22:19] <pcjc2> Something is waiting for something -> lock
[22:19] <pcjc2> Do you have compiz running?
[22:41] <alex_mayorga1> pcjc2: no as far as I know, anyway to tell from a console if compiz is going
[23:01] <Amaranth> alex_mayorga1: pgrep compiz