[beagleboard] rtl_adsb and/or network issue under opensuse 12.2

Any chance can you grab the "dmesg" after this usb lockup occurs...2
bugs come to mind, and this would give us a good hint..

Regards,

BTW, it is netcat not netcast (brain fart).

I ran rtl_adsb > /dev/null and it locked up. So that takes the network out of the loop.

I don’t know how to save dmesg, but it you have instructions, I will give it a try. I looked at files in /var/log, but I don’t know where exactly to look for dmesg.

I suspect power management. The reason I say so is when I was running wireshark, the system was up for hours. [I suspect wireshark was enough of a load to prevent the system from using power saving tricks.] I don’t know where to edit the bios to turn off acpi, uh mostly because it doesn’t seem to be their when I check the bootloader in yast. :wink: Otherwise I would turn off ACPI and see what happens. The same goes for the XFCE display turning off. I haven’t found where to set that. I run KDE on my intel box.

dmesg > log.txt

copy log.txt to pc, upload to pastebin.com...

Regards,

Here is the file:
http://pastebin.com/acppjXgM

Yeap, that'll work... So now you just have to wait for it to lock up
and break and then login over serial and do the same thing so we can
see the kernel messages when it locked up.. (or just leave the serial
connected and wait for the kernel to spam the serial port when it
locks up..)

Regards,

I’m not following you at all.

At the moment, I don’t believe it has anything to do with eth0, so I can just log in that way. But once it locks up, I can’t get back into the BB XM. Locked up is locked up. All I can do is boot and start over.

I'm not following you at all.

At the moment, I don't believe it has anything to do with eth0, so I can
just log in that way. But once it locks up, I can't get back into the BB XM.
Locked up is locked up. All I can do is boot and start over.

I found the command to set the CPU frequency. I locked it at 800MHz and
repeated the experiment with rtl_adsb. It locked up and no way to get back
in.

It's really simple.. WE can't help you with no debugging info..

So if you run something and it just hardlocks, well can't help..

So, login over serial where usually the kernel will spam error
messages, and run "rtl_adsb" lockup, if your kernel was configured
with some useful debug options it should dump one last gasp/opps over
serial... If it isn't doing that talk to the guys who actually built
your kernel/os and get some debugging enabled..

Regards,

OK. It wasn’t clear to me that the serial port was anything other than another way to log into the system.

I’m not following you at all.

At the moment, I don’t believe it has anything to do with eth0, so I can
just log in that way. But once it locks up, I can’t get back into the BB XM.
Locked up is locked up. All I can do is boot and start over.

I found the command to set the CPU frequency. I locked it at 800MHz and
repeated the experiment with rtl_adsb. It locked up and no way to get back
in.

It’s really simple… WE can’t help you with no debugging info…

So if you run something and it just hardlocks, well can’t help…

So, login over serial where usually the kernel will spam error
messages, and run “rtl_adsb” lockup, if your kernel was configured
with some useful debug options it should dump one last gasp/opps over
serial… If it isn’t doing that talk to the guys who actually built
your kernel/os and get some debugging enabled…

Regards,


Robert Nelson
http://www.rcn-ee.com/

OK. It wasn’t clear to me that the serial port was anything other than another way to log into the system.

No useful diagnostics on the serial port.

I guess at this point I need to check with opensuse.