Re: 2.6.12-rc1-mm2
Le 25.03.2005 02:00, Patrick Mochel a écrit : On Thu, 24 Mar 2005, Andrew Morton wrote: Laurent Riffard <[EMAIL PROTECTED]> wrote: hello, Same kinds of problem here. It depends on the removed module. I mean: "rmmod loop" or "rmmod pcspkr" works. But "rmmod snd_ens1371" or "rmmod ohci1394" hangs. Sysrq-T when rmmoding snd_ens1371 : It looks like we're getting stuck in the wait_for_completion() in the new klist_remove(). D'oh! It's getting hung while waiting to remove the current node from the list (which it can't remove because it's being used). The patch below should fix it. Pat = drivers/base/dd.c 1.3 vs edited = --- 1.3/drivers/base/dd.c 2005-03-21 12:25:04 -08:00 +++ edited/drivers/base/dd.c2005-03-24 16:55:21 -08:00 @@ -177,7 +177,7 @@ sysfs_remove_link(>kobj, kobject_name(>kobj)); sysfs_remove_link(>kobj, "driver"); - klist_remove(>knode_driver); + klist_del(>knode_driver); down(>sem); device_detach_shutdown(dev); Ok, I can confirm this patch solved the problem. Thanks for your help. -- laurent signature.asc Description: OpenPGP digital signature
Re: 2.6.12-rc1-mm2: crash in drm_agp_init
> (Why does -mm2 kernel have > tendency to appear within hour from me downloading -mm1? It happened > two times now...) you just need a faster internet link :) - 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.12-rc1-mm2: crash in drm_agp_init
Hi! > > ..with -rc1-mm2 I get crash during bootup, in some function called > > from drm_agp_init. I'm turned off CONFIG_AGP for now, and machine now > > boots as expected. > > try -mm3 we had a bit of a patch clash between myself, Davej and > Adrian, I think -mm3 has all the fixes in it .. Thanks for the info and sorry for the noise. (Why does -mm2 kernel have tendency to appear within hour from me downloading -mm1? It happened two times now...) Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - 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.12-rc1-mm2: crash in drm_agp_init
> > ..with -rc1-mm2 I get crash during bootup, in some function called > from drm_agp_init. I'm turned off CONFIG_AGP for now, and machine now > boots as expected. try -mm3 we had a bit of a patch clash between myself, Davej and Adrian, I think -mm3 has all the fixes in it .. Dave. - 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.12-rc1-mm2: crash in drm_agp_init
..with -rc1-mm2 I get crash during bootup, in some function called from drm_agp_init. I'm turned off CONFIG_AGP for now, and machine now boots as expected. try -mm3 we had a bit of a patch clash between myself, Davej and Adrian, I think -mm3 has all the fixes in it .. Dave. - 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.12-rc1-mm2: crash in drm_agp_init
Hi! ..with -rc1-mm2 I get crash during bootup, in some function called from drm_agp_init. I'm turned off CONFIG_AGP for now, and machine now boots as expected. try -mm3 we had a bit of a patch clash between myself, Davej and Adrian, I think -mm3 has all the fixes in it .. Thanks for the info and sorry for the noise. (Why does -mm2 kernel have tendency to appear within hour from me downloading -mm1? It happened two times now...) Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - 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.12-rc1-mm2: crash in drm_agp_init
(Why does -mm2 kernel have tendency to appear within hour from me downloading -mm1? It happened two times now...) you just need a faster internet link :) - 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.12-rc1-mm2
Le 25.03.2005 02:00, Patrick Mochel a écrit : On Thu, 24 Mar 2005, Andrew Morton wrote: Laurent Riffard [EMAIL PROTECTED] wrote: hello, Same kinds of problem here. It depends on the removed module. I mean: rmmod loop or rmmod pcspkr works. But rmmod snd_ens1371 or rmmod ohci1394 hangs. Sysrq-T when rmmoding snd_ens1371 : snip It looks like we're getting stuck in the wait_for_completion() in the new klist_remove(). D'oh! It's getting hung while waiting to remove the current node from the list (which it can't remove because it's being used). The patch below should fix it. Pat = drivers/base/dd.c 1.3 vs edited = --- 1.3/drivers/base/dd.c 2005-03-21 12:25:04 -08:00 +++ edited/drivers/base/dd.c2005-03-24 16:55:21 -08:00 @@ -177,7 +177,7 @@ sysfs_remove_link(drv-kobj, kobject_name(dev-kobj)); sysfs_remove_link(dev-kobj, driver); - klist_remove(dev-knode_driver); + klist_del(dev-knode_driver); down(dev-sem); device_detach_shutdown(dev); Ok, I can confirm this patch solved the problem. Thanks for your help. -- laurent signature.asc Description: OpenPGP digital signature
Re: 2.6.12-rc1-mm2
On Thu, Mar 24, 2005 at 05:00:18PM -0800, Patrick Mochel wrote: > > On Thu, 24 Mar 2005, Andrew Morton wrote: > > > Laurent Riffard <[EMAIL PROTECTED]> wrote: > > > > > > hello, > > > > > > Same kinds of problem here. It depends on the removed module. I mean: > > > "rmmod loop" or "rmmod pcspkr" works. But "rmmod snd_ens1371" or "rmmod > > > ohci1394" hangs. > > > > > > Sysrq-T when rmmoding snd_ens1371 : > > > > > It looks like we're getting stuck in the wait_for_completion() in the new > > klist_remove(). > > D'oh! It's getting hung while waiting to remove the current node from the > list (which it can't remove because it's being used). The patch below > should fix it. Thanks, I've added this to my bk trees. 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.12-rc1-mm2
On Thursday 24 March 2005 23:21, Brice Goglin wrote: > Andrew Morton a écrit : > > Stefano Rivoir <[EMAIL PROTECTED]> wrote: > >>>--- linux-mm/include/linux/agp_backend.h.old > >>>+++ linux-mm/include/linux/agp_backend.h > >>>+extern struct agp_bridge_data * (*agp_find_bridge)(struct pci_dev *); > >>Right, that fixed it for me. > > > > There were contradictory patches in flight and I stuck the latest drm > > tree into rc1-mm2 at the last minute, alas. You should revert > > agp-make-some-code-static.patch. > > > > But I assume that fixing the compile warnings does not fix the oopses > > which Stefano and Brice are seeing? > > My patch does fix both the compile warnings and my oops on my Radeon > laptop. It also allows my machine to boot. Alexey ... drm_agp_init+0x30/0x8e drm_fill_in_dev+0xe7/0x195 drm_get_dev+0x4a/0xba kobject_get+0xf/0x13 do_initcalls+0x54/0xb0 init+0x0/0x100 init+0x0/0x100 kernel_thread_helper+0x0/0x0b kernel_thread_helper+0x5/0x0b ... <0>Kernel panic - not syncing: Attempted to kill init! - 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.12-rc1-mm2
On Thu, 24 Mar 2005, Andrew Morton wrote: > Laurent Riffard <[EMAIL PROTECTED]> wrote: > > > > hello, > > > > Same kinds of problem here. It depends on the removed module. I mean: > > "rmmod loop" or "rmmod pcspkr" works. But "rmmod snd_ens1371" or "rmmod > > ohci1394" hangs. > > > > Sysrq-T when rmmoding snd_ens1371 : > It looks like we're getting stuck in the wait_for_completion() in the new > klist_remove(). D'oh! It's getting hung while waiting to remove the current node from the list (which it can't remove because it's being used). The patch below should fix it. Pat = drivers/base/dd.c 1.3 vs edited = --- 1.3/drivers/base/dd.c 2005-03-21 12:25:04 -08:00 +++ edited/drivers/base/dd.c2005-03-24 16:55:21 -08:00 @@ -177,7 +177,7 @@ sysfs_remove_link(>kobj, kobject_name(>kobj)); sysfs_remove_link(>kobj, "driver"); - klist_remove(>knode_driver); + klist_del(>knode_driver); down(>sem); device_detach_shutdown(dev); - 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.12-rc1-mm2
Hi, Andrew Morton wrote: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm2/ - Added David Miller's networking tree to the -mm lineup as bk-net.patch. - Added Herbert Xu's crypto development tree to the -mm lineup as bk-cryptodev.patch. -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually they are pulled 3-4 hours before the release of the -mm kernel. Usually it is possible to determine the latest cset from each tree by looking at the first couple of lines of the relevant patch in the broken-out/ directory. Although sometimes it isn't there if I had to massage the diff. - There may be an x86_64 problem here, although it works for me. If it fails early in boot, try reverting x86_64-separate-amd-cmp-detection-from-hyper-threading.patch - There's some work here on the recent USB PM resume bugs. If you had problems there, please test and be sure to cc linux-usb-devel@lists.sourceforge.net in any reports. - Some fixes for the recent DRM problems. - Big DVB update - md updates - nfs4 server updates - Lots more fixes - Lots more bugs. Fails to compile for me: CC [M] fs/nfs/dir.o CC [M] fs/nfs/inode.o CC [M] fs/nfs/nfs4proc.o fs/nfs/nfs4proc.c:2976: error: static declaration of 'nfs4_file_inode_operations' follows non-static declaration fs/nfs/nfs4_fs.h:179: error: previous declaration of 'nfs4_file_inode_operations' was here make[2]: *** [fs/nfs/nfs4proc.o] Error 1 make[1]: *** [fs/nfs] Error 2 make: *** [fs] Error 2 I needed to remove this line: extern struct inode_operations nfs4_file_inode_operations; from fs/nfs/nfs4_fs.h. Patch attached. Reuben --- fs/nfs/nfs4_fs.h2005-03-25 11:40:51.0 +1200 +++ fs/nfs/nfs4_fs.h2005-03-25 11:44:28.0 +1200 @@ -176,7 +176,6 @@ extern struct dentry_operations nfs4_dentry_operations; extern struct inode_operations nfs4_dir_inode_operations; -extern struct inode_operations nfs4_file_inode_operations; /* inode.c */ extern ssize_t nfs4_getxattr(struct dentry *, const char *, void *, size_t);
Re: 2.6.12-rc1-mm2
Laurent Riffard <[EMAIL PROTECTED]> wrote: > > hello, > > Same kinds of problem here. It depends on the removed module. I mean: > "rmmod loop" or "rmmod pcspkr" works. But "rmmod snd_ens1371" or "rmmod > ohci1394" hangs. > > Sysrq-T when rmmoding snd_ens1371 : > > rmmod D C92EBE8C 0 8231 8159 (NOTLB) > c92ebea0 0082 0003 c92ebe8c 5685fc00 000f4253 cd624530 > cd624658 cff60874 cff60844 c92ebebc c92ebef0 c02618c7 > cd624530 > c0113137 0282 cd248c20 cd248c07 0001 > cd624530 > Call Trace: >[wait_for_completion+124/193] wait_for_completion+0x7c/0xc1 >[] wait_for_completion+0x7c/0xc1 >[device_release_driver+52/116] device_release_driver+0x34/0x74 >[] device_release_driver+0x34/0x74 >[__remove_driver+8/12] __remove_driver+0x8/0xc >[] __remove_driver+0x8/0xc >[driver_for_each_device+50/87] driver_for_each_device+0x32/0x57 >[] driver_for_each_device+0x32/0x57 >[driver_detach+17/19] driver_detach+0x11/0x13 >[] driver_detach+0x11/0x13 >[bus_remove_driver+76/130] bus_remove_driver+0x4c/0x82 >[] bus_remove_driver+0x4c/0x82 >[driver_unregister+14/23] driver_unregister+0xe/0x17 >[] driver_unregister+0xe/0x17 >[pci_unregister_driver+14/23] pci_unregister_driver+0xe/0x17 >[] pci_unregister_driver+0xe/0x17 >[sys_delete_module+322/379] sys_delete_module+0x142/0x17b >[] sys_delete_module+0x142/0x17b It looks like we're getting stuck in the wait_for_completion() in the new klist_remove(). - 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.12-rc1-mm2
Le 24.03.2005 23:31, Rafael J. Wysocki a écrit : Hi, On Thursday, 24 of March 2005 21:17, Andrew Morton wrote: Lee Revell <[EMAIL PROTECTED]> wrote: On Thu, 2005-03-24 at 04:41 -0800, Andrew Morton wrote: -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually they are pulled 3-4 hours before the release of the -mm kernel. Andrew, Do you notify the subsystem maintainers ahead of time so that critical fixes can be pushed to BK? Occasionally I'll go out and ping people, but almost always the subsystem guys know what the development cycle is, and they appropriately decide which code should go in, and when. I am thinking of the recent ALSA example, where the emu10k1 driver was b0rked in 2.6.12-mm1, but the fix had been in ALSA CVS for a week. We've been discussing how to get ALSA CVS into ALSA bk more promptly. BTW, on 2.6.12-rc1-mm2 I can't rmmod the snd_intel8x0 module (the process goes into the D state immediately), which did not happen before. This is 100% reproducible, on two different AMD64-based boxes, with different sound chips. Greets, Rafael hello, Same kinds of problem here. It depends on the removed module. I mean: "rmmod loop" or "rmmod pcspkr" works. But "rmmod snd_ens1371" or "rmmod ohci1394" hangs. Sysrq-T when rmmoding snd_ens1371 : rmmod D C92EBE8C 0 8231 8159 (NOTLB) c92ebea0 0082 0003 c92ebe8c 5685fc00 000f4253 cd624530 cd624658 cff60874 cff60844 c92ebebc c92ebef0 c02618c7 cd624530 c0113137 0282 cd248c20 cd248c07 0001 cd624530 Call Trace: [wait_for_completion+124/193] wait_for_completion+0x7c/0xc1 [] wait_for_completion+0x7c/0xc1 [device_release_driver+52/116] device_release_driver+0x34/0x74 [] device_release_driver+0x34/0x74 [__remove_driver+8/12] __remove_driver+0x8/0xc [] __remove_driver+0x8/0xc [driver_for_each_device+50/87] driver_for_each_device+0x32/0x57 [] driver_for_each_device+0x32/0x57 [driver_detach+17/19] driver_detach+0x11/0x13 [] driver_detach+0x11/0x13 [bus_remove_driver+76/130] bus_remove_driver+0x4c/0x82 [] bus_remove_driver+0x4c/0x82 [driver_unregister+14/23] driver_unregister+0xe/0x17 [] driver_unregister+0xe/0x17 [pci_unregister_driver+14/23] pci_unregister_driver+0xe/0x17 [] pci_unregister_driver+0xe/0x17 [sys_delete_module+322/379] sys_delete_module+0x142/0x17b [] sys_delete_module+0x142/0x17b Sysrq-T when rmmoding ohci1394 : rmmod D 0001 0 12353 10401 (NOTLB) cefa9ea0 0082 c012f3d9 0001 0001e848 e88bbbc0 000f426d cb613570 cb613698 cff60074 cff60044 cefa9ebc cefa9ef0 c02618d7 cb613570 c0113137 0286 cd379e60 cd379e47 0001 cb613570 Call Trace: [wait_for_completion+124/193] wait_for_completion+0x7c/0xc1 [] wait_for_completion+0x7c/0xc1 [device_release_driver+52/116] device_release_driver+0x34/0x74 [] device_release_driver+0x34/0x74 [__remove_driver+8/12] __remove_driver+0x8/0xc [] __remove_driver+0x8/0xc [driver_for_each_device+50/87] driver_for_each_device+0x32/0x57 [] driver_for_each_device+0x32/0x57 [driver_detach+17/19] driver_detach+0x11/0x13 [] driver_detach+0x11/0x13 [bus_remove_driver+76/130] bus_remove_driver+0x4c/0x82 [] bus_remove_driver+0x4c/0x82 [driver_unregister+14/23] driver_unregister+0xe/0x17 [] driver_unregister+0xe/0x17 [pci_unregister_driver+14/23] pci_unregister_driver+0xe/0x17 [] pci_unregister_driver+0xe/0x17 [sys_delete_module+322/379] sys_delete_module+0x142/0x17b [] sys_delete_module+0x142/0x17b [sysenter_past_esp+84/117] sysenter_past_esp+0x54/0x75 .config attached ~~ laurent # # Automatically generated make config: don't edit # Linux kernel version: 2.6.12-rc1-mm2 # Thu Mar 24 23:38:31 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_CLEAR_PAGES=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set CONFIG_EMBEDDED=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set #
Re: 2.6.12-rc1-mm2
On Thursday, 24 of March 2005 23:31, Rafael J. Wysocki wrote: > Hi, > > On Thursday, 24 of March 2005 21:17, Andrew Morton wrote: > > Lee Revell <[EMAIL PROTECTED]> wrote: > > > > > > On Thu, 2005-03-24 at 04:41 -0800, Andrew Morton wrote: > > > > -mm kernels now aggregate Linus's tree and 34 subsystem trees. > > > > Usually > > > > they are pulled 3-4 hours before the release of the -mm kernel. > > > > > > > > > > Andrew, > > > > > > Do you notify the subsystem maintainers ahead of time so that critical > > > fixes can be pushed to BK? > > > > Occasionally I'll go out and ping people, but almost always the subsystem > > guys know what the development cycle is, and they appropriately decide > > which code should go in, and when. > > > > > I am thinking of the recent ALSA example, where the emu10k1 driver was > > > b0rked in 2.6.12-mm1, but the fix had been in ALSA CVS for a week. > > > > > > > We've been discussing how to get ALSA CVS into ALSA bk more promptly. > > BTW, on 2.6.12-rc1-mm2 I can't rmmod the snd_intel8x0 module (the process > goes into the D state immediately), which did not happen before. This is 100% > reproducible, on two different AMD64-based boxes, with different sound chips. Er, sorry for the noise on alsa-devel. Actually, rmmod doesn't work for me at all on x86-64 (on two different boxes). Greets, Rafael -- - Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland" - 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.12-rc1-mm2
Hi, On Thursday, 24 of March 2005 21:17, Andrew Morton wrote: > Lee Revell <[EMAIL PROTECTED]> wrote: > > > > On Thu, 2005-03-24 at 04:41 -0800, Andrew Morton wrote: > > > -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually > > > they are pulled 3-4 hours before the release of the -mm kernel. > > > > > > > Andrew, > > > > Do you notify the subsystem maintainers ahead of time so that critical > > fixes can be pushed to BK? > > Occasionally I'll go out and ping people, but almost always the subsystem > guys know what the development cycle is, and they appropriately decide > which code should go in, and when. > > > I am thinking of the recent ALSA example, where the emu10k1 driver was > > b0rked in 2.6.12-mm1, but the fix had been in ALSA CVS for a week. > > > > We've been discussing how to get ALSA CVS into ALSA bk more promptly. BTW, on 2.6.12-rc1-mm2 I can't rmmod the snd_intel8x0 module (the process goes into the D state immediately), which did not happen before. This is 100% reproducible, on two different AMD64-based boxes, with different sound chips. Greets, Rafael -- - Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland" - 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.12-rc1-mm2 (patch to fix build error In function `zft_init')
Greg KH <[EMAIL PROTECTED]> wrote: > > > I glanced at the code, and this little patch fixes the problem: > > Ick, sorry, that was my fault. I've applied this patch to my trees, > thanks. > > Hm, I wonder how I missed this, I did do a 'make allmodconfig' build to > try to catch this kind of stuff... allmodconfig doesn't catch BROKEN_ON_SMP code. I've been caught out by that a few times. - 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.12-rc1-mm2 (patch to fix build error In function `zft_init')
On Thu, Mar 24, 2005 at 08:55:13AM -0700, Steven Cole wrote: > Steven Cole wrote: > >I'm getting the following build error with 2.6.12-rc1-mm2: > > > > CC init/version.o > > LD init/built-in.o > > LD .tmp_vmlinux1 > >drivers/built-in.o(.init.text+0x4323): In function `zft_init': > >: undefined reference to `class_device_creat' > >make: *** [.tmp_vmlinux1] Error 1 > > > > I glanced at the code, and this little patch fixes the problem: Ick, sorry, that was my fault. I've applied this patch to my trees, thanks. Hm, I wonder how I missed this, I did do a 'make allmodconfig' build to try to catch this kind of 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.12-rc1-mm2 - ppc32 build fails.
On Thu, 24 Mar 2005 12:28:08 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote: > cliff white <[EMAIL PROTECTED]> wrote: > > > > > > Error message: > > > > CC arch/ppc/kernel/setup.o > > In file included from arch/ppc/kernel/setup.c:43: > > include/asm/ppc_sys.h:29:2: #error "need definition of ppc_sys_devices" > > In file included from arch/ppc/kernel/setup.c:43: > > include/asm/ppc_sys.h:61: warning: parameter has incomplete type > > include/asm/ppc_sys.h:64: warning: parameter has incomplete type > > This should fix it. Fixes that problem, now i hit the kernel OOPS at drm initalization. Thought i saw a patch somewhere already for that... cliffw > > > From: Kumar Gala <[EMAIL PROTECTED]> > > > Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> > --- > > 25-akpm/arch/ppc/kernel/setup.c |5 - > 1 files changed, 4 insertions(+), 1 deletion(-) > > diff -puN > arch/ppc/kernel/setup.c~ppc32-report-chipset-version-in-common-proc-cpuinfo-handling-fix > arch/ppc/kernel/setup.c > --- > 25/arch/ppc/kernel/setup.c~ppc32-report-chipset-version-in-common-proc-cpuinfo-handling-fix >2005-03-24 12:27:39.0 -0800 > +++ 25-akpm/arch/ppc/kernel/setup.c 2005-03-24 12:27:39.0 -0800 > @@ -40,7 +40,10 @@ > #include > #include > #include > + > +#if defined(CONFIG_85xx) || defined(CONFIG_83xx) > #include > +#endif > > #if defined CONFIG_KGDB > #include > @@ -247,7 +250,7 @@ int show_cpuinfo(struct seq_file *m, voi > seq_printf(m, "bogomips\t: %lu.%02lu\n", > lpj / (50/HZ), (lpj / (5000/HZ)) % 100); > > -#if defined (CONFIG_85xx) || defined (CONFIG_83xx) > +#if defined(CONFIG_85xx) || defined(CONFIG_83xx) > if (cur_ppc_sys_spec->ppc_sys_name) > seq_printf(m, "chipset\t\t: %s\n", > cur_ppc_sys_spec->ppc_sys_name); > _ > > - > 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/ > -- "Ive always gone through periods where I bolt upright at four in the morning; now at least theres a reason." -Michael Feldman - 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.12-rc1-mm2 - ppc32 build fails.
cliff white <[EMAIL PROTECTED]> wrote: > > > Error message: > > CC arch/ppc/kernel/setup.o > In file included from arch/ppc/kernel/setup.c:43: > include/asm/ppc_sys.h:29:2: #error "need definition of ppc_sys_devices" > In file included from arch/ppc/kernel/setup.c:43: > include/asm/ppc_sys.h:61: warning: parameter has incomplete type > include/asm/ppc_sys.h:64: warning: parameter has incomplete type This should fix it. From: Kumar Gala <[EMAIL PROTECTED]> Signed-off-by: Andrew Morton <[EMAIL PROTECTED]> --- 25-akpm/arch/ppc/kernel/setup.c |5 - 1 files changed, 4 insertions(+), 1 deletion(-) diff -puN arch/ppc/kernel/setup.c~ppc32-report-chipset-version-in-common-proc-cpuinfo-handling-fix arch/ppc/kernel/setup.c --- 25/arch/ppc/kernel/setup.c~ppc32-report-chipset-version-in-common-proc-cpuinfo-handling-fix 2005-03-24 12:27:39.0 -0800 +++ 25-akpm/arch/ppc/kernel/setup.c 2005-03-24 12:27:39.0 -0800 @@ -40,7 +40,10 @@ #include #include #include + +#if defined(CONFIG_85xx) || defined(CONFIG_83xx) #include +#endif #if defined CONFIG_KGDB #include @@ -247,7 +250,7 @@ int show_cpuinfo(struct seq_file *m, voi seq_printf(m, "bogomips\t: %lu.%02lu\n", lpj / (50/HZ), (lpj / (5000/HZ)) % 100); -#if defined (CONFIG_85xx) || defined (CONFIG_83xx) +#if defined(CONFIG_85xx) || defined(CONFIG_83xx) if (cur_ppc_sys_spec->ppc_sys_name) seq_printf(m, "chipset\t\t: %s\n", cur_ppc_sys_spec->ppc_sys_name); _ - 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.12-rc1-mm2
Andrew Morton a écrit : Stefano Rivoir <[EMAIL PROTECTED]> wrote: --- linux-mm/include/linux/agp_backend.h.old2005-03-24 16:17:25.0 +0100 +++ linux-mm/include/linux/agp_backend.h2005-03-24 16:10:25.0 +0100 @@ -100,6 +100,7 @@ extern int agp_bind_memory(struct agp_memory *, off_t); extern int agp_unbind_memory(struct agp_memory *); extern void agp_enable(struct agp_bridge_data *, u32); +extern struct agp_bridge_data * (*agp_find_bridge)(struct pci_dev *); extern struct agp_bridge_data *agp_backend_acquire(struct pci_dev *); extern void agp_backend_release(struct agp_bridge_data *); Right, that fixed it for me. There were contradictory patches in flight and I stuck the latest drm tree into rc1-mm2 at the last minute, alas. You should revert agp-make-some-code-static.patch. But I assume that fixing the compile warnings does not fix the oopses which Stefano and Brice are seeing? My patch does fix both the compile warnings and my oops on my Radeon laptop. Brice - 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.12-rc1-mm2
Lee Revell <[EMAIL PROTECTED]> wrote: > > On Thu, 2005-03-24 at 04:41 -0800, Andrew Morton wrote: > > -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually > > they are pulled 3-4 hours before the release of the -mm kernel. > > > > Andrew, > > Do you notify the subsystem maintainers ahead of time so that critical > fixes can be pushed to BK? Occasionally I'll go out and ping people, but almost always the subsystem guys know what the development cycle is, and they appropriately decide which code should go in, and when. > I am thinking of the recent ALSA example, where the emu10k1 driver was > b0rked in 2.6.12-mm1, but the fix had been in ALSA CVS for a week. > We've been discussing how to get ALSA CVS into ALSA bk more promptly. - 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.12-rc1-mm2
Stefano Rivoir <[EMAIL PROTECTED]> wrote: > > Alle 16:18, giovedì 24 marzo 2005, Brice Goglin ha scritto: > > Stefano Rivoir a écrit : > > > Alle 13:41, giovedì 24 marzo 2005, Andrew Morton ha scritto: > > >>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/ > > >>2. 6.12-rc1-mm2/ > > >> > > >> > > >>- Some fixes for the recent DRM problems. > > > > > > Hi Andrew, > > > > > > While I was OK with DRM up to 2.6.12-rc1-mm1, now I get this at startup, > > > and Xorg fails to enable DRI (attached, lspci and .config): > > > --- linux-mm/include/linux/agp_backend.h.old2005-03-24 > > 16:17:25.0 +0100 > > +++ linux-mm/include/linux/agp_backend.h2005-03-24 > > 16:10:25.0 +0100 > > @@ -100,6 +100,7 @@ > > extern int agp_bind_memory(struct agp_memory *, off_t); > > extern int agp_unbind_memory(struct agp_memory *); > > extern void agp_enable(struct agp_bridge_data *, u32); > > +extern struct agp_bridge_data * (*agp_find_bridge)(struct pci_dev *); > > extern struct agp_bridge_data *agp_backend_acquire(struct pci_dev *); > > extern void agp_backend_release(struct agp_bridge_data *); > > Right, that fixed it for me. > There were contradictory patches in flight and I stuck the latest drm tree into rc1-mm2 at the last minute, alas. You should revert agp-make-some-code-static.patch. But I assume that fixing the compile warnings does not fix the oopses which Stefano and Brice are seeing? - 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.12-rc1-mm2
On Thu, 2005-03-24 at 04:41 -0800, Andrew Morton wrote: > -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually > they are pulled 3-4 hours before the release of the -mm kernel. > Andrew, Do you notify the subsystem maintainers ahead of time so that critical fixes can be pushed to BK? I am thinking of the recent ALSA example, where the emu10k1 driver was b0rked in 2.6.12-mm1, but the fix had been in ALSA CVS for a week. Lee - 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.12-rc1-mm2 (patch to fix build error In function `zft_init')
Steven Cole wrote:
I'm getting the following build error with 2.6.12-rc1-mm2:
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o(.init.text+0x4323): In function `zft_init':
: undefined reference to `class_device_creat'
make: *** [.tmp_vmlinux1] Error 1
I glanced at the code, and this little patch fixes the problem:
Steven
Signed-off by: Steven Cole <[EMAIL PROTECTED]>
--- linux-2.6.12-rc1-mm2/drivers/char/ftape/zftape/zftape-init.c.orig
2005-03-24 08:43:30.0 -0700
+++ linux-2.6.12-rc1-mm2/drivers/char/ftape/zftape/zftape-init.c
2005-03-24 08:43:56.0 -0700
@@ -331,7 +331,7 @@
zft_class = class_create(THIS_MODULE, "zft");
for (i = 0; i < 4; i++) {
- class_device_creat(zft_class, MKDEV(QIC117_TAPE_MAJOR, i),
NULL, "qft%i", i);
+ class_device_create(zft_class, MKDEV(QIC117_TAPE_MAJOR, i),
NULL, "qft%i", i);
devfs_mk_cdev(MKDEV(QIC117_TAPE_MAJOR, i),
S_IFCHR | S_IRUSR | S_IWUSR,
"qft%i", i);
Re: 2.6.12-rc1-mm2
Alle 16:18, giovedì 24 marzo 2005, Brice Goglin ha scritto: > Stefano Rivoir a écrit : > > Alle 13:41, giovedì 24 marzo 2005, Andrew Morton ha scritto: > >>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/ > >>2. 6.12-rc1-mm2/ > >> > >> > >>- Some fixes for the recent DRM problems. > > > > Hi Andrew, > > > > While I was OK with DRM up to 2.6.12-rc1-mm1, now I get this at startup, > > and Xorg fails to enable DRI (attached, lspci and .config): > --- linux-mm/include/linux/agp_backend.h.old2005-03-24 > 16:17:25.0 +0100 > +++ linux-mm/include/linux/agp_backend.h2005-03-24 > 16:10:25.0 +0100 > @@ -100,6 +100,7 @@ > extern int agp_bind_memory(struct agp_memory *, off_t); > extern int agp_unbind_memory(struct agp_memory *); > extern void agp_enable(struct agp_bridge_data *, u32); > +extern struct agp_bridge_data * (*agp_find_bridge)(struct pci_dev *); > extern struct agp_bridge_data *agp_backend_acquire(struct pci_dev *); > extern void agp_backend_release(struct agp_bridge_data *); Right, that fixed it for me. Thank you. -- Stefano Rivoir - 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.12-rc1-mm2
Stefano Rivoir a écrit : Alle 13:41, giovedì 24 marzo 2005, Andrew Morton ha scritto: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2. 6.12-rc1-mm2/ - Some fixes for the recent DRM problems. Hi Andrew, While I was OK with DRM up to 2.6.12-rc1-mm1, now I get this at startup, and Xorg fails to enable DRI (attached, lspci and .config): Same problem on my Radeon M6 LY here. This seems to be due to agp_find_bridge not being exported anymore in agp_backend.h. Dave might have forgotten it when reworking my patch. Patch attached. Brice Signoff-by: Brice Goglin <[EMAIL PROTECTED]> --- linux-mm/include/linux/agp_backend.h.old2005-03-24 16:17:25.0 +0100 +++ linux-mm/include/linux/agp_backend.h2005-03-24 16:10:25.0 +0100 @@ -100,6 +100,7 @@ extern int agp_bind_memory(struct agp_memory *, off_t); extern int agp_unbind_memory(struct agp_memory *); extern void agp_enable(struct agp_bridge_data *, u32); +extern struct agp_bridge_data * (*agp_find_bridge)(struct pci_dev *); extern struct agp_bridge_data *agp_backend_acquire(struct pci_dev *); extern void agp_backend_release(struct agp_bridge_data *); - 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.12-rc1-mm2
Stefano Rivoir wrote: > Alle 13:41, giovedì 24 marzo 2005, Andrew Morton ha scritto: > >>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2. >>6.12-rc1-mm2/ > > >>- Some fixes for the recent DRM problems. > > > Hi Andrew, > > While I was OK with DRM up to 2.6.12-rc1-mm1, now I get this at startup, and > Xorg fails to enable DRI (attached, lspci and .config): > > Unable to handle kernel paging request at virtual address 72ff64d7 > printing eip: > e087eb44 > *pde = > Oops: 0002 [#1] > PREEMPT > Modules linked in: radeon drm sd_mod scsi_mod lp hotkey fan container button > ide_cd 8250_pnp parport_pc parport floppy pcspkr sk98lin yenta_socket > rsrc_nonstatic pcmcia_core ehci_hcd usbhid ohci_hcd snd_intel8x0m 8250_pci > 8250 serial_core ohci1394 ieee1394 sis_agp agpgart vfat fat video thermal > processor ac battery snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss > snd_pcm snd_timer snd soundcore snd_page_alloc skge evdev > CPU:0 > EIP:0060:[]Not tainted VLI > EFLAGS: 00013286 (2.6.12-rc1-mm2) > EIP is at agp_find_bridge+0x0/0xc77f [agpgart] > eax: dff1d000 ebx: de228400 ecx: edx: 00d0 > esi: dd86 edi: de228450 ebp: e1a4bd90 esp: dd811f48 > ds: 007b es: 007b ss: 0068 > Process modprobe (pid: 4698, threadinfo=dd81 task=dfca3030) > Stack: e1a085fb dd86 e1a4c240 e1a06ed0 dd86 e1a4c240 dff1d000 >dd86 e1a071ce e1a4c240 c01abfaf e1a4bd90 dff1d000 e1a4c240 0310 >e1a03adf 0310 fffc e1a4e180 dd81 dd81 > Call Trace: > [] drm_agp_init+0x3b/0xb0 [drm] > [] drm_fill_in_dev+0xf0/0x1b0 [drm] > [] drm_get_dev+0x4e/0xc0 [drm] > [] kobject_get+0xf/0x20 > [] drm_init+0x6f/0xb0 [drm] > [] sys_init_module+0x139/0x1e0 > [] sysenter_past_esp+0x54/0x75 > Code: 6e 66 69 67 5f 62 79 74 65 00 61 67 70 5f 70 75 74 5f 62 72 69 64 67 65 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 65 00 a7 87 e0 dc 94 > cd de dc 94 cd de 00 00 00 00 00 00 00 00 00 I get a similar Oops at boot; I noticed this warning during compilation: drivers/char/drm/drm_agpsupport.c: In function `drm_agp_init': drivers/char/drm/drm_agpsupport.c:391: warning: implicit declaration of function `agp_find_bridge' drivers/char/drm/drm_agpsupport.c:391: warning: assignment makes pointer from integer without a cast I dont know what header to include/modify to make it go away. DRM and AGP are compiled into the kernel (no modules). -- Manuel Lauss - 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.12-rc1-mm2 (build error In function `zft_init')
I'm getting the following build error with 2.6.12-rc1-mm2: CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o(.init.text+0x4323): In function `zft_init': : undefined reference to `class_device_creat' make: *** [.tmp_vmlinux1] Error 1 2.6.12-rc1-mm1 built and is running just fine. I used the -rc1-mm1 .config, did make oldconfig, make bzImage. Here is the .config: [EMAIL PROTECTED] linux-2.6.12-rc1-mm2]$ grep ^CONFIG .config CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_CLEAR_PAGES=y CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION="-GX110" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KALLSYMS=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 CONFIG_BASE_SMALL=0 CONFIG_X86_PC=y CONFIG_MPENTIUMIII=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_P4THERMAL=y CONFIG_MICROCODE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_EDD=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y CONFIG_PHYSICAL_START=0x10 CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_LEGACY_PROC=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=32000 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_AOE_PARTITIONS=16 CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=y CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_IDEDMA_PCI_AUTO=y CONFIG_BLK_DEV_PIIX=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDEDMA_AUTO=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_NET_KEY=y CONFIG_INET=y CONFIG_IP_TCPDIAG=y CONFIG_XFRM=y CONFIG_NETDEVICES=y CONFIG_NET_ETHERNET=y CONFIG_MII=y CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=y CONFIG_INPUT=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y CONFIG_SERIO_LIBPS2=y CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_FTAPE=y CONFIG_ZFTAPE=y CONFIG_ZFT_DFLT_BLK_SZ=10240 CONFIG_ZFT_COMPRESSOR=y CONFIG_FT_NR_BUFFERS=3 CONFIG_FT_PROC_FS=y CONFIG_FT_NORMAL_DEBUG=y CONFIG_FT_STD_FDC=y CONFIG_FT_FDC_THR=8 CONFIG_FT_FDC_MAX_RATE=2000 CONFIG_FT_ALPHA_CLOCK=0 CONFIG_AGP=y CONFIG_AGP_INTEL=y CONFIG_VIDEO_DEV=y CONFIG_VIDEO_SELECT=y CONFIG_VGA_CONSOLE=y CONFIG_DUMMY_CONSOLE=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT3_FS=y CONFIG_JBD=y CONFIG_FS_MBCACHE=y CONFIG_REISER4_FS=y CONFIG_REISERFS_FS=y CONFIG_DNOTIFY=y CONFIG_ISO9660_FS=y CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=y CONFIG_NTFS_RW=y CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y CONFIG_DEVFS_FS=y CONFIG_TMPFS=y CONFIG_RAMFS=y CONFIG_PARTITION_ADVANCED=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_850=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y CONFIG_NLS_UTF8=y CONFIG_PRINTK_TIME=y CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_DEBUG_BUGVERBOSE=y CONFIG_FRAME_POINTER=y CONFIG_EARLY_PRINTK=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y CONFIG_SECURITY=y CONFIG_SECURITY_NETWORK=y CONFIG_SECURITY_CAPABILITIES=y CONFIG_CRC_CCITT=y CONFIG_CRC32=y CONFIG_LIBCRC32C=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_PC=y Steven - 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.12-rc1-mm2
Alle 13:41, giovedì 24 marzo 2005, Andrew Morton ha scritto: > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2. >6.12-rc1-mm2/ > - Some fixes for the recent DRM problems. Hi Andrew, While I was OK with DRM up to 2.6.12-rc1-mm1, now I get this at startup, and Xorg fails to enable DRI (attached, lspci and .config): Unable to handle kernel paging request at virtual address 72ff64d7 printing eip: e087eb44 *pde = Oops: 0002 [#1] PREEMPT Modules linked in: radeon drm sd_mod scsi_mod lp hotkey fan container button ide_cd 8250_pnp parport_pc parport floppy pcspkr sk98lin yenta_socket rsrc_nonstatic pcmcia_core ehci_hcd usbhid ohci_hcd snd_intel8x0m 8250_pci 8250 serial_core ohci1394 ieee1394 sis_agp agpgart vfat fat video thermal processor ac battery snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc skge evdev CPU:0 EIP:0060:[]Not tainted VLI EFLAGS: 00013286 (2.6.12-rc1-mm2) EIP is at agp_find_bridge+0x0/0xc77f [agpgart] eax: dff1d000 ebx: de228400 ecx: edx: 00d0 esi: dd86 edi: de228450 ebp: e1a4bd90 esp: dd811f48 ds: 007b es: 007b ss: 0068 Process modprobe (pid: 4698, threadinfo=dd81 task=dfca3030) Stack: e1a085fb dd86 e1a4c240 e1a06ed0 dd86 e1a4c240 dff1d000 dd86 e1a071ce e1a4c240 c01abfaf e1a4bd90 dff1d000 e1a4c240 0310 e1a03adf 0310 fffc e1a4e180 dd81 dd81 Call Trace: [] drm_agp_init+0x3b/0xb0 [drm] [] drm_fill_in_dev+0xf0/0x1b0 [drm] [] drm_get_dev+0x4e/0xc0 [drm] [] kobject_get+0xf/0x20 [] drm_init+0x6f/0xb0 [drm] [] sys_init_module+0x139/0x1e0 [] sysenter_past_esp+0x54/0x75 Code: 6e 66 69 67 5f 62 79 74 65 00 61 67 70 5f 70 75 74 5f 62 72 69 64 67 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 65 00 a7 87 e0 dc 94 cd de dc 94 cd de 00 00 00 00 00 00 00 00 00 -- Stefano Rivoir # # Automatically generated make config: don't edit # Linux kernel version: 2.6.12-rc1-mm2 # Thu Mar 24 14:26:36 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_CLEAR_PAGES=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y CONFIG_REGPARM=y
Re: 2.6.12-rc1-mm2
Alle 13:41, giovedì 24 marzo 2005, Andrew Morton ha scritto: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2. 6.12-rc1-mm2/ - Some fixes for the recent DRM problems. Hi Andrew, While I was OK with DRM up to 2.6.12-rc1-mm1, now I get this at startup, and Xorg fails to enable DRI (attached, lspci and .config): Unable to handle kernel paging request at virtual address 72ff64d7 printing eip: e087eb44 *pde = Oops: 0002 [#1] PREEMPT Modules linked in: radeon drm sd_mod scsi_mod lp hotkey fan container button ide_cd 8250_pnp parport_pc parport floppy pcspkr sk98lin yenta_socket rsrc_nonstatic pcmcia_core ehci_hcd usbhid ohci_hcd snd_intel8x0m 8250_pci 8250 serial_core ohci1394 ieee1394 sis_agp agpgart vfat fat video thermal processor ac battery snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc skge evdev CPU:0 EIP:0060:[e087eb44]Not tainted VLI EFLAGS: 00013286 (2.6.12-rc1-mm2) EIP is at agp_find_bridge+0x0/0xc77f [agpgart] eax: dff1d000 ebx: de228400 ecx: edx: 00d0 esi: dd86 edi: de228450 ebp: e1a4bd90 esp: dd811f48 ds: 007b es: 007b ss: 0068 Process modprobe (pid: 4698, threadinfo=dd81 task=dfca3030) Stack: e1a085fb dd86 e1a4c240 e1a06ed0 dd86 e1a4c240 dff1d000 dd86 e1a071ce e1a4c240 c01abfaf e1a4bd90 dff1d000 e1a4c240 0310 e1a03adf 0310 fffc e1a4e180 dd81 dd81 Call Trace: [e1a085fb] drm_agp_init+0x3b/0xb0 [drm] [e1a06ed0] drm_fill_in_dev+0xf0/0x1b0 [drm] [e1a071ce] drm_get_dev+0x4e/0xc0 [drm] [c01abfaf] kobject_get+0xf/0x20 [e1a03adf] drm_init+0x6f/0xb0 [drm] [c0130589] sys_init_module+0x139/0x1e0 [c0102fdb] sysenter_past_esp+0x54/0x75 Code: 6e 66 69 67 5f 62 79 74 65 00 61 67 70 5f 70 75 74 5f 62 72 69 64 67 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 65 00 c0 a7 87 e0 dc 94 cd de dc 94 cd de 00 00 00 00 00 00 00 00 00 -- Stefano Rivoir # # Automatically generated make config: don't edit # Linux kernel version: 2.6.12-rc1-mm2 # Thu Mar 24 14:26:36 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_CLEAR_PAGES=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI
Re: 2.6.12-rc1-mm2 (build error In function `zft_init')
I'm getting the following build error with 2.6.12-rc1-mm2: CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o(.init.text+0x4323): In function `zft_init': : undefined reference to `class_device_creat' make: *** [.tmp_vmlinux1] Error 1 2.6.12-rc1-mm1 built and is running just fine. I used the -rc1-mm1 .config, did make oldconfig, make bzImage. Here is the .config: [EMAIL PROTECTED] linux-2.6.12-rc1-mm2]$ grep ^CONFIG .config CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_CLEAR_PAGES=y CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_LOCALVERSION=-GX110 CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KALLSYMS=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 CONFIG_BASE_SMALL=0 CONFIG_X86_PC=y CONFIG_MPENTIUMIII=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_P4THERMAL=y CONFIG_MICROCODE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_EDD=y CONFIG_NOHIGHMEM=y CONFIG_MTRR=y CONFIG_PHYSICAL_START=0x10 CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_LEGACY_PROC=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=32000 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE= CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_AOE_PARTITIONS=16 CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=y CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_IDEDMA_PCI_AUTO=y CONFIG_BLK_DEV_PIIX=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDEDMA_AUTO=y CONFIG_NET=y CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_NET_KEY=y CONFIG_INET=y CONFIG_IP_TCPDIAG=y CONFIG_XFRM=y CONFIG_NETDEVICES=y CONFIG_NET_ETHERNET=y CONFIG_MII=y CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=y CONFIG_INPUT=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=y CONFIG_SERIO_LIBPS2=y CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_NR_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_SHARE_IRQ=y CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_FTAPE=y CONFIG_ZFTAPE=y CONFIG_ZFT_DFLT_BLK_SZ=10240 CONFIG_ZFT_COMPRESSOR=y CONFIG_FT_NR_BUFFERS=3 CONFIG_FT_PROC_FS=y CONFIG_FT_NORMAL_DEBUG=y CONFIG_FT_STD_FDC=y CONFIG_FT_FDC_THR=8 CONFIG_FT_FDC_MAX_RATE=2000 CONFIG_FT_ALPHA_CLOCK=0 CONFIG_AGP=y CONFIG_AGP_INTEL=y CONFIG_VIDEO_DEV=y CONFIG_VIDEO_SELECT=y CONFIG_VGA_CONSOLE=y CONFIG_DUMMY_CONSOLE=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT3_FS=y CONFIG_JBD=y CONFIG_FS_MBCACHE=y CONFIG_REISER4_FS=y CONFIG_REISERFS_FS=y CONFIG_DNOTIFY=y CONFIG_ISO9660_FS=y CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1 CONFIG_NTFS_FS=y CONFIG_NTFS_RW=y CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y CONFIG_DEVFS_FS=y CONFIG_TMPFS=y CONFIG_RAMFS=y CONFIG_PARTITION_ADVANCED=y CONFIG_MSDOS_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT=iso8859-1 CONFIG_NLS_CODEPAGE_437=y CONFIG_NLS_CODEPAGE_850=y CONFIG_NLS_ASCII=y CONFIG_NLS_ISO8859_1=y CONFIG_NLS_UTF8=y CONFIG_PRINTK_TIME=y CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=14 CONFIG_DEBUG_BUGVERBOSE=y CONFIG_FRAME_POINTER=y CONFIG_EARLY_PRINTK=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y CONFIG_SECURITY=y CONFIG_SECURITY_NETWORK=y CONFIG_SECURITY_CAPABILITIES=y CONFIG_CRC_CCITT=y CONFIG_CRC32=y CONFIG_LIBCRC32C=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_PC=y Steven - 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.12-rc1-mm2
Stefano Rivoir wrote: Alle 13:41, giovedì 24 marzo 2005, Andrew Morton ha scritto: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2. 6.12-rc1-mm2/ - Some fixes for the recent DRM problems. Hi Andrew, While I was OK with DRM up to 2.6.12-rc1-mm1, now I get this at startup, and Xorg fails to enable DRI (attached, lspci and .config): Unable to handle kernel paging request at virtual address 72ff64d7 printing eip: e087eb44 *pde = Oops: 0002 [#1] PREEMPT Modules linked in: radeon drm sd_mod scsi_mod lp hotkey fan container button ide_cd 8250_pnp parport_pc parport floppy pcspkr sk98lin yenta_socket rsrc_nonstatic pcmcia_core ehci_hcd usbhid ohci_hcd snd_intel8x0m 8250_pci 8250 serial_core ohci1394 ieee1394 sis_agp agpgart vfat fat video thermal processor ac battery snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc skge evdev CPU:0 EIP:0060:[e087eb44]Not tainted VLI EFLAGS: 00013286 (2.6.12-rc1-mm2) EIP is at agp_find_bridge+0x0/0xc77f [agpgart] eax: dff1d000 ebx: de228400 ecx: edx: 00d0 esi: dd86 edi: de228450 ebp: e1a4bd90 esp: dd811f48 ds: 007b es: 007b ss: 0068 Process modprobe (pid: 4698, threadinfo=dd81 task=dfca3030) Stack: e1a085fb dd86 e1a4c240 e1a06ed0 dd86 e1a4c240 dff1d000 dd86 e1a071ce e1a4c240 c01abfaf e1a4bd90 dff1d000 e1a4c240 0310 e1a03adf 0310 fffc e1a4e180 dd81 dd81 Call Trace: [e1a085fb] drm_agp_init+0x3b/0xb0 [drm] [e1a06ed0] drm_fill_in_dev+0xf0/0x1b0 [drm] [e1a071ce] drm_get_dev+0x4e/0xc0 [drm] [c01abfaf] kobject_get+0xf/0x20 [e1a03adf] drm_init+0x6f/0xb0 [drm] [c0130589] sys_init_module+0x139/0x1e0 [c0102fdb] sysenter_past_esp+0x54/0x75 Code: 6e 66 69 67 5f 62 79 74 65 00 61 67 70 5f 70 75 74 5f 62 72 69 64 67 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 65 00 c0 a7 87 e0 dc 94 cd de dc 94 cd de 00 00 00 00 00 00 00 00 00 I get a similar Oops at boot; I noticed this warning during compilation: drivers/char/drm/drm_agpsupport.c: In function `drm_agp_init': drivers/char/drm/drm_agpsupport.c:391: warning: implicit declaration of function `agp_find_bridge' drivers/char/drm/drm_agpsupport.c:391: warning: assignment makes pointer from integer without a cast I dont know what header to include/modify to make it go away. DRM and AGP are compiled into the kernel (no modules). -- Manuel Lauss - 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.12-rc1-mm2
Stefano Rivoir a écrit : Alle 13:41, giovedì 24 marzo 2005, Andrew Morton ha scritto: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2. 6.12-rc1-mm2/ - Some fixes for the recent DRM problems. Hi Andrew, While I was OK with DRM up to 2.6.12-rc1-mm1, now I get this at startup, and Xorg fails to enable DRI (attached, lspci and .config): Same problem on my Radeon M6 LY here. This seems to be due to agp_find_bridge not being exported anymore in agp_backend.h. Dave might have forgotten it when reworking my patch. Patch attached. Brice Signoff-by: Brice Goglin [EMAIL PROTECTED] --- linux-mm/include/linux/agp_backend.h.old2005-03-24 16:17:25.0 +0100 +++ linux-mm/include/linux/agp_backend.h2005-03-24 16:10:25.0 +0100 @@ -100,6 +100,7 @@ extern int agp_bind_memory(struct agp_memory *, off_t); extern int agp_unbind_memory(struct agp_memory *); extern void agp_enable(struct agp_bridge_data *, u32); +extern struct agp_bridge_data * (*agp_find_bridge)(struct pci_dev *); extern struct agp_bridge_data *agp_backend_acquire(struct pci_dev *); extern void agp_backend_release(struct agp_bridge_data *); - 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.12-rc1-mm2
Alle 16:18, giovedì 24 marzo 2005, Brice Goglin ha scritto: Stefano Rivoir a écrit : Alle 13:41, giovedì 24 marzo 2005, Andrew Morton ha scritto: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/ 2. 6.12-rc1-mm2/ - Some fixes for the recent DRM problems. Hi Andrew, While I was OK with DRM up to 2.6.12-rc1-mm1, now I get this at startup, and Xorg fails to enable DRI (attached, lspci and .config): --- linux-mm/include/linux/agp_backend.h.old2005-03-24 16:17:25.0 +0100 +++ linux-mm/include/linux/agp_backend.h2005-03-24 16:10:25.0 +0100 @@ -100,6 +100,7 @@ extern int agp_bind_memory(struct agp_memory *, off_t); extern int agp_unbind_memory(struct agp_memory *); extern void agp_enable(struct agp_bridge_data *, u32); +extern struct agp_bridge_data * (*agp_find_bridge)(struct pci_dev *); extern struct agp_bridge_data *agp_backend_acquire(struct pci_dev *); extern void agp_backend_release(struct agp_bridge_data *); Right, that fixed it for me. Thank you. -- Stefano Rivoir - 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.12-rc1-mm2 (patch to fix build error In function `zft_init')
Steven Cole wrote:
I'm getting the following build error with 2.6.12-rc1-mm2:
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o(.init.text+0x4323): In function `zft_init':
: undefined reference to `class_device_creat'
make: *** [.tmp_vmlinux1] Error 1
I glanced at the code, and this little patch fixes the problem:
Steven
Signed-off by: Steven Cole [EMAIL PROTECTED]
--- linux-2.6.12-rc1-mm2/drivers/char/ftape/zftape/zftape-init.c.orig
2005-03-24 08:43:30.0 -0700
+++ linux-2.6.12-rc1-mm2/drivers/char/ftape/zftape/zftape-init.c
2005-03-24 08:43:56.0 -0700
@@ -331,7 +331,7 @@
zft_class = class_create(THIS_MODULE, zft);
for (i = 0; i 4; i++) {
- class_device_creat(zft_class, MKDEV(QIC117_TAPE_MAJOR, i),
NULL, qft%i, i);
+ class_device_create(zft_class, MKDEV(QIC117_TAPE_MAJOR, i),
NULL, qft%i, i);
devfs_mk_cdev(MKDEV(QIC117_TAPE_MAJOR, i),
S_IFCHR | S_IRUSR | S_IWUSR,
qft%i, i);
Re: 2.6.12-rc1-mm2
On Thu, 2005-03-24 at 04:41 -0800, Andrew Morton wrote: -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually they are pulled 3-4 hours before the release of the -mm kernel. Andrew, Do you notify the subsystem maintainers ahead of time so that critical fixes can be pushed to BK? I am thinking of the recent ALSA example, where the emu10k1 driver was b0rked in 2.6.12-mm1, but the fix had been in ALSA CVS for a week. Lee - 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.12-rc1-mm2
Stefano Rivoir [EMAIL PROTECTED] wrote: Alle 16:18, giovedì 24 marzo 2005, Brice Goglin ha scritto: Stefano Rivoir a écrit : Alle 13:41, giovedì 24 marzo 2005, Andrew Morton ha scritto: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/ 2. 6.12-rc1-mm2/ - Some fixes for the recent DRM problems. Hi Andrew, While I was OK with DRM up to 2.6.12-rc1-mm1, now I get this at startup, and Xorg fails to enable DRI (attached, lspci and .config): --- linux-mm/include/linux/agp_backend.h.old2005-03-24 16:17:25.0 +0100 +++ linux-mm/include/linux/agp_backend.h2005-03-24 16:10:25.0 +0100 @@ -100,6 +100,7 @@ extern int agp_bind_memory(struct agp_memory *, off_t); extern int agp_unbind_memory(struct agp_memory *); extern void agp_enable(struct agp_bridge_data *, u32); +extern struct agp_bridge_data * (*agp_find_bridge)(struct pci_dev *); extern struct agp_bridge_data *agp_backend_acquire(struct pci_dev *); extern void agp_backend_release(struct agp_bridge_data *); Right, that fixed it for me. There were contradictory patches in flight and I stuck the latest drm tree into rc1-mm2 at the last minute, alas. You should revert agp-make-some-code-static.patch. But I assume that fixing the compile warnings does not fix the oopses which Stefano and Brice are seeing? - 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.12-rc1-mm2
Lee Revell [EMAIL PROTECTED] wrote: On Thu, 2005-03-24 at 04:41 -0800, Andrew Morton wrote: -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually they are pulled 3-4 hours before the release of the -mm kernel. Andrew, Do you notify the subsystem maintainers ahead of time so that critical fixes can be pushed to BK? Occasionally I'll go out and ping people, but almost always the subsystem guys know what the development cycle is, and they appropriately decide which code should go in, and when. I am thinking of the recent ALSA example, where the emu10k1 driver was b0rked in 2.6.12-mm1, but the fix had been in ALSA CVS for a week. We've been discussing how to get ALSA CVS into ALSA bk more promptly. - 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.12-rc1-mm2
Andrew Morton a écrit : Stefano Rivoir [EMAIL PROTECTED] wrote: --- linux-mm/include/linux/agp_backend.h.old2005-03-24 16:17:25.0 +0100 +++ linux-mm/include/linux/agp_backend.h2005-03-24 16:10:25.0 +0100 @@ -100,6 +100,7 @@ extern int agp_bind_memory(struct agp_memory *, off_t); extern int agp_unbind_memory(struct agp_memory *); extern void agp_enable(struct agp_bridge_data *, u32); +extern struct agp_bridge_data * (*agp_find_bridge)(struct pci_dev *); extern struct agp_bridge_data *agp_backend_acquire(struct pci_dev *); extern void agp_backend_release(struct agp_bridge_data *); Right, that fixed it for me. There were contradictory patches in flight and I stuck the latest drm tree into rc1-mm2 at the last minute, alas. You should revert agp-make-some-code-static.patch. But I assume that fixing the compile warnings does not fix the oopses which Stefano and Brice are seeing? My patch does fix both the compile warnings and my oops on my Radeon laptop. Brice - 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.12-rc1-mm2 - ppc32 build fails.
cliff white [EMAIL PROTECTED] wrote: Error message: CC arch/ppc/kernel/setup.o In file included from arch/ppc/kernel/setup.c:43: include/asm/ppc_sys.h:29:2: #error need definition of ppc_sys_devices In file included from arch/ppc/kernel/setup.c:43: include/asm/ppc_sys.h:61: warning: parameter has incomplete type include/asm/ppc_sys.h:64: warning: parameter has incomplete type This should fix it. From: Kumar Gala [EMAIL PROTECTED] Signed-off-by: Andrew Morton [EMAIL PROTECTED] --- 25-akpm/arch/ppc/kernel/setup.c |5 - 1 files changed, 4 insertions(+), 1 deletion(-) diff -puN arch/ppc/kernel/setup.c~ppc32-report-chipset-version-in-common-proc-cpuinfo-handling-fix arch/ppc/kernel/setup.c --- 25/arch/ppc/kernel/setup.c~ppc32-report-chipset-version-in-common-proc-cpuinfo-handling-fix 2005-03-24 12:27:39.0 -0800 +++ 25-akpm/arch/ppc/kernel/setup.c 2005-03-24 12:27:39.0 -0800 @@ -40,7 +40,10 @@ #include asm/nvram.h #include asm/xmon.h #include asm/ocp.h + +#if defined(CONFIG_85xx) || defined(CONFIG_83xx) #include asm/ppc_sys.h +#endif #if defined CONFIG_KGDB #include asm/kgdb.h @@ -247,7 +250,7 @@ int show_cpuinfo(struct seq_file *m, voi seq_printf(m, bogomips\t: %lu.%02lu\n, lpj / (50/HZ), (lpj / (5000/HZ)) % 100); -#if defined (CONFIG_85xx) || defined (CONFIG_83xx) +#if defined(CONFIG_85xx) || defined(CONFIG_83xx) if (cur_ppc_sys_spec-ppc_sys_name) seq_printf(m, chipset\t\t: %s\n, cur_ppc_sys_spec-ppc_sys_name); _ - 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.12-rc1-mm2 - ppc32 build fails.
On Thu, 24 Mar 2005 12:28:08 -0800 Andrew Morton [EMAIL PROTECTED] wrote: cliff white [EMAIL PROTECTED] wrote: Error message: CC arch/ppc/kernel/setup.o In file included from arch/ppc/kernel/setup.c:43: include/asm/ppc_sys.h:29:2: #error need definition of ppc_sys_devices In file included from arch/ppc/kernel/setup.c:43: include/asm/ppc_sys.h:61: warning: parameter has incomplete type include/asm/ppc_sys.h:64: warning: parameter has incomplete type This should fix it. Fixes that problem, now i hit the kernel OOPS at drm initalization. Thought i saw a patch somewhere already for that... cliffw From: Kumar Gala [EMAIL PROTECTED] Signed-off-by: Andrew Morton [EMAIL PROTECTED] --- 25-akpm/arch/ppc/kernel/setup.c |5 - 1 files changed, 4 insertions(+), 1 deletion(-) diff -puN arch/ppc/kernel/setup.c~ppc32-report-chipset-version-in-common-proc-cpuinfo-handling-fix arch/ppc/kernel/setup.c --- 25/arch/ppc/kernel/setup.c~ppc32-report-chipset-version-in-common-proc-cpuinfo-handling-fix 2005-03-24 12:27:39.0 -0800 +++ 25-akpm/arch/ppc/kernel/setup.c 2005-03-24 12:27:39.0 -0800 @@ -40,7 +40,10 @@ #include asm/nvram.h #include asm/xmon.h #include asm/ocp.h + +#if defined(CONFIG_85xx) || defined(CONFIG_83xx) #include asm/ppc_sys.h +#endif #if defined CONFIG_KGDB #include asm/kgdb.h @@ -247,7 +250,7 @@ int show_cpuinfo(struct seq_file *m, voi seq_printf(m, bogomips\t: %lu.%02lu\n, lpj / (50/HZ), (lpj / (5000/HZ)) % 100); -#if defined (CONFIG_85xx) || defined (CONFIG_83xx) +#if defined(CONFIG_85xx) || defined(CONFIG_83xx) if (cur_ppc_sys_spec-ppc_sys_name) seq_printf(m, chipset\t\t: %s\n, cur_ppc_sys_spec-ppc_sys_name); _ - 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/ -- Ive always gone through periods where I bolt upright at four in the morning; now at least theres a reason. -Michael Feldman - 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.12-rc1-mm2 (patch to fix build error In function `zft_init')
On Thu, Mar 24, 2005 at 08:55:13AM -0700, Steven Cole wrote: Steven Cole wrote: I'm getting the following build error with 2.6.12-rc1-mm2: CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o(.init.text+0x4323): In function `zft_init': : undefined reference to `class_device_creat' make: *** [.tmp_vmlinux1] Error 1 I glanced at the code, and this little patch fixes the problem: Ick, sorry, that was my fault. I've applied this patch to my trees, thanks. Hm, I wonder how I missed this, I did do a 'make allmodconfig' build to try to catch this kind of 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.12-rc1-mm2 (patch to fix build error In function `zft_init')
Greg KH [EMAIL PROTECTED] wrote: I glanced at the code, and this little patch fixes the problem: Ick, sorry, that was my fault. I've applied this patch to my trees, thanks. Hm, I wonder how I missed this, I did do a 'make allmodconfig' build to try to catch this kind of stuff... allmodconfig doesn't catch BROKEN_ON_SMP code. I've been caught out by that a few times. - 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.12-rc1-mm2
Hi, On Thursday, 24 of March 2005 21:17, Andrew Morton wrote: Lee Revell [EMAIL PROTECTED] wrote: On Thu, 2005-03-24 at 04:41 -0800, Andrew Morton wrote: -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually they are pulled 3-4 hours before the release of the -mm kernel. Andrew, Do you notify the subsystem maintainers ahead of time so that critical fixes can be pushed to BK? Occasionally I'll go out and ping people, but almost always the subsystem guys know what the development cycle is, and they appropriately decide which code should go in, and when. I am thinking of the recent ALSA example, where the emu10k1 driver was b0rked in 2.6.12-mm1, but the fix had been in ALSA CVS for a week. We've been discussing how to get ALSA CVS into ALSA bk more promptly. BTW, on 2.6.12-rc1-mm2 I can't rmmod the snd_intel8x0 module (the process goes into the D state immediately), which did not happen before. This is 100% reproducible, on two different AMD64-based boxes, with different sound chips. Greets, Rafael -- - Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll Alice's Adventures in Wonderland - 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.12-rc1-mm2
On Thursday, 24 of March 2005 23:31, Rafael J. Wysocki wrote: Hi, On Thursday, 24 of March 2005 21:17, Andrew Morton wrote: Lee Revell [EMAIL PROTECTED] wrote: On Thu, 2005-03-24 at 04:41 -0800, Andrew Morton wrote: -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually they are pulled 3-4 hours before the release of the -mm kernel. Andrew, Do you notify the subsystem maintainers ahead of time so that critical fixes can be pushed to BK? Occasionally I'll go out and ping people, but almost always the subsystem guys know what the development cycle is, and they appropriately decide which code should go in, and when. I am thinking of the recent ALSA example, where the emu10k1 driver was b0rked in 2.6.12-mm1, but the fix had been in ALSA CVS for a week. We've been discussing how to get ALSA CVS into ALSA bk more promptly. BTW, on 2.6.12-rc1-mm2 I can't rmmod the snd_intel8x0 module (the process goes into the D state immediately), which did not happen before. This is 100% reproducible, on two different AMD64-based boxes, with different sound chips. Er, sorry for the noise on alsa-devel. Actually, rmmod doesn't work for me at all on x86-64 (on two different boxes). Greets, Rafael -- - Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll Alice's Adventures in Wonderland - 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.12-rc1-mm2
Le 24.03.2005 23:31, Rafael J. Wysocki a crit : Hi, On Thursday, 24 of March 2005 21:17, Andrew Morton wrote: Lee Revell [EMAIL PROTECTED] wrote: On Thu, 2005-03-24 at 04:41 -0800, Andrew Morton wrote: -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually they are pulled 3-4 hours before the release of the -mm kernel. Andrew, Do you notify the subsystem maintainers ahead of time so that critical fixes can be pushed to BK? Occasionally I'll go out and ping people, but almost always the subsystem guys know what the development cycle is, and they appropriately decide which code should go in, and when. I am thinking of the recent ALSA example, where the emu10k1 driver was b0rked in 2.6.12-mm1, but the fix had been in ALSA CVS for a week. We've been discussing how to get ALSA CVS into ALSA bk more promptly. BTW, on 2.6.12-rc1-mm2 I can't rmmod the snd_intel8x0 module (the process goes into the D state immediately), which did not happen before. This is 100% reproducible, on two different AMD64-based boxes, with different sound chips. Greets, Rafael hello, Same kinds of problem here. It depends on the removed module. I mean: rmmod loop or rmmod pcspkr works. But rmmod snd_ens1371 or rmmod ohci1394 hangs. Sysrq-T when rmmoding snd_ens1371 : rmmod D C92EBE8C 0 8231 8159 (NOTLB) c92ebea0 0082 0003 c92ebe8c 5685fc00 000f4253 cd624530 cd624658 cff60874 cff60844 c92ebebc c92ebef0 c02618c7 cd624530 c0113137 0282 cd248c20 cd248c07 0001 cd624530 Call Trace: [wait_for_completion+124/193] wait_for_completion+0x7c/0xc1 [c02618c7] wait_for_completion+0x7c/0xc1 [device_release_driver+52/116] device_release_driver+0x34/0x74 [c01f0ae3] device_release_driver+0x34/0x74 [__remove_driver+8/12] __remove_driver+0x8/0xc [c01f0b2b] __remove_driver+0x8/0xc [driver_for_each_device+50/87] driver_for_each_device+0x32/0x57 [c01f0bd8] driver_for_each_device+0x32/0x57 [driver_detach+17/19] driver_detach+0x11/0x13 [c01f0b40] driver_detach+0x11/0x13 [bus_remove_driver+76/130] bus_remove_driver+0x4c/0x82 [c01f05eb] bus_remove_driver+0x4c/0x82 [driver_unregister+14/23] driver_unregister+0xe/0x17 [c01f0cb2] driver_unregister+0xe/0x17 [pci_unregister_driver+14/23] pci_unregister_driver+0xe/0x17 [c019b242] pci_unregister_driver+0xe/0x17 [sys_delete_module+322/379] sys_delete_module+0x142/0x17b [c0128356] sys_delete_module+0x142/0x17b Sysrq-T when rmmoding ohci1394 : rmmod D 0001 0 12353 10401 (NOTLB) cefa9ea0 0082 c012f3d9 0001 0001e848 e88bbbc0 000f426d cb613570 cb613698 cff60074 cff60044 cefa9ebc cefa9ef0 c02618d7 cb613570 c0113137 0286 cd379e60 cd379e47 0001 cb613570 Call Trace: [wait_for_completion+124/193] wait_for_completion+0x7c/0xc1 [c02618d7] wait_for_completion+0x7c/0xc1 [device_release_driver+52/116] device_release_driver+0x34/0x74 [c01f0aeb] device_release_driver+0x34/0x74 [__remove_driver+8/12] __remove_driver+0x8/0xc [c01f0b33] __remove_driver+0x8/0xc [driver_for_each_device+50/87] driver_for_each_device+0x32/0x57 [c01f0be0] driver_for_each_device+0x32/0x57 [driver_detach+17/19] driver_detach+0x11/0x13 [c01f0b48] driver_detach+0x11/0x13 [bus_remove_driver+76/130] bus_remove_driver+0x4c/0x82 [c01f05f3] bus_remove_driver+0x4c/0x82 [driver_unregister+14/23] driver_unregister+0xe/0x17 [c01f0cba] driver_unregister+0xe/0x17 [pci_unregister_driver+14/23] pci_unregister_driver+0xe/0x17 [c019b242] pci_unregister_driver+0xe/0x17 [sys_delete_module+322/379] sys_delete_module+0x142/0x17b [c0128356] sys_delete_module+0x142/0x17b [sysenter_past_esp+84/117] sysenter_past_esp+0x54/0x75 .config attached ~~ laurent # # Automatically generated make config: don't edit # Linux kernel version: 2.6.12-rc1-mm2 # Thu Mar 24 23:38:31 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_CLEAR_PAGES=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set CONFIG_EMBEDDED=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set
Re: 2.6.12-rc1-mm2
Laurent Riffard [EMAIL PROTECTED] wrote: hello, Same kinds of problem here. It depends on the removed module. I mean: rmmod loop or rmmod pcspkr works. But rmmod snd_ens1371 or rmmod ohci1394 hangs. Sysrq-T when rmmoding snd_ens1371 : rmmod D C92EBE8C 0 8231 8159 (NOTLB) c92ebea0 0082 0003 c92ebe8c 5685fc00 000f4253 cd624530 cd624658 cff60874 cff60844 c92ebebc c92ebef0 c02618c7 cd624530 c0113137 0282 cd248c20 cd248c07 0001 cd624530 Call Trace: [wait_for_completion+124/193] wait_for_completion+0x7c/0xc1 [c02618c7] wait_for_completion+0x7c/0xc1 [device_release_driver+52/116] device_release_driver+0x34/0x74 [c01f0ae3] device_release_driver+0x34/0x74 [__remove_driver+8/12] __remove_driver+0x8/0xc [c01f0b2b] __remove_driver+0x8/0xc [driver_for_each_device+50/87] driver_for_each_device+0x32/0x57 [c01f0bd8] driver_for_each_device+0x32/0x57 [driver_detach+17/19] driver_detach+0x11/0x13 [c01f0b40] driver_detach+0x11/0x13 [bus_remove_driver+76/130] bus_remove_driver+0x4c/0x82 [c01f05eb] bus_remove_driver+0x4c/0x82 [driver_unregister+14/23] driver_unregister+0xe/0x17 [c01f0cb2] driver_unregister+0xe/0x17 [pci_unregister_driver+14/23] pci_unregister_driver+0xe/0x17 [c019b242] pci_unregister_driver+0xe/0x17 [sys_delete_module+322/379] sys_delete_module+0x142/0x17b [c0128356] sys_delete_module+0x142/0x17b It looks like we're getting stuck in the wait_for_completion() in the new klist_remove(). - 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.12-rc1-mm2
Hi, Andrew Morton wrote: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc1/2.6.12-rc1-mm2/ - Added David Miller's networking tree to the -mm lineup as bk-net.patch. - Added Herbert Xu's crypto development tree to the -mm lineup as bk-cryptodev.patch. -mm kernels now aggregate Linus's tree and 34 subsystem trees. Usually they are pulled 3-4 hours before the release of the -mm kernel. Usually it is possible to determine the latest cset from each tree by looking at the first couple of lines of the relevant patch in the broken-out/ directory. Although sometimes it isn't there if I had to massage the diff. - There may be an x86_64 problem here, although it works for me. If it fails early in boot, try reverting x86_64-separate-amd-cmp-detection-from-hyper-threading.patch - There's some work here on the recent USB PM resume bugs. If you had problems there, please test and be sure to cc linux-usb-devel@lists.sourceforge.net in any reports. - Some fixes for the recent DRM problems. - Big DVB update - md updates - nfs4 server updates - Lots more fixes - Lots more bugs. Fails to compile for me: CC [M] fs/nfs/dir.o CC [M] fs/nfs/inode.o CC [M] fs/nfs/nfs4proc.o fs/nfs/nfs4proc.c:2976: error: static declaration of 'nfs4_file_inode_operations' follows non-static declaration fs/nfs/nfs4_fs.h:179: error: previous declaration of 'nfs4_file_inode_operations' was here make[2]: *** [fs/nfs/nfs4proc.o] Error 1 make[1]: *** [fs/nfs] Error 2 make: *** [fs] Error 2 I needed to remove this line: extern struct inode_operations nfs4_file_inode_operations; from fs/nfs/nfs4_fs.h. Patch attached. Reuben --- fs/nfs/nfs4_fs.h2005-03-25 11:40:51.0 +1200 +++ fs/nfs/nfs4_fs.h2005-03-25 11:44:28.0 +1200 @@ -176,7 +176,6 @@ extern struct dentry_operations nfs4_dentry_operations; extern struct inode_operations nfs4_dir_inode_operations; -extern struct inode_operations nfs4_file_inode_operations; /* inode.c */ extern ssize_t nfs4_getxattr(struct dentry *, const char *, void *, size_t);
Re: 2.6.12-rc1-mm2
On Thu, 24 Mar 2005, Andrew Morton wrote: Laurent Riffard [EMAIL PROTECTED] wrote: hello, Same kinds of problem here. It depends on the removed module. I mean: rmmod loop or rmmod pcspkr works. But rmmod snd_ens1371 or rmmod ohci1394 hangs. Sysrq-T when rmmoding snd_ens1371 : snip It looks like we're getting stuck in the wait_for_completion() in the new klist_remove(). D'oh! It's getting hung while waiting to remove the current node from the list (which it can't remove because it's being used). The patch below should fix it. Pat = drivers/base/dd.c 1.3 vs edited = --- 1.3/drivers/base/dd.c 2005-03-21 12:25:04 -08:00 +++ edited/drivers/base/dd.c2005-03-24 16:55:21 -08:00 @@ -177,7 +177,7 @@ sysfs_remove_link(drv-kobj, kobject_name(dev-kobj)); sysfs_remove_link(dev-kobj, driver); - klist_remove(dev-knode_driver); + klist_del(dev-knode_driver); down(dev-sem); device_detach_shutdown(dev); - 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.12-rc1-mm2
On Thursday 24 March 2005 23:21, Brice Goglin wrote: Andrew Morton a écrit : Stefano Rivoir [EMAIL PROTECTED] wrote: --- linux-mm/include/linux/agp_backend.h.old +++ linux-mm/include/linux/agp_backend.h +extern struct agp_bridge_data * (*agp_find_bridge)(struct pci_dev *); Right, that fixed it for me. There were contradictory patches in flight and I stuck the latest drm tree into rc1-mm2 at the last minute, alas. You should revert agp-make-some-code-static.patch. But I assume that fixing the compile warnings does not fix the oopses which Stefano and Brice are seeing? My patch does fix both the compile warnings and my oops on my Radeon laptop. It also allows my machine to boot. Alexey ... drm_agp_init+0x30/0x8e drm_fill_in_dev+0xe7/0x195 drm_get_dev+0x4a/0xba kobject_get+0xf/0x13 do_initcalls+0x54/0xb0 init+0x0/0x100 init+0x0/0x100 kernel_thread_helper+0x0/0x0b kernel_thread_helper+0x5/0x0b ... 0Kernel panic - not syncing: Attempted to kill init! - 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.12-rc1-mm2
On Thu, Mar 24, 2005 at 05:00:18PM -0800, Patrick Mochel wrote: On Thu, 24 Mar 2005, Andrew Morton wrote: Laurent Riffard [EMAIL PROTECTED] wrote: hello, Same kinds of problem here. It depends on the removed module. I mean: rmmod loop or rmmod pcspkr works. But rmmod snd_ens1371 or rmmod ohci1394 hangs. Sysrq-T when rmmoding snd_ens1371 : snip It looks like we're getting stuck in the wait_for_completion() in the new klist_remove(). D'oh! It's getting hung while waiting to remove the current node from the list (which it can't remove because it's being used). The patch below should fix it. Thanks, I've added this to my bk trees. 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/
