All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: bero@arklinux.org, Thomas.Duffy.99@alumni.brown.edu
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: [PATCH] 2.6.8.1 modprobe tg3 oopses
Date: Sat, 21 Aug 2004 17:36:54 -0700	[thread overview]
Message-ID: <20040821173654.6e5b9982.rddunlap@osdl.org> (raw)
In-Reply-To: <20040820161141.28043ee8.rddunlap@osdl.org>


| Subject: 2.6.8.1 "modprobe tg3" oopses with gcc 3.4.1
| 
| 
| 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):

I wouldn't expect this to be compiler-dependent.  There's an obvious
problem with add_pin_to_irq().  It shouldn't be __init.  Patch below.
(I thought that I had already mailed this one time, but I don't
see it anywhere.)

| CPU:    0
| EIP:    0060:[<c03ba270>]    Not tainted VLI
| EFLAGS: 00210216   (2.6.8-1ark)
| EIP is at add_pin_to_irq+0x0/0x60     <<<<< code is gone

--

add_pin_to_irq() should not be __init; it is used after init code.

Signed-off-by: Randy Dunlap <rddunlap@osdl.org>

diffstat:=
 arch/i386/kernel/io_apic.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -Naurp ./arch/i386/kernel/io_apic.c~ioapic_non_init ./arch/i386/kernel/io_apic.c
--- ./arch/i386/kernel/io_apic.c~ioapic_non_init	2004-08-14 03:55:10.000000000 -0700
+++ ./arch/i386/kernel/io_apic.c	2004-08-21 17:26:52.695599728 -0700
@@ -85,7 +85,7 @@ int vector_irq[NR_VECTORS] = { [0 ... NR
  * shared ISA-space IRQs, so we have to support them. We are super
  * fast in the common case, and fast for shared ISA-space IRQs.
  */
-static void __init add_pin_to_irq(unsigned int irq, int apic, int pin)
+static void add_pin_to_irq(unsigned int irq, int apic, int pin)
 {
 	static int first_free_entry = NR_IRQS;
 	struct irq_pin_list *entry = irq_2_pin + irq;

       reply	other threads:[~2004-08-22  0:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040820161141.28043ee8.rddunlap@osdl.org>
2004-08-22  0:36 ` Randy.Dunlap [this message]
2004-08-23 22:57   ` [PATCH] 2.6.8.1 modprobe tg3 oopses Thomas Duffy

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=20040821173654.6e5b9982.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=Thomas.Duffy.99@alumni.brown.edu \
    --cc=akpm@osdl.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.