public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Theurer <habanero@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: linux-acenic@SunSITE.dk
Subject: acenic problems on 2.5.47
Date: Mon, 11 Nov 2002 14:16:56 -0600	[thread overview]
Message-ID: <200211111416.56167.habanero@us.ibm.com> (raw)

I seem to be having a driver issue with acenic Gb adapters on 2.5.47.  Out of 
four adapters, usually one, but sometimes two of the four adapters are 
initialized upon 'insmod acenic':

acenic.c: v0.92 08/05/2002  Jes Sorensen, linux-acenic@SunSITE.dk
                            http://home.cern.ch/~jes/gige/acenic.html
eth1: Alteon AceNIC Gigabit Ethernet at 0xfba00000, irq 3
  Tigon II (Rev. 6), Firmware: 12.4.11, MAC: 00:60:cf:21:2a:78
  PCI cache line size set incorrectly (64 bytes) by BIOS/FW, correcting to 128
  PCI bus width: 64 bits, speed: 66MHz, latency: 240 clks
  Disabling PCI memory write and invalidate
eth1: Firmware NOT running!
eth1: Alteon AceNIC Gigabit Ethernet at 0xfbb00000, irq 4
  Tigon II (Rev. 6), Firmware: 12.4.11, MAC: 00:60:cf:21:2a:7c
  PCI cache line size set incorrectly (64 bytes) by BIOS/FW, correcting to 128
  PCI bus width: 64 bits, speed: 66MHz, latency: 240 clks
  Disabling PCI memory write and invalidate
eth1: Firmware NOT running!
eth1: Alteon AceNIC Gigabit Ethernet at 0xfbc00000, irq 10
  Tigon II (Rev. 6), Firmware: 12.4.11, MAC: 00:60:cf:21:27:df
  PCI cache line size set incorrectly (64 bytes) by BIOS/FW, correcting to 128
  PCI bus width: 64 bits, speed: 66MHz, latency: 240 clks
  Disabling PCI memory write and invalidate
eth1: Firmware NOT running!
eth1: Alteon AceNIC Gigabit Ethernet at 0xfbc04000, irq 11
  Tigon II (Rev. 6), Firmware: 12.4.11, MAC: 00:60:cf:21:27:e5
  PCI cache line size set incorrectly (64 bytes) by BIOS/FW, correcting to 128
  PCI bus width: 64 bits, speed: 66MHz, latency: 240 clks
  Disabling PCI memory write and invalidate
eth1: Firmware up and running


It appears the first three cards do not get the firmware up and running, while 
the fourth one does, and is assigned eth1.  I swear I have seen this before, 
but can't remember what the problem was.  Anybody know?  Also, an oops on 
rmmod:

Unable to handle kernel paging request at virtual address f8956140
f891b562
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0060:[<f891b562>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: f7c72000   ebx: 000003fc   ecx: 37d4a200   edx: f8956000
esi: f7c72160   edi: 00000100   ebp: f7c72000   esp: f6821f84
ds: 0068   es: 0068   ss: 0068
Stack: f891b000 fffffff0 f891b000 bfffe6fc c0116e53 f891b000 fffffff0 f6845000
       bfffe6fc c011639f f891b000 00000000 f6820000 0805fbf4 bfffe6dc c010874f
       bffff8f2 08067008 00000100 0805fbf4 bfffe6dc bfffe6fc 00000081 0000002b
Call Trace: [<c0116e53>]  [<c011639f>]  [<c010874f>]
Code: 8b 82 40 01 00 00 0d 00 00 01 00 89 82 40 01 00 00 83 7e 14

>>EIP; f891b562 <END_OF_CODE+384afc46/????>   <=====
Trace; c0116e52 <free_module+16/98>
Trace; c011639e <sys_delete_module+ea/1b0>
Trace; c010874e <syscall_call+6/a>
Code;  f891b562 <END_OF_CODE+384afc46/????>
00000000 <_EIP>:
Code;  f891b562 <END_OF_CODE+384afc46/????>   <=====
   0:   8b 82 40 01 00 00         mov    0x140(%edx),%eax   <=====
Code;  f891b568 <END_OF_CODE+384afc4c/????>
   6:   0d 00 00 01 00            or     $0x10000,%eax
Code;  f891b56c <END_OF_CODE+384afc50/????>
   b:   89 82 40 01 00 00         mov    %eax,0x140(%edx)
Code;  f891b572 <END_OF_CODE+384afc56/????>
  11:   83 7e 14 00               cmpl   $0x0,0x14(%esi)



Thanks,

Andrew Theurer

             reply	other threads:[~2002-11-11 20:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-11 20:16 Andrew Theurer [this message]
2002-11-11 20:26 ` acenic problems on 2.5.47 Jes Sorensen

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=200211111416.56167.habanero@us.ibm.com \
    --to=habanero@us.ibm.com \
    --cc=linux-acenic@SunSITE.dk \
    --cc=linux-kernel@vger.kernel.org \
    /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