Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
--- Kay Sievers <[EMAIL PROTECTED]> wrote: > Greg, > it seems that: > arch/x86/pci/legacy.c :: pci_legacy_init() > > tries to create already created "bridge" symlinks in 2.6.24. So we > discover the same devices twice? Can this be a reason for the hang? No, it can't be because it's *not* hanging in this configuration :-). It hangs when I *don't* add the acpi=noirq option, whereas here it's just adding noise to the dmesg log. (I'm guessing Linux doesn't call pci_legacy_init() when ACPI takes charge of the IRQs.) Cheers, Chris __ Sent from Yahoo! Mail. A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
On Tue, Feb 19, 2008 at 9:47 AM, Kay Sievers <[EMAIL PROTECTED]> wrote: > On Feb 18, 2008 9:06 PM, Stephen Hemminger <[EMAIL PROTECTED]> wrote: > > On Mon, 18 Feb 2008 19:42:25 + (GMT) > > Chris Rankin <[EMAIL PROTECTED]> wrote: > > > > > --- Stephen Hemminger <[EMAIL PROTECTED]> wrote: > > > > > > 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 > > > > > > [] show_trace_log_lvl+0x1a/0x2f > > > > > > [] show_trace+0x12/0x14 > > > > > > [] dump_stack+0x6c/0x72 > > > > > > [] sysfs_add_one+0x57/0xbc > > > > > > [] sysfs_create_link+0xc2/0x10d > > > > > > [] pci_bus_add_devices+0xbd/0x103 > > > > > > [] pci_legacy_init+0x56/0xe3 > > > > > > [] kernel_init+0x157/0x2c3 > > > > > > [] kernel_thread_helper+0x7/0x10 > > > > > > === > > > > > > pci :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() Greg, it seems that: arch/x86/pci/legacy.c :: pci_legacy_init() tries to create already created "bridge" symlinks in 2.6.24. So we discover the same devices twice? Can this be a reason for the hang? I guess in 2.6.25, the warning is gone with: commit fd7d1ced29e5beb88c9068801da7a362606d8273 Author: Greg Kroah-Hartman <[EMAIL PROTECTED]> Date: Tue May 22 22:47:54 2007 -0400 PCI: make pci_bus a struct device This moves the pci_bus class device to be a real struct device and at the same time, place it in the device tree in the correct location. Note, the old "bridge" symlink is now gone. Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
On Feb 18, 2008 9:06 PM, Stephen Hemminger <[EMAIL PROTECTED]> wrote: > On Mon, 18 Feb 2008 19:42:25 + (GMT) > Chris Rankin <[EMAIL PROTECTED]> wrote: > > > --- Stephen Hemminger <[EMAIL PROTECTED]> wrote: > > > > > 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 > > > > > [] show_trace_log_lvl+0x1a/0x2f > > > > > [] show_trace+0x12/0x14 > > > > > [] dump_stack+0x6c/0x72 > > > > > [] sysfs_add_one+0x57/0xbc > > > > > [] sysfs_create_link+0xc2/0x10d > > > > > [] pci_bus_add_devices+0xbd/0x103 > > > > > [] pci_legacy_init+0x56/0xe3 > > > > > [] kernel_init+0x157/0x2c3 > > > > > [] kernel_thread_helper+0x7/0x10 > > > > > === > > > > > pci :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 > > > > > [] show_trace_log_lvl+0x1a/0x2f > > > > > [] show_trace+0x12/0x14 > > > > > [] dump_stack+0x6c/0x72 > > > > > [] sysfs_add_one+0x57/0xbc > > > > > [] sysfs_create_link+0xc2/0x10d > > > > > [] pci_bus_add_devices+0xbd/0x103 > > > > > [] pci_bus_add_devices+0xa5/0x103 > > > > > [] pci_legacy_init+0x56/0xe3 > > > > > [] kernel_init+0x157/0x2c3 > > > > > [] kernel_thread_helper+0x7/0x10 > > > > > === > > > > > > > > I have a vague feeling that this was fixed, perhaps in 2.6.24.x? > > > > > > Never heard of this, what is the initialization script that causes this? > > > Also do you have the SYSFS_DEPRECATED option configured? that caused > > > issues > > > with regular network drivers. > > > > Yes, SYSFS_DEPRECATED is enabled. And the init scripts are from Fedora 8. > > There was a bug (fixed in 2.6.24) that had to do with sysfs_create_link > and SYSFS_DEPRECATED probably there is a similar problem with directories. Chris, could you enable CONFIG_DEBUG_KOBJECT=y, it might show what objects try to claim the same name. Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
On Mon, 18 Feb 2008 19:42:25 + (GMT) Chris Rankin <[EMAIL PROTECTED]> wrote: > --- Stephen Hemminger <[EMAIL PROTECTED]> wrote: > > > > 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 > > > > [] show_trace_log_lvl+0x1a/0x2f > > > > [] show_trace+0x12/0x14 > > > > [] dump_stack+0x6c/0x72 > > > > [] sysfs_add_one+0x57/0xbc > > > > [] sysfs_create_link+0xc2/0x10d > > > > [] pci_bus_add_devices+0xbd/0x103 > > > > [] pci_legacy_init+0x56/0xe3 > > > > [] kernel_init+0x157/0x2c3 > > > > [] kernel_thread_helper+0x7/0x10 > > > > === > > > > pci :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 > > > > [] show_trace_log_lvl+0x1a/0x2f > > > > [] show_trace+0x12/0x14 > > > > [] dump_stack+0x6c/0x72 > > > > [] sysfs_add_one+0x57/0xbc > > > > [] sysfs_create_link+0xc2/0x10d > > > > [] pci_bus_add_devices+0xbd/0x103 > > > > [] pci_bus_add_devices+0xa5/0x103 > > > > [] pci_legacy_init+0x56/0xe3 > > > > [] kernel_init+0x157/0x2c3 > > > > [] kernel_thread_helper+0x7/0x10 > > > > === > > > > > > I have a vague feeling that this was fixed, perhaps in 2.6.24.x? > > > > Never heard of this, what is the initialization script that causes this? > > Also do you have the SYSFS_DEPRECATED option configured? that caused issues > > with regular network drivers. > > Yes, SYSFS_DEPRECATED is enabled. And the init scripts are from Fedora 8. There was a bug (fixed in 2.6.24) that had to do with sysfs_create_link and SYSFS_DEPRECATED probably there is a similar problem with directories. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
--- Stephen Hemminger <[EMAIL PROTECTED]> wrote: > > > 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 > > > [] show_trace_log_lvl+0x1a/0x2f > > > [] show_trace+0x12/0x14 > > > [] dump_stack+0x6c/0x72 > > > [] sysfs_add_one+0x57/0xbc > > > [] sysfs_create_link+0xc2/0x10d > > > [] pci_bus_add_devices+0xbd/0x103 > > > [] pci_legacy_init+0x56/0xe3 > > > [] kernel_init+0x157/0x2c3 > > > [] kernel_thread_helper+0x7/0x10 > > > === > > > pci :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 > > > [] show_trace_log_lvl+0x1a/0x2f > > > [] show_trace+0x12/0x14 > > > [] dump_stack+0x6c/0x72 > > > [] sysfs_add_one+0x57/0xbc > > > [] sysfs_create_link+0xc2/0x10d > > > [] pci_bus_add_devices+0xbd/0x103 > > > [] pci_bus_add_devices+0xa5/0x103 > > > [] pci_legacy_init+0x56/0xe3 > > > [] kernel_init+0x157/0x2c3 > > > [] kernel_thread_helper+0x7/0x10 > > > === > > > > I have a vague feeling that this was fixed, perhaps in 2.6.24.x? > > Never heard of this, what is the initialization script that causes this? > Also do you have the SYSFS_DEPRECATED option configured? that caused issues > with regular network drivers. Yes, SYSFS_DEPRECATED is enabled. And the init scripts are from Fedora 8. Cheers, Chris __ Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
On Mon, 18 Feb 2008 05:00:49 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote: > On Sun, 17 Feb 2008 00:54:08 + (GMT) Chris Rankin <[EMAIL PROTECTED]> > 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 > > [] show_trace_log_lvl+0x1a/0x2f > > [] show_trace+0x12/0x14 > > [] dump_stack+0x6c/0x72 > > [] sysfs_add_one+0x57/0xbc > > [] sysfs_create_link+0xc2/0x10d > > [] pci_bus_add_devices+0xbd/0x103 > > [] pci_legacy_init+0x56/0xe3 > > [] kernel_init+0x157/0x2c3 > > [] kernel_thread_helper+0x7/0x10 > > === > > pci :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 > > [] show_trace_log_lvl+0x1a/0x2f > > [] show_trace+0x12/0x14 > > [] dump_stack+0x6c/0x72 > > [] sysfs_add_one+0x57/0xbc > > [] sysfs_create_link+0xc2/0x10d > > [] pci_bus_add_devices+0xbd/0x103 > > [] pci_bus_add_devices+0xa5/0x103 > > [] pci_legacy_init+0x56/0xe3 > > [] kernel_init+0x157/0x2c3 > > [] kernel_thread_helper+0x7/0x10 > > === > > I have a vague feeling that this was fixed, perhaps in 2.6.24.x? Never heard of this, what is the initialization script that causes this? Also do you have the SYSFS_DEPRECATED option configured? that caused issues with regular network drivers. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
--- Andrew Morton <[EMAIL PROTECTED]> wrote: > > 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 > > [] show_trace_log_lvl+0x1a/0x2f > > [] show_trace+0x12/0x14 > > [] dump_stack+0x6c/0x72 > > [] sysfs_add_one+0x57/0xbc > > [] sysfs_create_link+0xc2/0x10d > > [] pci_bus_add_devices+0xbd/0x103 > > [] pci_legacy_init+0x56/0xe3 > > [] kernel_init+0x157/0x2c3 > > [] kernel_thread_helper+0x7/0x10 > > === > > pci :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 > > [] show_trace_log_lvl+0x1a/0x2f > > [] show_trace+0x12/0x14 > > [] dump_stack+0x6c/0x72 > > [] sysfs_add_one+0x57/0xbc > > [] sysfs_create_link+0xc2/0x10d > > [] pci_bus_add_devices+0xbd/0x103 > > [] pci_bus_add_devices+0xa5/0x103 > > [] pci_legacy_init+0x56/0xe3 > > [] kernel_init+0x157/0x2c3 > > [] kernel_thread_helper+0x7/0x10 > > === > > I have a vague feeling that this was fixed, perhaps in 2.6.24.x? Obviously not in 2.6.24.1, and I thought that 2.6.24.2 just added the fix for the vmsplice exploit. So unless 2.6.24.3 has been released...? Cheers, Chris ___ Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/ -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
On Sun, 17 Feb 2008 00:54:08 + (GMT) Chris Rankin <[EMAIL PROTECTED]> 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 > [] show_trace_log_lvl+0x1a/0x2f > [] show_trace+0x12/0x14 > [] dump_stack+0x6c/0x72 > [] sysfs_add_one+0x57/0xbc > [] sysfs_create_link+0xc2/0x10d > [] pci_bus_add_devices+0xbd/0x103 > [] pci_legacy_init+0x56/0xe3 > [] kernel_init+0x157/0x2c3 > [] kernel_thread_helper+0x7/0x10 > === > pci :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 > [] show_trace_log_lvl+0x1a/0x2f > [] show_trace+0x12/0x14 > [] dump_stack+0x6c/0x72 > [] sysfs_add_one+0x57/0xbc > [] sysfs_create_link+0xc2/0x10d > [] pci_bus_add_devices+0xbd/0x103 > [] pci_bus_add_devices+0xa5/0x103 > [] pci_legacy_init+0x56/0xe3 > [] kernel_init+0x157/0x2c3 > [] kernel_thread_helper+0x7/0x10 > === I have a vague feeling that this was fixed, perhaps in 2.6.24.x? -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
