On Wed, 02 Jan 2008 01:19:33 +0100 [EMAIL PROTECTED] wrote: > same with radio-sf16fmr2 and esp > > after repeatedly modrpobe/modprobe -r radio-sf16fmr2, i can hang my system > when loading esp afterwards > > before loading esp, doing a "cat /proc/ioport" segfaults > > this is with 2.6.24rc6 and also with 2.6.22 > > i have found these issues by running some (probably sick :D ) module > load/unload test across all modules >
Hi, Please provide more kernel crash info, as listed in the REPORTING-BUGS file in the top-level directory of the kernel source tree. Thanks. > > -----Ursprüngliche Nachricht----- > > Von: [EMAIL PROTECTED] > > Gesendet: 01.01.08 21:46:30 > > An: linux-kernel@vger.kernel.org > > Betreff: Re: [BUG] crash - module l440gx buggy ? interfere > > > > > same/similar behaviour with > > > > l440gx and container > > l440gx and acpiphp > > > > after load of l440gx, container and acpiphp modules do also hang my system > > on load/unload. > > > > maybe l440gx leaving the system in some weird state after probe ? > > > > > > > -----Ursprüngliche Nachricht----- > > > Von: <[EMAIL PROTECTED]> > > > Gesendet: 01.01.08 20:57:08 > > > An: linux-kernel@vger.kernel.org > > > Betreff: [BUG] crash - modules l440gx and parport_pc interfere > > > > > > > > > > there seems some weird interference between l440gx and parport_pc modules > > > > > > i can reproduceable crash my box by either: > > > > > > modprobe parport_pc;modprobe l440gx;rmmod parport_pc > > > > > > or > > > > > > modprobe l440gx; modprobe parport_pc;rmmod parport_pc > > > > > > this happens on 2.6.24rc6 and also older kernel (2.6.22) > > > > > > nothing in dmesg - just > > > >JEDEC: Found no L440GX BIOS device at location zero > > > >JEDEC probe on BIOS chip failed. Using ROM > > > > > > because i haven`t appropriate hardware. > > > > > > don`t know if this is a bug in parport_pc or l440gx but maybe its worth > > > reporting. > > > > > > regards > > > roland --- ~Randy desserts: http://www.xenotime.net/linux/recipes/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
