/srv/irclogs.ubuntu.com/2014/04/17/#ubuntu-kernel.txt

=== zz_nhayashi is now known as nhayashi
=== TheDrums is now known as TheMaster
=== TheMaster is now known as DalekSec
=== fmasi is now known as Guest98598
=== Guest98598 is now known as fmasi
=== shuduo_ is now known as shuduo
tjaaltonif it proves working, would something like https://git.kernel.org/cgit/linux/kernel/git/johan/usb-serial.git/patch/?id=cec285642a121069e9c05cfb4189871043d8c39c qualify as SAUCE?13:10
tjaaltonmy youngest daughter has type1 diabetes, and sending data off the insulin pump for the doctor needs this damn device13:11
=== nhayashi is now known as zz_nhayashi
ogasawaratjaalton: I'd consider that patch saucy worthy.  looks like it was undergoing some review/testing upstream on the linux-usb list14:03
tjaaltonyeah14:03
rtgogasawara, it is deeply disturbing to me that you and tjaalton are considering patches for a released kernel that have not been exposed to the Ubuntu community. poke, poke.14:11
ogasawarartg: heh, well I'm assuming tjaalton will send a patch to the mailing list when he's ready :)14:12
=== maxb_ is now known as maxb
tjaaltonsure :)14:19
tjaaltonnot assuming you to pull it from there14:19
tjaaltonactually, I'm hitting that enumeration issue with superspeed ports14:19
tjaaltonbut it happens regardless of the patch14:20
tjaaltonyeah seems to work on usb2, now I need to figure out how to get the data from it..14:23
tjaaltonlooks like there are no tools for it yet, so I'll check out the situation and get back to you when there's something to use with it14:44
tjaaltonsome background in http://www.diabetesmine.com/2013/01/the-ethical-imperative-of-diabetes-interoperability.html14:44
tjaaltonbewest is the guy who emailed linux-usb about the enumeration issue14:45
bjftjaalton, saucy doesn't have a lot longer on support15:05
tjaaltonbjf: yeah I meant as sauce patch15:13
tjaaltonit's not upstream yet, maybe for 3.1615:13
bjftjaalton, still... best be upgrading to trusty :-)15:13
tjaaltonthat's what I use15:14
tjaaltonogasawara probably just typoed it :)15:14
tjaaltonsauce/saucy15:14
ogasawaratjaalton: oops, yes, that was a typo.  I did mean sauce15:15
tjaalton:)15:15
smoserrtg, you have trusty on your x120e ?16:15
rtgsmoser, yup16:16
smoserrtg, does it resume from suspend ?16:33
smoserbecause i dont. 16:33
smoserit dies, to the point where i have to pull the battery out on next reboot16:34
rtgsmoser, actually, it has _never_ failed. I'll go update it andmake sure.16:34
smoserrtg, well, its only ever worked really well for me (suspend/resume). but just did fresh install last night (which is a pita because of the UEFI issue bug 1040320).16:38
ubot2Launchpad bug 1040320 in ubiquity (Ubuntu) "Lenovo x120e install fails when in UEFI mode" [Undecided,New] https://launchpad.net/bugs/104032016:38
smoserrtg, well, ijust filed bug 130911216:57
ubot2Launchpad bug 1309112 in linux (Ubuntu) "x120e does not resume from suspend" [Undecided,New] https://launchpad.net/bugs/130911216:57
rtgsmoser, mine is still updating16:57
=== sz0 is now known as sz0`
rtgppisati, looks like some of the arm configs just turn off stack size warnings. 'git grep CONFIG_FRAME_WARN'17:08
ppisatirtg: i can see it's in our config _at least_17:09
ppisati(trusty-amd64)ppisati@tangerine:~/ubuntu-trusty$ grep -Ri FRAME_WARN debian.master/config/17:09
ppisatidebian.master/config/powerpc/config.common.powerpc:CONFIG_FRAME_WARN=102417:09
ppisatidebian.master/config/armhf/config.common.armhf:CONFIG_FRAME_WARN=102417:09
ppisatidebian.master/config/amd64/config.common.amd64:CONFIG_FRAME_WARN=102417:09
ppisatidebian.master/config/arm64/config.common.arm64:CONFIG_FRAME_WARN=102417:09
ppisatidebian.master/config/i386/config.common.i386:CONFIG_FRAME_WARN=102417:09
ppisatidebian.master/config/ppc64el/config.common.ppc64el:CONFIG_FRAME_WARN=204817:09
rtgppisati, yup, which I why I noticed it. OK, looks like an upstream patch.17:09
rtgwhich is*17:10
rtgppisati, hmm, must be an artifact of building that module for powerpc. on armhf the frame size is only 472 bytes.17:22
rtgI am assuming wireless/ti/wlcore can only be loaded on arm17:22
ppisatiyep17:23
rtgok, guess I'll leave it alone17:23
ppisatirtg: you got 8k usage for wlcore on ppc?17:24
rtgppisati, 917217:24
ckingstack scribbler then17:25
rtgcking, except that wlcore will never get loaded on powerpc17:25
ckingah17:25
ppisatirtg: well, i don't know if TI relicensed it's wifi IP for a discerete chip/company17:26
ppisatirtg: but i doubt17:26
ppisatirtg: and in any case it would be another driver17:26
=== sz0` is now known as sz0
smoserrtg, upgraded  yet?18:06
rtgsmoser, uh, yeah. works fine.18:06
smoserreally?18:06
rtgwould I kid you ?18:06
smoseri think you have that rtl wireless.18:06
smoseri dont knw what could be different.18:06
smoserother than i put a ssd in yesterday18:07
rtgsmoser, what is your wifi ? I haven't looked at the bug yet18:07
rtgI have an SSD18:07
rtgrtl8188ce18:07
smoserhttps://launchpadlibrarian.net/173032656/susres.2014-04-17_12%3A45%3A58.004375.crash18:08
smoserrtg, you dont boot with UEFI do you?18:09
rtgsmoser, not that I recall. I'm pretty sure I don't have grub-efi installed.18:09
rtgsmoser, actually, I _do_ have grub-efi-amd64 installed.18:10
smoseri could not get bios to recognize anything the installer laid down.18:11
smoseri let it do auto once18:11
smoserand did it myself another.18:11
smoseri wonder why i'm unlucky.18:19
smoserapw, your name is on /usr/share/apport/apportcheckresume18:28
smoserthat runs after my system fails to resume. and i think it crashes.  *it* causes a dialog (i think). but maybe i'm misunderstanding something.18:29
apwsmoser, it is meant to cause an apport report when resume fails indeed18:29
apwsmoser, its job is to work out that we have booted but that the last thing we did was suspend not shutdown; in that case it files a bug report18:30
smoserwell... hm.. its confusing.18:30
smoserwhat you're saying makes perfecdt sense. and thats what i thought18:31
smoserbut then18:31
smoserthe dialog that comes up says18:31
smoser"Sorry, the application apportcheckresume has stopped unexpectedly"18:31
smoserExecutablePath /usr/share/apport/apportcheckresume18:31
smoserwhiich made me think *it* crashed when something else ran it.18:32
smoseram i just not reading the dialog right?18:32
apwit may well have does it wrong, can you let it file a bug, and send me the name18:32
apwnumber even18:33
smoserwell, on that system it never gets there.18:33
smoserthe dialogs just go away18:33
smoseri say "continue", then nothing.18:33
apwwell that is quality, ok, i'll try and reproduce it, could you email me direct and remind me, as i will forget by tuesday18:33
smoserhappy easter.18:34
smoseri'll try to remember too.18:34
apwsmoser, you too :)  /me blames it on p itt i or someone :)18:34
=== sz0 is now known as sz0`

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!