From: Thomas Duffy <Thomas.Duffy.99@alumni.brown.edu>
To: bero@arklinux.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8.1 "modprobe tg3" oopses with gcc 3.4.1
Date: Fri, 20 Aug 2004 09:38:43 -0700 [thread overview]
Message-ID: <1093019923.20094.14.camel@duffman> (raw)
In-Reply-To: <200408201148.48206.bero@arklinux.org>
[-- Attachment #1: Type: text/plain, Size: 2388 bytes --]
On Fri, 2004-08-20 at 11:48 +0000, bero@arklinux.org wrote:
> I get this when trying to modprobe tg3 on an Acer Aspire 1500 notebook (32bit
> mode) when the kernel [tried 2.6.8.1 and 2.6.8.1-mm1] is compiled with gcc
> 3.4.1 (3.3.4 works):
This looks like a similar oops I reported yesterday. Although I was
using gcc 3.3.3 in 64 bit x86_64 and modprobe'ing ehci_hcd:
CPU 0
Modules linked in: ehci_hcd button battery asus_acpi ac xfs qla2322 qla2xxx scsi_transport_fc sd_mod scsi_mod
Pid: 507, comm: modprobe Not tainted 2.6.8.1-mm2
RIP: 0010:[<ffffffff8048eb81>] <ffffffff8048eb81>{add_pin_to_irq+1}
RSP: 0018:00000100cf245d00 EFLAGS: 00000212
RAX: 0000000000000089 RBX: 0000000000000017 RCX: 0000000000000080
RDX: 0000000000000017 RSI: 0000000000000000 RDI: 0000000000000017
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000017 R15: 0000000000000000
FS: 0000002a9557b4c0(0000) GS:ffffffff8047ef80(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000420f30 CR3: 0000000000101000 CR4: 00000000000006e0
Process modprobe (pid: 507, threadinfo 00000100cf244000, task 000001007f0ceee0)
Stack: ffffffff80120778 0000000000000000 0000000000000000 0000000000000000
0100000000018900 0000000000000000 ffffffff80219834 0000000000000017
0000000000000001 0000000000000000
Call Trace:<ffffffff80120778>{io_apic_set_pci_routing+152} <ffffffff80219834>{acpi_pci_link_allocate+266}
<ffffffff8011c7e8>{acpi_register_gsi+104} <ffffffff80219db8>{acpi_pci_irq_lookup+59}
<ffffffff80219f95>{acpi_pci_irq_enable+265} <ffffffff802bcee6>{pcibios_enable_device+22}
<ffffffff801f7746>{pci_enable_device_bars+38} <ffffffff801f7775>{pci_enable_device+21}
<ffffffff8029eb26>{usb_hcd_pci_probe+70} <ffffffff801bde59>{sysfs_make_dirent+41}
<ffffffff801f8dfd>{pci_device_probe_static+61} <ffffffff801f8e59>{__pci_device_probe+41}
<ffffffff801f8eb0>{pci_device_probe+48} <ffffffff80245d97>{bus_match+71}
<ffffffff80245eb6>{driver_attach+70} <ffffffff80246385>{bus_add_driver+133}
<ffffffff801f9179>{pci_register_driver+121} <ffffffffa00fd01d>{:ehci_hcd:init+29}
<ffffffff80154c1e>{sys_init_module+270} <ffffffff8011194a>{system_call+126}
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-20 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 11:48 2.6.8.1 "modprobe tg3" oopses with gcc 3.4.1 bero
2004-08-20 16:38 ` Thomas Duffy [this message]
2004-08-20 20:23 ` Jeff Garzik
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=1093019923.20094.14.camel@duffman \
--to=thomas.duffy.99@alumni.brown.edu \
--cc=bero@arklinux.org \
--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