mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: devzero@web.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] crash - module radio-sf16fmr2 and esp interfere
Date: Tue, 1 Jan 2008 21:29:45 -0800	[thread overview]
Message-ID: <20080101212945.fad9cae3.randy.dunlap@oracle.com> (raw)
In-Reply-To: <80670983@web.de>

On Wed, 02 Jan 2008 01:19:33 +0100 devzero@web.de 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: devzero@web.de
> > 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: <devzero@web.de>
> > > 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/

  reply	other threads:[~2008-01-02  5:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02  0:19 devzero
2008-01-02  5:29 ` Randy Dunlap [this message]
2008-01-02 14:03 devzero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080101212945.fad9cae3.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=devzero@web.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome