public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* I2O and Promise SuperTrak SX6000 Kernel Oops
@ 2002-01-08 16:41 Sebastian Zimmermann
  0 siblings, 0 replies; only message in thread
From: Sebastian Zimmermann @ 2002-01-08 16:41 UTC (permalink / raw)
  To: linux-kernel

Thanks to everyone that helped us with i2o and the Promise SuperTrak 
SX6000. However, there is still something strange that we cannot fix:

When the system is powered up, the SuperTrak BIOS is initializing the 
adapter. If we manually *abort* the initialization, Linux will boot 
without problems and we can use the hardware raid.

However, if we let the controller initialze the adapter (that is the 
default), the kernel will always Oops when I2O is loaded:

Oops: 0000
Call Trace: 
[<c01f7fd6>][<c0107d6d>][<c0107ed6>][<c0105150>][<c0105150>][<c0109d48>][<c0105150>][<c0105150>][<c0105173>][<c01051d9>][<c0105000>][<c0105027>]
Warning (Oops_read): Code line not seen, dumping what data is available

Trace; c01f7fd6 <i2o_pci_interrupt+a/14>
Trace; c0107d6c <handle_IRQ_event+30/5c>
Trace; c0107ed6 <do_IRQ+6a/a8>
Trace; c0105150 <default_idle+0/28>
Trace; c0105150 <default_idle+0/28>
Trace; c0109d48 <call_do_IRQ+6/e>
Trace; c0105150 <default_idle+0/28>
Trace; c0105150 <default_idle+0/28>
Trace; c0105172 <default_idle+22/28>
Trace; c01051d8 <cpu_idle+40/54>
Trace; c0105000 <_stext+0/0>
Trace; c0105026 <rest_init+26/28>


Please help ;-)

Sebastian

P.S.: this happens with all kernels that we tried (2.4.7, 2.4.9, 2.4.14, 
2.4.17)


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-01-08 16:41 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-08 16:41 I2O and Promise SuperTrak SX6000 Kernel Oops Sebastian Zimmermann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox