mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Sambrook <jonathan.sambrook@dsvr.co.uk>
To: greg@kroah.com, Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	David Hinds <dhinds@sonic.net>
Cc: linux-kernel@vger.kernel.org
Subject: PCI subsystem related - kernel panic on boot
Date: Thu, 8 Jul 2004 20:36:34 +0100	[thread overview]
Message-ID: <20040708193634.GF3895@jsambrook> (raw)
In-Reply-To: <01F2769B-CF26-11D8-BFEC-000A956E7DA6@thomasrepro.com>

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

At 01:25 on Tue 06/07/04, afeldhacker@thomasrepro.com masquerading as 'Andrew Feldhacker' wrote:
> 
> Thanks so much for your replies; if there's anything else you might 
> need, please let me know.
> 
> --Andrew Feldhacker

I've been getting the same problem on a somewhat different setup (see
below for details).

However I've narrowed things down the situation where if I remove one
PCI card the machine boots. I replace it and get exactly the same crash
as Feldhacker.

The card in question in the CardBus bridge: Texas Instruments PCI1410 PC
card Cardbus Controller as listed below.

Of note is that recent 2.4 kernels have failed to set this card up
properly. Older 2.4's, up to 2.4.22 (or maybe 2.4.23 - untested) work
fine, but later ones misdetect the inserted Cardbus card.

Any suggestions on how to proceed welcome.

Anyhow, those details I mentioned:

$ cat /proc/cpuinfo    
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 8
model name      : AMD Athlon(TM) XP 1800+
stepping        : 1
cpu MHz         : 1529.402
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips        : 3053.97



$ lspci 
00:00.0 Host bridge: nVidia Corporation nForce CPU bridge 
00:00.1 RAM memory: nVidia Corporation nForce 220/420 Memory Controller
00:00.2 RAM memory: nVidia Corporation nForce 220/420 Memory Controller
00:00.3 RAM memory: nVidia Corporation: Unknown device 01aa 
00:01.0 ISA bridge: nVidia Corporation nForce ISA Bridge 
00:01.1 SMBus: nVidia Corporation nForce PCI System Management 
00:02.0 USB Controller: nVidia Corporation nForce USB Controller
00:03.0 USB Controller: nVidia Corporation nForce USB Controller
00:04.0 Ethernet controller: nVidia Corporation nForce Ethernet
Controller 
00:05.0 Multimedia audio controller: nVidia Corporation: Unknown device
01b0 
00:06.0 Multimedia audio controller: nVidia Corporation nForce Audio
00:08.0 PCI bridge: nVidia Corporation nForce PCI-to-PCI bridge 
00:09.0 IDE interface: nVidia Corporation nForce IDE 
00:1e.0 PCI bridge: nVidia Corporation nForce AGP to PCI Bridge 
01:06.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus
Controller 
01:08.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
02:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro
Ultra TF



Regards,
Jonathan

__
                   
 Jonathan Sambrook 
Software  Developer 
 Designer  Servers

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-07-08 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A6974D8E5F98D511BB910002A50A6647615FF248@hdsmsx403.hd.intel.com>
2004-07-06  2:28 ` 2.6 series kernels on HP Netserver LH4 " Len Brown
2004-07-06  6:14   ` Denis Vlasenko
2004-07-06  8:25     ` Andrew Feldhacker
2004-07-06 21:07       ` Jonathan Sambrook
2004-07-08 19:36       ` Jonathan Sambrook [this message]

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=20040708193634.GF3895@jsambrook \
    --to=jonathan.sambrook@dsvr.co.uk \
    --cc=dhinds@sonic.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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

all inboxes | Powered by JetHome®