/srv/irclogs.ubuntu.com/2005/11/28/#ubuntu-kernel.txt

BenCand it uses rdtsc(), so it's x86 only12:04
BenCmjg59: any idea what a good portable replacement is for rdtsc()?12:04
BenCand when it says "work with current 802.11 stack", it means that in the loosest way12:05
BenCit's still using local ieee80211 headers, and abusing the real stack12:05
mjg59BenC: What fun12:06
BenCI'm not sure about including it...my biggest fear is that I'll become so frustrated with it that I'll end up getting an 8180 card and rewrite the whole driver12:07
mjg59What's it actually using rdtsc for?12:07
mjg59Ha12:07
BenCmjg59: filling in some hosttime in a struct12:07
mjg59Does it look important, or does it just need a monotonic timer?12:08
BenCmjg59: don't laugh, that's how I ended up taking over the ieee1394 stack :)12:08
=== rtcm_ [n=jman@81.84.150.197] has joined #ubuntu-kernel
mjg59Oh dear12:08
BenCit's something to do with a prism header12:08
mjg59Nngh.12:09
mjg59BenC: It only seems to be for monitor mode12:10
mjg59BenC: Other code just seems to use jiffies12:14
BenCit has it commented out to use jiffies near the top of that function12:14
BenCguess I'll do that aswell12:14
mjg59I'd just go back to that, TBH12:14
mjg59It seems to be a fairly standard 802.11 thing12:14
BenCwait, that's mac_time12:15
BenCoh well, I can use it still12:15
mjg59If you dig for hosttime in drivers/net/wireless, there's no shortage of hits12:16
BenCsweet03:39
=== BenC discovers git-bisect
BenCthat is the most awesome tool and makes git totally worth using, even if it was the crappiest scm in the world03:39
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel
=== _native_ [n=alpha@cpe-66-87-4-181.ut.sprintbbd.net] has joined #ubuntu-kernel
=== _native_ [n=alpha@cpe-66-87-4-181.ut.sprintbbd.net] has left #ubuntu-kernel ["cabal]
Earthpigbenc: would be nice if it could be automated.07:52
=== chmj [n=chmj@wbs-146-184-221.telkomadsl.co.za] has joined #ubuntu-kernel
=== CataEnry [n=cataenry@host204-30.pool8248.interbusiness.it] has joined #ubuntu-kernel
CataEnryhi all11:58
CataEnrycya12:17
=== michel [n=michel@zux006-048-229.adsl.green.ch] has joined #ubuntu-kernel
micheli want to patch ltsp-kernel of ubuntu, howto? 12:23
=== jane_ [n=JaneW@wbs-146-151-44.telkomadsl.co.za] has joined #ubuntu-kernel
=== Alhica [n=Torresm@a81-84-252-5.cpe.netcabo.pt] has joined #ubuntu-kernel
=== Alhica [n=Torresm@a81-84-252-5.cpe.netcabo.pt] has left #ubuntu-kernel []
fabbioneBenC: is it possible to do firewire back to back?01:50
fabbionebetween 2 controllers i mean01:51
fabbioneif so do i need a special cable or something?01:51
=== chmj_ [n=chmj@wbs-146-161-75.telkomadsl.co.za] has joined #ubuntu-kernel
=== CataEnry [n=cataenry@host204-30.pool8248.interbusiness.it] has joined #ubuntu-kernel
CataEnryhi all01:57
BenCfabbione: yeah01:58
BenCjust a normal cable01:58
BenCthink of firewire as a network where any device with more than one port is like a hub :)01:59
BenCI've had a winxp, macosx, 2 linux boxes, 3 firewire storage devices, firewire camera, all connected on a bus together02:00
BenCusing IPover1394 between the winxp/macosx/linux boxes too02:00
fabbioneah cool02:00
fabbioneok02:00
fabbionei only have 2 boxes02:00
fabbionenothing fancy02:00
fabbionecurious to try it02:01
fabbioneprobably more02:01
fabbionehow fast can it go?02:01
infinity~400 Mbps, in theory.02:02
fabbionethat would be a cheap way to upgrade my 100Mb LAN to a ~ 400Mb02:02
fabbioneor buy a gigabit switch02:02
jbaileyfabbione: Do you actually have any disks that can push data that fast?02:02
fabbionebut the latter is hutterly expensive02:02
fabbionejbailey: yes02:03
jbaileyHandy. =)02:03
BenCfabbione: the linux IPover1394 isn't all that stable02:03
fabbioneBenC: well.. it's a good way to push you to fix it :P02:03
BenCfabbione: not my driver :P02:03
fabbionestill your kernel ;)02:04
BenCI just did the initial ethernet-over-1394, the RFC stuff came from someone else02:04
BenCthe ethernet-over-1394 was really stable, since it was just a firewire packet wrapped around a normal ethernet packet02:04
BenCbut it was linux-only02:04
fabbioneyeah  i could guess so02:05
fabbionei guess i will switch to GigaEthernet02:05
fabbionebuild a 1394 network as backup02:05
fabbioneand use the 100Mb for management02:05
fabbioneor something like that02:05
BenCget some S800 firewire cards, and you'll almost be gigabit :)02:05
fabbioneBenC: i have the cards.. i need the switch02:06
fabbioneand a good switch is $$$02:06
kikohey there02:06
kikoquick question02:06
BenChey kiko02:06
kikowhat's the difference between linux-image-2.6.10-6-686-smp and linux-image-2.6.10-5-686-smp?02:07
BenCkiko: about 4 revisions :)02:07
fabbioneAHAHAHHAHA02:07
kikoreally?02:08
BenCkiko: you'll need to be more specific than -6 and -5, since it could be -5.10 and -6.9902:08
kikooh. those are just the package names02:08
BenCkiko: the functional difference is from -5 to -6, the kernel ABI changes02:08
kikoii  linux-image-2.6.10-5-686-smp                 2.6.10-34.702:08
kikothat's what we have installed02:09
BenCoh, I don't know how the revisions worked back then, I only know the current convention for breezy/dapper02:09
kikohum hum02:10
BenCBisecting: 2 revisions left to test after this02:10
=== BenC loves git-bisect
Earthpigdo you have vmware?02:11
BenCyes, but not installed right now02:12
Earthpigwe use vmware 5's snapshots for that kind of iteration testing. 'tis wonderful.02:12
fabbioneBenC: it's the same convention02:13
fabbionekiko: it's an ABI change02:13
fabbioneyou install the new one.. boot in the new one.. you are done02:13
BenCfabbione: I know the ABI bump is, but the 34.7 thing isn't :)02:13
fabbioneoh right02:13
fabbioneyes02:13
fabbionewe did add the ABI number to the debian version only in breezy02:13
BenCEarthpig: for testing kernel regressions?02:13
fabbionethe old pkgs have standard numbers02:13
kikofabbione, should I be using the newer kernel or does it not really matter?02:14
kikoby newer kernel I mean newer-ABI-kernel02:14
fabbionekiko: well it's a security update that covers no less than 10 vulnerabilities02:14
fabbionekiko: it's up to you02:14
fabbionei suggest to use the new one02:14
kikooh02:14
kikoso the -5 kernel was not updated?02:14
kikoah. I think I understand the problem02:15
kikoI shouldn't have installed the -X kernel explicitly, right?02:15
Earthpigbenc: well, we don't do kernels, so no. :)02:15
BenCkiko: the security update forced a bump to -602:15
kikoI see02:15
kikothat's okay02:15
kikoso it won't automatically update?02:15
kiko(i.e. JRU does an apt-get update apt-get dist-upgrade and no new kernel)02:15
BenCnot unless you have linux-image-686-smp installed02:15
BenCthe meta-packages should pull in the upgrades02:15
kikoyeah, that's what I should have.02:15
BenCwhich is the default02:16
Earthpigbenc: we do use it for automated testing of nightlies though.02:16
BenCEarthpig: cool02:16
BenCfabbione: I think -4.4 is going to go out today02:16
BenCafter which I will attempt to get l-r-m built against 2.6.15, and then go for linux-meta02:17
infinityBenC : Please don't.02:17
infinityBenC : l-r-m will be unuseably broken as soon as the new X finally builds (which will happen in the next day, it looks like), so I need to do more than just "make it build" anyway.02:17
BenCinfinity: when's your next planned upload of l-r-m?02:17
fabbioneBenC: ok.. but it's pointless to upload until the gcj thing is sorted02:18
fabbioneBenC: basically all the archive is unbuildable atm02:18
=== BenC sighs
fabbioneBenC: plus infinity loves to spank l-r-m :)02:18
infinityBenC : I'll make l-r-m a priority tomorrow, since I expect to see X build tonight.02:18
BenCyou people enjoy dashing my hopes don't you? :)02:18
BenCinfinity: ok, I'll leave it alone, and just get linux-meta ready for when things settle down02:19
infinityI'd like to see CDs built with shiny new kernels too, so I'm on your side.  Don't worry. :)02:20
infinitySpeaking of CDs, I really need to test that 640x400 vga16fb patch and get you to include it ASAP.02:20
fabbioneBenC: Kamion wants to coordinate with you some udeb reorganization stuff02:20
infinityCertainly before we do the next flight CD anyway.02:21
BenCfabbione: yeah, I'm in #ubuntu-boot, but so far, I don't know what coordination I need to do02:22
BenCI was under the impression that once I got the kernel uploaded, the rest was on him :)02:22
fabbioneBenC: basically Kamion wants to revert a few changes in the amount of udebs we do build02:22
fabbioneBenC: yeah well.. he might need your help to setup git and stuff02:22
BenCinfinity: yeah, I can test that on atleast one system where I know vga16 has always been broken02:22
fabbionehe knows what needs to touch02:22
infinityBenC : Note that Kamion/Keybuk would really rather not see linux-meta updated until we're sure the udev stuff is sorted.02:22
infinityBenC : You have such a system?... ROCK THE FUCK ON.  I've been resigned to doing this blind until now. :)02:23
BenCinfinity: it's an ATI card connected to a TV via svideo, so it's not the normal brokeness, but it is broken02:23
BenCI've been using vesa happily02:23
BenCfabbione: ok02:24
fabbionetranslating infinity to a more common language: "Dear Ben, given your card is broken, you win! FIX IT! kthxbye!"02:24
BenClol02:25
infinityBenC : Hrm, not sure if this fix will fix your case, but bonus if it does.02:25
BenCinfinity: I have a couple of vgacon "fixes" from -mm that I want to test too...not going into our kernel yet, but I'll let you know02:26
BenCrather wait for your patch before I touch vgacon at all02:27
BenChrmm...not sure if I need to mark that last boot as git-bisect bad, or good02:27
BenCit booted way past where it normally crashed, but it got a segv in the initrd, and couldn't mount the rootdev02:28
infinityBenC : My patch should just be touching the size/timings struct, if you're mucking with stuff outside that, we won't conflict.02:29
infinityBenC : I just need to pick the "right" timings, and test the fuck out of them before I go blowing up people's hardware.02:29
=== rtcm [n=jman@81.84.150.197] has joined #ubuntu-kernel
=== sivang [i=sivan@ubuntu/member/sivang] has joined #ubuntu-kernel
sivangBenC: Hey Ben, 'sup? I installed 2.6.15 and am now getting "BUG: Soft lockup on CPU#0"02:48
sivangBenC: anything I can help to sovle this, or do more testing for you?02:48
BenCsivang: backtrace or oops of any kind?02:49
sivangBenC: if logs were not rotated, I should be able to give those . let's see02:49
sivangBenC: re: oops, machine can't boot past it. not even in "rescue" mode02:51
sivangBenC: can't seem to find it in the syslog, where else should I be looking?02:53
BenCdmesg02:53
BenCwhen it happens, does the machine lockup?02:53
=== CataEnry [n=cataenry@host204-30.pool8248.interbusiness.it] has joined #ubuntu-kernel
sivangBenC: yes sir :)02:53
CataEnryre02:54
=== spike [n=spike@unaffiliated/spike] has joined #ubuntu-kernel
spikehi there03:01
BenCsivang: does Alt+SysRQ work?03:03
spikeI was trying to get myself acquainted with dapper and thinking of kernel specs for dapper and ubuntu-server03:03
spikeis selinux/grsec integration planned?03:04
spikeand what about ELSA/CSA patches?03:04
spikeor this sort of questions are welcome here?03:04
spikearent*03:05
sivangBenC: I will have to try. also, I can't seem to find the dmesg logs for that hangup03:07
sivangBenC: any tips on that?03:07
sivangBenC: (this all mean boot cycles for me)03:07
BenCsivang: if it was a lockup, it wont be there03:08
BenCyou'll need to do a alt+sysrq, and either hand write the trace, or take a photo of it and email that too me03:08
sivangBenC: ok, I will give it a try.03:09
sivangI'll be bak ;-)03:09
sivangBenC: now it locked up, on the corrupted USPlash screen , Alt+SysRq does nothing03:32
infinitysivang : If you boot without "splash" you can avoid usplash.03:33
infinitysivang : You might at least get some better debugging output then.03:33
infinitysivang : And take away "quiet" from the command line too, if you want a bit more verbosity about where it might be dying.03:34
sivanginfinity: eh right, dumb me, not like I don't know that. (I used to do that when bootsplash just entered, since I am used to see text messages and bootsplash was bit uncomfortable.03:34
sivanginfinity: anyway, yet-another-boot-cycle03:34
sivangok, couldn't see the "Soft lock" anymore03:41
sivangbut I did see where it halted, again SysRq helped me none03:42
sivang[17179589.808000]  Intel ISA PCIC probe: not found. Before that I got "* /etc/network/options is deprecated"03:43
=== rtcm_ [n=jman@81.84.150.197] has joined #ubuntu-kernel
=== JaneW [n=JaneW@wbs-146-151-44.telkomadsl.co.za] has joined #ubuntu-kernel
sivangBenC: any idea?03:57
BenCdid alt+sysrq work?03:57
BenCok, I see, no03:57
CataEnrybrb04:06
BenCsivang: I'm at a loss, try booting with "noapic", "nolapic", etc, to see if that changes anything04:08
=== CataEnry [n=Enrico@host204-30.pool8248.interbusiness.it] has joined #ubuntu-kernel
sivangBenC: ok, will do. Why isn't anything on the kernel that will open and close a log file in an atomic manner, that way if something wrong happens, we would always be able to see the logs?04:10
BenCsivang: at that point, the system dies, and likely is so trahed that opening a file would be disastrous04:12
sivangBenC: I see. What about doing that before it dies, or is there no possible sane way to know that before it acutally dies ? :)04:18
BenCit could die before even being able to access the disk04:19
sivangah right04:19
sivangdarn04:19
sivangoh well, I will try again in a sec04:19
sivangBenC: btw, what nolapic does?04:20
BenCNo Local APIC04:20
sivangk, thx04:20
BenCwhich kernel are you using anyway, -386, -686, -k7?04:20
sivangBenC: 686, the smp and UP enabled 04:22
BenCtry doing "smp2up=off" aswell then04:22
sivang/boot/vmlinuz-2.6.15-3-68604:22
sivangand that tells it to?04:23
BenCare you on an SMP machine?04:23
sivangyes04:24
BenCthen it wont do anything, so don't worry about it :)04:24
sivangBenC: there a way to know for sure if you're on an SMP machine if you're currently booted with a non smp kernel?04:27
BenCcat /proc/cpuinfo should list total cpu's04:29
Mithrandirit doesn't if you don't have an SMP kernel, iirc04:30
Mithrandiryup, verified on the live cd.04:31
Mithrandirdoesn't tell me about my second core, just my first one04:31
Mithrandir(amd64)04:31
BenCprobably doesn't parse core's, but it should parse cpu's04:32
BenCncpus_probes should atleast04:32
BenCif not, it will be fixed in 2.6.15, since there were some patches for that04:32
MithrandirI don't have a real SMP machine here, so I can't test, but I've seen it not list all the CPUs listed before, at least.04:33
sivangMithrandir: I have a non real SMP machine, and when using an SMP kernel I always see two CPUs05:00
=== chuck_ [n=chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel
chuck_heylo05:07
=== chuck_ is now known as zul
mjg59BenC: It looks like the bcm430x people are moving to using much the same 80211 code as the rtl8180 people06:02
mjg59So with luck we'll have one softmac core for all of them06:03
=== siretart [i=siretart@ubuntu/member/siretart] has joined #ubuntu-kernel
siretartBenC: I noticed that iptables in breezy as well as in dapper there are some iptables modules missing, which are in debian's iptable06:09
siretartBenC: I filed therefore bugzilla #1997806:10
siretartBenC: the most notably difference to debian is that debian uses an own copy of kernel headers. Do you have an idea how to fix this?06:11
BenCsiretart: doesn't sound like something I can fix from the kernel side07:04
BenCeverything in the kernel is enabled07:04
BenCmjg59: I have a softmac patch in -4.4 that came from the bcm430x ftp site07:05
siretartBenC: well, I suspected that iptables source isn't too happy with the headers the kernel does currently provide07:05
siretartbecause the kernel headers are the only difference07:05
BenCsiretart: is that something that needs to change in the kernel, or just that iptables will need a hacked up copy of the headers for it's own build?07:06
dilingerheh07:06
dilingerone of my coworkers rebooted their hoary machine today.  i totally forgot about the ABINAME bump07:06
dilingerneedless to say, openafs didn't work all that well for them, as there was no openafs module compiled for the new kernel07:06
siretartBenC: debian seems to ship with a hacked up copy of the headers. fabbione changed the iptables package to use the kernel headers instead07:09
BenCprobably a good reason for that then07:10
BenCbut you'd have to ask him about what that reason was :)07:10
BenCsounds to me like this is all squarely on the iptables package, so it's probably best to submit it as a bug against that package07:10
siretartwell, there seems to be no direct maintainer, so I wanted to try to fix it07:11
BenCsure, if you fix it, then you can attach a patch to the bug report07:12
BenCyou can assign it to fabbione since he touched the source, and probably get an explanation from him about it07:13
BenCor you can do the upload yourself, but I suggest atleast talking to fabbione first to find out why he switched it07:14
siretartI uploaded a merged iptables package today which didn't FTBFS ;)07:16
siretartI consider this as an improvement :)07:17
lamont-awaysiretart: an old working version and a new ftbfs version is a completely different situation than a new compiled-but-non-working version07:26
lamont-awaysince in the first case, apt-get dist-upgrade doesn't trash a working system07:26
siretartlamont-away: yeah, right07:29
siretartlamont-away: but a quick testrun showed my that iptables seems to be functional (I can look at my tables)07:30
lamont-awaycool07:33
siretartbut my original problem stands: There is no /lib/iptables/libipt_recent.so being built anymore. the new version from debian didn't bring any change07:34
BenCwhat are the criteria for the package building that module?07:40
BenCdo you see any reference to it in the sources?07:40
BenCalso, is it possible that regardless of the kernel headers, it is checking uname and seeing that maybe the kernel doesn't support an obsolete interface?07:41
=== siretart rechecks
CataEnrybye all07:54
siretartsomething is strange with linux-kernel-headers07:56
BenClinux-kernels-headers is an oddity by design07:56
siretartsomehow all extensions of iptables get disabled when using linux-kernel-headers07:57
siretartperhaps thats the reason why iptables ships its own kernel headers07:58
siretartthe problem is that the package FTBFS with that headers on ubuntu.. hmmm07:58
BenCsiretart: iptables is probably one of those evil programs that defines __KERNEL__ when building userspace so it can get to some kernel internals07:59
BenCas such, linux-kernel-headers wont satisfy what it needs07:59
=== zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-kernel
kikoiptables again08:01
kikosign08:01
siretartI have an idea, let me try something..08:02
infinityiptables does Very Bad Things, yes.08:03
siretartI think I got it08:04
siretartdebian rules sets KERNEL_DIR to /usr/include, it has to be just '/usr' instead08:04
siretartinterstingly, iptables seems to need the kernel includes only for some extensions, not for all, and not for itself..08:05
siretartBenC: are you okay that I upload a package with just corrected KERNEL_DIR? quick check shows iptables works, even with '-m match' parameter08:06
BenCwhat do you mean "corrected KERNEL_DIR"?08:07
siretartBenC: http://paste.ubuntulinux.nl/492408:08
siretartthats the debdiff08:08
BenClooks good to me08:10
siretartok. uploading08:10
siretartthis patch should imo go to breezy-updates, too08:11
siretartbecause in breezy, there are no iptable extension modules atm08:12
jbaileyBenC: Yes, our lkh is designed to make those programs suck with low amounts of sympathy given.08:27
siretartwell, iptables builds nicely with lkh08:27
BenCsiretart: then iptables gets a gold star :)08:31
siretart:)08:31
sivangsiretart: lkh are so hard to compile with for something that depends on the kernel?08:32
siretartsivang: I didn't touch lkh at all08:33
zulaieeeeeeee08:49
sivangBenC: ok, I have some leads about the lockup08:51
sivangBenC: I have no digicam so that's what I managed to take by hand08:53
sivangBenC: pid 5570, comm   modprobe08:53
sivangBenC: EIP:0060:[<c02ec3d4>]  CPU:008:53
sivangBenC: EIP is at _spin_lock_irqsave+0x14/0x2008:54
sivangBenC: does that help?08:54
BenCdo you have the first few functions from the stack trace?08:54
BenCsounds like it is crashing in a module init08:54
BenCneed to know which module08:54
sivangBenC: how do I produce a stack trace there? I was virtually helpless when reaching that point08:55
BenCit didn't spit one out?08:55
BenCinteresting08:55
BenCany idea what the error was above the pid 5570 line?08:56
sivangBenC: sure, the one I told you before08:56
BenClike "BUG: ..."08:56
BenCsoftlockup, that's right08:56
sivangBenC: the first echo was that is started PCMCIA detection stuff08:56
sivangBenC: yes08:57
sivangBenC: exactly08:57
sivangBenC: on CPU#008:57
sivangBenC: I wonder if I can reproduce that on this machine as well08:57
sivangI will isntall this kernel here as well08:57
BenCok, -386 kernel works? if so, boot, and somehow disable pcmcia stuff08:57
sivangBenC: I can remove it's modules if they are there form /etc/modules ?08:57
BenCprobably a script in /etc/hotplug/ for it08:57
BenCor try mv /lib/modules/(version)/kernel/drivers/pcmcia to somewhere outside of /lib/modules08:58
sivangok, thanks for the tips08:58
sivangwill try and let you know08:59
BenCok, thanks08:59
mjg59BenC: Yeah, I think that's being replaced with a more general solution09:05
mjg59BenC: But basic Broadcom functionality seems to be getting fairly close09:05
BenCmjg59: well, they need something because ipw2200, bcm430x, prism54-softmac and rtl808x all seem to need it09:06
BenCrtl818x09:07
BenCand I'm getting tired if custom ieee80211 stacks in all our external wireless drivers :)09:07
mjg59ipw2200 should just need the ieee80211 stack09:07
BenCit does, but it has internal softmac stuff09:07
mjg59bcm430x, prism54-softmac and rtl808x need an extra softmac stack09:07
mjg59Oh, does it? Nngh.09:07
mjg59I thought it did all that in firmware09:08
mjg59Oh well, never mind09:08
BenCthe softmac patch for ieee80211 was partly based on ipw220009:08
BenCit may not need all the softmac, but it atleast has some functions that softmac needed (subset in ipw2200)09:09
siretartnot to mention madwifi...09:10
infinitymadwifi is a whole different kettle of fish.09:11
mjg59madwifi needs porting to Linux09:11
siretartit has its own ieee80211 stack. Sure, it is fishy because of other reasons, too..09:11
mjg59At the moment it's a *BSD driver that's shoehorned into the kernel09:11
infinityBenC : Should I assume from your vacation announcement that I have until Monday to spit polish LRM?09:15
=== spike [n=spike@unaffiliated/spike] has left #ubuntu-kernel ["bbl"]
BenCinfinity: yeah, definitely09:15
BenCabout to upload -4.4, so you can base work off of that09:15
infinityExcellent.  And we can shoot for an update -meta on Monday.09:15
infinity(Assuming other parties agree, I'll just upload -meta right after lrm builds everywhere)09:16
infinityI've decided that, after pulling an all-nighter, my Thursday is going to be a write-off.09:16
infinityGo me.09:17
infinityAnyhow.  I should go catch some "oh god, the sun's already been up for two hours, eek" shuteye.09:17
jbaileyBenC: Is -4.4 one I should test for ppc64 love?09:18
BenCjbailey: I don't expect it to work, but surely give it a try09:22
BenCinfinity: heh, get some sleep09:22
jbaileyBenC: If you're not expecting it to work, I'll just do it when I have time and not rush to it, then.09:27
jbaileyAll good. =)09:28
BenCno problem :)09:33
=== doko_ [n=doko@dslb-084-059-072-254.pools.arcor-ip.net] has joined #ubuntu-kernel
fabbionesiretart: i have no issued with you working on iptables..09:36
=== LaschW [n=LaschW@dyndsl-085-016-016-057.ewe-ip-backbone.de] has joined #ubuntu-kernel
LaschWAre there any reports of segmentation fault booting linux-image-2.6.12-10-k7 ?09:43
siretartfabbione: a fixed version of iptables should be in dapper now on all arches09:44
fabbioneLaschW: no. works here. we did score 9/9 successes on the tests09:44
siretartfabbione: I think we should upload a fixed version of iptables to breezy-updates09:44
fabbionesiretart: what is exaclty broken?09:44
siretartfabbione: debian/rules sets the variable KERNEL_DIR to /usr/include09:45
siretartfabbione: this is wrong. it must be just '/usr'09:45
fabbionespecially given that nobody did notice up till now09:45
siretartfabbione: without the kernel headers, a lot of optional extra modules won't get built09:45
fabbionesiretart: and problems does that bring?09:45
siretartfabbione: extra modules like recent match support and quite a few others09:45
fabbionehmmmm09:46
siretartI came to it because I wanted to play around with that 'recent' match target as suggested by someone on planet.debian.org09:46
siretartand was surprised that this doesn't work on breezy09:47
fabbionei think it is a good candidate for -updates09:49
fabbionesiretart: i am confident you did your homework09:49
LaschWfabbione: Is there a way how I may get / collect usefull information why this happens? 09:49
fabbioneplease explain to mdz and coordinate with him09:49
fabbioneLaschW: it depends what happens09:49
fabbioneLaschW: segfault what? what does segfault?09:50
fabbioneyou didn't tell me much09:50
LaschWfabbione: segfault before usplash started, si IMHO there are no logs in that state of boot, isn't it?09:50
LaschWs/si/so/09:50
fabbionethe kernel doesn't segfault09:50
fabbioneno there are no logs.. try to boot in recovery mode without usplash09:51
fabbionewhat's on the screen?09:51
fabbionecan you take a picture?09:51
=== zul__ [n=chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel
siretartmdz: would you accept a one-line patch to iptabes for breezy-updates? Rationale: due to a wrong variable, iptables fails to find its kernel headers and does not compile nearly all optional modules.09:52
LaschWfabbione: I will reproduce it and will see what I can do, give me a 1/4hour...09:52
=== LaschW [n=LaschW@dyndsl-085-016-016-057.ewe-ip-backbone.de] has left #ubuntu-kernel ["Leaving"]
fabbioneLaschW: in 1/4 hour i will be asleep09:53
fabbionebah ok09:53
=== ispiked [n=ispiked@unaffiliated/ispiked] has joined #ubuntu-kernel
=== ubuntulog [n=ubuntulo@port49.ds1-van.adsl.cybercity.dk] has joined #ubuntu-kernel
=== Topic for #ubuntu-kernel: Ubuntu kernel development discussion ONLY | New git tree for dapper: https://wiki.ubuntu.com/KernelGitGuide | 2.6.15-rc1-ubuntu2 uploaded (should build for x86, amd64, and ppc)
=== Topic (#ubuntu-kernel): set by BenC at Tue Nov 15 17:08:39 2005
mdzsiretart: yes10:05
mdzsiretart: send me a debdiff by mail for review10:06
siretartmdz: http://paste.ubuntulinux.nl/492410:08
siretartthats what I just uploaded to dapper, I'd upload of course with adjusted version number10:08
mdzsiretart: go ahead and prepare the package and upload as 1.3.1-2ubuntu1.110:09
mdzto breezy-updates10:09
siretarton my way10:10
=== LaschW [n=LaschW@dyndsl-085-016-009-044.ewe-ip-backbone.de] has joined #ubuntu-kernel
LaschWfabbione: linux-image2.6.12-10-k7 segfault during boot: 10:16
fabbionekernel doesn't segfault...10:16
fabbioneit OOPS10:16
LaschWfabbione: Last message isa: uncompressing Linux... OK booting....10:16
LaschWfabbione:then 10 lines segmentation fault10:17
LaschWfabbione: then a line: 010:17
fabbioneLaschW:  -> initramfs10:17
fabbionetry regenerate the initramfs10:17
LaschWfabbione: Ahh!10:17
dilingermm, neat10:20
dilingerhttp://www.selenic.com/linux-tiny/10:20
LaschWfabbione: regenerating initramfs for 2.6.12-10-k7 will affect the other kernels? I'm asking because till now I have a running system, using the older kernel images.10:21
fabbioneno10:21
fabbioneno if you do it properly10:21
LaschWfabbione: properly means: 'sudo dpkg-reconfigure linux-image-$(uname -r)'10:23
fabbioneyes10:24
fabbionethat is one10:24
fabbionethere are other ways10:25
fabbionebut use that one10:25
LaschWfabbione: OK, thanks a lot...10:25
=== LaschW [n=LaschW@dyndsl-085-016-009-044.ewe-ip-backbone.de] has left #ubuntu-kernel ["Leaving"]
fabbionei have the feeling i am going to get pissed soon10:26
fabbionethere is a user that keeps bombing me of emails in pvt10:26
BenCfabbione: bounce them all back to him, maybe he'll stop10:27
BenCfabbione: I saw one report that sound stopped working with 2.6.12-1010:27
fabbioneBenC: i did answer him and CC kernel-team10:28
fabbionelet see if he gets the clue (again)10:28
fabbioneBenC: quite impossible.. sound didn't change10:28
fabbionebug number?10:28
BenC1996910:29
zul__meh...since when did kernel-team ml become support10:29
BenCit's very vague10:30
BenClike, I think I just gave you all the info in the bug report10:30
zul__shoot em10:31
zul__how ubuntite of me ;)10:34
zul__later anyways10:35
fabbionewow10:35
fabbionewhat a bug10:35
fabbioneBenC: let the bug die there for the next 2/3 weeks and close it with prejudist10:36
fabbionebug is pointless. kthxbye10:36
fabbioneor ask Diziet to do it for you10:36
fabbione;)10:36
=== LaschW [n=LaschW@dyndsl-085-016-003-190.ewe-ip-backbone.de] has joined #ubuntu-kernel
LaschWfabbione: 'sudo dpkg-reconfigure linux-image-2.6.12-10-k7' didn't change anything. Still segfault messages...10:42
fabbioneLaschW: works here... ask jbailey how to debug initramfs10:43
LaschWfabbione: dpkg-reconfigure says: Not touching initrd symlinks since we are being reinstalled (2.6.12-10.24)10:43
BenClol10:43
fabbionethe kernel is ok10:43
BenCthe only way to know for sure is to regen the initramfs for the old kernel and see if that works10:44
BenCyou could also try the -386 kernel10:44
fabbioneyeah that's another option too10:44
fabbionebut i am pretty sure the kernel is fine10:45
fabbionespecially because my k7 is one of the test machines10:45
fabbioneoh JEEE10:46
fabbionethis guy is persistent10:46
fabbioneCC to kernel-team10:46
fabbionehe answer back without kernel-team10:46
=== fabbione reroutes to /dev/null
BenChe's embarassed :)10:47
fabbioneI AM PISSED10:47
fabbionewhy nobody cares about pissed Developers but only about embarassed (l)users? ;)10:48
=== fabbione modprobes overfiend.ko
fabbioneTHEY SHOULD ALL DIE A PAINFUL DEATH!10:48
=== fabbione LARTS
=== fabbione LARTS
=== fabbione rmmod overfiend.ko
fabbioneah10:48
fabbionesteaming down is healty10:48
LaschWBut how does it come that the 2.6.12-9-k7 works and the -10-k7 not? Just for beeing curious...10:49
fabbioneLaschW: the kernel works fine. the segfault is not coming from the kernel10:49
fabbionethe initramfs is probably corrupted or it is not generated properly10:50
fabbioneotherwise you won't see a segfault10:50
fabbionebut an OOPS10:50
fabbioneand it can be anything that breaks the initramfs10:50
fabbionereally...10:50
fabbioneLaschW: try booting 2.6.12-10-38610:50
fabbioneand see if it works10:50
fabbionenone of the security patches to touch boot10:51
fabbioneboot process i mean10:51
fabbioneanyway i am off to bed10:51
fabbionegood night *10:51
=== mdke [n=matt@ubuntu/member/mdke] has joined #ubuntu-kernel
mdkehello11:14
mdkei had some bugs about acx_pci closed without a comment recently. They are still reproduceable on dapper, how come they were closed, does anyone know?11:15
jbaileymdke: Bug number?11:16
mdkehmm11:17
mdkelemme find them11:17
mdkejbailey, i can't find them, i'll have to come back when I have my email with me11:21
=== mdke finds an open one
mdkeperhaps it was just housecleaning, and closing bugs instead of marking them as dups11:24

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