From: Marc Schiffbauer <marc.schiffbauer@links2linux.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: new aic7xxx oopses with AHA2940
Date: Sat, 26 May 2001 18:05:29 +0200 [thread overview]
Message-ID: <20010526180529.A7595@lisa.links2linux.home> (raw)
Hi *,
I have problems with the new aic7xxx-Driver. These problems exist
with vanilla (2.4.4, 2.5.5, other d.k.) and -ac
When I built it into the Kernel, it will panic on boot when it tries
to access the adapter.
Built as modules it segfaults when i try to insmod (modprobe) it,
following this Oops in messages:
May 26 17:52:33 homer kernel: PCI: Found IRQ 9 for device 00:0d.0
May 26 17:52:33 homer kernel: PCI: The same IRQ used for device 00:04.2
May 26 17:52:33 homer kernel: PCI: The same IRQ used for device 00:04.3
May 26 17:52:33 homer kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
May 26 17:52:33 homer kernel: printing eip:
May 26 17:52:33 homer kernel: e0a7b3a7
May 26 17:52:33 homer kernel: *pde = 00000000
May 26 17:52:33 homer kernel: Oops: 0000
May 26 17:52:33 homer kernel: CPU: 0
May 26 17:52:33 homer kernel: EIP: 0010:[usbcore:usb_devfs_handle_Re9c5f87f+161255/198895517]
May 26 17:52:33 homer kernel: EFLAGS: 00010096
May 26 17:52:33 homer kernel: eax: 00000041 ebx: 00000000 ecx: dd5d6e00 edx: 00000000
May 26 17:52:33 homer kernel: esi: 00000000 edi: 000000ff ebp: dd5d6e00 esp: dd165cbc
May 26 17:52:33 homer kernel: ds: 0018 es: 0018 ss: 0018
May 26 17:52:33 homer kernel: Process modprobe (pid: 766, stackpage=dd165000)
May 26 17:52:33 homer kernel: Stack: 00000000 00000000 000000ff dd5d6e00 41000357 e0a7b79d dd5d6e00 00000000
May 26 17:52:33 homer kernel: ffffffff 00000041 ffffffff 000000ff 00000000 00000041 00000000 dd5d6e00
May 26 17:52:33 homer kernel: dd5d6e00 00000001 00000001 00000001 00000001 00000001 00000000 00000001
May 26 17:52:33 homer kernel: Call Trace: [usbcore:usb_devfs_handle_Re9c5f87f+162269/198894503] [usbcore:usb_devfs_handle_Re9c5f87f+164966/198891806] [__delay+19/48] [usbcore:usb_devfs_handle_Re9c5f87f+166493/198890279] [usbcore:usb_devfs_handle_Re9c5f87f+117712/198939060] [usbcore:usb_devfs_handle_Re9c5f87f+185577/198871195] [usbcore:usb_devfs_handle_Re9c5f87f+171751/198885021]
May 26 17:52:33 homer kernel: [rpc_new_task+240/368] [usbcore:usb_devfs_handle_Re9c5f87f+113534/198943238] [usbcore:usb_devfs_handle_Re9c5f87f+150165/198906607] [usbcore:usb_devfs_handle_Re9c5f87f+113361/198943411] [usbcore:usb_devfs_handle_Re9c5f87f+113392/198943380] [usbcore:usb_devfs_handle_Re9c5f87f+201920/198854852] [pci_announce_device+28/80] [usbcore:usb_devfs_handle_Re9c5f87f+202048/198854724]
May 26 17:52:33 homer kernel: [usbcore:usb_devfs_handle_Re9c5f87f+202144/198854628] [pci_register_driver+68/96] [usbcore:usb_devfs_handle_Re9c5f87f+202144/198854628] [usbcore:usb_devfs_handle_Re9c5f87f+201920/198854852] [usbcore:usb_devfs_handle_Re9c5f87f+125626/198931146] [usbcore:usb_devfs_handle_Re9c5f87f+113038/198943734] [usbcore:usb_devfs_handle_Re9c5f87f+201920/198854852] [usbcore:usb_devfs_handle_Re9c5f87f+111272/198945500]
May 26 17:52:33 homer kernel: [scsi_register_host+73/720] [usbcore:usb_devfs_handle_Re9c5f87f+201920/198854852] [usbcore:usb_devfs_handle_Re9c5f87f+201920/198854852] [usbcore:usb_devfs_handle_Re9c5f87f+111272/198945500] [usbcore:usb_devfs_handle_Re9c5f87f+111168/198945604] [usbcore:usb_devfs_handle_Re9c5f87f+111272/198945500] [scsi_register_module+45/96] [usbcore:usb_devfs_handle_Re9c5f87f+201920/198854852]
May 26 17:52:33 homer kernel: [usbcore:usb_devfs_handle_Re9c5f87f+111168/198945604] [usbcore:usb_devfs_handle_Re9c5f87f+125206/198931566] [usbcore:usb_devfs_handle_Re9c5f87f+201920/198854852] [sys_init_module+1277/1440] [eepro100:__insmod_eepro100_O/lib/modules/2.4.5/kernel/drivers/net/ee+0/96] [usbcore:usb_devfs_handle_Re9c5f87f+111264/198945508] [system_call+51/56]
May 26 17:52:33 homer kernel:
May 26 17:52:33 homer kernel: Code: 8b 02 8b 7c 24 20 8b 6c 24 28 0f b6 40 19 f6 81 f0 00 00 00
Does it crash with the USB-Driver?? But USB works fine... even after
the Oops
BTW: The old aic7xxx-Driver works fine for me
Devices connected to the adapter:
- teac CDR
- old plextor cdrom
- ibm 4G HD
System is an AMD Thunderbird 800, 512MB, ASUS A7V
Do you need any further information?
Cheers
-Marc
--
| |
| |
| http://www.links2linux.de <-- Von Linux-Usern fuer Linux-User |
next reply other threads:[~2001-05-26 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-26 16:05 Marc Schiffbauer [this message]
2001-05-27 1:07 ` Keith Owens
2001-05-27 2:21 ` Marc Schiffbauer
2001-05-27 2:32 ` Keith Owens
2001-05-27 2:36 ` Jeff Garzik
2001-05-27 10:41 ` Marc Schiffbauer
2001-05-29 18:55 ` Justin T. Gibbs
2001-05-29 22:26 ` Marc Schiffbauer
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=20010526180529.A7595@lisa.links2linux.home \
--to=marc.schiffbauer@links2linux.de \
--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
all inboxes | Powered by JetHome®