Re: [PCI] duplicate sysfs symbols getting registered in current git
On Mon, Feb 25, 2008 at 11:03:38PM +0100, Guennadi Liakhovetski wrote: > On Mon, 25 Feb 2008, Greg KH wrote: > > > On Mon, Feb 25, 2008 at 09:31:22PM +0100, Guennadi Liakhovetski wrote: > > > On Mon, 25 Feb 2008, Greg KH wrote: > > > > > > > On Mon, Feb 25, 2008 at 07:15:57PM +0100, Guennadi Liakhovetski wrote: > > > > > On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote: > > > > > > > > > > > On Tue, 19 Feb 2008, Greg KH wrote: > > > > > > > > > > > > > On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski > > > > > > > wrote: > > > > > > > > Booting an x86 SMP PC with todays git-snapshot or just with > > > > > > > > 2.6.25-rc2 > > > > > > > > getting the following warnings (with a bit of context): > > > > > > > > > > > > > > Can you try enabling CONFIG_DEBUG_KOBJECT and sending the output > > > > > > > at boot > > > > > > > time from this? > > > > > > > > > > > > dmesg output with CONFIG_LOG_BUF_SHIFT=19 sent privately to Greg as > > > > > > unpacked, as it would have to be sent to the list, is 408K big. > > > > > > Will see > > > > > > what Greg says. > > > > > > > > > > Actually, the most annoying problem with post 2.6.24 kernels on this > > > > > machine is, that the system doesn't power off or reboot any more. And > > > > > seeing other reports, where the reason for not powering down was > > > > > unfreed > > > > > kobjects, maybe this is the problem here too? > > [snip] > > > Then I suggest filing a new bug report so it doesn't get lost. > > Have you found anything interesting in the kobj debugging output? Do you > think these are two related problems (kobj and failing power-off) or > separate? I have been busy with other things today, sorry haven't gotten the chance, it's in my queue. > So should I file two bug-reports or just one? You mean on bugzilla? Well, the kobject mess is one issue, and the shutdown issue is another one. bugzilla would be nice. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PCI] duplicate sysfs symbols getting registered in current git
On Mon, 25 Feb 2008, Greg KH wrote: > On Mon, Feb 25, 2008 at 09:31:22PM +0100, Guennadi Liakhovetski wrote: > > On Mon, 25 Feb 2008, Greg KH wrote: > > > > > On Mon, Feb 25, 2008 at 07:15:57PM +0100, Guennadi Liakhovetski wrote: > > > > On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote: > > > > > > > > > On Tue, 19 Feb 2008, Greg KH wrote: > > > > > > > > > > > On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski > > > > > > wrote: > > > > > > > Booting an x86 SMP PC with todays git-snapshot or just with > > > > > > > 2.6.25-rc2 > > > > > > > getting the following warnings (with a bit of context): > > > > > > > > > > > > Can you try enabling CONFIG_DEBUG_KOBJECT and sending the output at > > > > > > boot > > > > > > time from this? > > > > > > > > > > dmesg output with CONFIG_LOG_BUF_SHIFT=19 sent privately to Greg as > > > > > unpacked, as it would have to be sent to the list, is 408K big. Will > > > > > see > > > > > what Greg says. > > > > > > > > Actually, the most annoying problem with post 2.6.24 kernels on this > > > > machine is, that the system doesn't power off or reboot any more. And > > > > seeing other reports, where the reason for not powering down was > > > > unfreed > > > > kobjects, maybe this is the problem here too? [snip] > Then I suggest filing a new bug report so it doesn't get lost. Have you found anything interesting in the kobj debugging output? Do you think these are two related problems (kobj and failing power-off) or separate? So should I file two bug-reports or just one? You mean on bugzilla? Thanks Guennadi --- Guennadi Liakhovetski -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PCI] duplicate sysfs symbols getting registered in current git
On Mon, Feb 25, 2008 at 09:31:22PM +0100, Guennadi Liakhovetski wrote: > On Mon, 25 Feb 2008, Greg KH wrote: > > > On Mon, Feb 25, 2008 at 07:15:57PM +0100, Guennadi Liakhovetski wrote: > > > On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote: > > > > > > > On Tue, 19 Feb 2008, Greg KH wrote: > > > > > > > > > On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote: > > > > > > Booting an x86 SMP PC with todays git-snapshot or just with > > > > > > 2.6.25-rc2 > > > > > > getting the following warnings (with a bit of context): > > > > > > > > > > Can you try enabling CONFIG_DEBUG_KOBJECT and sending the output at > > > > > boot > > > > > time from this? > > > > > > > > dmesg output with CONFIG_LOG_BUF_SHIFT=19 sent privately to Greg as > > > > unpacked, as it would have to be sent to the list, is 408K big. Will > > > > see > > > > what Greg says. > > > > > > Actually, the most annoying problem with post 2.6.24 kernels on this > > > machine is, that the system doesn't power off or reboot any more. And > > > seeing other reports, where the reason for not powering down was unfreed > > > kobjects, maybe this is the problem here too? > > > > If you have cpufreq enabled, that should solve this problem after the > > 2.6.24-rc3 kernel release. Have you tried that version? > > Did you mean 25-rc3? Sorry, yes :) > But no, I do not have cpufreq enabled. Then I suggest filing a new bug report so it doesn't get lost. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PCI] duplicate sysfs symbols getting registered in current git
On Mon, 25 Feb 2008, Greg KH wrote: > On Mon, Feb 25, 2008 at 07:15:57PM +0100, Guennadi Liakhovetski wrote: > > On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote: > > > > > On Tue, 19 Feb 2008, Greg KH wrote: > > > > > > > On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote: > > > > > Booting an x86 SMP PC with todays git-snapshot or just with > > > > > 2.6.25-rc2 > > > > > getting the following warnings (with a bit of context): > > > > > > > > Can you try enabling CONFIG_DEBUG_KOBJECT and sending the output at boot > > > > time from this? > > > > > > dmesg output with CONFIG_LOG_BUF_SHIFT=19 sent privately to Greg as > > > unpacked, as it would have to be sent to the list, is 408K big. Will see > > > what Greg says. > > > > Actually, the most annoying problem with post 2.6.24 kernels on this > > machine is, that the system doesn't power off or reboot any more. And > > seeing other reports, where the reason for not powering down was unfreed > > kobjects, maybe this is the problem here too? > > If you have cpufreq enabled, that should solve this problem after the > 2.6.24-rc3 kernel release. Have you tried that version? Did you mean 25-rc3? But no, I do not have cpufreq enabled. Thanks Guennadi --- Guennadi Liakhovetski -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PCI] duplicate sysfs symbols getting registered in current git
On Mon, Feb 25, 2008 at 07:15:57PM +0100, Guennadi Liakhovetski wrote: > On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote: > > > On Tue, 19 Feb 2008, Greg KH wrote: > > > > > On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote: > > > > Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2 > > > > getting the following warnings (with a bit of context): > > > > > > Can you try enabling CONFIG_DEBUG_KOBJECT and sending the output at boot > > > time from this? > > > > dmesg output with CONFIG_LOG_BUF_SHIFT=19 sent privately to Greg as > > unpacked, as it would have to be sent to the list, is 408K big. Will see > > what Greg says. > > Actually, the most annoying problem with post 2.6.24 kernels on this > machine is, that the system doesn't power off or reboot any more. And > seeing other reports, where the reason for not powering down was unfreed > kobjects, maybe this is the problem here too? If you have cpufreq enabled, that should solve this problem after the 2.6.24-rc3 kernel release. Have you tried that version? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PCI] duplicate sysfs symbols getting registered in current git
On Mon, 25 Feb 2008, Guennadi Liakhovetski wrote: > On Tue, 19 Feb 2008, Greg KH wrote: > > > On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote: > > > Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2 > > > getting the following warnings (with a bit of context): > > > > Can you try enabling CONFIG_DEBUG_KOBJECT and sending the output at boot > > time from this? > > dmesg output with CONFIG_LOG_BUF_SHIFT=19 sent privately to Greg as > unpacked, as it would have to be sent to the list, is 408K big. Will see > what Greg says. Actually, the most annoying problem with post 2.6.24 kernels on this machine is, that the system doesn't power off or reboot any more. And seeing other reports, where the reason for not powering down was unfreed kobjects, maybe this is the problem here too? Thanks Guennadi --- Guennadi Liakhovetski -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PCI] duplicate sysfs symbols getting registered in current git
On Tue, 19 Feb 2008, Greg KH wrote: > On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote: > > Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2 > > getting the following warnings (with a bit of context): > > Can you try enabling CONFIG_DEBUG_KOBJECT and sending the output at boot > time from this? dmesg output with CONFIG_LOG_BUF_SHIFT=19 sent privately to Greg as unpacked, as it would have to be sent to the list, is 408K big. Will see what Greg says. Thanks Guennadi --- Guennadi Liakhovetski -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PCI] duplicate sysfs symbols getting registered in current git
On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote: > Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2 > getting the following warnings (with a bit of context): Can you try enabling CONFIG_DEBUG_KOBJECT and sending the output at boot time from this? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PCI] duplicate sysfs symbols getting registered in current git
Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2 getting the following warnings (with a bit of context): * Found PM-Timer Bug on the chipset. Due to workarounds for a bug, * this clock source is slow. Consider trying other clock sources pci :00:14.3: quirk: region f800-f83f claimed by PIIX4 ACPI pci :00:14.3: quirk: region fc00-fc0f claimed by PIIX4 SMB ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init ACPI: bus type pnp registered pnp: IRQ 5 override to level, low PCI: setting IRQ 5 as level-triggered pnp: IRQ 4 override to level, low PCI: setting IRQ 4 as level-triggered pnp: PnP ACPI: found 14 devices ACPI: ACPI bus type pnp unregistered PnPBIOS: Disabled by ACPI PNP SCSI subsystem initialized PCI: Probing PCI hardware kobject (c7c35b00): tried to init an initialized object, something is seriously wrong. Pid: 1, comm: swapper Not tainted 2.6.25-rc2 #6 [] kobject_init+0x89/0x90 [] device_initialize+0x1e/0x90 [] device_register+0xb/0x20 [] pci_bus_add_devices+0x98/0x140 [] ? pcibios_scan_root+0x27/0xa0 [] pci_legacy_init+0x50/0xf0 [] kernel_init+0x132/0x310 [] ? ret_from_fork+0x6/0x1c [] ? kernel_init+0x0/0x310 [] ? kernel_init+0x0/0x310 [] kernel_thread_helper+0x7/0x18 === sysfs: duplicate filename ':01' can not be created [ cut here ] WARNING: at fs/sysfs/dir.c:424 sysfs_add_one+0x80/0xa0() Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.25-rc2 #6 [] warn_on_slowpath+0x54/0x70 [] ? __call_console_drivers+0x5c/0x70 [] ? _spin_unlock_irqrestore+0x11/0x30 [] ? release_console_sem+0x1d9/0x1f0 [] ? vprintk+0x2ad/0x3b0 [] ? ida_get_new_above+0x89/0x180 [] ? sysfs_ilookup_test+0x0/0x20 [] ? _spin_unlock+0xf/0x30 [] ? ifind+0x8a/0x90 [] ? printk+0x1b/0x20 [] sysfs_add_one+0x80/0xa0 [] create_dir+0x49/0x90 [] sysfs_create_dir+0x2b/0x50 [] kobject_add_internal+0xae/0x190 [] ? kobject_set_name_vargs+0x2d/0x40 [] ? kobject_set_name_vargs+0x2d/0x40 [] kobject_add_varg+0x4f/0x60 [] kobject_add+0x2f/0x60 [] ? kobject_get+0x12/0x20 [] device_add+0xd7/0x550 [] ? kref_init+0xd/0x10 [] ? kobject_init+0x2b/0x90 [] device_register+0x12/0x20 [] pci_bus_add_devices+0x98/0x140 [] ? pcibios_scan_root+0x27/0xa0 [] pci_legacy_init+0x50/0xf0 [] kernel_init+0x132/0x310 [] ? ret_from_fork+0x6/0x1c [] ? kernel_init+0x0/0x310 [] ? kernel_init+0x0/0x310 [] kernel_thread_helper+0x7/0x18 === ---[ end trace ca143223eefdc828 ]--- kobject_add_internal failed for :01 with -EEXIST, don't try to register things with the same name in the same directory. Pid: 1, comm: swapper Not tainted 2.6.25-rc2 #6 [] kobject_add_internal+0x139/0x190 [] ? kobject_set_name_vargs+0x2d/0x40 [] kobject_add_varg+0x4f/0x60 [] kobject_add+0x2f/0x60 [] ? kobject_get+0x12/0x20 [] device_add+0xd7/0x550 [] ? kref_init+0xd/0x10 [] ? kobject_init+0x2b/0x90 [] device_register+0x12/0x20 [] pci_bus_add_devices+0x98/0x140 [] ? pcibios_scan_root+0x27/0xa0 [] pci_legacy_init+0x50/0xf0 [] kernel_init+0x132/0x310 [] ? ret_from_fork+0x6/0x1c [] ? kernel_init+0x0/0x310 [] ? kernel_init+0x0/0x310 [] kernel_thread_helper+0x7/0x18 === pci :00:01.0: Error registering pci_bus device bridge symlink, continuing... PCI: Using IRQ router PIIX/ICH [8086/7110] at :00:14.0 PCI->APIC IRQ transform: :00:0b.0[A] -> IRQ 21 PCI->APIC IRQ transform: :00:0c.0[A] -> IRQ 20 PCI->APIC IRQ transform: :00:0d.0[B] -> IRQ 18 PCI->APIC IRQ transform: :00:0d.1[C] -> IRQ 19 PCI->APIC IRQ transform: :00:0d.2[D] -> IRQ 16 PCI->APIC IRQ transform: :00:0d.3[A] -> IRQ 17 PCI->APIC IRQ transform: :00:0e.0[A] -> IRQ 19 PCI->APIC IRQ transform: :00:0f.0[A] -> IRQ 18 PCI->APIC IRQ transform: :00:0f.1[A] -> IRQ 18 PCI->APIC IRQ transform: :00:10.0[A] -> IRQ 16 PCI: using PPB :00:01.0[A] to get irq 22 PCI->APIC IRQ transform: :01:00.0[A] -> IRQ 22 ACPI: RTC can wake from S4 Time: tsc clocksource has been installed. system 00:0b: iomem range 0x0-0x9 could not be reserved system 00:0b: iomem range 0xe-0xf could not be reserved system 00:0b: iomem range 0x10-0xff could not be reserved system 00:0b: iomem range 0xfffc-0x could not be reserved system 00:0c: ioport range 0x15c-0x15d has been reserved system 00:0c: ioport range 0x4d0-0x4d1 has been reserved system 00:0c: ioport range 0x77e-0x77f has been reserved system 00:0c: ioport range 0xc06-0xc07 has been reserved system 00:0c: ioport range 0xc50-0xc51 has been reserved system 00:0c: ioport range 0xc70-0xc77 has been reserved system 00:0c: ioport range 0xc82-0xc82 has been reserved system 00:0d: ioport range 0xf800-0xf81f has been reserved system 00:0d: ioport range 0xf820-0xf83f has been reserved system 00:0d: ioport range 0xfc00-0xfc0f has been reserved PCI: Bridge: :00:01.0 IO window: disabled. MEM window: 0x5
