=== kemik [i=kemik@cloned.from.mutantgringos.com] has joined #ubuntu-kernel [12:20] http://paste.ubuntulinux.nl/3358 <- should i post a bug ? [12:21] that stuff keep happening [12:21] and i dunno what todo === doko_ [n=doko@dslb-084-059-071-190.pools.arcor-ip.net] has joined #ubuntu-kernel === joh [n=joh@cD90888E8.sdsl.catch.no] has joined #ubuntu-kernel === johnm [n=johnm@gentoo/developer/johnm] has joined #ubuntu-kernel === iram [n=iram@eycb01-00-cntnga-69-164-216-192.atlaga.adelphia.net] has joined #ubuntu-kernel === lamont [n=lamont@15.238.7.124] has joined #ubuntu-kernel === _maydayjay_ [n=maydayja@ip101109.101.nas.net] has joined #ubuntu-kernel === kemik [i=kemik@cloned.from.mutantgringos.com] has left #ubuntu-kernel ["Leaving"] === jane_ [n=JaneW@wbs-146-172-194.telkomadsl.co.za] has joined #ubuntu-kernel === carsten [n=carsten@wikipedia/carsten] has joined #ubuntu-kernel [10:18] Moin moin [10:19] dholbach told me to get in touch with you ;-) [10:19] This is still reproducible for me, http://bugzilla.ubuntu.com/show_bug.cgi?id=15413 === Yagisan [n=jamie@60-240-196-15.tpgi.com.au] has joined #ubuntu-kernel === chmj [n=chmj@wbs-146-144-69.telkomadsl.co.za] has joined #ubuntu-kernel === BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel === jdub [n=jdub@home.waugh.id.au] has joined #ubuntu-kernel [03:46] yoink! [03:47] 23:45 < jdub> BenC: my machine has hard locked 3 times today [03:47] 23:45 < jdub> BenC: now that i'm not running firefox, it hasn't happened [03:47] 23:45 < jdub> but [03:47] 23:45 < jdub> i like the web [03:47] 23:45 < jdub> it's not the hard disk thing either [03:47] 23:45 < jdub> heard of anything like this on breezy? [03:47] [03:47] for context [03:47] guessing it's network related [03:47] what are you using for network? [03:48] ipw2200 [03:48] hmm [03:48] that sounds fairly likely, given the usage patterns it was happening in [03:49] though i have fetchmail and ssh running atm without problems [03:49] so firefox was making new connections and stuff, and then it locked [03:50] firefox seems to expose more network bugs than most programs [03:51] this is with latest breezy kernel (9.23)? [03:51] yep [03:51] linux-image-2.6.12-9-686 2.6.12-9.23 [03:51] jdub : Other hardware specifics? [03:52] um [03:52] dell x300 [03:52] I'm using ipw2200 on a centrino laptop here as well, and except for the occasional firmware timeout, driver goes nuts issues, nothing bad. [03:52] only using ipw2200 wifi atm [03:52] firefox has also been known to tickle odd X (or X driver) bugs. [03:52] running all latest breezy stuff [03:52] infinity: it could be X [03:52] that's true too [03:52] intel i855 video === johnm [n=johnm@gentoo/developer/johnm] has joined #ubuntu-kernel [03:54] infinity: what video is yours? [03:57] Mine's radeon. [03:57] it's only been happening really badly today [03:57] which is od [03:57] i815 and ipw2200 is a dead common combination though, so that leaves us at square one for a scapegoat, since I'd expect "I lock up 3 times a day" to be a pretty commonly reported bug, if it's common to that setup. [03:58] because my usage patter while travelling has not changed much from last week to today [03:58] jdub : Checked the usual suspects, like filesystem corruption, dying RAM, etc? [03:58] did a fsck last night [03:58] for stupid reasons [03:58] going to do memcheck tonight === carsten [n=carsten@wikipedia/carsten] has left #ubuntu-kernel ["Konversation] [03:58] Maybe the fsck broke something. ;) [03:59] heh [03:59] beagle + user_xattr made a big mess [03:59] Heat could also be a factor. If you're computing on your lap, not getting enough airflow, firefox is hard on a CPU... [03:59] quite scary [03:59] could be [04:00] Despite the moniker "laptop", I've noticed that most laptops are very unhappy in laps. [04:00] At least, for extended usage. [04:01] jdub: when it happens it is dead-dead, or can you still ping it? [04:02] hrm [04:02] i will have to check [04:02] not a very good debugging environment here ;) [04:02] sorry, that would have been a sensible thing to do [04:03] no problem [04:03] dead-dead still doesn't tell us much. kernel panics, X locking the hardware, or heat would all cause dead-dead. [04:04] OTOH, if it's NOT dead-dead, you probably don't want ubuntu-kernel. :) === mkrufky [n=mk@68.160.103.77] has joined #ubuntu-kernel [04:15] not being dead-dead means the kernel is still able to give us information :) [04:26] jdub: Check #17128, see if it's related to you === jdub tries w3m :) [04:27] oh [04:27] that "screen stays blank" thing happened to me too [04:40] yay, 2.6.14 tree is _almost compiling_ [04:41] week of shoving crap into without testing if it compiles can put a hurt on a tree :) [04:41] BenC: what fails? [04:41] it's little things [04:41] ah, ok [04:42] right now the at76c50x driver just doesn't seem to like 2.6.14 [04:42] Linus released -rc5 this morning, if u didnt see yet [04:42] I'll just do a pull later [04:42] k [04:42] my tree is probably close to rc5 anyway [04:42] BenC: you guys planning on adopting pcmciautils anytime soon? [04:43] it fixes those nasty maximum file limit reached errors and the like [04:43] johnm: dunno, probably need to ask whoever handles pcmcia in userspace [04:44] BenC: will do :) [04:45] I'd package pcmciautils, but I have no pcmcia cards to test it with currently. [04:46] Someone should probably put it on my TODO anyway, as I understand it's the Right Way to make pcmcia and udev happy with each other. [04:55] yeah it totally is [04:55] and recent versions have added udev support, so doesn't rely on hotplug [05:05] Well, if we have the time, I think we'd like to move to a completely udev-based, hotplug-free system (assuming that actually WORKS), so this may well be a part of that. === lamont [n=lamont@15.238.5.50] has joined #ubuntu-kernel === Yagisan [n=jamie@60-240-196-15.tpgi.com.au] has left #ubuntu-kernel [] [11:57] fabbione: ping