public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brad Cramer" <bcramer@callahanfuneralhome.com>
To: <root@chaos.analogic.com>
Cc: "'Guennadi Liakhovetski'" <g.liakhovetski@gmx.de>,
	"'Linux kernel'" <linux-kernel@vger.kernel.org>,
	<linux-scsi-owner@vger.kernel.org>
Subject: RE: sym53c8xx_2 driver and tekram dc-390u2w kernel-2.6.x
Date: Fri, 27 Feb 2004 10:12:22 -0500	[thread overview]
Message-ID: <008d01c3fd44$1d5ec760$6501a8c0@office> (raw)
In-Reply-To: <Pine.LNX.4.53.0402270955240.7189@chaos>

Sorry, yes I did rmmod the sym53c8xx driver before modprobeing the
sym53c8xx_2
Brad

-----Original Message-----
From: Richard B. Johnson [mailto:root@chaos.analogic.com] 
Sent: Friday, February 27, 2004 9:59 AM
To: Brad Cramer
Cc: 'Guennadi Liakhovetski'; Linux kernel; linux-scsi-owner@vger.kernel.org
Subject: RE: sym53c8xx_2 driver and tekram dc-390u2w kernel-2.6.x

On Fri, 27 Feb 2004, Brad Cramer wrote:

> OK, it took me some time, but here is what I did.
> I installed a debian kernel image (kernel_image-2.4.24-1-k7) to tell if
this
> was just a problem with the driver or because of the upgrade to kernel
2.6.x
> I the sym53c8xx and sym53c8xx_2 drivers are modules and this is what I
got.
>
> bigdaddy:~# modprobe sym53c8xx
> PCI: Found IRQ 11 for device 00:0f.0
> PCI: Sharing IRQ 11 with 00:0d.0
> PCI: Sharing IRQ 11 with 00:0d.1
[SNIPPED...everything was fine]

>
> and everything works fine, then when I do :
>

Did you `rmmod` the previos driver???  If not, you have
two drivers pounding on the same board, attempting to
handle the same disk(s). All bets are off.

> bigdaddy:~# modprobe sym53c8xx_2
[SNIPPED...]

Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.





  reply	other threads:[~2004-02-27 15:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 15:10 sym53c8xx_2 driver and tekram dc-390u2w kernel-2.6.x Brad Cramer
2004-02-13 22:39 ` Guennadi Liakhovetski
2004-02-17 16:23   ` Brad Cramer
2004-02-17 19:17     ` Guennadi Liakhovetski
2004-02-17 21:28       ` Brad Cramer
2004-02-17 23:42         ` Guennadi Liakhovetski
2004-02-18 14:44           ` Brad Cramer
2004-02-18 21:03             ` Guennadi Liakhovetski
2004-02-27 14:47               ` Brad Cramer
2004-02-27 14:59                 ` Richard B. Johnson
2004-02-27 15:12                   ` Brad Cramer [this message]
2004-02-28 18:02                 ` Guennadi Liakhovetski
2004-03-11 21:35                 ` Guennadi Liakhovetski

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='008d01c3fd44$1d5ec760$6501a8c0@office' \
    --to=bcramer@callahanfuneralhome.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi-owner@vger.kernel.org \
    --cc=root@chaos.analogic.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