[BUG] Sleeping function called from invalid context (2.6.18.6)

2007-01-20 Thread Chris Rankin
Hi, I have been testing my wireless zd1211rw driver with kismet, but have noticed my logs filling up with these messages instead: BUG: sleeping function called from invalid context at kernel/mutex.c:86 in_atomic():0, irqs_disabled():1 [c029688e] mutex_lock+0x12/0x1a [c02496ae]

Re: [BUG] Sleeping function called from invalid context (2.6.18.6)

2007-01-20 Thread Chris Rankin
This is for a 2.6.18.6 UP-preempt kernel compiled with gcc-4.1.1, BTW. Cheers, Chris ___ The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider.

ne driver crashes when unloaded in 2.6.22.6

2007-09-09 Thread Chris Rankin
Hi, While trying to get my NE2000 ISA card working with NetworkManager and Linux 2.6.22.6, I discovered that the ne module will cause the kernel to oops when it is unloaded. The problem is that the module's clean-up function tries to unregister a platform driver unconditionally, although the

Re: ne driver crashes when unloaded in 2.6.22.6

2007-09-09 Thread Chris Rankin
--- Dan Williams [EMAIL PROTECTED] wrote: Offhand question, does your ne2000 card support carrier detection? Err... there is a /sys/class/net/eth0/carrier entry (I think - not in front of that machine right now). IIRC it said 1 when I read it. Cheers, Chris

Re: ne driver crashes when unloaded in 2.6.22.6

2007-09-12 Thread Chris Rankin
--- Dan Williams [EMAIL PROTECTED] wrote: Offhand question, does your ne2000 card support carrier detection? Err... there is a /sys/class/net/eth0/carrier entry Does it read '0' when you unplug the cable? Hmm, apparently not. The light on the card goes out though, so could this just

Re: ne driver crashes when unloaded in 2.6.22.6

2007-09-15 Thread Chris Rankin
--- Dan Williams [EMAIL PROTECTED] wrote: On Wed, 2007-09-12 at 19:23 +0100, Chris Rankin wrote: Hmm, apparently not. The light on the card goes out though, so could this just be a lack of driver support? Likely, yes. I've been trawling the Internet for 8390 specifications and have

[PATCH] (Revised) USB VID/PID clash between pegasus and hci_usb drivers

2008-01-04 Thread Chris Rankin
PEGASUS_DEV_CLASS(pn, vid, pid, dclass, flags) \ + {.match_flags = (USB_DEVICE_ID_MATCH_DEVICE | USB_DEVICE_ID_MATCH_DEV_CLASS), \ + .idVendor = vid, .idProduct = pid, .bDeviceClass = dclass}, #include pegasus.h #undef PEGASUS_DEV +#undef PEGASUS_DEV_CLASS {}, {} }; Signed-off-by: Chris

Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?

2008-02-18 Thread Chris Rankin
--- Andrew Morton [EMAIL PROTECTED] wrote: sysfs: duplicate filename 'bridge' can not be created WARNING: at fs/sysfs/dir.c:424 sysfs_add_one() Pid: 1, comm: swapper Not tainted 2.6.24.1 #1 [c0105020] show_trace_log_lvl+0x1a/0x2f [c0105990] show_trace+0x12/0x14 [c010613d]

Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?

2008-02-18 Thread Chris Rankin
--- Stephen Hemminger [EMAIL PROTECTED] wrote: sysfs: duplicate filename 'bridge' can not be created WARNING: at fs/sysfs/dir.c:424 sysfs_add_one() Pid: 1, comm: swapper Not tainted 2.6.24.1 #1 [c0105020] show_trace_log_lvl+0x1a/0x2f [c0105990] show_trace+0x12/0x14 [c010613d]

Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?

2008-02-22 Thread Chris Rankin
--- Kay Sievers [EMAIL PROTECTED] wrote: Greg, it seems that: arch/x86/pci/legacy.c :: pci_legacy_init() tries to create already created bridge symlinks in 2.6.24. So we discover the same devices twice? Can this be a reason for the hang? No, it can't be because it's *not* hanging in this