RE: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda

2001-04-29 Thread Steve 'Denali'; McKnelly

Ahh... It doesn't even get that far... It just dies with the
undefined symbols...

-Original Message-
From: David Relson [mailto:[EMAIL PROTECTED]]
Sent: Sunday, April 29, 2001 11:32 AM
To: Steve 'Denali' McKnelly
Cc: Linux-Kernel mailing list
Subject: RE: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect
sda


At 12:17 PM 4/29/01, Steve 'Denali' McKnelly wrote:
>Howdy J.A.,
>
> Let me ask a possibly stupid question... How do you tell
>what version of the Gibbs Adaptec driver you're using?  Did I
>misunderstand you when you said the 2.4.4 kernel is using 6.1.5?
>Also, did I understand you to say the 6.1.12 version will fix
>my unresolved symbol problem?
>
>Thanks,
>Steve

Steve,

A message saying (roughly) AIC7XXX 6.1.xxx appears while the kernel is 
loading.  You can also grep the aic7xxx.c source file or run the strings 
command ( strings /lib/modules/2.4.4/kernel/drivers/scsi/aic7xxx ).

I'm not sure about your undefined symbols problem, but I was able to build 
2.4.4 with 6.1.11 with no trouble.

David


David Relson   Osage Software Systems, Inc.
[EMAIL PROTECTED]   Ann Arbor, MI 48103
www.osagesoftware.com  tel:  734.821.8800

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



RE: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda

2001-04-29 Thread Steve 'Denali'; McKnelly

Howdy J.A.,

Let me ask a possibly stupid question... How do you tell
what version of the Gibbs Adaptec driver you're using?  Did I
misunderstand you when you said the 2.4.4 kernel is using 6.1.5?
Also, did I understand you to say the 6.1.12 version will fix
my unresolved symbol problem?

Thanks,
Steve

-Original Message-
From: J . A . Magallon [mailto:[EMAIL PROTECTED]]
Sent: Sunday, April 29, 2001 5:26 AM
To: Steve 'Denali' McKnelly
Cc: Matthias Andree; Linux-Kernel mailing list
Subject: Re: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect
sda



On 04.29 Steve 'Denali' McKnelly wrote:
>  Command found on device queue
> aic7xxx_abort returns 8194
>

I have seen blaming for this error to aic7xxx new driver prior to version
6.1.11. It was included in the 2.4.3-ac series, but its has not got into
main 2.4.4 (there is still 6.1.5). Everything needs its time.

Grab the updated patch from people.freebsd.org/~gibbs/linux.

BTW (Alan?) new version is 6.1.12 (just patched 2.4.4 after offset
engineering and works fine).
Candidate for 2.4.4-ac1 or 2.4.5-pre1 ?

--
J.A. Magallon  #  Let the source
mailto:[EMAIL PROTECTED]  #  be with you,
Luke...

Linux werewolf 2.4.4 #1 SMP Sat Apr 28 11:45:02 CEST 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



RE: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda

2001-04-29 Thread Steve 'Denali'; McKnelly

Howdy Matthias,

Well, under 2.4.4, I can't even get the driver to load due to unresolved
symbols... So I know I won't be much help... :-(

Later,
Steve

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Matthias Andree
Sent: Saturday, April 28, 2001 1:22 PM
To: Linux-Kernel mailing list
Subject: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda


Hi,

I have several machines here, with either onboard aic7880 or with
AHA2940 (I don't recall) sitting on the PCI bus, which share the same
problem: they fail to detect the first disk (Id #0). The information
below is from lspci and /proc/scsi/scsi of Linux 2.2.19, in that order,
all Kernels have been compiled on a Duron/800 SuSE 7.0 Linux box
(running gcc 2.95.2).

Machine #1:

Pentium-II (Klamath)

00:09.0 SCSI storage controller: Adaptec AIC-7881U

Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: SEAGATE  Model: ST34572W Rev: 0718
  Type:   Direct-AccessANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 00
  Vendor: SEAGATE  Model: ST39140W Rev: 1498
  Type:   Direct-AccessANSI SCSI revision: 02

Machine #2:

Pentium-II (Deschutes)

00:09.0 SCSI storage controller: Adaptec AIC-7881U

Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: SEAGATE  Model: ST34572N Rev: 0784
  Type:   Direct-AccessANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: IBM  Model: DCAS-32160   Rev: S65A
  Type:   Direct-AccessANSI SCSI revision: 02

These have further devices (CD writer, CD-ROM drive), and these machines
are 100% in 2.2.19. With 2.4.3 and 2.4.4-pre8, I get this problem
(pencil & paper copy for Machine #2, DO NOT "grep"):

AIC 7XXX EISA/VLB/PCI SCSI HBA DRIVER 6.1.5
aic7880: wide Channel A, SCSI ID=7, 16/255 SCBs
scsi0: SCSI host adapter emulation for IDE devices
PCI: found IRQ 5 for dev 00:09.0
scsi1:0:0:0: Attempting to queue an abort message.
 Command found on device queue
aic7xxx_abort returns 8194

Then, the Kernel detects the SECOND SCSI disk and attaches it as sda
(Linux 2.2 would mount that as sdb), the first disk is "gone" (Linux 2.2
would mount that as sda).  Regretfully, my root partition is on the
FIRST SCSI disk, so the kernel panicks since it cannot mount /.

That's all I copied in a hurry, maybe it's sufficient to debug, if not,
I can try to grab a null modem cable and catch the full sequence; I'd be
glad if someone could mention the "canonical" aic7xxx LILO append
parameters for a full debug trace in that case.

Bottom line: I'm not buying Adaptec SCSI host adaptors ever again.

--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



RE: Motherboard Misdetect

2001-02-05 Thread Steve 'Denali'; McKnelly

Howdy Alan,

I won't disagree with what you and David are saying.  I
took a look at the picture of the 6KD, and they're similar.
Main difference is missing SCSI connectors and an extra long
PCI slot (on the 6KD).

Thanks!

Steve

-Original Message-
From: Alan Cox [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 5:46 AM
To: Steve 'Denali' McKnelly
Cc: [EMAIL PROTECTED]
Subject: Re: Motherboard Misdetect


>   I own a M-Technology M-668DS motherboard.  Linux 2.4.1
>   identifies my board as a Soyo SY-6KD.  They're not really
>   the same board, and they each have features the other doesn't

We read the data from the BIOS. Its actually only scanned to match against
known system bugs so won't be a problem. It sounds like they are using the
same bios image on a set of boards and didnt bother to fix the name.

It may well also be they are the same board minus a few components.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Motherboard Misdetect

2001-02-04 Thread Steve 'Denali'; McKnelly

Howdy everyone,

I own a M-Technology M-668DS motherboard.  Linux 2.4.1
identifies my board as a Soyo SY-6KD.  They're not really
the same board, and they each have features the other doesn't
have. (The 668DS has onboard SCSI, where as the 6KD doesn't.
The 6KD can be upgraded for I20 compatibiliy, whereas the 668DS
can't.)

Is this going to be a problem for me?  I will admit to knowing
nothing about kernel programming, but I'm willing to help
in any way.  Below is a copy of my dmesg output.

Thanks,
Steve

[root@shadowforge denali]: dmesg
achine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0183fbff   
CPU: After generic, caps: 0183fbff   
CPU: Common caps: 0183fbff   
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.37 (20001109) Richard Gooch ([EMAIL PROTECTED])
mtrr: detected mtrr type: Intel
CPU: Before vendor init, caps: 0183fbff  , vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0183fbff   
CPU: After generic, caps: 0183fbff   
CPU: Common caps: 0183fbff   
CPU0: Intel Pentium II (Deschutes) stepping 02
per-CPU timeslice cutoff: 1463.01 usecs.
Getting VERSION: 40011
Getting VERSION: 40011
Getting ID: 0
Getting ID: f00
Getting LVT0: 700
Getting LVT1: 400
enabled ExtINT on CPU#0
ESR value before enabling vector: 0004
ESR value after enabling vector: 
CPU present map: 1
Before bogomips.
Error: only one processor found.
Boot done.
ENABLING IO-APIC IRQs
...changing IO-APIC physical APIC ID to 2 ... ok.
Synchronizing Arb IDs.
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-18, 2-20, 2-21, 2-22, 2-23 not connected.
..TIMER: vector=49 pin1=2 pin2=0
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...
. (found pin 0) ...works.
activating NMI Watchdog ... done.
number of MP IRQ sources: 21.
number of IO-APIC #2 registers: 24.
testing the IO APIC...

IO APIC #2..
 register #00: 0200
...: physical APIC id: 02
 register #01: 00170011
... : max redirection entries: 0017
... : IO APIC version: 0011
 register #02: 
... : arbitration: 00
 IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
 00 001 01  000   0   01131
 01 001 01  000   0   01139
 02 000 00  100   0   00000
 03 001 01  000   0   01141
 04 001 01  000   0   01149
 05 001 01  000   0   01151
 06 001 01  000   0   01159
 07 001 01  000   0   01161
 08 001 01  000   0   01169
 09 001 01  000   0   01171
 0a 001 01  000   0   01179
 0b 001 01  000   0   01181
 0c 001 01  000   0   01189
 0d 000 00  100   0   00000
 0e 001 01  000   0   01191
 0f 001 01  000   0   01199
 10 001 01  110   1   011A1
 11 001 01  110   1   011A9
 12 000 00  100   0   00000
 13 001 01  110   1   011B1
 14 000 00  100   0   00000
 15 000 00  100   0   00000
 16 000 00  100   0   00000
 17 000 00  100   0   00000
IRQ to pin mappings:
IRQ0 -> 2
IRQ1 -> 1
IRQ3 -> 3
IRQ4 -> 4
IRQ5 -> 5
IRQ6 -> 6
IRQ7 -> 7
IRQ8 -> 8
IRQ9 -> 9
IRQ10 -> 10
IRQ11 -> 11
IRQ12 -> 12
IRQ13 -> 13
IRQ14 -> 14
IRQ15 -> 15
IRQ16 -> 16
IRQ17 -> 17
IRQ19 -> 19
 done.
calibrating APIC timer ...
. CPU clock speed is 300.6844 MHz.
. host bus clock speed is 66.8185 MHz.
cpu: 0, clocks: 668185, slice: 334092
CPU0
Setting commenced=1, go go go
PCI: PCI BIOS revision 2.10 entry at 0xfdba1, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
PCI->APIC IRQ transform: (B0,I7,P3) -> 19
PCI->APIC IRQ transform: (B0,I11,P0) -> 16
PCI->APIC IRQ transform: (B0,I13,P0) -> 17
PCI->APIC IRQ transform: (B1,I0,P0) -> 16
Limiting direct PCI/PCI transfers.
isapnp: Scanning for Pnp cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
DMI 2.0 present.
34 structures occupying 820 bytes.
DMI table at 0x000F748B.
BIOS Vendor: American Megatrends, Inc.
BIOS Version: 0627
BIOS Release: 07/15/95
Board Vendor: SOYO Computer Inc