Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 5 Feb 2003 02:27:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 5 Feb 2003 02:27:06 -0500 Received: from [66.111.45.40] ([66.111.45.40]:50842 "EHLO saltbox.argot.org") by vger.kernel.org with ESMTP id ; Wed, 5 Feb 2003 02:27:05 -0500 Date: Tue, 4 Feb 2003 23:36:37 -0800 From: Joshua Kwan To: jkmaline@cc.hut.fi Cc: linux-kernel@vger.kernel.org Subject: 2.5 kernel + hostap_cs + X11 = scheduling while atomic Message-ID: <20030205073637.GA10725@saltbox.argot.org> Reply-To: joshk@triplehelix.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.3i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2012 Lines: 49 Hi Jouni and LKML folks, In kernel 2.5.59 I built the hostap modules as stated in the Makefile. (make -C /usr/src/linux SUBDIRS=$PWD/driver/modules modules, etc.) However, a combination of running said kernel, hostap_cs, and X11 produces this nasty infinite string of errors: bad: scheduling while atomic! Call Trace: [] do_schedule+0x33a/0x33f [] schedule_timeout+0x5f/0xb3 [] proc_alloc_inode+0x4c/0x75 [] process_timeout+0x0/0x9 [] hfa384x_cmd+0x3eb/0x2d6b7eae [hostap_cs] [] get_new_inode_fast+0x48/0xf0 [] default_wake_function+0x0/0x3e [] default_wake_function+0x0/0x3e [] get_page_cache_size+0x12/0x1d [] hfa384x_get_rid+0x36/0x2d6b7606 [hostap_cs] [] hostap_get_wireless_stats+0xa6/0x2d6c77f1 [hostap] [] seq_printf+0x45/0x56 [] wireless_seq_show+0xd6/0xf7 [] do_mmap_pgoff+0x40e/0x6dc [] seq_read+0x1c9/0x2ee [] vfs_read+0xbc/0x127 [] sys_read+0x3e/0x55 [] syscall_call+0x7/0xb This will repeat itself over and over again in the same order, same everything. The second I kill X the messages stop completely. I use the radeon accelerated X server using an Intel AGP bridge (kernel supported.) Any ideas? It seems like it would be a problem in hostap_cs's main loop. Or it could be a kernel problem, which is why I'm forwarding it to LKML :) Why would it only happen when X11 is active though? Thanks for any insight anyone might have on this issue. Lately, I left my machine on and went to go eat lunch. When i came back, /var/log/syslog was overflowing with these errors and had filled up /var completely. Had to purge them all manually :) Regards Josh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/