[07:06] <apw> df
[07:09] <diwic> apw, /dev/brain, cells:2, used:2, available:0, Use: 100%, Mounted on: /dev/head
[07:09] <apw> diwic, sounds about right
[07:10] <apw> /dev/head, capacity:10, populated:0
[07:10] <diwic> eh
[07:11] <apw> i refer you to your first answer :)
[07:12] <diwic> refer? by a symlink or a hardlink? or a recursive loop device? :-)
[07:13] <apw> mount -o bind /dev/answer1 /dev/answer
[07:14]  * diwic realises he's out on deep water and quickly gets back to work ;-)
[07:31]  * smb strolls in
[10:45] <apw> bug 753994
[10:45] <ubot2> Launchpad bug 753994 in linux "[arrandale] Display is slanted when using 1360x768 resolution" [Medium,Confirmed] https://launchpad.net/bugs/753994
[10:50] <jussi> crioes, thats a strange looking bug
[10:52] <apw> stupid integer mistake in stride width
[11:03] <apw> RAOF, you any idea why this diagonal thingy fix is only applied to the fixes branch ?  seems odd behaviour
[11:04] <RAOF> I don't know; were I to guess, it would be because there will be a merge from -fixes to -next at some point in the future.
[11:06] <apw> hhmmmm
[11:57] <ilmari> what are the odds of the oneiric 3.0 drm-intel-next kernel packages working on natty?
[12:08] <Tommeh> ilmari: pretty high
[12:09] <Tommeh> I'm using mainline 3.0 from the kernel team PPA
[12:10] <Tommeh> At the end of the day it's only a few .deb packages, so if they don't work you've not lost much time. :)
[12:11]  * ilmari gives it a go
[12:49] <apw> RAOF, so i guess are you happy to have it in natty when its not yet upstream
[13:28] <hx_> Hello, I've got an Asus P53E and I installed Ubuntu 11.04, the problem i have is that my touchpad is recognized as a "PS/2 Logitech Wheel Mouse" and therefore the multitouch functionality doesn't work. I found out that this is could be a bug in the Kernel, so I installed the newest one (3.0 rc7) but still the problem is the same.. Is there a patch for this issue?
[13:34] <apw> hx_, what make of touchpad is it
[13:36] <hx_> apw, i think its an "elantech" type, but i cant find its name or anything in the manual
[13:36] <davmor2> ogasawara: just to confirm that after a fresh install of oneiric at the weekend the Ralink 5390 driver was working out of the box thanks :)
[13:37] <ogasawara> davmor2: cool, good to know
[13:39] <sforshee> hx_, I have a machine with an elantech touchpad that behaves the same. I'm planning to look into it but just haven't gotten around to it yet.
[13:39] <apw> hx_, i've heard of issues with new ALPS touchpads, but not with elantech.
[13:40] <apw> sforshee, must be a new device.  you'd think they could be compatible, its not like its complex
[13:40] <hx_> sforshee, ive done some research and a lot people are having this issue :(
[13:40] <sforshee> apw, it might just be a problem in detecting that it's an elantech device. Note that it's identified as a Logitech.
[13:41] <hx_> apw, how do i be sure which one i got?
[13:42] <apw> sforshee, yeah point
[13:42] <apw> hx_, a good question.  i hate h/w for a reason
[13:42] <apw> hx_, but i'd say its a bug yes
[13:42] <sforshee> hx_, is there a launchpad bug already open for this?
[13:42] <apw> hx_, did it every work on any older version ?
[13:43] <hx_> apw, it didnt work on an older kernel, but it worked on windows 7, with the native synaptics drivers
[13:43] <hx_> sforshee, im pretty sure there is already one open
[13:43] <apw> yeah windows isn't interesting in the sense that that just tells us they can detect their own h/w in their driver
[13:44] <hx_> yeah right, but i even tried several other distributions
[13:44] <hx_> fedora and opensuse
[13:44] <apw> and i assume they don't work either
[13:45] <hx_> no they dont same result
[13:45] <sforshee> detecting what's attached to PS/2 is just a bunch of black magic, there's no standard scheme for hw identification
[13:45] <sforshee> my guess is we mostly just need to determine the correct way to probe the device
[13:46] <sforshee> that's my hope anyway :)
[13:46] <apw> sforshee, yep, but thats only broke cause they changed it from their previous h/w, stupid stupid stupid
[13:46] <sforshee> apw, that pretty much sums up what I've been dealing with the past couple of weeks
[13:47] <apw> particularly the stupid, stupid, stupid part
[13:47] <hx_> im on that for a several days of googling before i decided to ask here
[13:48] <hx_> but cant i "just" assign the synaptics driver to the (wrongly detected) PS/2 Device?
[13:49] <sforshee> hx_, the elantech driver is probably refusing to work with it because it doesn't look like the things it knows about
[13:49] <apw> hx_, no cause unless you incant the right bytes at the deveice it behaves like a mouse
[13:49] <apw> hx_, the act of asking it if it is a touchpad (in the correct way) makes it into a touchpad, before that it fakes mouseness
[13:50] <apw> as i say .... STUPID
[13:50] <apw> all in the name of compatibility with dos 3.0 no doubt
[13:50] <hx_> oh okay, but can't the act of asking if it is a touchpad be patched?
[13:50] <sforshee> hx_, it can be patched but we have to find the right way to ask first
[13:51] <apw> hx_, yes, we could change how we ask it if it is a touchpad.. but .. what am i meant to say to it
[13:51] <apw> oh we don't know cause the vendor don't tell us
[13:51] <hx_> that looks like a hopeless situation..
[13:52] <apw> difficult at least yes
[13:52] <sforshee> hx_, there are ways to reverse engineer such things, it just takes time
[13:52] <apw> means someone has to watch windows doing it, and figure it out normally, which isn't easy
[13:52] <apw> and when its all said an done the vendors should just write it down and tell us
[13:53] <sforshee> that would be nice
[13:53] <sforshee> I'm not holding my breath though
[13:54] <hx_> what exact information would we need about the touchpad?
[13:54] <hx_> in order to detect it
[13:56] <hx_> apw, or is there a posibility of just using the windows drivers as with wireless cards?
[13:58] <apw> hx_, that is a black-art which i am not up on, i have not heard of any way to use the windows drivers no
[14:01] <hx_> apw, okay i hope this will be fixed in a new kernel version if possible, as a lot of people are having this issue
[14:03] <apw> hx_, well at least it works as a mouse
[14:03] <hx_> apw, yes but without multitouch i cant scroll which makes it rather useless
[14:04] <apw> hx_, not as useless as it not working as a mouse would be
[14:04] <apw> i understand your pain, but we are somewhat at the mercy of vendors
[14:05] <hx_> apw, thats true.. do you think i should ask for support at asus?
[14:05]  * apw looks pointedly at his stupid SD card slot which will likely never work cause of the vendors attitude
[14:05] <apw> hx_, i always feel its worth the vendors knowing people care
[14:06] <apw> whether it will help is another quesiotn
[14:07] <hx_> yes i will see, thanks for your support though
[14:15] <sforshee> hx_, please go ahead and look for a bug that matches your issue and click the link to indicate that you are also affected, or open a new bug if there isn't one already. Let me know the bug number. I hope to start looking into it with the hardware I have within the next couple of weeks.
[14:18] <hx_> sforshee, i think i found a patch for our problem
[14:18] <tgardner> apw, ogasawara: so far Oneiric is only building perf as a tool. do you suppose we should start building and packaging turbostat and x86_energy_perf_policy ?
[14:19] <apw> tgardner, i have been thinking i need to overhaul the tools as it doesn't package half of the stuff in perf
[14:19] <apw> tgardner, should i look at it or will you
[14:19] <tgardner> apw, you should since I'm gonna be gone for a few days later this week
[14:19] <apw> (and i suspect we should be including those other tools
[14:19] <apw> tgardner, ack
[14:19] <tgardner> well, I guess I have time though.
[14:20] <tgardner> I wtill have 3 days
[14:20] <tgardner> apw, are you swamped with other stuff ?
[14:20] <apw> there is always more stuff to do
[14:20] <sforshee> hx_, can you point me to the patch?
[14:20] <apw> i think its important, so i am happy to do it t
[14:20] <apw> though as i know the perf support files are missing
[14:20] <tgardner> apw: put it low on your list. I'll see if I can get it done before you get to it.
[14:21] <apw> tgardner, ok let me know when you are sure you arn't doing 
[14:21] <hx_> well i found a post with the link of a patch but im not sure if it is what where looking for
[14:21] <hx_> anyway: https://bbs.archlinux.org/viewtopic.php?id=115810
[14:21] <hx_> sforshee
[14:22]  * ogasawara back in 20
[14:22] <sforshee> hx_, I thought I tried that, but let me try again
[14:22] <hx_> look at the end of his post
[14:22] <mahmoh> how can I change the interrupt frequency via kernel command line?  Let's say I want to imitate the 100Hz server timing  vs. desktop 250?
[14:22] <sforshee> hx_, oh, okay, didn't see that before, let me take a look
[14:23] <hx_> sforshee, okay but i dont know how to use it
[14:24] <apw> sforshee, the patch is like 500 lines of doom :)
[14:24] <apw> and looks to do all sorts of bad things ... dimitri has asked for it to be split up
[14:25] <apw> though he asks them to do that on linux-imput, so it may be going on over there too
[14:25] <sforshee> yep
[14:26] <sforshee> ugh, I think I've seen touchscreens with problems similar to these touchpads
[14:26] <apw> first foray into MT
[14:27] <sforshee> apw, I'm pretty sure the nexus one touchscreen has the same problem -- it can't do real MT, and sometimes gets confused about where the fingers really are
[14:28] <sforshee> but getting that right isn't necessary for simple gestures, like two-fingered scrolling
[14:28] <apw> sforshee, yeah it doesn't support the spin in google maps for that reason
[14:28] <sforshee> apw, I worked on a device that used the same touchscreen :)
[14:28] <apw> heh ... no comment :)
[14:29] <sforshee> anyway, I guess my point is that a stripped-down version of the patch might work as a starting point and still support the gestures that are needed
[14:30] <hx_> im listening :)
[14:31] <sforshee> hx_, do you have a bug yet? It's going to be easier to track all this information in the context of a bug than in an irc discussion.
[14:32] <sforshee> hx_, it's still going to take some work. Like I said it's on my list, I just haven't been able to get to it yet.
[14:32] <hx_> sforshee, no i havent yet, should i create one?
[14:33] <sforshee> hx_, first you should check for an existing bug report, but if you can't find one then yes you should create one
[14:34] <hx_> sforshee, there already are bug reports, like https://bugs.launchpad.net/ubuntu/+source/linux/+bug/694222
[14:34] <ubot2> Ubuntu bug 694222 in linux "Synaptics touchpad incorrectly recognized as PS/2 Logitech mouse on a Samsung SF310 laptop (dup-of: 681904)" [Undecided,New]
[14:34] <ubot2> Ubuntu bug 681904 in linux "[arrandale] Samsung QX310/QX410/QX510/SF310/SF410/SF510/NF210/RF410/RF510/RF511/RF710 trackpad/touchpad not recognized" [Medium,Confirmed]
[14:35] <sforshee> hx_, that one's marked a duplicate of bug 681904
[14:35] <ubot2> Launchpad bug 681904 in linux "[arrandale] Samsung QX310/QX410/QX510/SF310/SF410/SF510/NF210/RF410/RF510/RF511/RF710 trackpad/touchpad not recognized" [Medium,Confirmed] https://launchpad.net/bugs/681904
[14:36] <sforshee> hx_, that looks like it's probably the same thing though. The machine I have with the elantech touchpad is a samsung.
[14:37] <hx_> sforshee, okay, well i have an asus but i think that doesnt matter if its an elantech
[14:37] <sforshee> and it's already tracking the upstream bug, so that's useful
[14:37] <sforshee> hx_, we'll just have to see if the same thing fixes your machine too
[14:38] <hx_> sforshee, yes what i would really appreciate
[14:39] <sforshee> hx_, subscribe to the bug and you'll get emails when I start posting stuff there
[14:39] <hx_> sforshee, okay wonderful thanks in advance
[14:40] <hx_> to that one right? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/681904
[14:40] <ubot2> Ubuntu bug 681904 in linux "[arrandale] Samsung QX310/QX410/QX510/SF310/SF410/SF510/NF210/RF410/RF510/RF511/RF710 trackpad/touchpad not recognized" [Medium,Confirmed]
[14:40] <sforshee> hx_, yes, that's the one I'll be using
[14:41] <hx_> sforshee, alright let me know if i can help in anyway (testing,..)
[14:41] <sforshee> hx_, will do, thanks!
[14:44] <hx_> sforshee, looking forward to it, thanks
[14:47] <ogasawara> anyone know who this julian wiedmann is?  he's doing some pretty good bug triage for us lately.
[14:49] <sforshee> ogasawara, don't know who he is, but I've noticed that he's been doing some good work
[14:50] <mahmoh> anyone?
[14:50] <apw> mahmoh, ?
[14:51] <mahmoh> apw: how can I change the interrupt frequency via kernel command line?  Let's say I want to imitate the 100Hz server timing  vs. desktop 250?
[14:51] <apw> no thats not tunable via the command line
[14:51] <mahmoh> I was afraid of that
[14:51] <apw> ogasawara, did we decide to harmonise on a value in the end
[14:52] <mahmoh> apw: thx :(
[14:54] <ogasawara> apw: i can't recall if we did actually
[14:54] <apw> ogasawara, jj may remember .. he has an ear for detail
[14:54] <ogasawara> apw: I think we agreed we should, but left it at that
[14:54] <apw> ogasawara, i think i remmber someone (maybe him) was going to go do some measurements
[14:55] <ogasawara> apw: I think I also vaguely remember needing to get our IPV6 configs sorted as well
[14:55]  * ogasawara puts it on the todo list
[14:56] <marcoceppi> Hello
[14:56] <apw> yeah harmonising them iirc
[14:57] <marcoceppi> I've got a question about building the Ubuntu Kernel. I've checked out ubuntu-lucid.git applied my patches and merges. I'm trying to build a src package to I can place in a PPA - I've built the control file but I need a change log. How can I get the current changelog for the ubuntu-lucid kernel?
[14:58] <apw> marcoceppi, if you clean the package first (fakeroot debian/rules clean), it'll appear.  the master is in debian.master/changelog
[14:58] <marcoceppi> apw: Thank you
[15:00] <marcoceppi> So, what's the best way for me to enter my changes to the log? Other than the obvious of "edit the changelog file generate"
[15:00] <sconklin> marcoceppi: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel may help a bit
[15:01] <marcoceppi> I've been loosely following https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
[15:01] <sconklin> edit the changelog and commit it to your local repo if you want to save it, otherwise, just build from the uncommitted tree
[15:01] <apw> (the master one)
[15:02] <sconklin> We have three or four wiki pages on how to build a kernel, unfortunately.
[15:02] <marcoceppi> sconklin: heh, I've noticed. They all have about the same information - just variations it seems apw Thanks, I'll do so
[15:02] <skaet> sconklin,  I haven't been able to move the SRU meeting to Tuesday,  you able to meet now?
[15:03] <sconklin> skaet: sure
[15:03] <sconklin> #ubuntu-meeting?
[15:10]  * tgardner bounces tangerine to make it'll boot without a CDROM.
[15:20]  * tgardner notes tangerine is back up
[15:21] <marcoceppi> So, I'm about to build with debuild -S -sa and i'm getting This package has a Debian revision number but there does not seem to be
[15:21] <marcoceppi> an appropriate original tar file or .orig directory in the parent directory;
[15:21] <marcoceppi> (expected one of linux_2.6.32-33.72.orig.tar.gz, linux_2.6.32-33.72.orig.tar.bz2,
[15:21] <marcoceppi> linux_2.6.32-33.72.orig.tar.lzma,  linux_2.6.32-33.72.orig.tar.xz or ubuntu-lucid.orig)
[15:21] <marcoceppi> continue anyway? (y/n)
[15:21] <marcoceppi> Is it safe to just continue?
[15:24] <apw> marcoceppi, the upload will be much bigger without it, but safe i beleive
[15:32] <skaet> bjf, sconklin - are you sure you want me to move lucid kernel to proposed?   Looking at bug 811745 comments from over the weekend looks like its not fixed quite yet.
[15:32] <ubot2> Launchpad bug 811745 in linux "Whole system freeze after safely remove external usb drive" [Undecided,Confirmed] https://launchpad.net/bugs/811745
[15:34] <skaet> or they were running the wrong kernel (ie. -71) and we need to move -72 in place for them to pick it up.
[15:34] <ohsix> i have a panic related to removing drives in the natty kernel, and in the ones where it's "fixed" by some stuff, i get acpi wakeup panics
[15:39] <herton> skaet: yes, 2.6.32-33.72 is the one that should fix the issue
[15:40] <bjf> skaet, yes, please copy 32-33.72
[15:40] <skaet> bjf,  thanks will do.
[15:40] <skaet> herton,  thanks
[15:43] <skaet> herton, bjf,  ok, have copied it in.   Could one of you update the status of 811745 bug to reflect fix committed and the correct importance.  
[15:44] <bjf> skaet, just fyi, i'm on rotation to QA this cycle, though i do still dabble in kernel team issues
[15:45] <skaet> thank for clarification bjf.
[15:48] <herton> bjf, skaet: I set it to fix commited and importance: high. Let me know if importance should be different. If a nomination is needed, I don't have permissions to approve, so someone must do it.
[15:49] <herton> *someone else
[15:49] <bjf> herton, which bug #?
[15:50] <herton> bug 811745
[15:50] <ubot2> Launchpad bug 811745 in linux "Whole system freeze after safely remove external usb drive" [Undecided,Confirmed] https://launchpad.net/bugs/811745
[15:50] <herton> bjf: ^
[15:50] <bjf> herton, thanks, looks like skaet got to it
[15:51] <skaet> herton,  ok,  have gone in and marked it for lucid.  
[15:51] <ohsix> you might be interested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/793796 as well, it's the panic i reported w/the natty kernel, removing an external drive
[15:51] <ubot2> Ubuntu bug 793796 in linux "2.6.38-10 panic after ejecting drive" [Undecided,In progress]
[15:54] <herton> ohsix: ? that one should be ok already, since 2.6.38-10.46. There is no upstream fix, so the patches that caused it are reverted since then
[15:54] <ohsix> it might be related with the freeze they're investigating, even if remotely :]
[15:54] <ohsix> btw, with tha tkernel i get acpi stuff in the stack for a panic after wakeup
[15:55] <skaet> herton,  linux-backports-modules-2.6.32 has been copied to proposed.
[16:03] <herton> skaet: ok thanks. If everything is on proposed, you must set the 'Promoted-to-proposed' task to 'Fix Released' on the tracking bug
[16:03] <skaet> herton,  was going in and doing that now.
[16:03] <herton> ah ok
[16:04] <herton> lunch, back in some minutes
[16:19] <skaet> going through the bugs for the natty move to proposed, and bug 791019 and bug 751681 don't have the right state,  can someone confirm it should be in and clean up the status of the bug.   also bug 731706 is not targetted to Natty - oversite?
[16:19] <ubot2> Launchpad bug 791019 in linux "yama_ptracer_del lockdep warning" [Undecided,Fix released] https://launchpad.net/bugs/791019
[16:19] <ubot2> Launchpad bug 751681 in linux "Lenovo Ideapad U350: Internal mic stopped working with natty kernel" [Undecided,Incomplete] https://launchpad.net/bugs/751681
[16:19] <ubot2> Launchpad bug 731706 in linux "[Dell Studio 1558] Driver advertises extra internal Microphone Input which does not work" [Undecided,Fix committed] https://launchpad.net/bugs/731706
[16:23] <bjf> skaet, that has often been the case in the past, not all bugs fixed in a upload necessarily have the correct status or have been nominated for a series
[16:35] <herton> ohsix: is the acpi stuff you mentioned a crash? (so resume from suspend fails?)
[16:35] <ohsix> herton: yes it's a panic, with stuff like "acpi_idle_enter_c1" (paraphrasing) in the stack
[16:36] <herton> ohsix: did it happen before, or a recent update triggers it?
[16:36] <skaet> bjf,  one of the steps of the process on the release side is walking through all the bugs and checking that they are have complete description, justification, have a stable release task, conformant to SRU rules, etc., so basically haven't been inadvertently included.   By setting the state of the bug to Fix Committed, it makes things more efficient for everyone - ie.  we know that it is intended to be released witho
[16:36] <skaet> ut having to ask.  ;)
[16:37] <ohsix> herton: well i was running the package with those eject fixes in them, but then i ended up with the acpi problem
[16:38] <bjf> skaet, interesting, since this is first anyone has asked
[16:41] <skaet> bjf,  ah well,  this is what happens when you get a backup trying to follow an existing process,  documentation gets read.  ;)  https://wiki.ubuntu.com/StableReleaseUpdates#Reviewing_procedure_and_tools
[16:44] <herton> ohsix: are you able to get dmesg/kernel log after the crash?
[16:45] <ohsix> herton: i can get a picture next time i boot that kernel; it's been 2 sets of new kernels i've had problems with so i've sort of decided to cut my losses
[16:46] <herton> ohsix: it helps know when the problem start, you can check if you had this problem with first natty kernel (8.42). In any case, open a bug about it.
[16:46] <herton> *started
[16:46] <bjf> skaet, heh, agreed
[16:47] <ohsix> i only had a problem with that patched version, i did not get to use the unpatched update for long cuz of the panic thing with the drive ejecting
[16:48] <ohsix> herton: so it is after 2.6.38-9-generic but as far as i know only as soon as 2.6.38-11-generic
[16:50] <herton> ohsix: did suspend/resume worked before on the same machine at some point?
[16:51] <ohsix> herton: aside from when i installed cgroup-bin (unrelated to anything, but tends to break suspend!) i've never had any problems with any version of anything i've ran on this laptop
[16:52] <herton> ohsix: which was the last kernel version you got suspend/resume working on this laptop?
[16:52] <ohsix> the last one i know for sure is 2.6.38-9-generic
[16:53] <ohsix> since i couldn't run -10 due to the eject thing; when i finally could, i encountered the problem for the first time, with 2.6.38-11.47
[16:56] <herton> ohsix: ok, that clears up things. let me know the bug number you open, we may do a bisect again just for this issue. Also if you can get the picture of the crash and attach on the bug, would be great.
[17:24] <ogasawara> anyone else you able to connect to tyler?
[17:24] <ohsix> herton: i'll try, i don't know when though; i use this laptop for "work" 99% of the day, rebooting even is a pain :]
[17:25] <tgardner> ogasawara, hmm, its lost tis love for me
[17:25] <ogasawara> tgardner: damn, it's probably lost my build that was in progress as well
[17:25] <tgardner> ogasawara, yantok seems to be down
[17:25] <tgardner> ogasawara, use gomeisa
[17:25] <ogasawara> ack
[18:02] <jmburges> I think bug 565543 can be marked as triaged...correct? I'm new to kernel bug triaging
[18:02] <ubot2> Launchpad bug 565543 in linux "Alps touchpad detected as ImPS/2 Generic Wheel Mouse(in VAIO E series) after the kernel upgrade" [Medium,Confirmed] https://launchpad.net/bugs/565543
[18:08]  * tgardner --> lunch
[18:55]  * apw calls its quits
[18:59]  * jjohansen -> lunch
[19:47] <pgraner> rtg:
[19:47] <pgraner> [   75.457505] pcieport 0000:00:01.0: AER: Multiple Corrected error received: id=0008
[19:47] <pgraner> [   75.457535] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0008(Receiver ID)
[19:47] <pgraner> [   75.457541] pcieport 0000:00:01.0:   device [8086:3c02] error status/mask=00000040/00002000
[19:47] <pgraner> [   75.457546] pcieport 0000:00:01.0:    [ 6] Bad TLP               
[19:47] <pgraner> [   75.457549] pcieport 0000:00:01.0:   Error of this Agent(0008) is reported first
[19:47] <pgraner> [   75.457556] pcieport 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0100(Transmitter ID)
[19:47] <pgraner> [   75.457560] pcieport 0000:01:00.0:   device [8086:1d74] error status/mask=000031c1/0000e000
[19:48] <pgraner> [   75.457564] pcieport 0000:01:00.0:    [ 0] Receiver Error         (First)
[19:48] <pgraner> [   75.457568] pcieport 0000:01:00.0:    [ 6] Bad TLP               
[19:48] <pgraner> [   75.457571] pcieport 0000:01:00.0:    [ 7] Bad DLLP              
[19:48] <pgraner> [   75.457574] pcieport 0000:01:00.0:    [ 8] RELAY_NUM Rollover    
[19:48] <pgraner> [   75.457578] pcieport 0000:01:00.0:    [12] Replay Timer Timeout  
[19:48] <pgraner> [   90.240075] pcieport 0000:00:01.0: AER: Multiple Corrected error received: id=0008
[19:48] <pgraner> [   90.240105] pcieport 0000:00:01.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0008(Receiver ID)
[19:58] <jjohansen> reboot
[20:40] <marcoceppi> Do I need to do anything special in order to create a deb source that LP can build?
[20:44]  * tgardner --> EOD
[20:52]  * herton -> eod