From: Andrew Morton <akpm@linux-foundation.org>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
Date: Mon, 18 Feb 2008 05:00:49 -0800 [thread overview]
Message-ID: <20080218050049.12bcc596.akpm@linux-foundation.org> (raw)
In-Reply-To: <23590.97305.qm@web52910.mail.re2.yahoo.com>
On Sun, 17 Feb 2008 00:54:08 +0000 (GMT) Chris Rankin <rankincj@yahoo.com> wrote:
> [Try this again, except this time I'll force the attachment as inline text!]
>
> Hi,
>
> I have managed to boot 2.6.24.1 on this machine, with the NMI watchdog enabled, by using the
> "acpi=noirq" option. (There does seem to be some unhappiness with bridge symlinks in sysfs,
> though.)
>
> ...
>
> sysfs: duplicate filename 'bridge' can not be created
> WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
> Pid: 1, comm: swapper Not tainted 2.6.24.1 #1
> [<c0105020>] show_trace_log_lvl+0x1a/0x2f
> [<c0105990>] show_trace+0x12/0x14
> [<c010613d>] dump_stack+0x6c/0x72
> [<c01991bf>] sysfs_add_one+0x57/0xbc
> [<c0199e41>] sysfs_create_link+0xc2/0x10d
> [<c01bae9a>] pci_bus_add_devices+0xbd/0x103
> [<c034016c>] pci_legacy_init+0x56/0xe3
> [<c03274e1>] kernel_init+0x157/0x2c3
> [<c0104c83>] kernel_thread_helper+0x7/0x10
> =======================
> pci 0000:00:01.0: Error creating sysfs bridge symlink, continuing...
> sysfs: duplicate filename 'bridge' can not be created
> WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
> Pid: 1, comm: swapper Not tainted 2.6.24.1 #1
> [<c0105020>] show_trace_log_lvl+0x1a/0x2f
> [<c0105990>] show_trace+0x12/0x14
> [<c010613d>] dump_stack+0x6c/0x72
> [<c01991bf>] sysfs_add_one+0x57/0xbc
> [<c0199e41>] sysfs_create_link+0xc2/0x10d
> [<c01bae9a>] pci_bus_add_devices+0xbd/0x103
> [<c01bae82>] pci_bus_add_devices+0xa5/0x103
> [<c034016c>] pci_legacy_init+0x56/0xe3
> [<c03274e1>] kernel_init+0x157/0x2c3
> [<c0104c83>] kernel_thread_helper+0x7/0x10
> =======================
I have a vague feeling that this was fixed, perhaps in 2.6.24.x?
next prev parent reply other threads:[~2008-02-18 13:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 0:54 Linux 2.6.24.1 - kernel does not boot; IRQ trouble? Chris Rankin
2008-02-18 13:00 ` Andrew Morton [this message]
2008-02-18 13:16 ` Chris Rankin
2008-02-18 16:53 ` Stephen Hemminger
2008-02-18 19:42 ` Chris Rankin
2008-02-18 20:06 ` Stephen Hemminger
2008-02-19 8:47 ` Kay Sievers
2008-02-22 9:11 ` Kay Sievers
2008-02-22 9:41 ` Chris Rankin
2008-02-18 13:00 ` Andrew Morton
2008-02-18 13:13 ` Chris Rankin
2008-02-26 22:36 ` Chris Rankin
2008-02-26 23:40 ` Greg KH
2008-02-27 0:55 ` Chris Rankin
2008-02-27 2:52 ` Andrew Morton
2008-02-27 8:39 ` Chris Rankin
2008-03-02 2:43 ` Linux 2.6.24.1 - kernel does not boot; Solution! Chris Rankin
-- strict thread matches above, loose matches on Subject: below --
2008-02-08 23:41 Linux 2.6.24.1 - kernel does not boot; IRQ trouble? Chris Rankin
2008-02-08 23:31 Chris Rankin
2008-02-09 6:48 ` Greg KH
2008-02-09 12:06 ` Chris Rankin
2008-02-09 18:06 ` Greg KH
2008-02-09 18:22 ` Chris Rankin
2008-02-09 19:03 ` Oliver Pinter
2008-02-09 19:26 ` Chris Rankin
2008-02-17 0:42 ` Chris Rankin
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=20080218050049.12bcc596.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rankincj@yahoo.com \
--cc=shemminger@linux-foundation.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.