From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Alexander Nyberg <alexn@telia.com>
Cc: linux-kernel@vger.kernel.org, bjorn.helgaas@hp.com
Subject: Re: 2.6.8.1-mm IRQ routing problems
Date: Mon, 23 Aug 2004 08:24:39 -0700 [thread overview]
Message-ID: <20040823082439.46c3c57b.rddunlap@osdl.org> (raw)
In-Reply-To: <1093088008.777.13.camel@boxen>
On Sat, 21 Aug 2004 13:33:28 +0200 Alexander Nyberg wrote:
| Using 2.6.8.1-mm3 I ran into some problems on x86_64. This
| only happens when fsck runs at bootup because in my case
| of the max-mount-count being reached (I use ext3). Booting
| with pci=routeirq makes problem go away.
|
| Do I win the weird problem prize?
Oops is fixed by this simple patch:
http://marc.theaimsgroup.com/?l=linux-kernel&m=109313574928853&w=2
| Loading modules...
| e1000
| e1000: Ignoring new-style parameters in presence of obsolete ones
| Intel(R) PRO/1000 Network Driver - version 5.3.19-k2-NAPI
| Copyright (c) 1999-2004 Intel Corporation.
| Unable to handle kernel paging request at 0000000000002000 RIP:
| <ffffffff8035f090>{add_pin_to_irq+0}
| PML4 3f55d067 PGD 3f77e067 PMD 0
| Oops: 0002 [1] SMP
| CPU 0
| Modules linked in: e1000
| Pid: 121, comm: modprobe Not tainted 2.6.8.1-mm3
| RIP: 0010:[<ffffffff8035f090>] <ffffffff8035f090>{add_pin_to_irq+0}
| RSP: 0018:000001003eff1d40 EFLAGS: 00010216
| RAX: 0000000000002000 RBX: 0000000000000012 RCX: 0000000000008000
| RDX: 0000000000000012 RSI: 0000000000000000 RDI: 0000000000000012
| RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
| R10: 0000000000000000 R11: ffffffff80232fa0 R12: 0000000000000001
| R13: 0000000000000001 R14: 0000000000000012 R15: 0000000000508b70
| FS: 0000002a95ac8380(0000) GS:ffffffff80351d40(0000) knlGS:0000000000000000
| CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
| CR2: 0000000000002000 CR3: 0000000000101000 CR4: 00000000000006e0
| Process modprobe (pid: 121, threadinfo 000001003eff0000, task 000001003f44aa50)
| Stack: ffffffff8011ac90 0000000000010000 0000000000000046 0000000000010000
| 010000000001a900 000001003ffda200 ffffffffa00115e8 0000000000000012
| 0000000000000001 0000000000000001
| Call Trace:<ffffffff8011ac90>{io_apic_set_pci_routing+160} <ffffffff80118b68>{acpi_register_gsi+104}
| <ffffffff801e8688>{acpi_pci_irq_enable+413} <ffffffff801cbe26>{pci_enable_device_bars+38}
| <ffffffff801cbe55>{pci_enable_device+21} <ffffffffa001408a>{:e1000:e1000_probe+42}
| <ffffffff80185346>{d_rehash+118} <ffffffff801cca8f>{pci_device_probe+111}
| <ffffffff8020afd7>{bus_match+71} <ffffffff8020b0fb>{driver_attach+75}
| <ffffffff8020b490>{bus_add_driver+144} <ffffffff801cc8ce>{pci_register_driver+62}
| <ffffffffa001403e>{:e1000:e1000_init_module+62} <ffffffff8014abb9>{sys_init_module+281}
| <ffffffff8010e25e>{system_call+126}
|
| Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
| RIP <ffffffff8035f090>{add_pin_to_irq+0} RSP <000001003eff1d40>
| CR2: 0000000000002000
--
~Randy
next prev parent reply other threads:[~2004-08-23 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 11:33 Alexander Nyberg
2004-08-23 15:24 ` Randy.Dunlap [this message]
[not found] ` <20040822180911.22bbbc96.akpm@osdl.org>
[not found] ` <1093264936.834.1.camel@boxen>
2004-08-23 16:16 ` Bjorn Helgaas
2004-08-23 18:45 ` Alexander Nyberg
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=20040823082439.46c3c57b.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=alexn@telia.com \
--cc=bjorn.helgaas@hp.com \
--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®