public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Higgins <dhiggins@netc.net>
To: linux-kernel@vger.kernel.org
Subject: crash/oops/loop in 2.6.0-test4 (CONFIG_IDE_TASK_IOCTL)
Date: Fri, 29 Aug 2003 15:28:41 -0400	[thread overview]
Message-ID: <1062185320.603.13.camel@Dhiggins> (raw)

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

when CONFIG_IDE_TASK_IOCTL is set on my machine, the kernel will loop
oopses during boot (and never come out of it)

attached is a log of all the errors (expunged of the most obvious
duplicates, but the one looping is the "bad: scheduling while atomic"
one) as well as my kernel config. note the kernel config has
CONFIG_IDE_TASK_IOCTL disabled (for obvious reasons)

the kernel is NOT tainted (ie, no NVIDIA module)

infos about my hardware follows:

Dhiggins:/var/log# lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
(rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge
(rev 03)
00:04.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:04.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:04.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:04.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:06.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891
00:09.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone]
(rev 30)
01:00.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2
Model 64/Model 64 Pro] (rev 15)


Dhiggins:/proc# cat /proc/ide/hda/model         
ASUS CD-S400/A
Dhiggins:/proc# cat /proc/ide/hdb/model 
FUJITSU MPE3064AT
Dhiggins:/proc# cat /proc/scsi/scsi 
Attached devices:
Host: scsi0 Channel: 00 Id: 06 Lun: 00
  Vendor: QUANTUM  Model: VIKING II 4.5WLS Rev: 4110
  Type:   Direct-Access                    ANSI SCSI revision: 02

Dhiggins:/proc# cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 7
model name      : Pentium III (Katmai)
stepping        : 3
cpu MHz         : 501.224
cache size      : 512 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 mmx fxsr sse
bogomips        : 991.23

Dhiggins:/proc# cat /proc/meminfo 
MemTotal:       255092 kB


please cc me any replies as i am not subscribed

[-- Attachment #2: kernconfig-2.4.6.gz --]
[-- Type: application/x-gzip, Size: 7714 bytes --]

[-- Attachment #3: kerncrash.gz --]
[-- Type: application/x-gzip, Size: 5531 bytes --]

                 reply	other threads:[~2003-08-29 19:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1062185320.603.13.camel@Dhiggins \
    --to=dhiggins@netc.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