/srv/irclogs.ubuntu.com/2009/05/06/#ubuntu-kernel.txt

smbcking, have you insight into the acpi processor declaration?09:16
ckingsmb: acpi processor declaration - only what the ACPI handbook says, and from memory, zilch, zero.09:16
ckingwhat's required?09:17
* apw notes the mtrr conv is still there in scroll back ... i think i have found the change which might make that come back, building a test kernel now09:17
smbI am revisiting a bug about these pause-until-keypress on boot. And some guy seems to be able to fix it for him with a custom dsdt.09:17
* apw wonders if he told you what he changed09:17
smbbeside other things in there, this looks a bit suspicious09:17
smb-    Scope (\_PR)09:18
smb+    Scope (_PR)09:18
smb     {09:18
smb-        Processor (CPU0, 0x00, 0x00001010, 0x06) {}09:18
smb-        Processor (CPU1, 0x01, 0x00001010, 0x06) {}09:18
smb+        Processor (CPU0, 0x00, 0x00000000, 0x06) {}09:18
smb+        Processor (CPU1, 0x01, 0x00000000, 0x06) {}09:18
smb     }09:18
ckingOK - me looks at manual09:18
smbIn the book it only says the number is the processor block address09:18
apwbut what is the processor block ...09:19
smbexactly09:19
ckinghow can that change fix the bug?(!)09:19
* apw connects a tap to cking's acpi brain centre09:19
apwif the processor block describes the processor, then it might change the capabilities of the cpus09:20
ckingcking's acpi brain centre is in need of coffee + some reading of the spec09:20
smbapw, That is my wild guess09:20
* apw couriers over some freshly ground beans09:20
smbThe rest of the changes mostly consist in using One instead of 0x0109:20
smband Zero instead of 0x00 and renames like \_PR to _PR (which looks slightly wrongish to me)09:21
ckingI'm googling for some info..09:23
* apw plays the countdown clock tune in the backgroun09:28
* cking is now reading some pdfs..09:32
hughhalfo09:34
* smb is scared of what he has done...09:38
smbActually 0x0 could mean nothing which would be slightly contradicting the 0x06 length but on the other hand there was a little sentence somewhere else about ignoring those definitions...09:43
ckingFrom my limited googling know-how, the address refers to the PBLK address which allows inter processor communication some how - if set to zero it essentially states there is no PBLK. I assume the hang is because something is borked on the interprocessor communication.09:43
ckingIs this an AMD processor?09:43
smbIts one of those bugs with 320 comments... I believe yes, some with MCP67 based hardware... 09:46
ckingsmb: acpi_processor_get_power_info_fadt() checks the PBLK - and probably this is used when the system goes idle. I've seen some comments that this may be broken on some AMD cpus09:46
ckingIs than enough to get ones teeth into?09:47
* smb notes that down09:47
smbThat is a pointer to look at. Thanks09:47
apwsmb did we ask them to try idle=foo type selectors?09:47
smbapw, I don't think so. Hard to tell under that pile of comments... nope, does not look like it09:48
smbbug 27224709:49
ubot3Malone bug 272247 in linux "System freezes during boot, unless I hold a key down" [High,Confirmed] https://launchpad.net/bugs/27224709:49
smbwear your danger-sensitie-googles09:49
apwsmb, damn i think we talked about putting a list of options to try together for them, seems we talked and failed to act09:49
smbYeah, and in the mean time some of those just gather a lot of other drifts09:50
apwyou just know its going to be a 2 line quirk once its found09:52
smbapw, most of the affected in that report seem to be hp pavilion laptops. but I just look at one stating he got a P4 moile with an intel chipset...09:53
smbToshiba Satellite A3009:53
apwhrm ... 09:53
apwthough many people see the same bug when it cannot be the same09:53
smbHP Pavilion dv6646us, AMD turion64x2, nVidia, Broadcom.09:54
smbyeah, at this point it is hard to make out any real issue09:54
smbIt can be the same or various things09:55
smbI would think the essence is that for some reason the system ends up in a sleep state without a wake up trigger. That could be some timer issue or processor definition...09:56
smbBest action is to try to dig into that with that one system I got with that problem...09:57
* cking agrees09:58
smbOk, that would be a system which defines a register block only for CPU0 (on a amd dual core)10:00
smbSo I could both try the idle= and the modified dsdt10:04
smbThis one is special though, as it only has problems with C1E enabled10:04
ckingsmb: maybe this has some background hints - https://bugzilla.redhat.com/show_bug.cgi?id=46563710:04
ubot3bugzilla.redhat.com bug 465637 in kernel "C1 state unsupported on modern AMD mobiles" [Medium,Closed: cantfix] 10:04
smbcking, Thanks for that link. Will have a read on that10:05
ckingit may be related, hope it does not waste your time.10:05
smbThe beginning sounds intresting anyway10:05
ckingI like the comment "I will never again buy any AMD product "10:06
cking states are processor power states. C1 is mandantory and reached on IA32 compatible processors using the HLT instruction, C2 and C3 are optional and must be configured.10:09
ckingC states can be configured in ACPI using two methods:10:09
cking   1. by defining the P_BLK base address in the Processor() Definition, and P_LVLx_LAT values in the FADT10:09
cking   2. using the _CST object 10:09
ckingP_BLK is easier to configure, if the hardware supports that method. ACPI defines that there must be two registers at P_BLK+4 and P_BLK+5 that initiate a transition to C2 or C3 when the register is read. After sleep, the read returns 0. P_LVLx_LAT define the worst case latency of the state transition.10:09
cking_CST is necessary if you want to support more than 3 C states, or if the transition procedure doesn't follow the ACPI requirement. 10:10
ckingsmb: ^^ may be worth checking the P_LVLx_LAT values in the FADT too10:10
smbThe system does not seem to define any C2 or C3, so be compliant what I take from glancing over the comments.10:12
Chrom_hi all11:48
Chrom_hey guys, did anybody try to dist-upgrade jaunty today? there-s a leftover package that prevents linux-restricted-modules-generic to be installed11:49
gigasoft i have problem with Workspace Switcher, how to reinstall it or install another one12:19
amitkgigasoft: and how is that related to the kernel? :)12:21
ograamitk, modprobe new-workspace.ko :P12:21
amitkplease try #ubuntu12:21
gigasofti do not know12:21
ograyeah12:21
ogra#ubuntu for support is the right place12:22
gigasoftthanks anyway12:22
gigasoftbue12:22
gigasoftbye12:22
_rubenheh12:27
apwikepanhc, you about today?13:07
ikepanhcapw: what?13:07
apwhi, was just looking at a bunch of intel graphiscs issues, and see you have the A17 swizzle bug.  wondering what you are doing with it, which patch you are going to propose for sru13:08
ikepanhceh, bad, I almost forget that. sorry. Do it as highest priority13:10
apwikepanhc, no problem.  i can just as easily do it if you arn't activly doing it now13:10
ikepanhcThanks, I think I can do it today13:11
apwi assume you were going to propose this patch: http://launchpadlibrarian.net/24790669/i915-gem-disable.patch13:12
ikepanhceh? I prepare to cherry-pick from upstream: 280b713b5b0fd84cf2469098aee88acbb5de859c13:13
apwthat is a pretty huge commit ... 13:13
ikepanhcYes it is :-(13:14
apwfrom what i read the alternative is to allow gem to be disabled, using that other patch.  that might be more appropriate for sru13:15
ikepanhcI think I shall look at the thread again13:15
apwok13:15
ikepanhcLast time I look at the thread, they said the mainline build which has the commit works fine.13:16
apwyeah, but the patch doesn't just cherry-pick, and its pretty big.  your call if you think its worth trying the backport13:17
ikepanhcBut we need the shortest commit, am I right?13:17
apwsmaller means less risk of regressions, and regressions for previously unaffected users are something to avoid for sure13:17
ikepanhcHmmm, checking the thread again.13:19
ikepanhcapw: so, we have a huge commit with proper fix and another simple patch but not proper fix13:44
apwyep thats the one13:45
ikepanhcya, I think simple is the best :-D13:45
apwsmb, you wanted to have a link to the mtrr test kernels, they can be found here: https://bugs.edge.launchpad.net/ubuntu/jaunty/+source/linux/+bug/314928/comments/5413:56
ubot3apw: Error: Could not parse data returned by Malone: The read operation timed out13:56
smbapw, cool, will test13:56
* apw spanks ubot313:56
apwsmb, i am going a bit mad ... any idea which damn applet does volume?16:13
apwie which one converts alsa changes into an OSD?16:13
smbno, sorry no idea. I would try #ubuntu-devel...16:14
johanbrI don't think that's an applet. That's just some core component of gnome (gnome-settings-daemon?).16:22
=== thunderstruck is now known as gnomefreak
=== awe is now known as awe-lunch
=== awe-lunch is now known as awre
=== awre is now known as awe
awesconklin: ping20:24
sconklinawe: hello20:25
awehey was wondering if you saw rtg's reply to my SRU for the broadcom wl driver.  are we going to create netbook-lpia branches for the lrm git trees?20:25
rtgawe: haven't the ABI's already diverged?20:26
sconklinhmm. Was that request for the driver to go into lrm? The way the request was made it would apply to the main hardy distro kernel20:27
awertg: I think so, but I didn't check...20:27
sconklinI think it should go into lrm.20:28
awesconklin: yes, since cking and I get notified whenever a new version is released, I decided I'd handle it across all releases.20:28
awesconklin: it's already in lrm, this is an update20:28
rtgsconklin: drop it on master, SRU it, then cherry-pick to netbook-lpia ?20:28
awesconklin: I still need to do an SRU for intrepid and jaunty20:28
sconklinrtg: that's what I assumed when you pointed him at srb, but I wanted to make sure20:29
awertg: OK, so if I handle the SRUs, then sconklin can cherry pick?20:29
sconklinawe: yes20:29
awecool20:29
rtgawe: yeah, what sconklin said20:29
sconklinawe: but it never hurts to bug me and make sure I don't miss it20:30
awertg: also, one other thing that concerns me is that our change to using git has made the process of upgrading to a new version more error prone.20:30
awertg: the ACK process alone doesn't really ensure that I haven't made a mistake in untar'ing / manual manipulation required20:31
sconklinawe: on another topic . . . when can we sync up your dennis branch in lum into our repo, and possibly combine it with the netbook-lpia branch?20:31
awertg: perhaps I should ask someone like cking to verify out-of-band that it looks right?20:31
rtgawe: thats a good idea, though I don't see how git could but help. you can at least see whats changed.20:32
awertg: it doesn't help...  colin would need to validate the git tree against the zip from broadcom20:33
awesconklin: it's on my list.  I promise I'll get the patch requests sent out before next week's kernel mtg.20:33
sconklinawe: as long as you're on it - you're the one mostly affected, and you are aware of the (6 or so patches) delta between your branch and ours.20:34
awesconklin: I'm actually working on the desktop team for the karmic cycle, and am still trying to get my bearings20:34
sconklinawe: I completely understand20:34
awesconklin: I am aware of it, and it's at the top of my list post updating the wl driver20:34
rtgawe: we've unrolled the zip in Hardy LRM. I'm not sure wherein lie your concerns.20:35
* awe beats himself over the head for volunteering to upgrade the 'wl' driver20:35
rtgawe: c'mon, it can't take 10 minutes.20:36
awe_rtg: sorry 'bout that... !@#% X lockup/crash...20:40
awe_rtg: anyways. ot20:40
awe_it's not the simple.  we used to be able to just copy the new tarballs in place and tweak the rules20:40
awe_now, since any patches we have are applied as commits, we have to untar, re-apply the patches ( MODULE_LICENSE / Makefile )20:41
awe_...then copy the architecture-specific binary files into place ( they're now suffixed with the arch )20:41
awe_it's not hard, just alot of manual steps...which makes it error prone20:42
rtgawe: what about carrying the patches in the patches directory like we used to?20:42
rtgthat seems to have disappeared. hmm20:43
awe_yup20:43
rtgawe: I see your point.20:43
awe_;)20:43
rtglemme annoy smb about it a little.20:43
awe_OK, should I hold off on the SRU for intrepid / jaunty then?20:44
rtgyeah, lets get that sorted first.20:44
awe_sounds good20:45
=== awe_ is now known as awe
sconklinawk has damaged me20:45
aweisn't that a song by your buddies from brooklyn?  ;)20:47
sconklinawe: something like that. they damaged me too :)20:48
=== awe is now known as awe-afk
=== awe-afk is now known as awe
rtgawe: what patches are we carrying 'out-of-band' for Broadcom wl?21:07
awethere's used to be a Makefile patch and a vlan patch ( which also included the MODULE_LICENSE update )21:08
rtgawe: i think the vlan patch was eventually accepted by Broadcom21:08
awevlan has been fixed in the driver, however the MODULE_LICENSE still needs to be set, so that should get rolled into it's own patch21:09
rtgawe: do you have the MODULE_LICENSE patch somewhere?21:10
aweI applied it directly as a commit in my tree referenced in the SRU request21:10
rtgawe: k, lemme look21:11
awehmmm...actually maybe it wasn't a separate commit21:11
rtgawe: it would help if it was. could you extract it?21:11
aweI do have a version of the patch for our dennis-specific lrm21:11
pace_t_zuluanyone running karmic as a virtual machine experiencing lockups since 2.6.30 was installed?21:22
rtgawe: I've responded to your LRM patch request. I'm outta here. beers await.21:51
awertg: thanks dude.  sake for me shortly...  ;)21:53
samourai_41Slt21:55
=== matt64- is now known as erle-

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