[01:13] <Darxus> Wow, new upstream merged two days before kernel freeze.
[04:52] <MTecknology> What's the difference between Ubuntu-2.6.31-14.46 and Ubuntu-2.6.31-302.7 ?
[04:54] <MTecknology> obviously the numbers - I'm just curious what the really high numbers are used for
[06:56] <billybigrigger> does anyone here maintain submit fixes to upstream for the gspca v4l2 modules?
[06:57] <billybigrigger> maintain/submit
[06:57] <billybigrigger> rather :P
[06:57] <MTecknology> I tried to build a package and when I did "make install" I got this error. I'm wondering what's missing in the kernel to make it work. "include/linux/autoconf.h or include/config/auto.conf are missing."
[06:57] <billybigrigger> just wondering how i go about getting my webcam to work, it hasn't worked throughout the whole 2.6.31 kernel development, and i was hoping by now that it might have been fixed
[07:00] <billybigrigger> do those files exist in your kernel source directory?
[07:07] <MTecknology> me?
[07:07] <MTecknology> ya
[07:07] <MTecknology> they do
[07:11] <MTecknology> billybigrigger: do you know ho to find out what option compiles the files?
[07:11] <billybigrigger> no
[07:11] <billybigrigger> haven't done any compiling for months
[07:11] <MTecknology> I'm shooting for a 2.5MB kernel
[07:11] <billybigrigger> since A2 :P
[07:11] <billybigrigger> oh
[07:11] <billybigrigger> hehe
[07:46] <MTecknology> 12min to dload vbox - hurray crappy internet
[08:24] <Darxus> I got the kernel source package to build and boot patched with both the bfs cpu scheduler and the bfq i/o scheduler.
[11:56] <xteejx> hi guys, member of bug control here, there is a bug 425756 in the Ubuntu kernel which affects the SB6/700 sata controller with an ata soft lockup, there seems to be a patch at http://kerneltrap.org/mailarchive/git-commits-head/2008/6/14/2122314 does this look any good, and is there any chance we can get it in? :)
[11:56] <ubot3`> Malone bug 425756 in linux "[Karmic] cd/dvd drive not detected ." [Undecided,New] https://launchpad.net/bugs/425756
[11:58] <L_X_> hi there! I have a little trouble installing the backports-modules
[11:58] <xteejx> !ubuntu
[11:58] <ubot3`> Ubuntu is a complete Linux-based operating system, freely available with both community and professional support. It is developed by a large community and we invite you to participate too! - Also see http://www.ubuntu.com
[11:58] <xteejx> oops
[11:58] <xteejx> L_X_, the place for help and asking questions is #ubuntu this is the kernel teams IRC chatroom :)
[11:59] <L_X_> only in launchpad (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/445931) it says to ask the question here... maybe you should clarify...
[11:59] <ubot3`> Malone bug 445931 in linux "linux-backports-modules-karmic not installable, dependency problem" [Undecided,New] 
[11:59]  * L_X_ is heading to 
[11:59]  * L_X_ is heading to #ubuntu
[11:59] <L_X_> cya
[12:01] <xteejx> Kernel Team: Sorry to be a pain, but I'd appreciate if you could look at that patch if/when you're not busy bug 425756 with patch :)
[12:01] <ubot3`> Malone bug 425756 in linux "[Karmic] cd/dvd drive not detected ." [Undecided,New] https://launchpad.net/bugs/425756
[12:01] <xteejx> and thank you
[12:40] <csurbhi> In hotplugging, a bus probe occurs after which a matching driver probes a device. The driver is chosen based on the device id and the vendor id.
[12:40] <csurbhi> Is this understanding right ?
[12:41] <csurbhi>  Or does a bus driver probe for every device (without looking at the device id) ?
[13:09] <smb> csurbhi, It is add devid,vendorid based. When a new device appears it will register to a bus and each driver already registered with that bus will get its probe function called with the device id until one driver claims it or no more drivers are present. As there s an add event for the device udev can match that id of the device with alias strings of drivers and load one if one is found which is not already present. New drivers registering ag
[13:09] <smb> ain get their probe function called with every device on the bus, which is not yet claimed.
[13:13] <csurbhi> ok
[13:14] <csurbhi> but is not  /lib/modules/modules.alias looked at to modprobe a particular driver?
[13:15] <smb> right, that file is generated from the information in the modules when you run depmod
[13:15] <csurbhi> i thought that the bus looks at the vendor id and the product id and then looks at the modules.alias and then appropriately that driver module gets inserted
[13:15] <smb> the bus (from the kernel) does nothing here. It is udev that loads modules
[13:16] <smb> if you insert a device, this jsut generates an add event and causes currently loaded drivers to be called
[13:17] <csurbhi> but what happens if a driver (compiled as a module) for a device is not yet loaded
[13:17] <smb> if you do a modinfo on a driver you will notice alias strings, these are used to make the modules.alias file and that is used by udev to match an add event on a bus with a driver
[13:18] <csurbhi> right..so who generates the event on the bus
[13:18] <Keybuk> what bus?
[13:18] <csurbhi> because that event should have the device id and the vendor id
[13:19] <csurbhi> when you add a device an event is generated. on a bus ? so who generates that ?
[13:19] <smb> I would call it the bus subsystem (not sure this is the correct term)
[13:20] <Keybuk> when new devices are detected, the subsystem driver creates stub kernel objects for them
[13:20] <csurbhi> yes.. thats why i said that the bus might look at the device id and the vendor id
[13:20] <csurbhi> ok.. but i get it
[13:20] <csurbhi> ..
[13:20] <Keybuk> the properties of those kernel objects include things like their port id, and any bus-specific information like vendor id, device id, etc.
[13:21] <Keybuk> driver core creates entries in the /sys filesystem for these
[13:21] <Keybuk> and it sends a message on a special netlink socket announcing the new device
[13:21] <Keybuk> it then *also* runs its internal match table against built-in and already loaded modules
[13:21] <csurbhi> yes.. and then udev gets this message looks at the module.alias and modprobes the device driver
[13:21] <csurbhi> :)
[13:21] <Keybuk> and those modules may claim the device (in which case they take over the kernel object and begin added more details, like interfaces and device nodes)
[13:22] <Keybuk> udev receives this message
[13:22] <Keybuk> inside this message is a "modalias" string
[13:22] <Keybuk> this is a single string made up of the important kernel object information
[13:22] <Keybuk> the format of the string is generally <subsystem>:<info>
[13:22] <Keybuk> so for example, a PCI subsystem modalias would look like
[13:22] <Keybuk> pci:v00001180d00000843sv00001028sd00000209bc08sc80i00
[13:22] <Keybuk> while a USB subsystem modalias looks like
[13:23] <Keybuk> usb:v413Cp8126d0367dcE0dsc01dp01icE0isc01ip01
[13:23] <Keybuk> as you can probably tell, inside that is the vendor id, device id, etc.
[13:23] <Keybuk> modules themselves have match tables which are used in the kernel to match against a module
[13:23] <Keybuk> from these wildcard modalias strings are generated
[13:24] <csurbhi> ok
[13:24] <Keybuk> these have the "any of these" bits of the string replaced by *
[13:24] <Keybuk> and you can see these by running modinfo on a module
[13:24] <Keybuk> # modinfo ricoh_mmc | grep alias
[13:24] <Keybuk> alias:          pci:v00001180d00000843sv*sd*bc*sc*i*
[13:24] <csurbhi> two questions 1) at boot time, how is a bus driver claimed ?
[13:24] <Keybuk> so whenever it receives a netlink message with a modalias in it, udev calls "modprobe $MODALIAS"
[13:25] <Keybuk> modprobe matches the string against the known module names, and known module aliases
[13:25] <Keybuk> using wildcard matching
[13:25] <Keybuk> and thus you end up with a particular driver loaded
[13:25] <Keybuk> as this driver loads, its _init() function will bind it in-kernel to any kobjects
[13:25] <Keybuk> and since it's loaded, any new devices it claims will be bound in-kernel too
[13:25] <Keybuk> that's it ;)
[13:26] <Keybuk> csurbhi: I have answered that question above
[13:26] <csurbhi> so by this logic a driver should be invoked only when a device id is registered in it
[13:26] <Keybuk> yes
[13:26] <csurbhi> if a device id is not registered it should not be called
[13:26] <Keybuk> I don't know what you mean by "called"
[13:27] <csurbhi> called = invoked
[13:27] <Keybuk> a driver is not bound to a device that it hasn't claimed
[13:27] <Keybuk> I don't know what you mean by "invoked"
[13:27] <Keybuk> drivers aren't called or invoked, they claim devices
[13:27] <Keybuk> the devices become bound to the driver
[13:27] <csurbhi> but a modalias of a driver will have a device id and a vendor id
[13:28] <Keybuk> csurbhi: not necessarily
[13:28] <Keybuk> it's quite valid to have a modalias wildcard match that matches all devices
[13:28] <Keybuk> pci:*
[13:28] <Keybuk> that would be a driver that can claim any pci device
[13:28] <Keybuk> (for example)
[13:28] <csurbhi> ok
[13:28] <Keybuk> that'd be bad though, only one driver can claim any one device
[13:28] <Keybuk> there are drivers that match entire device class or interface classes though
[13:28] <csurbhi> but then what is the point of this:
[13:28] <Keybuk> usb-storage for example
[13:29] <Keybuk> alias:          usb:v*p*d*dc*dsc*dp*ic08isc06ip50*
[13:29] <csurbhi> less 2.6.28-15-generic/modules.alias | grep sdhci
[13:29] <csurbhi> alias pci:v*d*sv*sd*bc08sc05i* sdhci_pci
[13:29] <csurbhi> yes.. exactly
[13:29] <Keybuk> csurbhi: exactly my point
[13:29] <csurbhi> have a v*d* ?
[13:29] <csurbhi> why have that ?
[13:29] <Keybuk> any vendor's device, that has a PCI base class of 08 and subclass of 05
[13:30] <csurbhi> could there be a clash ? when another driver for eg: says bc*sc*
[13:30] <csurbhi> and one driver says v*d*
[13:30] <Keybuk> had to look that up
[13:30] <Keybuk> and some eejit has moved pci.ids
[13:30] <Keybuk> PCI class 08 is "Generic system peripheral"
[13:30] <Keybuk> subclass 05 is "SD Host controller"
[13:31] <csurbhi> hmmm...thanks a lot :)
[13:31] <Keybuk> so you have a case there where there is a generic kernel driver for that entire device class
[13:31] <csurbhi> that helped me a lot.. :) 
[13:31] <Keybuk> that's actually a Linux tendancy
[13:31] <csurbhi> now i get it
[13:31] <Keybuk> if you can do away with a driver-per-device and instead have generic drivers that deal with the special cases through quirks, that's a big WIN!
[13:32] <Keybuk> yes, you're quite right that if you added another driver that matched the same device (e.g. by vendor/device id) they would clash
[13:32] <Keybuk> both would be able to claim the device
[13:32] <Keybuk> in which case there are rules about which one wins
[13:32] <Keybuk> (look at the modules.order file :p)
[13:32] <csurbhi> i can see a sdhci-pci driver getting called and failing and then another driver getting called.. and i was wondering why the sdhci-pci was getting called.. i can now see why !
[13:32] <Keybuk> a driver is quite permitted to decline a device
[13:33] <Keybuk> "oh, I don't know about *this* one"
[13:33] <csurbhi> ok
[13:33] <Keybuk> in which case, the next driver in line can have a go
[13:33] <csurbhi> yess
[13:33] <csurbhi> now i get it :) thanks a lot !!
[13:33] <csurbhi> one more question
[13:33] <csurbhi> i also read somewhere
[13:33] <Keybuk> the Windows developers hate this
[13:33] <csurbhi> that hotplugging could be scpi intermediated
[13:33] <csurbhi> :)
[13:33] <Keybuk> gregkh gave a wonderful presentation at a devcon about Linux driver core
[13:33] <Keybuk> and the windows people were sitting with dropped jaws
[13:34] <csurbhi> :D
[13:34] <Keybuk> they have nothing as simple and elegant as this ;)
[13:34] <csurbhi> :)
[13:34] <csurbhi> boy !!! thanks a lot!!!!
[13:34] <Keybuk> csurbhi: I'm not sure how scpi applies in this question?
[13:34] <Keybuk> did you mean acpi?
[13:34] <csurbhi> i not get the whole thing !! i took a great deal of time looking at why ricoh_mmc was getting called after a sdhci-pci driver
[13:34] <csurbhi> now i get it completely !!! wow !
[13:35] <csurbhi> yes.. i meant acpi
[13:35] <Keybuk> oh wow that was a totally freaky guess
[13:35] <Keybuk> I picked ricoh_mmc simply because it was the last thing with a pci modalias in my udev log ;)
[13:35] <csurbhi> heehee
[13:35] <Keybuk> right
[13:35] <Keybuk> ACPI is a whole world of pain
[13:35] <csurbhi> so can u pleaee tell me how this thing works
[13:35] <csurbhi> when acpi mediates ?
[13:36] <Keybuk> everything I am about to say is a lie
[13:36] <csurbhi> i believe u
[13:36] <csurbhi> :P
[13:36] <Keybuk> but it's a lie that explains how things work
[13:36] <Keybuk> ACPI is a system that allows your computer to have software that is executed by the kernel
[13:36] <Keybuk> when the kernel needs to do something (e.g. enumerate the PCI bus), it actually runs this special software
[13:36] <Keybuk> this special software is run on a virtual machine that Linux implements
[13:37] <Keybuk> and produces the results the kernel expects
[13:37] <Keybuk> this can also deal with interrupt handlers, and so forth
[13:37] <Keybuk> the side-effects of running this software ideally include programming chips on the board to do the right things
[13:37] <Keybuk> that way the kernel doesn't need to know how to program the MMC
[13:37] <Keybuk> or PCI controller
[13:37] <Keybuk> the motherboard can know that
[13:37] <csurbhi> so cool
[13:37] <Keybuk> but the motherboard doesn't need an operating system on it
[13:38] <Keybuk> so the kernel executes code on the motherboard's behalf
[13:38] <Keybuk> so on boot, the kernel will begin executing the acpi code
[13:38] <Keybuk> this will result in the hardware being programmed correctly
[13:38] <Keybuk> linux arranges (through standard acpi methods) for pci hotplugging to be enabled
[13:39] <Keybuk> this may require, for example, that when a card is hotplugged that further acpi methods are invoked to communicate with the pci controller and find out what happens
[13:39] <Keybuk> but this results in Linux's registers being updated
[13:39] <Keybuk> so it can know what cards were added/removed
[13:39] <Keybuk> and can arrange for the new card to be initialised
[13:39] <Keybuk> or resources of the old card to be freed
[13:39] <Keybuk> etc.
[13:39] <csurbhi> ok
[13:40] <csurbhi> so when its not acpi mediated, the pci subsystem gets the interrupt when a device is added
[13:40] <csurbhi> whereas when it is acpi initiated, acpi gets the interrupt
[13:40] <Keybuk> no, it's still all done with interrupts the old fashioned way
[13:40] <Keybuk> the difference is that when not using acpi, Linux has to do the leg work to talk to the pci controller
[13:41] <Keybuk> and has to know every detail about your pci controller
[13:41] <Keybuk> whereas with acpi, that is somewhat abstracted
[13:41] <csurbhi> ok
[13:41] <csurbhi> and one last question
[13:41] <csurbhi> the modules.order
[13:41] <csurbhi> who creates that and based on what ? 
[13:42] <Keybuk> the kernel build system creates that
[13:42] <Keybuk> based on the order that modules are listed in its Makefiles
[13:42] <csurbhi> ok
[13:42] <csurbhi> :)
[13:42] <Keybuk> this is the same order that the code would be statically linked into the kernel if they were all built-in
[13:42] <csurbhi> ok
[13:42] <csurbhi> thanks a lottt
[13:43] <csurbhi> that was veryy insightful
[13:44] <joaopinto> hello, is the generic kernel built with PAE enabled ?
[13:46] <joaopinto> oh, its linux-image-2.6.31-14-generic-pae
[15:54] <apw> amitk, bjf, all new shiney arm kernels of both types are in the archive
[15:55] <apw> lool, i belive you should find a good linux-libc-dev for armel in the archive now
[15:56] <wzssyqa> [Bug 447791]
[15:56] <ubot3`> Malone bug 447791 in linux "after update to 2.6.31-13,the virtual Console Huap" [Undecided,New] https://launchpad.net/bugs/447791
[15:57] <happyaron> hi team, could I ask which package should we exactly file bug against for this bug? ^^^
[15:57] <bjf> apw, thanks, looks like I might have a regression on mvl
[15:58] <bjf> bug 450940
[15:58] <ubot3`> Malone bug 450940 in linux-mvl-dove "Regression in linux-mvl-dove 207 and later causes Y0 boards to hang seconds after booting" [High,Confirmed] https://launchpad.net/bugs/450940
[15:58] <lool> apw: Thanks
[15:58] <lool> apw: I did see the build output the package at least
[15:59] <apw> bjf, hrm, is that your new fix or something in the rebase do we think
[15:59] <bjf> apw, I've not touched dove other than that config issue, possible rebase / stable updates fallout, not sure
[16:00] <apw> hrm yes it was a simple config change.  then again the rebase shouldn't have changed much core it was mostly stable updates and that was pretty limited
[16:01] <apw> and cirtainy nothing on the mvl-dove boot i'd think 
[16:07] <lool> Too bad we cant bisect it -- exactly what was to be solved by rebasing the tree  :-)
[16:07] <lool> we could cherry pick stable updates on top of the previous mvl tag and see how long it works
[16:14] <MTecknology> Did you guys know that rolling your own kernel can be heap load if fun and irritation :)
[16:25] <Keybuk> rtg: got one for you
[16:25] <Keybuk> ext4 doesn't seem to be syncing data on shutdown or SysRq-S
[16:25] <Keybuk> an explicit sync() does seem to work
[16:26] <rtg> Keybuk, that seems more like one for Ted
[16:27] <MTecknology> did I break something?
[16:27] <Keybuk> well, it's causing me at the moment to fail to boot after upgrading the kernel ;)
[16:27] <Keybuk> because the initramfs is trunctated
[16:28] <rtg> Keybuk, ick!
[16:28] <rtg> Keybuk, so, we don't normally sync() on shutdown or reboot? it should sync on unmount.
[16:28] <Keybuk> we don't call sync() no
[16:29] <Keybuk> the kernel should do that
[16:30] <rtg> Keybuk, does rootfs get unmounted before shutdown? I'd think it couldn't as long as /sbin/init was alive.
[16:30] <Keybuk> yes
[16:30] <rtg> so that should sync
[16:32] <Keybuk> of course, now that I look at it, I can't find that sync
[16:32] <Keybuk> maybe ext4 doesn't sync the filesystem on remount readonly now?
[16:33] <rtg> hell if I know
[16:33] <rtg> its hard to imagine that an issue this systemic would not have been noticed already
[16:35] <Keybuk> doesn't look like it does now
[16:36] <rtg> Keybuk, drat, lemme wrap up LBM. are you gonna file a bug? this seems like a show stopper.
[16:36] <Keybuk> the kernel comment for reboot() says you should sync() first
[16:37] <rtg> how can remount readonly _not_ sync first? especially if there are not outstanding I/O errors.
[16:38] <Keybuk> it just doesn't
[16:38] <Keybuk> ext3 clearly does
[16:38] <Keybuk> ext4 clearly does not
[16:38] <Keybuk> this looks like a change in ext4 relatively close to .31
[16:39] <rtg> Keybuk, well, we should confirm this with Ted
[16:39] <Keybuk> I'm going to put the sync() call back into reboot anyway
[16:39] <Keybuk> it's probably for the best
[16:39] <rtg> Keybuk, do shutdown and reboot go through the same path at some point?
[16:39] <Keybuk> yes
[16:39] <rtg> app sapce or kernel?
[16:40] <Keybuk> app space
[16:40] <Keybuk> kernel is quite different
[16:40] <rtg> I haven't looked at the shutdown path in the kernel since 2.4 days
[16:44] <Keybuk> let's see if this fixes it
[16:45] <apw> Keybuk, so how did you notice, ext4 always dirty on reboot?
[16:46] <Keybuk_> that seemed better
[16:46] <Keybuk_> will probably need to do a few of those to be sure
[16:46] <apw> Keybuk, so how did you notice, ext4 always dirty on reboot?
[16:46] <rtg> apw, I'm wondering if this might have something to do with the KVM folks complaining about fsck on boot
[16:46] <apw> rtg very likely ...
[16:46] <apw> i am supprised noone noticed before, like you or me
[16:46] <Keybuk> apw: no, truncated files or empty files after reboot
[16:47] <rtg> Keybuk, I must update kernels several times a day on different machines.
[16:47] <csurbhi>  but there was an article on lwn about truncation of files for ext4
[16:47] <Keybuk> yeah, but depends how much gets flushed to disk
[16:47] <Keybuk> speed of reboot
[16:47] <Keybuk> etc.
[16:47] <Keybuk> reboot here is fast, I'm on SSD, but it's *ahem* not production
[16:48] <apw> Keybuk, i note my main lappy is still ext3, but my 10v is ext4 and i've not seen it there
[16:48] <csurbhi> it seems that it does a sync only after a timeout and before that if you reboot or shutdown, u can loose data
[16:48] <apw> but its likely i am idle for ages before reboot often
[16:48] <csurbhi> http://lwn.net/Articles/322823/
[16:48] <Keybuk> apw: I've been doing a lot of "update-initramfs -u ; reboot" in the last 24 hours
[16:48] <Keybuk> and that's when I've noticed it
[16:49] <apw> oh is this the cause of your bust initramfs you mentioned ... hrm
[16:50] <Keybuk> possible
[16:50] <Keybuk> anyway, comment in the kernel above the definition of reboot() says you must call sync() first
[16:50] <Keybuk> so I call sync() first :p
[16:50] <rtg> it sure can't hurt
[16:58] <apw> Keybuk, i wonder what use there is to not sync and hit reboot ...
[17:02] <Keybuk> apw: speeeeed
[17:03] <apw> Keybuk, speedily losing my data, yay
[17:04] <apw> bjf, did you say your y0 was ok on that kernel?
[17:04] <bjf> apw, so far so good
[17:04] <apw> bjf, so panic 'less'
[17:05] <bjf> apw, because it's Y0 and now Y1 I panic 'less'
[17:06] <apw> bjf, basically it works on all your h/w ?
[17:06] <bjf> apw, it works on my Y0  and lool's Y1
[17:06] <bjf> apw, I've not had a chance to test my Y1
[17:07] <bjf> apw, these are not fat machines to install onto
[17:07] <apw> no i guess not
[17:07] <bjf> *fat*fast
[17:08]  * apw didn't even see that
[17:08] <lool> bjf: so you coulduse yesterday;s image to install and then upgrade to today's kernel?
[17:08] <bjf> lool, yup, doing that
[17:11] <MTecknology> How can I find out if I have any EFI firmware?
[17:14] <rtg> MTecknology, unless you are running a recent server, then you likely _don't_ have EFI. 
[17:14] <rtg> apw, care to have a look at karmic LBM?
[17:14] <MTecknology> rtg: thanks
[17:15] <apw> rtg sure
[17:39] <Q-FUNK> smb: howdy! is there anything else I should test for the Geode bug?
[17:41] <smb> Q-FUNK, Hi there. As much I hate to say so, the last days have been busily filled with other work, so I never had much time to get back to that.
[17:44] <MTecknology> kernel freeze is tomorrow, isn't it?
[17:45] <Q-FUNK> smb: understood. please let me know if there's anything else I can do.
[17:45] <Q-FUNK> s/if/r/when
[17:47] <rtg> MTecknology, its effectively already frozen.
[17:47] <smoser> jjohansen, you re-run your kernel tests ?
[17:48] <smb> Q-FUNK, Sure will do. I'll put any updates into the bug
[17:48] <smoser> i do remember that we had some intermittent issues with kernel logs, but nothing since we attached chuck's patch that i was aware of.
[17:49] <Q-FUNK> smb: ok.  I'm just wondering how we're gonna manage to fix this on time for Karmic's release, though.  right now, the whole Geode product line no longer works on Ubuntu, which pretty much kills the investment that Canonical made into LTSP.
[17:50] <jjohansen> smoser: not yet, and I haven't seen any problems since chucks patch either until yesterday
[17:51] <smoser> bugger
[17:51] <smoser> do you happen to have available to you the region that they failed in ? you might wnant to try ther eagain
[17:54] <Darxus> This is why freezes should happen sooner and be more strict :)
[17:55] <smb> Q-FUNK, It is quite unlikely that this will happen in the Karmic release. The kernel freeze is tomorrow. We will have fix it in later updates.
[17:57] <Darxus> Wow.
[17:58] <Q-FUNK> smb: sad to hear.  
[18:00] <smb> Q-FUNK, Yes, I know
[18:01] <Q-FUNK> smb: espeically considering that support for older geodes already fell down a few kernel releases ago and the bug was not acted upon.
[18:01] <Darxus> Is LTSP still usable under hardy?
[18:01] <rtg> smb, have we broken something in the 386 flavour?
[18:02] <Q-FUNK> Darxus: yes and no.  support for Geode x86  CPU is currently broken, which essentially kills support for the most wide-spread CPU used in thin clients.
[18:03] <Darxus> Ah, Geode is a CPU, thanks :)
[18:04] <Darxus> I would be more comfortable with this if I felt it was less likely to happen on an LTS release, but I see kernel freeze wasn't any longer for Hardy.
[18:05] <Q-FUNK> Darxus: hardy was the release that broke if for older Geode variants, actually.  it's never been fixed.
[18:05] <Q-FUNK> now, karmic broke it for more recent Geode variants, which affects the OLPC as well.
[18:05] <Darxus> Wow.
[18:06] <smb> rtg, It is a one byte corruption in inodes early on boot, but as far as I can tell only on geode
[18:06] <Darxus> The ubuntu release process is weird :)
[18:06] <Q-FUNK> all this because upstream kernel developers cannot be bothered with answering bug reports.
[18:06] <Darxus> Q-FUNK: Ah, that sucks.
[18:06] <Darxus> Q-FUNK: Does it work in upstream?
[18:06] <Q-FUNK> meanwhile, smb does his best to pinpoint the source of the regression, but he has so much work on his hands that he's unlikely to figure out the solution on time for Karmic.
[18:07] <AlanBell> ooh, did someone say OLPC?
[18:07] <Q-FUNK> Darxus: as I already said, upstream is the one that broke it.
[18:07] <Darxus> Q-FUNK: Ah, okay.  I didn't catch that.
[18:07] <Q-FUNK> AlanBell: yup. OLPC support broken starting with Karmic, due to upstream regressions in kernel.
[18:08] <AlanBell> did it ever work? I didn't think the DCON drivers were in the Ubuntu kernel
[18:08] <Darxus> (I guess submitting an upstream bug report is sufficient implication that the problem was upstream.)
[18:08] <Q-FUNK> AlanBell: yes, they are in the standard kernel
[18:09] <AlanBell> at the moment mine never unfreezes the display after the open firmware bit
[18:09] <Q-FUNK> AlanBell: well, the problem is not DCON support as much as the fact that kernel 2.6.31 flat out won't boot on Geode LX.
[18:10] <AlanBell> oh, mine flashes the microphone light after 10 seconds or so which I thought was an indication it was doing some stuff
[18:10] <Q-FUNK> AlanBell: the kernel dies sometimes during the loading of the initramfs image.
[18:11] <AlanBell> isn't the viglen mpc-l a geode?
[18:11] <Q-FUNK> AlanBell: viglen products use either a geode GX or a geode LX, depending on which one you're talking about.
[18:13] <AlanBell> quite a few Ubuntu-UK people have the MPC-L. There was a special discount offer via the Ubuntu-uk podcast
[18:13] <Darxus> Do you think, for LTS releases, kernel freeze and final freeze should be doubled, to a month?
[18:14] <Daviey> AlanBell: *IS* still the offer L(
[18:14] <Daviey> :)
[18:14] <AlanBell> hi Daviey 
[18:14] <Daviey> \o
[18:15] <popey> pip pip
[18:16] <AlanBell> popey has an MPC-L
[18:16] <popey> or two
[18:16] <AlanBell> will they boot Karmic is the question
[18:17] <AlanBell> live CD should prove it one way or the other
[18:17] <popey> i dont have cd, i can try off a usb stick, if that helps
[18:17] <popey> or pxe
[18:18] <AlanBell> popey: is it a geode GX or a geode LX?
[18:18] <popey> http://popey.com/~alan/viglen/hardware.html says it's a GX2
[18:19] <AlanBell> ah, so that might work
[18:19] <AlanBell> apparently the kernel 2.6.31 flat out won't boot on Geode LX
[18:20] <smb> Q-FUNK, I just noticed in the latest dmesg, that there is a crashkernel line in the parameters. Has that been always enabled when you booted newer kernels? The original boot with 2.6.30 does not seem to have one. Maybe just desperate but ...
[18:20] <popey> bug 396286
[18:20] <ubot3`> Malone bug 396286 in linux "2.6.31-generic: kernel panic near the end of initramfs" [High,In progress] https://launchpad.net/bugs/396286
[18:21] <Q-FUNK> smb: I installed crashkernel recently.  actually, I think that was pulled by recent ubuntu-standard.
[18:23] <Darxus> Any objection to me adding "geode" to the title of that bug?
[18:24] <smb> Hm, then rather not. The bad pointers seem to start right after mounting the root fs. Before much else is done... :/
[18:33] <apw> popey, did you try the very latest kernel, there were a couple of allocation off by two bytes style bugs fixed in .46
[18:33] <popey> I haven't done any testing at all yet
[18:33] <popey> mine run hardy, I'm just here in case someone needs something confirmed/tested
[18:35] <Q-FUNK> Darxus: I just updated it now
[18:37] <smb> Q-FUNK, Also, as apw said, it might be at least worth a check with -14.46
[18:38] <AlanBell> anything I can do on the OLPC to confirm whether or not this is the bug I am stumped by?
[18:38] <Q-FUNK> smb: I check with every new kernel that pops up.  if any of them ever fixed anything, I'd report it. :)
[18:38] <apw> so you checked .46 today
[18:39] <Q-FUNK> AlanBell: yes.  boot with usplash disabled and snap a picture of what happens when it freezes.
[18:39] <apw> smb, it would be good to report the addy of the i_default_acl ptr in the debug next time
[18:39] <apw> so we can see if its one inode its reporting or 10 differnet ones
[18:39] <Darxus> Q-FUNK: Thanks.
[18:40] <apw> as you cannot get the name
[18:41] <Q-FUNK> apw: yup.that one crashes too.
[18:41] <smb> apw, Ok, I update the patch with that
[18:42] <apw> smb, as it occurs really early in boot, you could consider printing the addy of every inode too as they are added to dcache, with the file
[18:42] <apw> a
[18:42] <apw> and see if we get a name that way
[18:43] <apw> i guess that does assume we ahve some way to collect a long boot output
[18:43] <smb> apw, I already had the check whenever one was looked up, and that seems to happen rare to never
[18:44] <apw> smb, i see in the last one there are three bad ones at 83583s in ... so very late in the day
[18:45] <apw> smb, when you report it, are you releasing the inode then?  ie. its guarenteed to be a different one?
[18:45] <smb> apw, Yes this actually reverses the claim that it only happens early
[18:45] <smb> apw, Yep, the inode gets released just the call to release the acl struct is suppressed
[18:50] <jjohansen> smb: which bug# is this again?
[18:51] <dhillon-v10> ogasawara: hi, did you recieve my email
[18:51] <smb> jjohansen, bug 396286
[18:51] <ubot3`> Malone bug 396286 in linux "[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs" [High,In progress] https://launchpad.net/bugs/396286
[18:52] <AlanBell> Q-FUNK: I don't think the OLPC would do usplash as the kernel is loaded from open firmware rather than grub
[18:54] <AlanBell> I get an Open Firmware screen indicating it is loading the kernel then the ramdisk image into memory, then it should start the kernel and the kernel should start the DCON screen after it gets going. That never happens
[18:54] <ogasawara> dhillon-v10: I did, unfortunately haven't had time to dig into it
 that's okay, I know that you are very busy but its something interesting I can assure you that :)
[18:55] <superm1> apw, so re what happens with the half of the patch that's already applied, you aren't able to get wifi enabled still if you boot with it turned off
[18:55] <superm1> with my other half applied it works properly in either scenario
[18:56] <rtg> superm1, looking at it.
 I'll talk to you later bye
[19:19] <jjohansen> smb: what problem with AppArmor did you see with bug 396286, AA uses the inode in very limited ways so it would be good to know what exactly you were seeing
[19:19] <ubot3`> Malone bug 396286 in linux "[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs" [High,In progress] https://launchpad.net/bugs/396286
[19:20] <smb> jjohansen, None in the end. But I like to try to blame apparmor first
[19:20] <jjohansen> smb: ah, what made you think there were AA problems
[19:21] <smb> jjohansen, Just as the first messages came in one case after apparmor loaded profiles
[19:21] <jjohansen> hrmm, well that isn't any help for debugging this :(
[19:22] <smb> jjohansen, No especially after running with apparmor turned off and still getting the problem. So it is not the reason
[19:22] <jjohansen> smb: I was just hoping it would be another avenue of looking at the problem
[19:23] <jjohansen> smb: your and apw discussion failing to get the name peaked my curiousity
[19:23] <apw> we have an inode getting corrupted, specifically the i_default_acl gets mushed
[19:24] <apw> and we find out too late to find the name of the file as the dentry has gone
[19:24] <smb> jjohansen, I am about to update the patch. but unfort. at the time off seeing (inode destroy) the names are likely gone
[19:24] <apw> so was trying the inode num and device out the inode as they are likely there
[19:24] <jjohansen> smb: yeah that seems to be always the case
[19:25] <jjohansen> smb: is the address reliable enough to stick a hardware debug watch on it
[19:26] <smb> jjohansen, that is what we need to find out
[19:26]  * jjohansen will be interested to see the results
[19:27] <apw> sadly the aa off by two has been ruled out ... was hoping
[19:28] <jjohansen> haha, I guess smb wasn't joking when he said he wanted to blame AA first :)
[19:28] <apw> heh nope :)
[19:32] <jjohansen> thats alright, I do too.  The LSM is so invasive, that and AA used be mucking around with the vfs, so it was much more likely
[19:35] <Q-FUNK> jjohansen: except that I *did* try purging AA and it did not resolve the issue.
[19:37] <jjohansen> Q-FUNK: yeah, not saying it is the problem, just that it is a good first candidate to suspect
[19:37] <jjohansen> any LSM module really
[19:37] <Q-FUNK> jjohansen: smb indeed first thought about AA being the culprit, except that purging it didn't solve it.
[19:39] <jjohansen> Q-FUNK: yeah, though I was hoping he was actually seeing something in AA when it wasn't disabled as that might have been another avenue to debugging the problem
[19:39] <smb> Q-FUNK, I am right now compiling a new debug version, which I will upload as soon as it is done, just be prepared that it has received no boot testing and its later into a long day here... :-P
[19:40] <apw> superm1, this dell patch set seems to stop dell laptop loading completly for the mini10
[19:40] <Q-FUNK> smb: noted :)
[19:40] <superm1> apw, which is intended behavior
[19:40] <apw> it is loaded on my mini 10 now, is it doing nothing?
[19:40] <superm1> apw, it doesnt do anything there, you are supposed to use compal-laptop
[19:41] <superm1> apw, smbios 17,11 doesn't work on compal laptops made  this year or earlier
[19:41] <apw> superm1, hrm i have both loaded
[19:41] <superm1> apw, so you can try to run rfkill block on the dell-laptop rfkill interface for the mini 10, but it won't do anything useful.  if you run rfkill block for the compal-laptop interface, it will actually block
[19:42] <apw> superm1, well as it has wl poop in it i assume it actually won't ?
[19:42] <superm1> apw, actually it should still work with wl
[19:42] <apw> wild /me tries
[19:43] <apw> superm1, so it does ... amazing
[19:44] <superm1> apw, yeah that's some stuff i wrote into compal-laptop earlier this cycle
[19:44] <apw> shame its not connected to the wireless button on the keyboard still
[19:44] <superm1> apw, yeah still have a problem that FN-F2 is spitting out what looks like the wrong keycode though
[19:44] <superm1> once can figure out why the kernel thinks that FN-F2 is the same as XF86AudioNext, then that part can be fixed
[19:45] <superm1> it's more troublesome for the 11z which actually does have an XF86AudioNext key too
[19:46] <apw> heh
[20:51] <sconklin> apw and rtg, I'm looking at changing the CONFIG_VERSION_SIGNATURE setting for netbok-lpia, I'm not sure how the files in debian/rules.d get included. What's different for the case of "fdr binary-custom"? 
[20:53] <rtg> sconklin, the rules files get included in debian.master/rules (or whatever the topic branch name is). This must be for Hardy still?
[20:53] <rtg> did we convert Hardy to the abstracted build yet?
[20:53] <sconklin> rtg: oh yeah, sorry. I'm stuck in the past :)
[20:55] <sconklin> there's a sed string substitution done by 2-binary-arch.mk that's not happening in the lpis case for the binary-custom target
[20:55] <sconklin> er lpia
[20:55] <rtg> sconklin, custom binaries were handled in special places. it'll take me a bit to remember
[20:56] <rtg> sconklin, look in 6-binary-custom.mk
[20:56] <apw> yea
[20:57] <rtg> but why is the netbook branch building  a custom binary? that was for xen, etc
[20:57] <sconklin> rtg: I don't know, I inherited it
[20:58] <apw> rtg it was always a custom-binary lpia, and i just moved the patches to the branch and made them null in the custom bit
[20:58] <apw> probabally should have been converted ... but
[20:58] <rtg> apw, oh, its all rushing back. ick!
[20:59] <apw> i know... stem that memory tide you will hurt self
[20:59] <sconklin> there be dragons here
[20:59] <rtg> apw, if folks are to continue building lpia in the netbook branch, we should normalize it with master.
[20:59] <rtg> sconklin, anyway,  6-binary-custom.mk is where the majik happens
[20:59] <sconklin> rtg ok thanks
[21:01] <sconklin> oh yeah, custom-prepare- instead of prepare-
[21:44] <SyL> I'm getting hard freezes about 2 minutes after booting like clockwork when it boots normally. it works find when I boot into the rescue mode. can someone tell me what is the differences?
[21:47] <Darxus> SyL: What do you select when rescue mode asks how you want to procede?
[21:49] <SyL> Darxus: when grub boots (hitting escape) I see the menu to select the kernel I want. the rescue mode is from that. 
[21:49] <Darxus> SyL: Right, then it asks you if you want to drop to a root shell or something, right?
[21:49] <SyL> once I'm there I do the "drop to root" item and when I select that, it asks for root password and it works
[21:50] <Darxus> Heh, yeah, there's a bunch of other stuff that runs normally.  Pretty much everything.
[21:50] <Darxus> SyL: I think your best chance of debugging is the kernel debugger.
[21:50] <Darxus> Assuming you're not getting anything in logs, like /var/log/syslog
[21:51] <SyL> Darxus: I have an identical box which is running 2.6.28-* fine. 
[21:51] <SyL> Darxus: yeah, there is nothing in messages, kern, syslog, etc. 
[21:51] <SyL> just freese and I have to reboot again
[21:51] <Darxus> SyL: So you have a bad bug in the current kernal, and the way to figure out what's going on is the kernel debugger.
[21:52] <rtg> superm1, you around? looking at your rfkill patch.
[21:52] <SyL> but it almost happens after a minute and 30 seconds
[21:52] <SyL> Darxus: and how do I select that? 
[21:52] <Darxus> SyL: Report a bug with the command "debian-bugs linux"
[21:52] <superm1> rtg, sure, what's up?
[21:53] <rtg> superm1, how does the dell-laptop driver get notified when the physical rfkill switch changes?
[21:53] <superm1> rtg, input interface, that was mjg59's first patch
[21:53] <Darxus> SyL: I don't know, it might not be packaged.  If it's not packaged it probably means patching and recompiling the kernel, which is not something the average user is expected to do.  File the bug.
[21:53] <superm1> rtg, dell_rfkill_update gets called when the keypress arrives over the input interface
[21:54] <rtg> superm1, but the key code event isn't sufficient to tell you the state of the switch, is it?
[21:54] <rtg> dell_rfkill_update() simple tioggle the existing state
[21:54] <superm1> rtg, unfortunately not.  it's just XF86WLAN.  so you need to keep track of the state in the driver
[21:54] <superm1> exactly
[21:54] <rtg> simply toggles*
[21:55] <rtg> so, if you boot with rfkill enabled it detects the state of the kill switch, then depends on key codes thereafter?
[21:55] <superm1> Yup
[21:55] <superm1> by doing it this way you don't lose soft kills that were manually set either
[21:56] <rtg> ok, I get it. I've added a couple of comments, but have left the code intact.
[21:57] <superm1> sounds good.  whenever mjg59 has his new i8042 stuff ready, i'll rework this on top of that too
[22:04] <SyL> Darxus: ok, so I'm SOL until it's fixed. gotcha
[22:04] <SyL> Darxus: thanks
[22:08] <Darxus> SyL: It won't get fixed if you don't submit a bug.
[22:09] <Darxus> SyL: Also, if you submit a bug, people who know a *lot* more than me about the ubuntu kernels will see it.
[22:09] <SyL> Darxus: I am submitting a bug. I don't seem to have debian-bugs command, which package is that in? 
[22:09] <Darxus> ubuntu-bugs, sorry.  Did I say debian?
[22:09] <SyL> Darxus: that makes more sense, thanks. =) 
[22:11] <SyL> Darxus: what package is ubuntu-bugs in? 
[22:11] <Darxus> apport?
[22:12] <Darxus> Yes.
[22:12] <Darxus> Ah, ubuntu-bug, not plural.
[22:14] <SyL> Darxus: that was it, thanks. 
[22:15] <SyL> Darxus: one last thing. is there a way to force grub to force you to pick a kernel? 
[22:22] <Darxus> SyL: Probably.
[22:22] <Darxus> SyL: Probably by setting the timeout to unlimited.
[22:24] <Darxus> SyL: http://www.gnu.org/software/grub/manual/html_node/Configuration.html#Configuration
[22:24] <Darxus> SyL: Set timeout to something big.