/srv/irclogs.ubuntu.com/2009/03/11/#ubuntu-kernel.txt

Maahesare there known issues with kernel 2.6.27-13 generic and all versions of the Nvidia binary drivers?02:47
Maahesbecause I am getting....beyond bad issues with all versions thereof. like binary information being written out on config files02:48
Maahesinterspersed with strings in german, for some reason02:48
Maahesin any event, so far as I can tell 2.6.27-13 is broken for Nvidia binaries 177.82-0ubuntu0.1 and 173.14.12-1-0ubuntu5.102:54
Maaheswhether installed via envyng or restricted manager02:54
* Maahes decides to revert to 2.6.27-12 for awhile02:55
purentropyWHen I try to boot from the live CD my system HANGS at [ 97.125547] ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15  06:07
purentropynever gets to the desktop06:07
purentropyi can't run any terminal commands because i never get to the livecd desktop.  Can anyone make any sense of this message?06:07
purentropyI have Nvidia Nforce 630i chipset.  WDC 500GB SATA HDD.  Using 8.10 LiveCD. No externals plugged in besides monitor,keyboard,mouse,ethernet06:10
n2diypurentropy: ask the whole question in #ubuntu, the Nvidia stuff is important, and not kernel related.06:13
davmor2Guys I just completed a 64bit Ubuntu install from netboot mini.iso and am greeted with a nice little window that says....  Kerneloops-ui  Your system had a kernel failure09:51
=== mdz_ is now known as mdz
davmor2What logs do you need is it just /var/log/kern.log?10:09
davmor2I'm having to carry on testing so I've put logs here:  http://www.davmor2.co.uk/kern.log  http://www.davmor2.co.uk/debug.log  http://www.davmor2.co.uk/dmesg.log10:25
smb_tp_davmor2, I am at a loss about what kerneloops is complaining. There is nothing apparent in the log files...10:40
davmor2smb_tp_: No idea either.  I finished the install rebooted and was greeted by 2 kerneloops windows one behind the other.  I'm doing a kubuntu install so I'll check if it happens again10:42
smb_tp_davmor2, ok. I'll peek at the package in the meantime10:43
davmor2smb_tp_: It wouldn't be because it is a netboot install and part that it wanted was missing could it?10:44
davmor2if so I'll have a look in the installer folder and see if there is a kern.log in there too which might help10:44
smb_tp_I wouldn't rule out this at the moment since I am not sure what it looks for exactly. At least it sounds unlikely that it found something in the dmesg10:45
smb_tp_Except it take the WARNINGs as something bad, which would be bad10:45
davmor2it only affects 64bit to 32 bit worked fine10:47
smb_tp_davmor2, The ui is IIRC triggered by a file being  in /var/crash... Maybe that has some info10:47
davmor2smb_tp_: if I get it again in kubuntu (which I'm guessing I should)  I'll have a look and see if there is anything in there for you10:48
smb_tp_ok10:48
iahello. maybe it's wrong place for this question, but i don't know, where else i can ask about it. I use jaunty with latest updates at 2.6.28-9.29 kernel. during boot i get a few (~10) messages with modprobe usage text and when gnome starts, it shows warning that kernel can't use cpu frequency scaling. at 8.27 and earlier everything was fine. I just intresting to know, does anybody else have the same strange issue?12:47
davmor2smb_tp_: Can't reproduce at the moment might just of been an install issue If it does come back up I'll post any crash logs too :)12:57
smb_tp_davmor2, Ok, sure. Lets see12:59
wmatia: ensure you're system has the latest BIOS13:02
wmatia: then review the Launchpad bugs for fpu frequency scaling as there's been a few13:03
wmatia: s/fpu/cpu13:04
sconklin have we ever considered pulling the upstream video4linux directly into a distro? The reason I ask is that there's a good bit of device enablement in the delta between what we have in jaunty and what's upstream in v4l15:14
smb_tp_I do not remember this being discussed before...15:16
smb_tp_But I could think this increases the burden when syncing. rtg knows the pain for wireless15:17
sconklinI'm looking at a patch now that fixes an open bug, but it's against upstream. Still not too hard to backport, but I wondered whether it was worth the risk to take the whole pile. I think I'd be willing to serve as the go-between for our kernels. I think it's too late for Jaunty in any case.15:22
rtgsmb_tp_: it all depends on how often we sync. we could think about it for Karmic.15:23
sconklinLike wireless, it would take someone following upstream, syncing bugs, etc.15:23
rtgsconklin: sprint topic?15:24
sconklinrtg: sure, if there are any open slots. I'd be happy to moderate15:24
* smb_tp_ nods15:24
rtgsconklin: surely we could find an hour out of 3 days to chat about it15:24
sconklinok, I'll ask pgraner to schedule it is he can. If he can't I'll just be opportunistic about bringing it up15:25
sconklinif he can15:25
rtgKeybuk: Re: [PATCH 29/31] esp: Auto-load esp module when device opened. Alan Cox says "NAK - the default esp behaviour is to do unsafe ISA probes to find the ports. We don't want it autoloading therefore.". I tend to agree with him when it comes to ISA probing.16:04
Keybuksure16:04
Keybukin fact, I'm of the opinion that all of these patches should be dropped for the next ubuntu kernel if they haven't been merged upstream16:04
Keybukthus I realise they shouldn't have been "SAUCE"16:05
Keybukthe whole sauce non-sauce thing confuses me a little ;)16:05
Keybukthe important thing is that we had an alias to auto-load that driver16:05
Keybukwe turned it into the kernel patch16:05
Keybukand someone upstream said it was wrong16:05
Keybukwhich means our alias was wrong too16:05
Keybukso it's fine for both to go :p16:05
rtgKeybuk: OK, I'll revert at least the esp patch.16:08
KeybukI'd probably wait until karmic, unless you feel a pressing need16:09
Keybuksimply on the basis that there may be people who've been testing jaunty so far and relying on it working16:09
Keybukit's less rude to break such things at the start of a release16:09
rtgKeybuk: that patch has only existed for the last couple of uploads. Probing of ISA ports is a bad thing.16:09
Keybukright, but we had a modprobe.d alias before16:10
Keybukwhich had the exact same effect16:10
rtgso, you're saying its always been loaded automagically?16:10
Keybukright16:27
KeybukI'm quite happy to drop that on Alan's word that it shouldn't be16:27
=== zul_ is now known as zul
Keybukbut wishy-washily-vaguely leaning towards doing that drop when we rebase for karmic rather than right before jaunty beta :p16:27
* JanC wonders why an extra-sensory-perception module has to do isa-probing :P16:47
cjhmm?  esp?  isa?  are you talking about ipsec?17:08
anubhav cj: ithink its http://lxr.linux.no/linux+v2.6.28.4/drivers/char/esp.c17:10
cjah, not Encapsulated Security Payload / Internet Security and Acceleration17:13
anubhavjohanbr: did the "up_threshold" param solve your issue?17:35
johanbranubhav: I've been pretty busy so I haven't actually tried it yet. But I'll keep it in mind next time I compile something.17:36
anubhavjohanbr: oh okay :)17:37
porq69hi17:43
=== JanC_ is now known as JanC
LureI am using https://wiki.ubuntu.com/KernelBugFixing to try one upstream fix, but the build in PPA fails with ABI error20:37
Lurehttp://launchpadlibrarian.net/23761073/buildlog_ubuntu-jaunty-lpia.linux_2.6.28-9.29~lure~lp285834_FAILEDTOBUILD.txt.gz20:37
Lureis something missing regarding ABI in the wiki page?20:38
TheMusoLure: You need to fetch the abi files for a previous kernel if there were any, otherwise you need to disable ABI checking.20:40
TheMusoI'm guessing this is the first kernel you are building, so disabling the abi check is probably the best option.20:41
TheMusoif its your ppa only20:41
LureTheMuso: how can I disable ABI check in package?20:47
TheMusoLure: probably the easiest way is to add something like "skipabi = true" and "skipmodule = true" to the top of debian/rules.d/0-common-vars.mk20:48
TheMusoactually, add those two lines exactly to the top of that file, and things should be ok.20:48
LureTheMuso: thanks - will try now20:48
LureTheMuso: you are audio guy, right?20:49
TheMusoLure: yes20:49
LureTheMuso: can you comment how likely is to get quirk fix from sound-2.6.git into Jaunty - I am talking about bug 28583420:50
ubot3Malone bug 285834 in alsa-driver "Audio out on x200/x200s dockingstation doesn't work" [Undecided,New] https://launchpad.net/bugs/28583420:50
LureI plan to test it first and hopefully it will work for me and other reporters...20:50
* TheMuso checks to see whether the commit needed is in 2.6.2920:50
TheMusoLure: it is not in 2.6.29 yet, and I don't think rtg et al like pulling commits from anywhere else but upstream, and its a rather big diff, so I am not sure if the kernel team would be comfortable merging it.20:53
TheMusoUpstream here being Linus' tree.20:53
LureTheMuso: ok, will check back only if we have positive testing reports20:54
Lureotherwise I may maintain custom kernel in ppa20:55
LureTheMuso: thanks a lot for you help20:55
TheMusoLure: np20:55
rtgTheMuso: I just replied to email about missing commits21:01
rtgto your email21:02
TheMusortg: right21:04
dandel><; any ideas on where i can get generic 2.6.25 and 2.6.26 series of mainline in binary?21:13
rtgdandel: I tarted a mainline build for 2.6.25, watch the kernel team mailling list for completion21:19
rtgstarted*21:19
dandelRTG, that's good to know... i'll be looking for it then.22:20

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