public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dale K Dicks <dale_d@telusplanet.net>
To: linux-kernel@vger.kernel.org
Subject: ieee1394 subsystem causes segfaults
Date: Wed, 17 Dec 2003 07:10:22 -0700	[thread overview]
Message-ID: <1071670222.2519.5.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

1. when unloading the ochi1394 or sbp2 modules from a 2.6.0-test11
kernel, a segfault occurs every time.

2. modprobe ohci1394, modprobe sbp2, rmmod sbp2 and/or rmmod ohci1394,
segfault, lsmod hangs after this as well as the originating tty

3. modules

4. 2.6.0-test11

5. no oops message

6. see 2.

7. Gentoo Linux

7.2. [ ddicks@linuxbox ~ ] $ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 1
model name      : Intel(R) Pentium(R) 4 CPU 1.80GHz
stepping        : 2
cpu MHz         : 1808.041
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips        : 3588.09


DKD
Calgary, Alberta, Canada
dale_D at telusplanet dot net

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-12-17 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17 14:10 Dale K Dicks [this message]
2003-12-17 14:10 ` ieee1394 subsystem causes segfaults Ben Collins
2003-12-19 17:03   ` Randy.Dunlap

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=1071670222.2519.5.camel@localhost \
    --to=dale_d@telusplanet.net \
    --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