Re: ral0 bugs on openbsd 3.8 i386?

2006-01-18 Thread Joachim Schipper
On Wed, Jan 18, 2006 at 12:48:36AM +0100, Emmanuel Jarri wrote:
 On 1/16/06, Theo de Raadt [EMAIL PROTECTED] wrote:
   Hey guys, I'm having problem with ral0 running in hostap mode on my
   openbsd box (i386, running 3.8-stable).
 
  By running -stable, this is a choice you make.
 
  That choice is:
 
  Do I want to track fixes made as they head to the next
  release
 
  or
 
  Do I want only 10-20 super-important fixes over a 6 month
  period
 
  You chose the latter.  Therefore even though there have been about
  40 commits to the ral driver, those will *NEVER* make it into -stable
  and therefore, you are hosed by your own choice.
 Hi,
 
 You can download the last rt driver and compile it.
 You can find it on the cvs at sys/dev/ic/rt2560.*
 (According to Damien Bergamini advices on his forum
 (http://damien.bergamini.free.fr))

However, don't expect any help if you're deviating from both -stable
and -current.

Joachim



Re: ral0 bugs on openbsd 3.8 i386?

2006-01-17 Thread Emmanuel Jarri
Hi,

You can download the last rt driver and compile it.
You can find it on the cvs at sys/dev/ic/rt2560.*
(According to Damien Bergamini advices on his forum
(http://damien.bergamini.free.fr))

Good luck

On 1/16/06, Theo de Raadt [EMAIL PROTECTED] wrote:
  Hey guys, I'm having problem with ral0 running in hostap mode on my
  openbsd box (i386, running 3.8-stable).

 By running -stable, this is a choice you make.

 That choice is:

 Do I want to track fixes made as they head to the next
 release

 or

 Do I want only 10-20 super-important fixes over a 6 month
 period

 You chose the latter.  Therefore even though there have been about
 40 commits to the ral driver, those will *NEVER* make it into -stable
 and therefore, you are hosed by your own choice.



Re: ral0 bugs on openbsd 3.8 i386?

2006-01-16 Thread Theo de Raadt
 Hey guys, I'm having problem with ral0 running in hostap mode on my  
 openbsd box (i386, running 3.8-stable).

By running -stable, this is a choice you make.

That choice is:

Do I want to track fixes made as they head to the next
release

or

Do I want only 10-20 super-important fixes over a 6 month
period

You chose the latter.  Therefore even though there have been about
40 commits to the ral driver, those will *NEVER* make it into -stable
and therefore, you are hosed by your own choice.



ral0 bugs on openbsd 3.8 i386?

2006-01-16 Thread Reza Muhammad
Hey guys, I'm having problem with ral0 running in hostap mode on my  
openbsd box (i386, running 3.8-stable).


At the moment, the ral0 device acts as an access point and only using  
mac address filtering to be able to go on the internet.  So I don't  
use the WEP, or IPSec, or anything like that.  This is already the  
second time I got the integer divide fault trap and then I got into  
the ddb  prompt (I attached the output as well as dmesg below).  Is  
this an known issue? Can someone help me out with this, so that I can  
have my ral0 device runs in hostap mode flawlessly?


If there's anymore info needed, please let me know.

Thanks in advance,
Reza



ral0: device timeout
kernel: integer divide fault trap, code=0
Stopped at  ral_setup_tx_desc+0xae: idivl   %ebx,%eax
ddb trace
ral_setup_tx_desc(d0c89000, e6c38000,200,5fc,0) at ral_setup_tx_desc 
+0xae

ral_tx_data(d0c89000,d6192e00,d0d662200,0) at ral_tx_data+0x552
ral_start(d0c89030,d6192ef6,6,5aa1274) at ral_start+0x16c
ether_output(d0c89030,d6380c00,d05d3be8,d62193d0,30) at ether_output 
+0x35b

ip_output(d6380c00,0,d05d3be4,1,0,0,0,0) at ip_output+0x930
ip_forward(d6380c00,1,0,50,d6138900) at ip_forward+0x159
ipv4_input(d6380c00,d0c8c140,0,d06f) at ipv4_input+0x25a
ipintr(d0c50058,10,d06f0010,14e90010,d06f) at ipintr+0x67
Bad frame pointer: 0xd06f1e44
ddb ps
PID PPIDPGRPUID S   FLAGS   WAITCOMMAND
24709   995924709   10003   0x4086  pause   screen
20661   790320661   10013   0x4086  pollirssi
79031   790310013   0x84select  screen
995929511   995910003   0x4086  pause   ksh
29511   29827   29827   10003   0x184   select  sshd
29827   281329827   0   3   0x4084  netio   sshd
30612   24484   30612   10003   0x4086  pollirssi
24488   1   24484   10003   0x84select  screen
20303   1   20303   0   3   0x4086  ttyin   
getty
13008   1   13008   0   3   0x84select  rtadvd
16081   16080   3   0x4086  ttyin   
getty
15017   1   15017   0   3   0x4086  ttyin   
getty
31978   1   31978   0   3   0x4086  ttyin   
getty
92891   92890   3   0x4086  ttyin   
getty
14226   1   14226   0   3   0x84select  cron
16627   1   16627   0   3   0x84nanosleep   
tspc
28131   28130   3   0x84select  sshd
24316   1   24316   0   3   0x184   select  inetd
79951   799577  3   0x184   poll
dhcpd
28113   4646464674  3   0x184   bfp pflogd
46461   46460   3   0x84netio   pflogd
20294   27009   27009   73  3   0x184   pollsyslogd
27009   1   27009   0   3   0x84netio   syslogd
27208   1   27208   77  3   0x184   poll
dhclient
19447   1   21831   0   3   0x86poll
dhclient
11  0   0   0   3   0x10024 
crypto_wa   crypto
10  0   0   0   3   0x10024 
aiodonedaiodoned
9   0   0   0   3   0x10024 
syncer  update
8   0   0   0   3   0x10024 
cleaner cleaner
7   0   0   0   3   0x10024 
reaper  reaper
6   0   0   0   3   0x10024 
pgdaemonpgdaemon
5   0   0   0   3   0x10024 
pftmpfpurge
4   0   0   0   3   0x10024 
usbtsk  usbtask
3   0   0   0   3   0x10024 
usbevt  usb0
2   0   0   0   3   0x10024 
kmalloc kmthread
1   0   1   0   3   0x4084  
waitinit
0   -1  0   0   3   0x80204 
scheduler   swapper
ddb show registers
ds  0xd0330010  in6_init_prefix_ltimes+0x80
es  0xd06f0010  end+0x759c0
fs  0xd0c50058  end+0x5d5a08
gs  0xd6190010  end+0x5b159c0
edi 0xd0c89030  end+0x60e9e0
esi 0xe6c38000  
ebp 0xd06f1a84