[01:52] <h00k> I'm desparately trying to get netconsole to work properly, I've followed https://wiki.ubuntu.com/KernelTeam/Netconsole "to the 't'" and I am unable to get netconsole to log between my netbook and laptop.
[01:53] <h00k> I've also tried a crossover between the two, manually setting the IP's
[01:53] <h00k> I cannot get my netbook to show that its receiving data
[01:57] <h00k> I'm getting a kernel panic and I'd like to try to track it down, nothing is showing up in the logs
[01:58] <jk-> h00k: does the device you're trying to debug have a serial port?
[01:58] <h00k> jk-: negative, thats why I'm trying netconsole
[01:58] <jk-> 'k
[01:59] <jk-> you're using netcat to receive?
[01:59] <h00k> I was trying netcat, also syslog-ng
[02:00] <jk-> yeah, stick with netcat for now, less to go wrong
[02:00] <h00k> alright
[02:00] <h00k> syslog-ng baleeted
[02:00] <jk-> so you're getting the 'netconsole' init messages in dmesg on the sender?
[02:00] <jk-> :)
[02:01] <jk-> (from step 5)
[02:02] <h00k> jk-: I do see the netconsole messages, the last one being reported "device eth0 not up yet, forcing it"
[02:02] <jk-> ok
[02:02] <h00k> oop
[02:02] <h00k> and then I see netconsole: network logging started
[02:04] <h00k> so, apparently this is working. (this is since I've tried it last on a crossover cable between the two)
[02:04] <jk-> and the MAC address it shows is correct for your receiving machine? (do an 'ip link show dev eth0' on the receiver to check its MAC)
[02:05] <jk-> oh, it's working then?
[02:05] <h00k> I mean, netconsole reports as logging on the sender machine
[02:05] <jk-> yep, ok
[02:06] <h00k> the MAC shows as correct (as reported by ifconfig eth0): HWaddr 00:22:15:75:be:99
[02:07] <jk-> so to generate some output from the kernel:
[02:07] <jk-> echo '?' | sudo dd of=/proc/sysrq-trigger
[02:08] <jk-> nothing showing up in the netcat?
[02:08] <h00k> well, I'm on the receiving device now (wifi)
[02:08] <h00k> I...can't...have wireless/crossover going at the same time...can I?
[02:09] <jk-> hm, could you explain your setup a little more? you're using wifi on the receiving machine at the same time?
[02:09] <h00k> no, right now I have disconnected the crossover cable to go online and get some more information
[02:10] <jk-> ah, ok.
[02:10] <h00k> when I'm actually going to test it, I disconnect my netbook from wireless, plug the crossover in, and do it that way
[02:10] <jk-> you can use both at the same time
[02:10] <h00k> I've tried to generate kernel activity
[02:10] <h00k> orly
[02:10] <h00k> okay
[02:10] <h00k> I've tried to generate kernel activity by plugging in a USB device
[02:10] <jk-> just means you have to be a little more careful with the setup :)
[02:10] <jk-> yeah, that should work too.
[02:10] <h00k> oh look at that.
[02:10] <h00k> I didn't realize I could
[02:10] <h00k> hang on, lemme netcat
[02:11] <jk-> you need to make sure that eth0 is up and configured correctly though
[02:11] <h00k> eth0 is connected as my static IP
[02:11] <h00k> to the sender
[02:11] <jk-> ip link show dev eth0 ?
[02:11] <jk-> and:
[02:11] <jk-> ip addr show dev eth0
[02:12] <h00k> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:22:15:75:be:99 brd ff:ff:ff:ff:ff:ff
[02:12] <jk-> ok
[02:13] <h00k> so, lemme try that to generate some output
[02:13] <jk-> hang on, do the second command too:
[02:13] <jk-> ip addr show dev eth0
[02:13] <h00k> I have netcat running: netcat -l -p 6666 -u 192.168.0.2  | tee ~/netconsole.log
[02:13] <h00k> k
[02:14] <h00k> http://pastebin.ubuntu.com/302476/
[02:15] <jk-> cool, could you pastebin the 'dmesg | grep netconn' on the sender too?
[02:17] <jk-> if it's too tricky (ie, the machine isn't on a network), don't worry
[02:18] <h00k> hang on, I can get it
[02:18] <jk-> sorry, 'netcon' not 'netconn'
[02:19] <h00k> already fix'd
[02:19] <h00k> surprised in this little using it it hasn't panicked yet ;)
[02:20] <h00k> http://pastebin.ubuntu.com/302480/
[02:20] <h00k> (usb drive)
[02:21] <h00k> I mean, from what I can see, everything /should/ be working.
[02:21] <jk-> yeah, all looks good
[02:21] <jk-> on the receiver:
[02:21] <jk-> sudo tcpdump -ni eth0
[02:22] <jk-> then generate some console output on the sender
[02:22] <h00k> for example?
[02:22] <h00k> previous example above?
[02:22] <jk-> yeah
[02:22] <jk-> echo '?' | sudo dd of=/proc/sysrq-trigger
[02:23] <h00k> echo '?' | sudo dd of=/proc/sysrq-trigger
[02:23] <h00k> yeah
[02:23] <jk-> then pastebin the output of tcpdump, if there is any
[02:24] <h00k> http://pastebin.ubuntu.com/302483/
[02:24] <h00k> so, apparently that is working
[02:24] <jk-> cool
[02:24] <h00k>  er, wait
[02:24] <h00k> note: 21:23:35.760788 IP 192.168.0.2 > 192.168.0.1: ICMP 192.168.0.2 udp port 6666 unreachable, length 59
[02:25] <jk-> your netcat isn't running then?
[02:25] <h00k> er.
[02:25]  * h00k facepalms
[02:26] <h00k> there, it ran, netcat reported:invalid connection to [192.168.0.2] from (UNKNOWN) [192.168.0.1] 6666
[02:26] <h00k> once I generated the '?' and dd'd it to /proc/sysrq-trigger
[02:27] <jk-> hm, you must have a different netcat to me
[02:27] <h00k> jk-: I did this: netcat -l -p 6666 -u 192.168.0.2 | tee ~/netconsole.log
[02:27] <h00k> that IP being my netbook (receiver's IP)
[02:27] <h00k> correct?
[02:27] <jk-> yeah, my netcat won't accept -l and -p at the same time
[02:28] <h00k> ah, that was copy/pasted from the ubuntu wiki
[02:28] <h00k> what is good to use..then?
[02:29] <jk-> netcat is good, just gotta figure out the correct options :)
[02:29] <jk-> is this an ubuntu machine (the receiver)?
[02:29] <h00k> yes
[02:29] <h00k> -l is listen mode, p specifies port
[02:30] <h00k> u is udp mode
[02:30] <jk-> [jk@pororo ~]$ nc -l -p 6666 -u 192.168.0.2
[02:30] <jk-> nc: cannot use -p and -l
[02:30] <h00k> 0.0
[02:30] <jk-> there are two flavours of netcat though
[02:30] <h00k> ah, okay
[02:31] <h00k> [v1.10-38]
[02:31] <jk-> ok, sudo netstat -apu
[02:31] <jk-> see if you can find netcat listening on the right port there
[02:31] <h00k> http://pastebin.ubuntu.com/302486/
[02:31] <jk-> (it's netcat-openbsd vs netcat-traditional)
[02:32] <jk-> ok, no netcat there :/
[02:33] <h00k> http://pastebin.ubuntu.com/302487/
[02:33] <h00k> okay, there we goo.
[02:33] <h00k> jk-: thanks in advance for all of your help.
[02:33] <jk-> cool, working now?
[02:33] <jk-> it's listening on 6666, did you change anything?
[02:33] <h00k> no, I didn't
[02:33] <jk-> hm
[02:34] <jk-> and what happens if you do the "echo '?' ...." now ?
[02:34] <h00k> jk-: netcat dies: invalid connection to [192.168.0.2] from (UNKNOWN) [192.168.0.1] 6666
[02:34] <h00k> same :/
[02:36] <jk-> i'm not sure why netcat needs that IP address
[02:36] <jk-> maybe take it out and use "-s 192.168.0.2" instead?
[02:36] <h00k> I don't know either, perhaps I should get rid of it.
[02:36] <jk-> .. or yeah, take it out altogether
[02:37] <h00k> http://pastebin.ubuntu.com/302490/
[02:37] <h00k> ta-da!
[02:37] <jk-> woot
[02:37] <h00k> in just using this mode: netcat -l -p 6666 -u | tee ~/netconsole.log
[02:37] <jk-> cool, looks better to me :)
[02:37] <h00k> thanks, jk-. I really appreciate you taking the time.
[02:37] <jk-> no problem :)
[02:38] <jk-> now see if you can pop the bug :)
[02:38] <h00k> so, the instructions on the wiki said to have the ip in the netcat listener, too.
[02:38] <h00k> now lets see if I can get this sucker to crash
[02:49] <pturing> Can anyone tell me the new way to regenerate the control file?
[02:49] <pturing> used to be:   touch debian/rules.d/control.stub.in; fakeroot debian/rules clean
[02:49] <pturing> but doesn't seem to work for me with karmic
[02:54] <jk-> pturing: just a guess, but touch s/debian/debian.master/ ?
[02:54] <jk-> https://wiki.ubuntu.com/KernelTeam/AbstractedDebian
[02:54] <jk-> ie, touch debian.master/rules.d/control.stub.in
[02:57] <pturing> ok thanks for the link
[02:59] <h00k> jk-: thank you again for the help, I'll part the channel and perhaps be back, depending on what I find
[02:59] <jk-> h00k: no problem, good luck.
[03:00] <h00k> thanks.
[03:07] <pturing> btw, do you know the reason why Ubuntu builds loopback device support in now, while debian still has it as a module?
[04:07] <h00k> jk-: I think its my proc
[04:12] <jk-> h00k: how so?
[04:19] <h00k> jk-: standby
[04:20] <h00k> jk-: http://pastebin.ubuntu.com/302528/
[04:21] <jk-> eep
[04:21] <h00k> jk-: appears to be processor?
[04:21] <h00k> jk-: I think...not exactly sure how to decypher this
[04:25] <h00k> jk-: so, I'm happy that this wworked.
[04:25] <h00k> jk-: thank you very much, again.
[04:26] <jk-> any kernel output before your last paste?
[04:26] <h00k> no, that was it
[04:26] <h00k> jk-: prior to it was the '?' generated by myself
[04:26] <h00k> then I was watching "Fight Club" to try to get it to kernel panic
[04:27] <jk-> it says to run it through mcelog --ascii
[04:27] <h00k> and sure enough, it did.
[04:27] <jk-> ah, ok
[04:27] <h00k> yeah, i'm doing that, its not showing any output, I should learn what its doing
[04:27] <jk-> but yeah, does look like something hardware-related. what machine is this?
[04:28] <h00k> jk-: Dell XPS M1530
[04:29] <h00k> jk-: Intel T7250 processor, 3gb RAM, 200gb 7200rpm HD w/freefall sensor, nvidia 8600mgt video car
[04:29] <h00k> d
[04:31] <h00k> mcelog --ascii, is this something that I would run when i try to get it to die again?
[04:33] <jk-> no, you use it to parse that kernel output
[04:33] <jk-> mcelog --ascii < your-kernel-log.txt
[04:33] <h00k> oh, oh, i get it.
, manpage
[04:34] <jk-> "Note that when the panic comes from a different machine than where mcelog is running on you might need to specify the correct architecture ( --k8 or --p4 or --core2 )"
[04:38] <h00k> jk-: I ran it through with the --core2 flag, it just appears to echo the log back.
[04:40] <h00k> this is interesting  because its specifically saying 64bit kernels
[04:40] <jk-> h00k: hm, i don't know much about the MCE stuff, sorry :(
[04:40] <h00k> I am on 32bit
[04:41] <h00k> jk-: I'll check ##hardware, they appear to be arguing about gfx cards.
[17:03] <Pici> Theres an upstream package linked on the ubuntu-meta package https://launchpad.net/ubuntu/+source/linux-meta that's making the upstream description a bit weird.  If thats supposed to be there, then so be it, but I'm pretty sure that it should be removed.