[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200610231454.00238.s0348365@sms.ed.ac.uk>
Date: Mon, 23 Oct 2006 14:54:00 +0100
From: Alistair John Strachan <s0348365@....ed.ac.uk>
To: Zhu Yi <yi.zhu@...el.com>
Cc: LKML <linux-kernel@...r.kernel.org>, jketreno@...ux.intel.com
Subject: Re: 2.6.19-rc2: ieee80211/ipw2200 regression
On Monday 23 October 2006 14:22, Alistair John Strachan wrote:
> On Monday 23 October 2006 04:42, Zhu Yi wrote:
> > On Mon, 2006-10-23 at 02:44 +0100, Alistair John Strachan wrote:
> > > [alistair] 02:42 [~/linux-git] cat /boot/System.map-`uname -r` | grep
> > > arc4
> > > c01f7970 t arc4_crypt
> > > c01f7a10 t arc4_set_key
> > > c0341be0 d arc4_alg
> > > c0390cc0 t arc4_init
> > > c03a393c t __initcall_arc4_init
> > > c03a6380 t arc4_exit
> >
> > It should be OK if you configured ARC4 and CRC32 in kernel. Can you also
> > see the symbols in /proc/kallsyms? (In case /boot/System.map-`uname -r`
> > differs with the currently running kernel.)
>
> You're right, they're not there. However the files were built at the same
> time!
Actually, sorry, I was looking at the wrong machine. They are indeed there:
[alistair] 14:20 [~] cat /proc/kallsyms | grep arc4
c01f7970 t arc4_crypt
c01f7a10 t arc4_set_key
c0390cc0 t arc4_init
>
> [alistair] 14:20 [~] ls -lah /boot/*2.6.19-rc2*
> -rw-r--r-- 1 root root 36K 2006-10-13 21:46 /boot/config-2.6.19-rc2
> -rw-r--r-- 1 root root 798K 2006-10-13 21:46 /boot/System.map-2.6.19-rc2
> -rw-r--r-- 1 root root 1.7M 2006-10-13 21:46 /boot/vmlinuz-2.6.19-rc2
>
> Maybe it's a problem with the crypto subsystem?
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists