public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
* 2.6.6 Kernel + Adaptec aic7890/91 = Kernel panic
@ 2004-06-06 11:55 Ralph Bergmann
       [not found] ` <166998953.1086771720@stonetable>
  0 siblings, 1 reply; 3+ messages in thread
From: Ralph Bergmann @ 2004-06-06 11:55 UTC (permalink / raw)
  To: linux-scsi

Hello!

If I use the 2.6.6 kernel, I get a "Kernel panic" when starting.

I use a Debian unstable, last update 31.Mai 2004.

Kernel:
kernel-image-2.6.6-1-686-smp

System:
0000:00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 05)
0000:00:00.1 Host bridge: ServerWorks CNB20LE Host Bridge (rev 05)
0000:00:01.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge 
(non-transparent mode) (rev 13)
0000:00:04.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 01)
0000:00:06.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 
100] (rev 08)
0000:00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 4f)
0000:00:0f.1 IDE interface: ServerWorks OSB4 IDE Controller
0000:00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller 
(rev 04)
0000:01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 
AGP (rev 85)
0000:02:01.0 SCSI storage controller: Adaptec AHA-2940U2/U2W

Error-Message:
SCSI subsystem initialized
FATAL: Error inserting aic7xxx 
(/lib/modules/2.6.6-1-686-smp/kernel/drivers/scsi/aic7xxx/aic7xxx.ko) Nu 
such device
pivot_root: No such file or directory
/sbin/init: 424: cannot open dev/console: No such file
Kernel panic: Attempted to kill init!

The kernel-image-2.4.25-1-686-smp works fine.

Does someone have an idea?

Ralph


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.6.6 Kernel + Adaptec aic7890/91 = Kernel panic
       [not found]     ` <123170000.1086819395@aslan.scsiguy.com>
@ 2004-08-04 19:53       ` Ralph Bergmann
  2004-08-04 21:41         ` Luben Tuikov
  0 siblings, 1 reply; 3+ messages in thread
From: Ralph Bergmann @ 2004-08-04 19:53 UTC (permalink / raw)
  To: Justin T. Gibbs; +Cc: luben_tuikov, linux-scsi

Justin T. Gibbs wrote:

>>Justin T. Gibbs wrote:
>>
>>
>>>...  Can you provide the output of
>>>"lspci -vv -n" which will indicate the PCI ID information of your
>>>controller?
>>
>>
>>yes of course
>>
>>0000:02:01.0 Class 0100: 9005:0010
>>         Subsystem: 9005:a180
> 
> 
> Hmm.  Those IDs should be supported in the driver.  Can you add
> printk statements in aic7xxx_osm_pci.c just before each location
> where the driver returns "-ENODEV".  This should help narrow down
> why the driver is refusing to attach to the controller.  If I
> had to guess, I would say that pci_enable_device() is failing for
> some strange reason.
> 
> --
> Justin
> 

First of all I have to excuse, because you have to wait so long for my 
answer. But I've got good news: the problem is partially fixed. I put 
the scsi-adapter in another pci-slot (now a 32bit one in contradiction 
to the 64bit one I used before), and now it's working. But I've got some 
questions concerning this:

1. should it have worked, no matter, which kind of pci-slot I use? When 
i used the 2.4 kernel, there were no error-messages, but when i switched 
to 2.6 kernel, I run into trouble as you know... So is it a 
kernel-problem or a hardware-thing?

2. And if you want to have the specific output nevertheless,  I would 
prefer, that you send me the special adjusted file I have to use, 
because I have no idea about kernel-programming at all...

Ralph

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.6.6 Kernel + Adaptec aic7890/91 = Kernel panic
  2004-08-04 19:53       ` Ralph Bergmann
@ 2004-08-04 21:41         ` Luben Tuikov
  0 siblings, 0 replies; 3+ messages in thread
From: Luben Tuikov @ 2004-08-04 21:41 UTC (permalink / raw)
  To: Ralph Bergmann; +Cc: Justin T. Gibbs, linux-scsi

Taken off linux-scsi.

Ralph Bergmann wrote:
> Justin T. Gibbs wrote:
> 
>  >>Justin T. Gibbs wrote:
>  >>
>  >>
>  >>>...  Can you provide the output of
>  >>>"lspci -vv -n" which will indicate the PCI ID information of your
>  >>>controller?
>  >>
>  >>
>  >>yes of course
>  >>
>  >>0000:02:01.0 Class 0100: 9005:0010
>  >>         Subsystem: 9005:a180
>  >
>  >
>  > Hmm.  Those IDs should be supported in the driver.  Can you add
>  > printk statements in aic7xxx_osm_pci.c just before each location
>  > where the driver returns "-ENODEV".  This should help narrow down
>  > why the driver is refusing to attach to the controller.  If I
>  > had to guess, I would say that pci_enable_device() is failing for
>  > some strange reason.
>  >
>  > --
>  > Justin
>  >
> 
> First of all I have to excuse, because you have to wait so long for my
> answer. But I've got good news: the problem is partially fixed. I put
> the scsi-adapter in another pci-slot (now a 32bit one in contradiction
> to the 64bit one I used before), and now it's working. But I've got some
> questions concerning this:
> 
> 1. should it have worked, no matter, which kind of pci-slot I use? When
> i used the 2.4 kernel, there were no error-messages, but when i switched
> to 2.6 kernel, I run into trouble as you know... So is it a
> kernel-problem or a hardware-thing?
> 
> 2. And if you want to have the specific output nevertheless,  I would
> prefer, that you send me the special adjusted file I have to use,
> because I have no idea about kernel-programming at all...
> 
> Ralph
> 

-- 
Luben



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-08-04 21:41 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-06-06 11:55 2.6.6 Kernel + Adaptec aic7890/91 = Kernel panic Ralph Bergmann
     [not found] ` <166998953.1086771720@stonetable>
     [not found]   ` <40C76B6F.3010103@dasralph.de>
     [not found]     ` <123170000.1086819395@aslan.scsiguy.com>
2004-08-04 19:53       ` Ralph Bergmann
2004-08-04 21:41         ` Luben Tuikov

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