/srv/irclogs.ubuntu.com/2006/03/01/#ubuntu-kernel.txt

=== bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has joined #ubuntu-kernel
bluefoxicyI want oops insurance04:58
bluefoxicywhen my kernel oopses I want it to file a bug and mail the full oops output to every kernel dev so I KNOW they're fixing it  :D04:59
infinitybluefoxicy: Every time I commit a fix for something, I want it instantly forced on every user's machine, and I want them to be forced to test it immediately.  (Also, we can't always get what we want)05:30
bluefoxicyinfinity:  it was a joke05:31
infinitySo was mine.  Sort of. ;)05:31
bluefoxicyinfinity:  although instant testing would be nice ;)05:31
=== j_ack [n=nico@p508D940A.dip0.t-ipconnect.de] has joined #ubuntu-kernel
=== CataEnry [n=cataenry@host152-2.pool8261.interbusiness.it] has joined #ubuntu-kernel
dilingerinfinity: i'd like every user to accompany their bug reports w/ patches that solve the problem.  also, a pony.  i want a pony.10:05
Mithrandirdilinger: what colour?10:09
=== CataEnry [n=cataenry@host152-2.pool8261.interbusiness.it] has joined #ubuntu-kernel
dilingerblue10:11
=== dilinger works on making x86_64's printk_address print something reasonable looking
dilinger[  123.737130]  Call Trace: [ffffffff802e0e15]  schedule_timeout+0x25/0xd010:49
dilinger[  123.737143]   [ffffffff8014b803]  prepare_to_wait+0x23/0x8010:49
dilinger[  123.737148]   [ffffffff802dc383]  unix_stream_recvmsg+0x2c3/0x5d010:49
dilinger[  123.737155]   [ffffffff8014b550]  autoremove_wake_function+0x0/0x3010:49
dilingerhey look, it's an almost readable backtrace, just like i386 and sparc6410:50
dilingerugh, is that intentional?11:19
dilingerdmesg output:11:19
dilinger[   82.375220]   [<ffffffff8019adc0>]  __pollwait+0x0/0xf011:19
dilingersyslog (kern.log):11:19
dilingerFeb 24 05:15:42 throat kernel: [   82.375220]   [__pollwait+0/240]  __pollwait+0x0/0xf011:19
=== jane_ [n=JaneW@dsl-146-140-66.telkomadsl.co.za] has joined #ubuntu-kernel
mjg59BenC: Why the change to CONFIG_2GB?12:16
dokois it intended for a server setup that the hard disk spin down after activity? and if yes, that period seems to be too short01:17
=== fabbione [i=fabbione@gordian.fabbione.net] has joined #ubuntu-kernel
BenCdoko: that would be one of the startup scripts doing that, or it's your bios01:31
BenCmjg59: mainly to allow laptops with 1GB of ram to still be able to suspend/resume01:31
dokoBenC: no, did start sometime in the dapper cycle01:31
BenCdoko: has to be a startup script then...not sure which one though01:32
mjg59BenC: Eh?01:32
mjg59BenC: Suspend/resume should work with highmem...01:32
BenCmjg59: I've had reports that it doesn't, also read it somewhere01:32
mjg59BenC: How weird01:32
mjg59BenC: It has the side effect of breaking sbcl01:32
BenCyeah, it seems to be breaking more than it fixes01:33
Mithrandirwhen I get "recursive die() failure, output supressed", that's bad, right?01:33
fabbionehey BenC 01:33
BenChey fabbione01:33
mjg59BenC: Suspend to RAM or suspend to disk?01:33
BenCfabbione: I did silo last night, just forgot to upload new upstream tarball01:33
Mithrandirour current live CD seems exceedingly unhappy in vmware.01:33
BenCmjg59: can't recall, let me check01:33
fabbioneBenC: please pull from my tree. changes: more sun4v love, config changes for sparc to move sunhme, sungem and esp from mod to inline to spare people a few errors in d-i01:34
BenCfabbione: those d-i problems were supposed to be fixed, I filed bugs :/01:34
fabbioneBenC: i am talking about modprobe errors during install01:35
BenCfabbione: did you also make scsi/sd built-in aswell?01:35
fabbioneno i didn't01:35
BenCwhat sort of modprobe errors?01:35
fabbioneonly sunhme, sungem and esp01:35
fabbioneit's problem with the drivers01:35
fabbionewhen the hw is not there, they exit badly01:35
fabbioneand d-i catch the error and show a big fat red screen to the user01:35
fabbione= scary01:35
fabbionebu01:36
fabbioneBUT01:36
fabbioneif they are compiled in, hw is still recognized01:36
fabbioneand there is no need to modprobe them01:36
fabbione= works01:36
BenCgotcha01:36
fabbioneBenC: i also added the sparc ABI files for 16.22 and 16.2301:37
fabbioneand removed the abi checker01:38
fabbionesorry i meant the sparc.ignore01:38
BenCok01:38
fabbionenow it takes me about 20 minutes to build :)01:38
BenChow's the DC sparc hw coming?01:39
BenC20 minutes? my machine can do it in 10 :)01:40
BenCbtw, someone is giving me an e3.5k01:41
BenCnot sure where I'll put it, or why I need it, but it's free01:41
infinitymjg59: swsusp is the one that supposedly doesn't work with > 1GB of RAM (according to reports on user lists and forums, etc), though it's worked in the past on my laptop with 2GB of RAM..01:41
fabbioneBenC: 20 minutes including udebs and without ccache?01:42
fabbioneBenC: 20 is full dpkg-buildpackage :)01:42
infinityBenC: Don't suppose they want to spend ridiculous sums to ship it to Australia?01:42
fabbioneBenC: the machines are installed in a rack.. i think elmo crashed before installing anything on them01:42
BenCfabbione: full udebs, but ccache, yes01:42
fabbionekill ccache :)01:43
fabbioneand we can talk ;)01:43
BenCinfinity: maybe I can sneek it through customs in to germany in my duffle bag01:43
infinityBenC: You must have gotten a larger duffle bag since last we met...01:43
BenCI think It was 30 minutes without ccache01:43
fabbioneFeb 24 04:40:30 sunrise udevd[2686] : get_netlink_msg: unable to receive kernel netlink message: No buffer space available01:43
fabbioneHMM01:44
fabbionekernel or udev issue?01:44
BenCfabbione: AHA! someone else sees it aswell01:44
BenCthat's been fucking up my e3k for weeks now01:44
infinityBlame davem.01:44
BenCit has to be kernel, I haven't seen it anywhere else01:44
BenCsomeone the netlink foo is returning ENOBUF but I can't see how01:45
fabbioneBenC: AHHHHH01:45
BenCs/someone/somewhere/01:45
fabbionecrap01:45
fabbionei will blame davem :)01:45
infinityOr, blame davem's girlfriend.  She's too distracting.01:46
BenCinfinity: s/duffle bag/empty crago hold/01:46
fabbionebecause it looks like udevplug is triggering that thing exactly when it needs to probe the network driver01:46
BenCfabbione: for me it occurs when it needs to load sd_mod, which means I have to manually bring the machine past initrd stage01:46
fabbioneok..01:47
fabbioneso it's random..01:47
fabbionegood to know01:47
fabbionedavid will love to fix that :)01:47
BenCnot really, for me sd_mod is the first thing it is trying to do01:47
fabbionethe netdriver is not the first01:48
fabbioneit's way past that i think01:48
fabbionebut i collected all the infos together01:48
BenCit's probably the first thing that requires a kernel event01:48
fabbionecould be01:50
fabbioneBenC: btw.. silo is up01:53
fabbioneuploaded this morning01:53
=== Keybuk [n=scott@213-78-32-60.ppp.onetel.net.uk] has joined #ubuntu-kernel
BenCyeah, saw that02:11
fabbionecool02:12
fabbionehey Keybuk 02:12
fabbionei was just waiting for you02:12
fabbioneKeybuk: http://people.ubuntu.com/~fabbione/sparc/02:12
fabbionethis is the error i am getting on sparc02:12
fabbionethere is lspci, the error in syslog and the strace of both udevd and udevplug02:13
fabbioneeach time i run udevplug i can reproduce the error02:13
fabbionewhat i see at each reboot is network not loaded (e1000)02:13
fabbionebut BenC for instance has no sd_mod02:13
=== BenC concurs
fabbioneBenC: i also fixed hw-detect and Mithrandir did kbd-chooser02:14
fabbionethe latter will make that annoying error disappear when you don't have a keyboard installed02:15
BenCso hw-detect should find my sbus devices now?02:15
fabbioneBenC: only after you will upload the new kernel...02:15
fabbionethat has esp built in02:15
BenCwell that's no help, new kernel will make my sbus modules built-in :P02:15
Keybukcute, that error message isn't listed in the recv() manpage02:16
KeybukENOBUFS02:16
fabbioneBenC: i will look at hw-detect in debian and see what they have 02:16
BenCKeybuk: that error is from the netlink core02:16
KeybukBenC: how do we avoid that error?02:16
fabbioneBenC: otherwise yeah. i guess that's the solution :/02:16
BenCKeybuk: I couldn't figure out why it happened02:16
BenCnetlink code is so confusing02:16
Keybukcould it be that the kernel overflowed the netlink buffer space02:17
BenCfabbione: they have a working libdetect that correctly descends secondary sbus busses :)02:17
BenCKeybuk: seems that it some how does02:17
fabbioneBenC: what package is that?02:18
BenCfabbione: detect or libdetect or something like that02:19
BenCfrom what I remember, we don't use the same thing they do to detect devices02:19
fabbioneBenC: oh you mean discover?02:19
BenCyeah, that's it02:19
fabbionethey did get rid of it02:19
fabbioneand the fix for the double sbus was merged in breezy under my "heavy" pressure02:20
KeybukBenC: what's BUFFER_SIZE in lib/kobject_uevent.c ?02:20
Keybuk(that's the size allowed for a single uevent)02:21
BenCKeybuk: no idea, but there is no ENOBUFS in that code, so I think it's elsewhere02:21
Keybukit could be that it's trying to generate a uevent that's too big02:22
Keybukor it could that it's queuing too many uevents, and udevd isn't getting enough cpu time to slurp them all02:22
BenCthe BUFFER_SIZE overun case returns ENOMEM02:22
fabbioneit's probably the latter02:22
fabbionetoo many events02:22
BenCnet/netlink/genetlinks:ctrl_build_msg() returns ENOBUFS02:23
BenCand so does net/netlink/af_netlink:netlink_overrun()02:24
BenCit's probably the second one generating the error02:24
Keybukthat function's called in a few places02:24
fabbioneKeybuk: is it possible to build udevplug to wait let say half second between sending each event?02:25
fabbionethat would exclude the "too many events at once"02:25
Keybukfabbione: you'd be in the ten-minutes-to-boot area with that delay02:25
fabbioneKeybuk: i don't need to run at it boot :)02:25
fabbionei can test it in userland02:25
fabbionei get the same error02:25
fabbionein both situation02:26
fabbione10 minutes.. no problem ;)02:26
Keybukrun "udevplug -s" to test if that's the case02:26
Keybukthat waits for the previous event to be processed before sending the next02:26
fabbionewhat does -s do?02:26
fabbioneok02:26
fabbionesure i can do02:26
fabbionein a few minutes..02:26
fabbionei am enjoying this extremely cleaned up d-i02:26
KeybukBenC: could be caused by nlmsg_new not returning a message, though I can't find that function02:27
BenCdo_one_broadcast() also has a few failure points02:27
=== Keybuk looks in the header files
Keybukstatic inline struct sk_buff *nlmsg_new(int size)02:27
Keybuk{02:27
Keybuk        return alloc_skb(NLMSG_GOODSIZE, GFP_KERNEL);02:27
Keybuk}02:27
BenCnetlink_broadcast_deliver() seems like a likely candidate02:28
Keybukyeah, there's a whole bunch of them there02:29
BenCit tries to push one to the queue02:29
Keybukif only we could tag it so we knew which one it was02:29
BenCif fabio's test doesn't prove anything I'll start sprinkling some printk's to find out where it is failing02:29
Keybukah, that pushes into an actual socket rcvbuf ... so if that was full, then it wouldn't fit02:29
BenCright02:29
Keybukinteresting that this has only affected sparc so far though02:30
fabbionehmmm02:30
BenChey, can you increase udev's socket bufsize?02:30
fabbioneKeybuk: it might be a cpu speed issue?02:30
KeybukI'd've thought an amd64 would show up more02:30
BenCKeybuk: sparc64 is slower02:30
Keybukahh, of course, sparc is slower so udevd gets less time because the kernel is using it all02:30
BenCit's odd that it happens on a 6-way system though02:30
KeybukBenC: remind me how to do that02:30
BenCmy sparc64 has 6 cpu's and 6gigs of ram :/02:31
Keybukit's a setsockopt isn't it?02:31
fabbione"mine" only 32 CPUs and 16GB of ram02:31
=== fabbione ducks
=== pappan [n=ppadman@bgepxyout-02.asiapac.hp.net] has joined #ubuntu-kernel
Keybukfabbione: cat /proc/sys/net/core/rmem_max /proc/sys/net/core/rmem_default02:31
fabbioneKeybuk: you will have to wait.. i am in the middle of testing parted.. just a few minutes02:32
BenCKeybuk: maybe setsockopt(), let me check02:32
fabbionerebooting now...02:33
BenCfabbione: maybe we have just too much memory/cpu and it's confusing udev :)02:33
=== fabbione goes for a break while POST
fabbioneBenC: possibly02:33
=== Keybuk wonders what SO_RCVBUFFFORCE is
fabbioneBenC: these udev hackers and their laptops02:33
BenClol02:33
BenCKeybuk: IIRC, you can set the buffer to a local one02:33
BenCSO_RCVBUF maybe02:35
Keybukit already sets that SO_RCVBUFFORCE thing02:37
BenCwhat does that do?02:38
Keybukdunno02:39
fabbionere02:40
Keybukah02:40
Keybukgot it, sets the rcvbuf and forces it over the maximum if necessary02:40
Keybuk        const int buffersize = 16 * 1024 * 1024;02:41
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-kernel
fabbioneKeybuk: ok.. now i am without network02:41
Keybuk        setsockopt(uevent_netlink_sock, SOL_SOCKET, SO_RCVBUFFORCE, &buffersize, sizeof(buffersize));02:41
Keybukso that forces the rcvbuf of that socket to 16MB02:41
fabbioneroot@sunrise:~# cat /proc/sys/net/core/rmem_max /proc/sys/net/core/rmem_default02:41
fabbione13107102:41
fabbione12492802:41
Keybukwhich is roughly 16,000 uevents02:41
BenCKeybuk: maybe that's broken on sparc02:41
fabbioneBenC: or events are bigger?02:42
Keybukevents are fixed at 1024 in the kernel and in udev02:42
Keybukfabbione: try "udevplug -s -v | tee events.txt" then count how many lines you get :)02:42
fabbioneKeybuk: udevplug -s is running02:43
Keybukah, ok02:43
fabbionei can do that later again :)02:43
fabbionethe error did always appear before..02:43
fabbioneso one run more or less won't cahnge my life02:44
Keybukok02:45
BenCKeybuk: are you checking the return value of setsockopt()?02:45
Keybuksee whether it appears this run first02:45
KeybukBenC: no...02:46
BenCit may be failing02:46
KeybukBenC: looking at the code, it can only fail with -EPERM02:46
BenCyeah, but it could also be something as stupid as a signed extension or 32/64 value that is getting junked and causing it to be set at minimum bufsiz02:47
BenCbut that wouldn't error out02:47
BenCamd64 isn't doing this in 32-bit02:47
fabbioneKeybuk: it looks like that the run did not generate the error, but it still doesn't bring up the network02:47
fabbioneBenC: amd64 doesn't need memory to be alligned at 64 bit02:48
fabbionethat can cause issues02:48
fabbionelike it was with apt in breezy02:48
BenCno, I mean amd64 isn't pushing this through a compat layer02:48
fabbioneyes i understand02:48
fabbioneare we?02:48
fabbioneyes02:48
fabbionei think..02:48
=== fabbione is tired and confused
fabbioneKeybuk: i have the events file..02:49
Keybukfabbione: just "wc -l" it02:50
fabbionewc -l events.txt 02:50
fabbione0 events.txt02:50
=== zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-kernel
zulheyl02:50
fabbione?02:50
fabbionehey zul 02:50
BenClooks like it just pushes it through as a compat, no translation02:50
Keybukfabbione: you ran with -v ?02:51
fabbioneudevplug -s -v | tee events.txt02:51
Keybukweird02:51
fabbioneexactly as you wrote it02:51
Keybukdunno why that didn't give you anything02:51
Keybukdoes it without the | tee ?02:51
Keybukie just udevplug -s -v ?02:51
fabbioneyeah02:51
BenCKeybuk: doesn't give me anything on my amd64 box either02:51
fabbioneudevplug -s -v | wc -l 02:52
Keybukfabbione: is /sys mounted? :)02:52
BenCah, are you in a chroot?02:52
fabbioneKeybuk: you joking right? it's ubuntu running system 100%02:52
fabbioneno chroot02:52
Keybukfind /sys -name uevent02:52
fabbionefind /sys -name uevent | wc -l02:53
fabbione73002:53
KeybukBenC: it works just fine on mine, I get a huge number of /sys lines printed02:53
BenCI do now that /sys is mounted02:53
BenCI need a serial console to my sparc so I can test this stuff too02:54
Keybukfabbione: what about just "udevplug -v" does that print anything?02:54
BenCI ran udevplug under linux32 in an i386 chroot on my amd64, which should use the same codepath as sparc, and it was just fine02:54
fabbioneKeybuk: checking in a sec02:55
KeybukBenC: yeah, I've just done the same02:55
Keybukquest scott# time udevplug -v | wc -l02:55
Keybuk77302:55
Keybukudevplug -v  0.01s user 0.03s system 2% cpu 1.685 total02:55
fabbionehmm02:55
fabbioneit's taking too long02:55
=== doko [n=doko@dslb-084-059-085-222.pools.arcor-ip.net] has joined #ubuntu-kernel
Keybukfabbione: check you don't have an empty /dev/.udev/queue directory (just sudo rmdir it)02:56
fabbioneKeybuk: yeah that's where i was sticking my nose :)02:56
Keybukthat's a common failure mode of previous udevd02:56
fabbionetime udevplug -v | wc -l02:56
fabbione73502:56
fabbionereal    0m1.093s02:56
fabbioneuser    0m0.048s02:56
fabbionesys     0m0.164s02:56
Keybukcould also explain why -s doesn't work (it's also waiting for that to go away first, and just times out after three minutes)02:56
Keybukok02:56
fabbioneso now02:56
fabbionelet's try again the -s02:57
Keybukwell, you don't have any more events than my amd64, slightly less in fact02:57
fabbionei got the error in syslog02:57
Keybukthose should take only 735,000 bytes of memory to hold in the kernel02:57
KeybukBenC: do you know of a way to find out the size of a socket from userspace?02:57
Keybuklsof?02:57
fabbionehmmm this is interesting02:58
fabbioneKeybuk: if i run udevplug -v -s03:00
fabbioneit gets to /sys/class/vc/vcsa03:00
fabbione /sys/devices/pci0000:0203:00
fabbioneand it stalls there03:00
Keybukprobably aborts with SIGALRM :)03:00
fabbioneno no03:01
fabbioneudevplug is still running03:01
fabbionei had to ctrl+c03:01
Keybukodd03:01
Keybukwhat's in /dev/.udev/queue?03:01
fabbioneno queue03:01
Keybukhmm03:01
Keybukstrace it03:01
=== fabbione tries again
fabbioneit's polling queue03:03
fabbioneprobably udev is still processing03:03
Keybukdoes queue still exist?03:03
fabbioneyes03:03
fabbionebut it's empty03:04
Keybukah03:04
Keybukdid you rmdir it first?03:04
fabbioneyes03:04
=== fabbione will do again to be sure
fabbionelike i said03:06
fabbioneudevplug did generate the queue03:06
fabbioneand waiting for it to disappear03:06
fabbionebut it's empty03:06
BenCKeybuk: getsockopt()03:06
fabbioneKeybuk: udevd is doing nothing03:06
Keybukthat's weird03:07
Keybukthat suggests the kernel never gave the event to udevd03:07
fabbionewell it did03:07
Keybukcan you run "udevmonitor -e" as well?03:07
fabbioneotherwise i would have no / ;)03:07
Keybukif it had given the event to udevd, udevd would have done something and removed the queue directory03:07
fabbioneok one sec..03:08
fabbionei am setting up a slightly better env03:09
fabbionelike 20 xterm03:09
Keybukudevmonitor should give you a UEVENT and UDEV for each things udevplug prints (with -s)03:09
fabbioneroot@sunrise:/dev/.udev# ls -asl03:10
fabbionetotal 003:10
fabbione0 drwxr-xr-x  4 root root    80 Feb 24 06:09 .03:10
fabbione0 drwxr-xr-x 14 root root 13920 Feb 24 06:05 ..03:10
fabbione0 drwxr-xr-x  2 root root   520 Feb 24  2006 db03:10
fabbione0 drwxr-xr-x  2 root root    40 Feb 24 06:09 failed03:10
fabbioneroot@sunrise:~# udevmonitor -e03:10
fabbioneudevmonitor prints the received event from the kernel [UEVENT] 03:10
fabbioneand the event which udev sends out after rule processing [UDEV] 03:10
fabbioneok?03:10
fabbionedo we agree that it is ok?03:10
Keybukok03:10
fabbionei can see the events03:10
Keybukthat's a good starting point03:11
=== pappan [n=ppadman@bgepxyout-02.asiapac.hp.net] has joined #ubuntu-kernel
Keybuk"udevplug -s -v" on that ... for each thing it prints you should see a UEVENT and then a UDEV for it03:11
Keybukif you get no UEVENT, then that's bad03:11
Keybukif you get a UEVENT and no UDEV, that's even worse03:11
fabbioneUEVENT[1140790262.767691]  add@/class/vc/vcsa03:11
fabbioneUDEV  [1140790262.770291]  add@/class/vc/vcsa03:11
fabbioneok?03:11
Keybukok03:11
Keybukand udevplug printed /sys/class/vc/vcsa as well?03:11
fabbioneit didn't get that far???03:12
fabbione /sys/class/tty/tty403:12
fabbioneit stopped a few letters before03:12
fabbionemake that 4003:12
fabbioneit did skip 403:12
fabbionemeh 003:12
fabbionethere is a queue03:13
fabbioneand it is empty03:13
Keybukok, what was the last thing udevplug printed?03:13
fabbioneyes03:13
Keybukwhat was?03:13
fabbione /sys/class/tty/tty403:13
Keybukok03:13
fabbionenow03:13
Keybukwhat was the last UEVENT/UDEV combo printed?03:13
fabbioneok one second dude03:14
fabbionewhen udevplug was at /sys/class/tty/tty403:14
=== mxpxpod [n=BryanFor@unaffiliated/mxpxpod] has joined #ubuntu-kernel
fabbioneudevmonitor was printing the vcsa03:14
Keybukthat's a bit weird03:14
fabbionethere was a queue and it was empty03:14
fabbionenow one more thing03:14
fabbionei did remove the queue03:14
fabbioneand saw it recreated03:14
fabbionemore events did pass03:14
fabbioneand udevplug did finish03:15
Keybuk(btw, worth noting that "udevplug -s" is not very well tested)03:15
Keybukit could be just a general bug with it03:15
fabbioneso ok.. what do you want me to test next?03:15
Keybukhmm03:15
Keybukso udevplug completed normally03:15
Keybukand you didn't get that error03:15
fabbionenope03:15
Keybuknope it didn't complete noramlly?03:16
fabbionebut know i don't know if it would have loaded the module03:16
fabbionenope = no error03:16
fabbionei think the problem is here:03:16
Keybukright, so this suggests that the netlink buffer doesn't overflow if you go slowly03:16
fabbionetty4 was way before than /sys/class/vc/vcsa03:16
Keybukhow do you know? :)03:17
fabbione(in the print from udevplug)03:17
fabbionethe print order?03:17
fabbionenow03:17
fabbionelisten up03:17
Keybukdid udevplug never do vcsa before then?03:17
fabbioneno it didn't03:17
fabbioneit did it after03:17
fabbioneif you let me :)03:17
fabbioneudevplug was printing tty4 - udevmonitor was at vcsa03:18
fabbionethe line after vcsa in udevplug is /sys/devices/pci0000:0203:18
fabbionethe same where it was hanging a long time before03:18
fabbionenow...03:18
Keybukyeah, I get the same behaviour here (though udevplug actually prints that ... I suggest your stdout buffers weren't flushed <g>)03:19
fabbionecould it be a bug in /sys parsing of that device?03:19
Keybukthis is just a "-s" bug03:19
fabbionenext test...03:20
fabbionequeue was never deleted tho03:20
fabbioneif i run only udevplug03:20
fabbionei can see all the events and the error03:20
fabbionethat happens very early03:20
pappanis there kernel debugging tool in ubuntu03:20
fabbionealmost at the beginning03:20
Keybukright, because udevd had finished processing the event, and was waiting for the next ... where udevplug had made the queue directory and then ended up waiting on it03:21
pappani am facing a problem with reboot in my laptop03:21
fabbionebut if i run it normally, the queue dir disappear03:21
KeybukI'll have to debug that, but it's reasonably safe race :)03:22
Keybukso ignore that for now03:22
fabbioneKeybuk: so do you think the bug is from udev itself?03:22
Keybukfabbione: no, I think this is a kernel bug03:22
fabbionei am not really worried about the message itself03:23
Keybuksending the events slowly seems to not produce ENOBUFS03:23
Keybuksending them at normal speed produces it03:23
Keybukso, BenC, can we get some printk()s to find out which -ENOBUF that is?03:23
fabbioneit's only annoying that it doesn't bring up the ethernet03:23
fabbioneanyway i need to take off for a while now03:23
fabbioneKeybuk: thanks a lot dude03:23
BenCKeybuk: yeah, let me get my sparc back up03:23
fabbionelater guys03:24
zultoodles03:25
Keybukdamn, that -s bug is entirely consistent at the first pci device03:29
Keybuktickle: uevent: '/sys/devices/pci0000:00/uevent'03:30
Keybukmake_queue: directory: '/dev/.udev/queue'03:30
Keybukcreate_path: stat '/dev/.udev'03:30
Keybukwait_for_queue: directory: '/dev/.udev/queue'03:30
Keybukoh03:30
Keybukbecause tickling /sys/devices/pci0000:00/uevent DOES NOTHING03:30
KeybukBenC: kernel bug! kernel bug! kernel bug! :)03:31
BenCKeybuk: stop picking on me! :)03:31
Keybuk(this is irrelevant to the ENOBUFS error, it's just amusing to find more errors along the way to debugging that one)03:32
BenCI think ENOBUFS is a red herring03:32
Keybukyou do?03:33
BenCmore than likely our problem is more related to uevents not getting where they should03:33
Keybukyeah, but if the socket buffer is full, they won't get there03:33
Keybukthe fact that pci0000:00 doesn't generate a uevent is only important when using "-s" where it waits patiently for the event ... during normal booting it's irrelevant03:34
BenCI can't see generic sockets getting full...lots of things would be broken03:34
Keybukaye03:34
Keybukudevd used to do it quite regularly until they increased the size to 16MB03:34
BenCwere the symptoms the same?03:34
Keybukyeah, I think so03:35
BenCI just can't see 16k uevents occuring, even on a sparc :)03:35
Keybukwe know there's only 730 events03:35
BenCso filling it would take a lot of effort03:35
Keybukwhich is less than my amd6403:35
KeybukI'm wondering whether it's actually that there's an event bigger than 1K03:35
Keybukan event is just an env buffer, after all03:35
BenCtrue...guess I can put some debug to see what the event size is03:36
BenCor just check for > 1k03:36
KeybukI wonder ...03:39
Keybukthe fact udev wants the socket buffer to be 16MB is just a hint about how big it should never grow past03:39
Keybukit doesn't mean it can actually grow that big, the kernel might not have any free memory to grab03:39
Keybukso it may actually be effectively smaller than the 730K needed to do the job03:39
=== __keybuk [n=scott@82.108.80.242] has joined #ubuntu-kernel
=== j_ack [n=nico@p508D940A.dip0.t-ipconnect.de] has joined #ubuntu-kernel
=== Keybuk [n=scott@82.108.80.245] has joined #ubuntu-kernel
=== CataEnry [n=cataenry@host152-66.pool876.interbusiness.it] has joined #ubuntu-kernel
=== BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel
=== shaya [n=spotter@user-0ccembr.cable.mindspring.com] has joined #ubuntu-kernel
shayaanyone home?07:35
=== cmvo [n=cmvo@62.225.11.174] has joined #ubuntu-kernel
shayajust filed a bug, can help try to debug it if that would help?07:36
=== cmvo [n=cmvo@62.225.11.174] has left #ubuntu-kernel ["Konversation]
=== cjb [n=cjb@islay.ra.phy.cam.ac.uk] has joined #ubuntu-kernel
cjbSorry, stupid question:  dmesg/lspci dumps for lkml, should they go inline or attached?11:07
cjb(The only examples I can find were all attached, so I wonder if there's some differing standard for dmesg as opposed to patches.)11:07

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