Re: 2.6.21-rc6-mm1 USB related boot hang - bisection result
On Fri, 27 Apr 2007 23:04:58 +0200 Helge Hafting <[EMAIL PROTECTED]> wrote: > On Fri, Apr 27, 2007 at 12:39:19AM +0200, Jiri Kosina wrote: > > On Fri, 27 Apr 2007, Helge Hafting wrote: > > > > > 2.6.21-rc6 boots up fine. Both rc6 and rc7 has a different problem - > > > the machine tends to hang after some minutes work in X. That hang is > > > unusual in that moving the mouse still move the X cursor, but everything > > > else stops and sysrq fails me. But that is another story. > > [...] > > > The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch > > > > Hi Helge, > > > > thanks for the effort. If you take stock rc6-mm1 and revert just > > git-acpi.patch, doesn the machine behave correctly? > > Just compiled & booted such a kernel - it came up fine! > So it looks like USB is fine then, and the problem is in > that ACPI patch. > OK, thanks. Len&co: we've established that 2.6.21-rc6-mm1's git-acpi.patch causes this: > 2.6.21-rc6 boots up fine. Both rc6 and rc7 has a different problem - the > machine tends to hang after some minutes work in X. That hang is > unusual in that moving the mouse still move the X cursor, but > everything else stops and sysrq fails me. But that is another story. > > rc6 boots, rc6-mm1 hangs at the "usbcore registered hiddev" message. > Bisection: > 1, 2, 3: the three first hangs at "usbcore registered hiddev" > 4, 5, 6: the next three hangs at a message about ACPI PCI[A]->IRQ17 > I decided to keep bisecting these hangers as "bad", I don't really know > if this could be the same thing or completely different issues. If they are > different, then one problem will mask the other anyway, so > calling every hanging kernel "bad" will at least find the first broken > patch. > 7: boots up ok! > 8,9,10: hangs at the aboce mentioned ACPI message > The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch > > - 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: 2.6.21-rc6-mm1 USB related boot hang - bisection result
On Fri, Apr 27, 2007 at 12:39:19AM +0200, Jiri Kosina wrote: > On Fri, 27 Apr 2007, Helge Hafting wrote: > > > 2.6.21-rc6 boots up fine. Both rc6 and rc7 has a different problem - > > the machine tends to hang after some minutes work in X. That hang is > > unusual in that moving the mouse still move the X cursor, but everything > > else stops and sysrq fails me. But that is another story. > [...] > > The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch > > Hi Helge, > > thanks for the effort. If you take stock rc6-mm1 and revert just > git-acpi.patch, doesn the machine behave correctly? Just compiled & booted such a kernel - it came up fine! So it looks like USB is fine then, and the problem is in that ACPI patch. Helge Hafting - 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: 2.6.21-rc6-mm1 USB related boot hang - bisection result
On Fri, 27 Apr 2007 00:39:19 +0200 (CEST) Jiri Kosina <[EMAIL PROTECTED]> wrote: > On Fri, 27 Apr 2007, Helge Hafting wrote: > > > 2.6.21-rc6 boots up fine. Both rc6 and rc7 has a different problem - > > the machine tends to hang after some minutes work in X. That hang is > > unusual in that moving the mouse still move the X cursor, but everything > > else stops and sysrq fails me. But that is another story. > [...] > > The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch linux-acpi: we have a problem. > Hi Helge, > > thanks for the effort. If you take stock rc6-mm1 and revert just > git-acpi.patch, doesn the machine behave correctly? > It would be easier and would produce a clearer result to test just 2.6.21-rc7 + 2.6.21-rc7-mm2's origin.patch + 2.6.21-rc7-mm2's acpi.patch from ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc7/2.6.21-rc7-mm2/broken-out/ - 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: 2.6.21-rc6-mm1 USB related boot hang - bisection result
On Fri, 27 Apr 2007, Helge Hafting wrote: > 2.6.21-rc6 boots up fine. Both rc6 and rc7 has a different problem - > the machine tends to hang after some minutes work in X. That hang is > unusual in that moving the mouse still move the X cursor, but everything > else stops and sysrq fails me. But that is another story. [...] > The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch Hi Helge, thanks for the effort. If you take stock rc6-mm1 and revert just git-acpi.patch, doesn the machine behave correctly? -- Jiri Kosina - 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: 2.6.21-rc6-mm1 USB related boot hang - bisection result
Jiri Kosina wrote: On Wed, 25 Apr 2007, Helge Hafting wrote: I don't know about 2.6.21-rc6, but 2.6.21-rc7 (from fresh sources) is good. It boots up without hanging, and my USB devices works too. Should I test rc7-mm1 then? That would also be useful. But really identifying offending patch using bisection would help most. And it should be pretty easy and not too much time consuming for you, as the bug triggers immediately upon boot in your case. 2.6.21-rc6 boots up fine. Both rc6 and rc7 has a different problem - the machine tends to hang after some minutes work in X. That hang is unusual in that moving the mouse still move the X cursor, but everything else stops and sysrq fails me. But that is another story. rc6 boots, rc6-mm1 hangs at the "usbcore registered hiddev" message. Bisection: 1, 2, 3: the three first hangs at "usbcore registered hiddev" 4, 5, 6: the next three hangs at a message about ACPI PCI[A]->IRQ17 I decided to keep bisecting these hangers as "bad", I don't really know if this could be the same thing or completely different issues. If they are different, then one problem will mask the other anyway, so calling every hanging kernel "bad" will at least find the first broken patch. 7: boots up ok! 8,9,10: hangs at the aboce mentioned ACPI message The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch Helge Hafting - 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: 2.6.21-rc6-mm1 USB related boot hang
I recompiled 2.6.21-rc6-mm1 from fresh sources. It still hangs initializing USBm but this time your patch applied. I rebooted with your patch, and got: Detailed lists of all the USB devices found (printer,mouse,...) Then usbcore registered various drivers, such as usblp, usb-storage, libusual, usbserial, ipaq These messages were intermixed with messages from the md raid system initializing The three last lines were: sdhci: Secure digital host controller interface driver sdhci: copyright Pierre Ossman usbcore: registered new interface driver hiddev And then the machine hung completely. I'll have a look at bisecting. :-( - 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: 2.6.21-rc6-mm1 USB related boot hang
Jiri Kosina wrote: On Wed, 25 Apr 2007, Helge Hafting wrote: Anyway, based on information you have provided in your later messages, it seems that it is probably not necessairly related neither to USB nor HID, as you are getting hangs at different stages of boot, depending on your local configuration/kernel version used. Is vanilla 2.6.21-rc6 ok? If so, would you have time to bisect the offending patch? I don't know about 2.6.21-rc6, but 2.6.21-rc7 (from fresh sources) is good. It boots up without hanging, and my USB devices works too. Should I test rc7-mm1 then? That would also be useful. But really identifying offending patch using bisection would help most. If there is an offending patch at all - my rc6-mm1 kernel must have been built from messed-up sources - we saw that when your patch did not apply. So my source had errors - right in the USB part. I haven't tested a correct rc6-mm1, so I don't even know if it has problems. I can make such a kernel of course. . . And it should be pretty easy and not too much time consuming for you, as the bug triggers immediately upon boot in your case. Indeed - it is easy to spot. :-) Helge Hafting - 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: 2.6.21-rc6-mm1 USB related boot hang
On Wed, 25 Apr 2007, Helge Hafting wrote: > > Anyway, based on information you have provided in your later messages, > > it seems that it is probably not necessairly related neither to USB > > nor HID, as you are getting hangs at different stages of boot, > > depending on your local configuration/kernel version used. Is vanilla > > 2.6.21-rc6 ok? If so, would you have time to bisect the offending > > patch? > I don't know about 2.6.21-rc6, but 2.6.21-rc7 (from fresh sources) is > good. It boots up without hanging, and my USB devices works too. Should > I test rc7-mm1 then? That would also be useful. But really identifying offending patch using bisection would help most. And it should be pretty easy and not too much time consuming for you, as the bug triggers immediately upon boot in your case. In case you are not convenient with "bisecting by hand" Andrew's quilt patchset, don't forget that it is also possible to obtain -mm tree through git, which provides very convenient means for bisecting. This is what I usually do. -- Jiri Kosina - 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: 2.6.21-rc6-mm1 USB related boot hang
Jiri Kosina wrote: [...] So I guess you are operating on some broken version of 2.6.21-rc6-mm1 codebase if you are getting rejects on this trivial patch. Didn't think of that - the codebase might be wrong. Anyway, based on information you have provided in your later messages, it seems that it is probably not necessairly related neither to USB nor HID, as you are getting hangs at different stages of boot, depending on your local configuration/kernel version used. Is vanilla 2.6.21-rc6 ok? If so, would you have time to bisect the offending patch? I don't know about 2.6.21-rc6, but 2.6.21-rc7 (from fresh sources) is good. It boots up without hanging, and my USB devices works too. Should I test rc7-mm1 then? Helge Hafting - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, 12 Apr 2007, Helge Hafting wrote: > Are you sure this is the correct patch - against 2.6.21-rc6-mm1 ? > Hunk 1 out of 1 failed . . . Well I am pretty sure: box:~/scratch # wget ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/2.6.21-rc6-mm1.bz2>/dev/null 2>&1 box:~/scratch # wget ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.20.tar.bz2>/dev/null 2>&1 box:~/scratch # wget ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.21-rc6.bz2>/dev/null 2>&1 box:~/scratch # tar xf linux-2.6.20.tar.bz2 box:~/scratch # cd linux-2.6.20/ box:~/scratch/linux-2.6.20 # mv ../patch-2.6.21-rc6.bz2 . box:~/scratch/linux-2.6.20 # bunzip2 patch-2.6.21-rc6.bz2 box:~/scratch/linux-2.6.20 # patch -p1 < patch-2.6.21-rc6 >/dev/null 2>&1; echo $? 0 box:~/scratch/linux-2.6.20 # mv ../2.6.21-rc6-mm1.bz2 . box:~/scratch/linux-2.6.20 # bunzip2 2.6.21-rc6-mm1.bz2 box:~/scratch/linux-2.6.20 # patch -p1 < 2.6.21-rc6-mm1 >/dev/null 2>&1; echo $? 0 box:~/scratch/linux-2.6.20 # cat tmp.patch diff --git a/drivers/hid/usbhid/hid-core.c b/drivers/hid/usbhid/hid-core.c index 1ddca31..d930f62 100644 --- a/drivers/hid/usbhid/hid-core.c +++ b/drivers/hid/usbhid/hid-core.c @@ -1550,15 +1550,22 @@ static int __init hid_init(void) retval = hiddev_init(); if (retval) goto hiddev_init_fail; + printk(KERN_DEBUG "hid_init: before usb_register()\n"); retval = usb_register(&hid_driver); + printk(KERN_DEBUG "hid_init: after usb_register(), retuned %d\n", retval); if (retval) goto usb_register_fail; info(DRIVER_VERSION ":" DRIVER_DESC); + printk(KERN_DEBUG "hid_init: returning 0\n"); + dump_stack(); return 0; usb_register_fail: + printk(KERN_DEBUG "hid_init: calling hiddev_exit()\n"); hiddev_exit(); hiddev_init_fail: + printk(KERN_DEBUG "hid_init: returning %d\n", retval); + dump_stack(); return retval; } box:~/scratch/linux-2.6.20 # patch -p1 < tmp.patch patching file drivers/hid/usbhid/hid-core.c box:~/scratch/linux-2.6.20 # So I guess you are operating on some broken version of 2.6.21-rc6-mm1 codebase if you are getting rejects on this trivial patch. Anyway, based on information you have provided in your later messages, it seems that it is probably not necessairly related neither to USB nor HID, as you are getting hangs at different stages of boot, depending on your local configuration/kernel version used. Is vanilla 2.6.21-rc6 ok? If so, would you have time to bisect the offending patch? Thanks, -- Jiri Kosina - 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: 2.6.21-rc6-mm1 USB related boot hang
Jiri Kosina wrote: On Thu, 12 Apr 2007, Jiri Kosina wrote: CONFIG_IPMI_SI=y hangs upon boot on the already mentioned printk from ipmi_si. With CONFIG_IPMI_SI=m the boot succeeds. When manually trying to modprobe ipmi_si after that, the modprobe itself hangs, but the machine remains usable otherwise. Actually, after approximately 6 minutes 30 seconds, the modprobe finishes with -ENODEV and the following is spitted into dmesg: ipmi_si: There appears to be no BMC at this location ACPI: PCI interrupt for device :02:00.4 disabled ipmi_si: Unable to find any System Interface(s) Anyway I just checked that I get precisely the same behavior with plain 2.6.21-rc6, so we can rule out -mm with this issue. It's possible that this system has some broken KCS. I will try to narrow this down. My guess is that this system spaces out its KCS registers, but there appears to be no way to specify register spacing or offsets with PCI. That would mean that the configuration register appears operational to the driver, but the data register is returning bogus data. Thus it appears "sort of" working to the driver, and it takes a long time to time out. I'm pretty sure it's possible to test to figure out where the registers are really located. However, I have no way to test this change. All the other configuration methods have a way to discover this information. Jiri, we should probably take this offline if you want to continue to work on it. Thanks, -corey - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, Apr 12, 2007 at 08:32:50PM +0200, Jiri Kosina wrote: > OK, so it hangs somewhere nearby usbhid's hid_init(), and the > usb_register() has been already invoked. Could you please apply the > superstupid patch below and send me the output up to the point it hangs? I > am curious to know whether it hangs somewhere inside usb_register(), or > elsewhere. > > Thanks. > Are you sure this is the correct patch - against 2.6.21-rc6-mm1 ? Hunk 1 out of 1 failed . . . > diff --git a/drivers/hid/usbhid/hid-core.c b/drivers/hid/usbhid/hid-core.c > index 1ddca31..d930f62 100644 > --- a/drivers/hid/usbhid/hid-core.c > +++ b/drivers/hid/usbhid/hid-core.c > @@ -1550,15 +1550,22 @@ static int __init hid_init(void) > retval = hiddev_init(); > if (retval) > goto hiddev_init_fail; > + printk(KERN_DEBUG "hid_init: before usb_register()\n"); > retval = usb_register(&hid_driver); > + printk(KERN_DEBUG "hid_init: after usb_register(), retuned %d\n", > retval); > if (retval) > goto usb_register_fail; > info(DRIVER_VERSION ":" DRIVER_DESC); > > + printk(KERN_DEBUG "hid_init: returning 0\n"); > + dump_stack(); > return 0; > usb_register_fail: > + printk(KERN_DEBUG "hid_init: calling hiddev_exit()\n"); > hiddev_exit(); > hiddev_init_fail: > + printk(KERN_DEBUG "hid_init: returning %d\n", retval); > + dump_stack(); > return retval; > } > - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, Apr 12, 2007 at 05:31:52PM +0200, Jiri Kosina wrote: > On Thu, 12 Apr 2007, Jiri Kosina wrote: > > > > - try booting without any HID devices plugged in (i.e. usb mice, usb > > > keyboards) if the problem persists? > > > - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps? > > Do you compile with CONFIG_HIDRAW? > > Helge, > > with your .config, my machine hangs upon IPMI initialization, the last > thing I see before total freeze is > > ipmi_si: Trying PCI-specified kcs state machine at mem address 0xd0121000, > slave address 0x0, irq 5 > > (this was run on 32bit machine) > > When I turn IPMI off, I can't reproduce your hang, evetything runs > smoothly. Could you please try recompiling the kernel with IPMI disabled, > if it could be related? > Removed IPMI, recompiled, rebooted, crashed the same way. Helge Hafting - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, Apr 12, 2007 at 09:50:54AM +0200, Jiri Kosina wrote: > On Thu, 12 Apr 2007, Helge Hafting wrote: > > > > OK. If you add initcall_debug to the kernel boot command line, what's the > > > last thing we call? > > The last messages (handwritten, somewhat shortened) > > calling hid_init+0x0/0x10() > > returned 0 > > ran for 0 msec > > calling hid_init+0x0/0x50() > > usbcore registered new interface driver hiddev > > and then it hangs completely. > > Hi Helge, > > 2.6.21-rc6 (without any -mm patches) works fine? > > Could you please > > - try booting without any HID devices plugged in (i.e. usb mice, usb > keyboards) if the problem persists? Pulled the usb mouse - this moved the crash around. usbhid was registered anyway, but later than usual. The last messages: md: <...> cpuidle: <...> sdhci: <...> sdhci: <...> usbcore: registered new interface hiddev usbcore: registered new interface usbhid drivers/hid/usbhid/hid_core.c v2.6 USB HID coredriver Advanced linux sound architecture <...> ACPI: PCI Interrupt :00:06.0[A]->GSI 17 (lewel,low)->IRQ 17 And then it hung. Rebooting into rc5mm4, I got this as the next msgs: gameport: Trident 4DWave is pci:00:06.0/gameport0, speed 1966kHz ALSA device list: #0: Trident TRID4DWAVENX PCI Audio at 0x9400, irq 17 oprofile: using NMI interrupt. Netfilter messages via NETLINK v0.30. I don't know if this is another problem, or what. > - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps? > Just downloaded it. Unfortunately, it will not revert cleanly: $ patch -p1 -R --dry-run < ../git-hid.patch patching file drivers/hid/Kconfig patching file drivers/hid/Makefile patching file drivers/hid/hid-core.c Hunk #1 succeeded at 30 (offset -1 lines). Hunk #2 succeeded at 871 (offset -1 lines). Hunk #3 succeeded at 968 (offset -1 lines). Hunk #4 succeeded at 984 (offset -1 lines). patching file drivers/hid/hid-input.c Hunk #1 succeeded at 433 (offset 2 lines). Hunk #2 succeeded at 533 (offset 2 lines). patching file drivers/hid/hidraw.c patching file drivers/hid/usbhid/Kconfig patching file drivers/hid/usbhid/Makefile patching file drivers/hid/usbhid/hid-core.c Unreversed patch detected! Ignore -R? [n] Apply anyway? [n] Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file drivers/hid/usbhid/hid-core.c. rej patching file drivers/hid/usbhid/hid-ff.c patching file drivers/hid/usbhid/hid-lgff.c patching file drivers/hid/usbhid/hid-pidff.c patching file drivers/hid/usbhid/hid-plff.c patching file drivers/hid/usbhid/hid-tmff.c patching file drivers/hid/usbhid/hid-zpff.c patching file drivers/hid/usbhid/hiddev.c patching file drivers/hid/usbhid/usbhid.h patching file drivers/hid/usbhid/usbkbd.c patching file drivers/hid/usbhid/usbmouse.c patching file drivers/usb/Makefile patching file drivers/usb/input/Kconfig patching file drivers/usb/input/Makefile Hunk #1 FAILED at 4. 1 out of 1 hunk FAILED -- saving rejects to file drivers/usb/input/Makefile.rej patching file drivers/usb/input/hid-core.c patching file drivers/usb/input/hid-ff.c patching file drivers/usb/input/hid-lgff.c patching file drivers/usb/input/hid-pidff.c patching file drivers/usb/input/hid-plff.c patching file drivers/usb/input/hid-tmff.c patching file drivers/usb/input/hid-zpff.c patching file drivers/usb/input/hiddev.c patching file drivers/usb/input/usbhid.h patching file drivers/usb/input/usbkbd.c patching file drivers/usb/input/usbmouse.c patching file include/linux/hid.h patching file include/linux/hidraw.h Do you want me to try that patch anyway? Helge Hafting - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, Apr 12, 2007 at 09:47:47AM -0700, Andrew Morton wrote: > On Thu, 12 Apr 2007 13:42:57 +0200 Helge Hafting <[EMAIL PROTECTED]> wrote: > > > Jiri Kosina wrote: > > > On Thu, 12 Apr 2007, Jiri Kosina wrote: > > > > > > > > >> Could you please > > >> - try booting without any HID devices plugged in (i.e. usb mice, usb > > >> keyboards) if the problem persists? > > >> - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it > > >> helps? > > >> > > > > > > Do you compile with CONFIG_HIDRAW? > > > > > No, that one is not set. > > > > I did use the new SLUB thing - could that possibly be the cause? > > yup. Went back to SLAB, got a compile error. Did a make clean and compiled again. Got some warnings: LD vmlinux SYSMAP System.map SYSMAP .tmp_System.map MODPOST vmlinux WARNING: init/built-in.o - Section mismatch: reference to .init.text:kernel_init from .text.rest_init after 'rest_init' (at offset 0xe) WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text.k mem_cache_create after 'kmem_cache_create' (at offset 0x40b) WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text.k mem_cache_create after 'kmem_cache_create' (at offset 0x568) AS arch/x86_64/boot/bootsect.o LD arch/x86_64/boot/bootsect AS arch/x86_64/boot/setup.o LD arch/x86_64/boot/setup AS arch/x86_64/boot/compressed/head.o CC arch/x86_64/boot/compressed/misc.o OBJCOPY arch/x86_64/boot/compressed/vmlinux.bin GZIParch/x86_64/boot/compressed/vmlinux.bin.gz LD arch/x86_64/boot/compressed/piggy.o LD arch/x86_64/boot/compressed/vmlinux OBJCOPY arch/x86_64/boot/vmlinux.bin HOSTCC arch/x86_64/boot/tools/build BUILD arch/x86_64/boot/bzImage Root device is (8, 49) Boot sector 512 bytes. Setup is 7302 bytes. System is 3075 kB Kernel: arch/x86_64/boot/bzImage is ready (#11) Then I booted this - and it hung exactly the same way. I thought SLUB was reasonbably safe, it is new but not marked experimental. Helge Hafting - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, 12 Apr 2007, Helge Hafting wrote: > The last messages (handwritten, somewhat shortened) > calling hid_init+0x0/0x10() > returned 0 > ran for 0 msec > calling hid_init+0x0/0x50() > usbcore registered new interface driver hiddev > and then it hangs completely. OK, so it hangs somewhere nearby usbhid's hid_init(), and the usb_register() has been already invoked. Could you please apply the superstupid patch below and send me the output up to the point it hangs? I am curious to know whether it hangs somewhere inside usb_register(), or elsewhere. Thanks. diff --git a/drivers/hid/usbhid/hid-core.c b/drivers/hid/usbhid/hid-core.c index 1ddca31..d930f62 100644 --- a/drivers/hid/usbhid/hid-core.c +++ b/drivers/hid/usbhid/hid-core.c @@ -1550,15 +1550,22 @@ static int __init hid_init(void) retval = hiddev_init(); if (retval) goto hiddev_init_fail; + printk(KERN_DEBUG "hid_init: before usb_register()\n"); retval = usb_register(&hid_driver); + printk(KERN_DEBUG "hid_init: after usb_register(), retuned %d\n", retval); if (retval) goto usb_register_fail; info(DRIVER_VERSION ":" DRIVER_DESC); + printk(KERN_DEBUG "hid_init: returning 0\n"); + dump_stack(); return 0; usb_register_fail: + printk(KERN_DEBUG "hid_init: calling hiddev_exit()\n"); hiddev_exit(); hiddev_init_fail: + printk(KERN_DEBUG "hid_init: returning %d\n", retval); + dump_stack(); return retval; } - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, 12 Apr 2007, Jiri Kosina wrote: > CONFIG_IPMI_SI=y > hangs upon boot on the already mentioned printk from ipmi_si. With > CONFIG_IPMI_SI=m > the boot succeeds. When manually trying to modprobe ipmi_si after that, > the modprobe itself hangs, but the machine remains usable otherwise. Actually, after approximately 6 minutes 30 seconds, the modprobe finishes with -ENODEV and the following is spitted into dmesg: ipmi_si: There appears to be no BMC at this location ACPI: PCI interrupt for device :02:00.4 disabled ipmi_si: Unable to find any System Interface(s) Anyway I just checked that I get precisely the same behavior with plain 2.6.21-rc6, so we can rule out -mm with this issue. It's possible that this system has some broken KCS. I will try to narrow this down. Anyway, the USB-related hang Helge is seeing is therefore a different story. -- Jiri Kosina - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, Apr 12, 2007 at 07:49:02PM +0200, Jiri Kosina wrote: > On Thu, 12 Apr 2007, Andrew Morton wrote: > > > Was that with ipmi linked into vmlinux? (Please send the output of grep > > IPMI .config) I thought we fixed that. > > Confirmed. 2.6.21-rc6-mm1 with > > CONFIG_IPMI_SI=y > > hangs upon boot on the already mentioned printk from ipmi_si. With > > CONFIG_IPMI_SI=m > > the boot succeeds. When manually trying to modprobe ipmi_si after that, > the modprobe itself hangs, but the machine remains usable otherwise. > > I still wonder if this could be related to what Helge was originally > reporting. Does this same .config hang in 2.6.21-rc6 without the -mm stuff? 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, 12 Apr 2007, Andrew Morton wrote: > Was that with ipmi linked into vmlinux? (Please send the output of grep > IPMI .config) I thought we fixed that. Confirmed. 2.6.21-rc6-mm1 with CONFIG_IPMI_SI=y hangs upon boot on the already mentioned printk from ipmi_si. With CONFIG_IPMI_SI=m the boot succeeds. When manually trying to modprobe ipmi_si after that, the modprobe itself hangs, but the machine remains usable otherwise. I still wonder if this could be related to what Helge was originally reporting. -- Jiri Kosina - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, Apr 12, 2007 at 09:55:31AM -0700, Andrew Morton wrote: > On Thu, 12 Apr 2007 17:31:52 +0200 (CEST) Jiri Kosina <[EMAIL PROTECTED]> > wrote: > > > On Thu, 12 Apr 2007, Jiri Kosina wrote: > > > > > > - try booting without any HID devices plugged in (i.e. usb mice, usb > > > > keyboards) if the problem persists? > > > > - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it > > > > helps? > > > Do you compile with CONFIG_HIDRAW? > > > > Helge, > > > > with your .config, my machine hangs upon IPMI initialization, the last > > thing I see before total freeze is > > > > ipmi_si: Trying PCI-specified kcs state machine at mem address 0xd0121000, > > slave address 0x0, irq 5 > > > > (this was run on 32bit machine) > > Was that with ipmi linked into vmlinux? (Please send the output of grep > IPMI .config) > > I thought we fixed that. I thought we fixed that too :( Can you run with the "print out what init function is running" option and see if it really is the ipmi driver that is dying or not? 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, 12 Apr 2007 17:31:52 +0200 (CEST) Jiri Kosina <[EMAIL PROTECTED]> wrote: > On Thu, 12 Apr 2007, Jiri Kosina wrote: > > > > - try booting without any HID devices plugged in (i.e. usb mice, usb > > > keyboards) if the problem persists? > > > - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps? > > Do you compile with CONFIG_HIDRAW? > > Helge, > > with your .config, my machine hangs upon IPMI initialization, the last > thing I see before total freeze is > > ipmi_si: Trying PCI-specified kcs state machine at mem address 0xd0121000, > slave address 0x0, irq 5 > > (this was run on 32bit machine) Was that with ipmi linked into vmlinux? (Please send the output of grep IPMI .config) I thought we fixed that. - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, 12 Apr 2007 13:42:57 +0200 Helge Hafting <[EMAIL PROTECTED]> wrote: > Jiri Kosina wrote: > > On Thu, 12 Apr 2007, Jiri Kosina wrote: > > > > > >> Could you please > >> - try booting without any HID devices plugged in (i.e. usb mice, usb > >> keyboards) if the problem persists? > >> - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps? > >> > > > > Do you compile with CONFIG_HIDRAW? > > > No, that one is not set. > > I did use the new SLUB thing - could that possibly be the cause? yup. > Going back to SLAB is easy enough. Yes, please try that. - 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: 2.6.21-rc6-mm1 USB related boot hang
Jiri, can you send me the output of "lspci -x" ? -corey Jiri Kosina wrote: On Thu, 12 Apr 2007, Jiri Kosina wrote: - try booting without any HID devices plugged in (i.e. usb mice, usb keyboards) if the problem persists? - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps? Do you compile with CONFIG_HIDRAW? Helge, with your .config, my machine hangs upon IPMI initialization, the last thing I see before total freeze is ipmi_si: Trying PCI-specified kcs state machine at mem address 0xd0121000, slave address 0x0, irq 5 (this was run on 32bit machine) When I turn IPMI off, I can't reproduce your hang, evetything runs smoothly. Could you please try recompiling the kernel with IPMI disabled, if it could be related? Corey added to CC. Thanks, - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, 12 Apr 2007, Jiri Kosina wrote: > > - try booting without any HID devices plugged in (i.e. usb mice, usb > > keyboards) if the problem persists? > > - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps? > Do you compile with CONFIG_HIDRAW? Helge, with your .config, my machine hangs upon IPMI initialization, the last thing I see before total freeze is ipmi_si: Trying PCI-specified kcs state machine at mem address 0xd0121000, slave address 0x0, irq 5 (this was run on 32bit machine) When I turn IPMI off, I can't reproduce your hang, evetything runs smoothly. Could you please try recompiling the kernel with IPMI disabled, if it could be related? Corey added to CC. Thanks, -- Jiri Kosina - 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: 2.6.21-rc6-mm1 USB related boot hang
Jiri Kosina wrote: On Thu, 12 Apr 2007, Jiri Kosina wrote: Could you please - try booting without any HID devices plugged in (i.e. usb mice, usb keyboards) if the problem persists? - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps? Do you compile with CONFIG_HIDRAW? No, that one is not set. I did use the new SLUB thing - could that possibly be the cause? Going back to SLAB is easy enough. Helge Hafting - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, 12 Apr 2007, Jiri Kosina wrote: > Could you please > - try booting without any HID devices plugged in (i.e. usb mice, usb > keyboards) if the problem persists? > - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps? Do you compile with CONFIG_HIDRAW? -- Jiri Kosina - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, 12 Apr 2007, Helge Hafting wrote: > > OK. If you add initcall_debug to the kernel boot command line, what's the > > last thing we call? > The last messages (handwritten, somewhat shortened) > calling hid_init+0x0/0x10() > returned 0 > ran for 0 msec > calling hid_init+0x0/0x50() > usbcore registered new interface driver hiddev > and then it hangs completely. Hi Helge, 2.6.21-rc6 (without any -mm patches) works fine? Could you please - try booting without any HID devices plugged in (i.e. usb mice, usb keyboards) if the problem persists? - recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps? I am unfortunately not able to reproduce it here on x86_64. Thanks, -- Jiri Kosina - 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: 2.6.21-rc6-mm1 USB related boot hang
On Thu, 12 Apr 2007 01:07:00 +0200 Helge Hafting <[EMAIL PROTECTED]> wrote: > On Wed, Apr 11, 2007 at 01:43:46PM -0700, Andrew Morton wrote: > > > > OK. If you add initcall_debug to the kernel boot command line, what's the > > last thing we call? > > The last messages (handwritten, somewhat shortened) > calling hid_init+0x0/0x10() > returned 0 > ran for 0 msec > calling hid_init+0x0/0x50() > usbcore registered new interface driver hiddev > > and then it hangs completely. > OK, thanks. If it happens to be, I'll bisect it down. Chances are it won't, and it gets merged, and we get to futz around with it for a week or two while holding up 2.6.22. I can only think we must enjoy doing it this way. - 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: 2.6.21-rc6-mm1 USB related boot hang
On Wed, Apr 11, 2007 at 01:43:46PM -0700, Andrew Morton wrote: > > OK. If you add initcall_debug to the kernel boot command line, what's the > last thing we call? The last messages (handwritten, somewhat shortened) calling hid_init+0x0/0x10() returned 0 ran for 0 msec calling hid_init+0x0/0x50() usbcore registered new interface driver hiddev and then it hangs completely. Helge Hafting - 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: 2.6.21-rc6-mm1 USB related boot hang
On Wed, 11 Apr 2007 21:42:27 +0200 Helge Hafting <[EMAIL PROTECTED]> wrote: > 2.6.21-rc6-mm1 locks up during boot. > The last message is: > usbcore: registered new interface driver hiddev > > Then it hangs so hard that not even sysrq+B have any effect. > > With 2.6.18-rc5-mm1, the next messages I normally get are: > usbcore: registered new interface driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > usbcore: registered new interface driver usbserial > > This is a x86-64 single processor > OK. If you add initcall_debug to the kernel boot command line, what's the last thing we call? - 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: 2.6.21-rc6-mm1 USB related boot hang
2.6.21-rc6-mm1 locks up during boot. The last message is: usbcore: registered new interface driver hiddev Then it hangs so hard that not even sysrq+B have any effect. With 2.6.18-rc5-mm1, the next messages I normally get are: usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver usbcore: registered new interface driver usbserial This is a x86-64 single processor Helge Hafting - 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/
