• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Sheevaplug - wireless access point  (Read 1743 times)
spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« on: March 30, 2011, 05:42:44 PM »

Using Debian Wheezy and  USB wireless I have a wireless access point working.
My current kernel is sheeva-with-linux 2.6.38.2

The USB wireless is a very cheap (~$20) Planex GW-USBMini2N. This would seem to be a handy solution for a wireless AP.

I am using the rt2800usb module driver (generic), hostapd and dnsmasq. (I can detail the setup of these if someone wants it. )
The result is good, low CPU utilzations, high speed ... except I get the occasional kernel panic and always when I am not watching it.

Modules linked in: iptable_filter ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables dm_crypt dm_mod rt2800usb rt2800lib rt2x00usb rt2x00lib mac80211 cfg80211 rfkill mv_cesa

I started with the 2.6.35.11 kernel and have shifted to the 2.6.38.2 hoping to have the problem go away. 

After using Sheevaplugs for some time now, this is my first kernel crash. What is the usual diagnostic path? It would seem that I have to wait for a day to generate the problem.

Anyone have any suggestions?
Logged

cbxbiker61
Global Moderator
Sr. Member
*****

Karma: 38
Posts: 497


View Profile
« Reply #1 on: March 30, 2011, 06:01:45 PM »

Using Debian Wheezy and  USB wireless I have a wireless access point working.
My current kernel is sheeva-with-linux 2.6.38.2

Modules linked in: iptable_filter ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables dm_crypt dm_mod rt2800usb rt2800lib rt2x00usb rt2x00lib mac80211 cfg80211 rfkill mv_cesa

I started with the 2.6.35.11 kernel and have shifted to the 2.6.38.2 hoping to have the problem go away. 

After using Sheevaplugs for some time now, this is my first kernel crash. What is the usual diagnostic path? It would seem that I have to wait for a day to generate the problem.

Anyone have any suggestions?


You must have a complete stack trace to be of much use.  It includes the function that was active when the crash occured and a backtrace.  That usually gives a pretty good idea of which code is problematic.
Logged

spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« Reply #2 on: March 31, 2011, 04:10:02 PM »

So far (fingers crossed) it would appear that 2.6.38.2 does not have the problem.
2.6.37.* and 2.6.35.11 definitely fail
Logged

Pages: [1]
Print
Jump to: