Re: taint/module: Fix problems when out-of-kernel driver defines true or false
Latest pull of 4.10-rc4 includes the fix. Kernel builds and so does modules for VirtualBox-5.1-5.1.14_112924. # lsmod|grep vbox vboxpci24576 0 vboxnetadp 28672 0 vboxnetflt 28672 0 vboxdrv 417792 3 vboxnetadp,vboxnetflt,vboxpci git show - commit 0aa0313f9d576affd7747cc3f179feb097d28990 Merge: 4b19a9e20bf9 5eb7c0d04f04 Author: Linus Torvalds Date: Tue Jan 17 14:49:21 2017 -0800 Merge tag 'modules-for-v4.10-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux Pull modules fix from Jessica Yu: - fix out-of-tree module breakage when it supplies its own definitions of true and false * tag 'modules-for-v4.10-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux: taint/module: Fix problems when out-of-kernel driver defines true or false Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks
Re: taint/module: Fix problems when out-of-kernel driver defines true or false
http://lkml.iu.edu//hypermail/linux/kernel/1701.0/01592.html says Larry's patch was applied Jan. 3 2017. So far it hasn't showed in pull updates. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks
Re: Linux 3.19-rc1 - merge window closed
On 22/12/14 23:22, Paul Bolle wrote: On Mon, 2014-12-22 at 15:02 -0800, Linus Torvalds wrote: Hmm. So it seems that there is something wrong with the dependency generation for the generated header files. Possibly limited to just the uapi files. But I can't seem to recreate it even by trying to first build 3.18-rc2 and then switching to 3.19-rc1. So there's something not-very-straightforward going on, possibly including some nasty race in the Makefiles. The basically random build failure in https://lkml.org/lkml/2014/12/22/164 might be related. Still makes no sense to me whatsoever. Paul Bolle tindog:/usr/src/linux-3.19.0-rc1 # grep GM204_DISP_CORE_CHANNEL_DMA drivers/gpu/drm/nouveau/core/include/nvif/class.h tindog:/usr/src/linux-3.19.0-rc1 # Checking the other 2 boxes it's defined so I started with a fresh clone and it's now defined. As usual I did git pull on all 3 boxes to get from 3.18.0 to 3.19-rc1. tindog:/usr/src/linux # grep GM204_DISP_CORE_CHANNEL_DMA drivers/gpu/drm/nouveau/core/include/nvif/class.h #define GM204_DISP_CORE_CHANNEL_DMA 0x957d Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 3.19.0-rc1 nouvea build failure on GeForce GT 610 only
On 22/12/14 13:54, Paul Bolle wrote:
On Mon, 2014-12-22 at 14:37 +0100, Paul Bolle wrote:
On Mon, 2014-12-22 at 13:01 +, Sid Boyce wrote:
CHK kernel/config_data.h
CC [M] drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o
drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c: In function
‘nvd0_dmaobj_bind’:
drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: error:
‘GM204_DISP_CORE_CHANNEL_DMA’ undeclared (first use in this function)
case GM204_DISP_CORE_CHANNEL_DMA:
^
drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: note: each
undeclared identifier is reported only once for each function it appears in
scripts/Makefile.build:257: recipe for target
'drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o' failed
make[4]: *** [drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o] Error 1
scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm/nouveau'
failed
make[3]: *** [drivers/gpu/drm/nouveau] Error 2
scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:402: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:938: recipe for target 'drivers' failed
make: *** [drivers] Error 2
01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT
610] (rev a1)
Why would that controller influence the build?
No problems on 2 other boxes with GeForce 8600 GT] (rev a1)
I ran into this error twice, while building Fedora 21 kernel rpms for
v3.19-rc1 on my outdated ThinkPad X41 (which uses i915, for what it's
worth). The error made very little sense to me. Especially since it
didn't happen when building in the local git repository.
So I basically, well, scrubbed the rpmbuild environment. And then the
the third attempt to build kernels rpm succeeded! I assumed a hardware
failure (see outdated above) and made a mental note to investigate that
one of these days.
But your report makes me think it's not my hardware. Could there be some
_random_ failure with this driver in the build? Very odd...
A theory based on Mark's message in
https://lkml.org/lkml/2014/12/8/602 :
My two failed builds somehow used previous version of class.h, that
didn't yet have commit 1f89b4756fb8 ("drm/gm204/disp: initial support")
applied. It's that commit which added the define for
GM204_DISP_CORE_CHANNEL_DMA.
Is that even possible? Perhaps rpmbuild has a surprising way to handle
symlinks? All very puzzling...
Paul Bolle
I did a git pull up to 3.19-rc1 separately on the 3 boxes and used the
.config from 3.18.0 as the base of make oldconfig.
When the build failed I did "make mrproper" and used the .config from
one of the other boxes, then from the other, all 3 .config gave the same
error.
Successfully rebooted one of the boxes.
sabre:~ # uname -r
3.19.0-rc1-smp+
Regards ... Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus
IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff
Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for
all Computing Tasks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
3.19.0-rc1 nouvea build failure on GeForce GT 610 only
CHK kernel/config_data.h CC [M] drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c: In function ‘nvd0_dmaobj_bind’: drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: error: ‘GM204_DISP_CORE_CHANNEL_DMA’ undeclared (first use in this function) case GM204_DISP_CORE_CHANNEL_DMA: ^ drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.c:54:8: note: each undeclared identifier is reported only once for each function it appears in scripts/Makefile.build:257: recipe for target 'drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o' failed make[4]: *** [drivers/gpu/drm/nouveau/core/engine/dmaobj/nvd0.o] Error 1 scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm/nouveau' failed make[3]: *** [drivers/gpu/drm/nouveau] Error 2 scripts/Makefile.build:402: recipe for target 'drivers/gpu/drm' failed make[2]: *** [drivers/gpu/drm] Error 2 scripts/Makefile.build:402: recipe for target 'drivers/gpu' failed make[1]: *** [drivers/gpu] Error 2 Makefile:938: recipe for target 'drivers' failed make: *** [drivers] Error 2 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) No problems on 2 other boxes with GeForce 8600 GT] (rev a1) Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] Fix hang problem with GeForce GT 560 Ti and nouveau in 3.13-rc
-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks This patch stops a console hang with VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) 3.13-rc defines NVDEV_SUBDEV_MC as nvc3_mc_oclass, it needs to be defined as nvc0_mc_oclass Signed off by: Sid Boyce (sbo...@blueyonder.co.uk) Tested by: Sid Boyce (sbo...@blueyonder.co.uk) --- drivers/gpu/drm/nouveau/core/engine/device/nvc0.c 1 -+ 1 file changed, 1 insertion(+), 1 deletion(-) INDEX: linux/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c = diff -up a/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c b/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c --- a/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c 2013-11-23 13:03:23.797604441 + +++ b/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c 2014-01-02 02:13:32.445643092 + @@ -161,7 +161,7 @@ nvc0_identify(struct nouveau_device *dev device->oclass[NVDEV_SUBDEV_THERM ] = &nva3_therm_oclass; device->oclass[NVDEV_SUBDEV_MXM] = &nv50_mxm_oclass; device->oclass[NVDEV_SUBDEV_DEVINIT] = &nvc0_devinit_oclass; - device->oclass[NVDEV_SUBDEV_MC ] = nvc3_mc_oclass; + device->oclass[NVDEV_SUBDEV_MC ] = nvc0_mc_oclass; device->oclass[NVDEV_SUBDEV_BUS] = nvc0_bus_oclass; device->oclass[NVDEV_SUBDEV_TIMER ] = &nv04_timer_oclass; device->oclass[NVDEV_SUBDEV_FB ] = nvc0_fb_oclass;
Re: Possible 3.13-rc nouveau regression with GT 560 Ti
On 02/01/14 02:40, Ilia Mirkin wrote: On Wed, Jan 1, 2014 at 9:36 PM, Sid Boyce wrote: On 01/01/14 18:46, Ilia Mirkin wrote: On Wed, Jan 1, 2014 at 9:04 AM, Sid Boyce wrote: On 01/01/14 00:55, Ilia Mirkin wrote: On Tue, Dec 31, 2013 at 7:41 PM, Sid Boyce wrote: On 31/12/13 10:36, Ilia Mirkin wrote: Having a dmesg would be nice. One thing I can think of off-hand is that 3.13-rc has MSI turned on by default. You can turn it off by adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should show the offending commit fairly quickly. -ilia Adding "nouveau.config=NvMSI=0" to the command line fixed the problem. So it looks like commit 049ffa8ab33a63b3bff672d1a0ee6a35ad253fe8 introduced it. Any chance you might mmiotrace the blob (version 325 or later) to see which registers it fiddles with? Or alternatively, if you have a NVCE card (you never did end up providing the logs which would have made that apparent), could you try replacing nvc3_mc_oclass with nvc0_mc_oclass for the 0xce case in drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without the MSI disabling.) The switch has already been made for NVC8 in 0bae1d61c75 -- perhaps there are more "odd" ones. -ilia Fails exactly the same. case 0xc3: device->cname = "GF106"; device->oclass[NVDEV_SUBDEV_VBIOS ] = &nouveau_bios_oclass; device->oclass[NVDEV_SUBDEV_GPIO ] = &nv50_gpio_oclass; device->oclass[NVDEV_SUBDEV_I2C] = &nv94_i2c_oclass; device->oclass[NVDEV_SUBDEV_CLOCK ] = &nvc0_clock_oclass; device->oclass[NVDEV_SUBDEV_THERM ] = &nva3_therm_oclass; device->oclass[NVDEV_SUBDEV_MXM] = &nv50_mxm_oclass; device->oclass[NVDEV_SUBDEV_DEVINIT] = &nvc0_devinit_oclass; device->oclass[NVDEV_SUBDEV_MC ] = nvc0_mc_oclass; <<<<< device->oclass[NVDEV_SUBDEV_BUS] = nvc0_bus_oclass; device->oclass[NVDEV_SUBDEV_TIMER ] = &nv04_timer_oclass; That's the 0xc3 case... you have a nvce card, not nvc3 -- you would need to change the NVDEV_SUBDEV_MC line to nvc0_mc_oclass for the 0xce case. The dmesg and Xorg.0.log with the problem captured across a ssh link. # ps fax|grep X 5633 pts/0S+ 0:00 \_ grep --color=auto X 5160 tty7 Ss+0:08 \_ /usr/bin/Xorg -br :0 vt7 -nolisten tcp -auth /var/lib/kdm/AuthFiles/A:0-yqspza Also # echo mmiotrace > /sys/kernel/debug/tracing/current_tracer -bash: echo: write error: Invalid argument. Take a look at https://wiki.ubuntu.com/X/MMIOTracing -ilia Of course it's a GF114. Made the change and it boots without the command line change. Great! Care to send a patch? -ilia Here it is. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --- /usr/src/linux-3.13.0-rc6/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c 2013-11-23 13:03:23.797604441 + +++ /usr/src/linux-3.13.0-rc61/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c 2014-01-02 02:13:32.445643092 + @@ -161,7 +161,7 @@ device->oclass[NVDEV_SUBDEV_THERM ] = &nva3_therm_oclass; device->oclass[NVDEV_SUBDEV_MXM] = &nv50_mxm_oclass; device->oclass[NVDEV_SUBDEV_DEVINIT] = &nvc0_devinit_oclass; - device->oclass[NVDEV_SUBDEV_MC ] = nvc3_mc_oclass; + device->oclass[NVDEV_SUBDEV_MC ] = nvc0_mc_oclass; device->oclass[NVDEV_SUBDEV_BUS] = nvc0_bus_oclass; device->oclass[NVDEV_SUBDEV_TIMER ] = &nv04_timer_oclass; device->oclass[NVDEV_SUBDEV_FB ] = nvc0_fb_oclass;
Re: Possible 3.13-rc nouveau regression with GT 560 Ti
On 01/01/14 18:46, Ilia Mirkin wrote: On Wed, Jan 1, 2014 at 9:04 AM, Sid Boyce wrote: On 01/01/14 00:55, Ilia Mirkin wrote: On Tue, Dec 31, 2013 at 7:41 PM, Sid Boyce wrote: On 31/12/13 10:36, Ilia Mirkin wrote: Having a dmesg would be nice. One thing I can think of off-hand is that 3.13-rc has MSI turned on by default. You can turn it off by adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should show the offending commit fairly quickly. -ilia Adding "nouveau.config=NvMSI=0" to the command line fixed the problem. So it looks like commit 049ffa8ab33a63b3bff672d1a0ee6a35ad253fe8 introduced it. Any chance you might mmiotrace the blob (version 325 or later) to see which registers it fiddles with? Or alternatively, if you have a NVCE card (you never did end up providing the logs which would have made that apparent), could you try replacing nvc3_mc_oclass with nvc0_mc_oclass for the 0xce case in drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without the MSI disabling.) The switch has already been made for NVC8 in 0bae1d61c75 -- perhaps there are more "odd" ones. -ilia Fails exactly the same. case 0xc3: device->cname = "GF106"; device->oclass[NVDEV_SUBDEV_VBIOS ] = &nouveau_bios_oclass; device->oclass[NVDEV_SUBDEV_GPIO ] = &nv50_gpio_oclass; device->oclass[NVDEV_SUBDEV_I2C] = &nv94_i2c_oclass; device->oclass[NVDEV_SUBDEV_CLOCK ] = &nvc0_clock_oclass; device->oclass[NVDEV_SUBDEV_THERM ] = &nva3_therm_oclass; device->oclass[NVDEV_SUBDEV_MXM] = &nv50_mxm_oclass; device->oclass[NVDEV_SUBDEV_DEVINIT] = &nvc0_devinit_oclass; device->oclass[NVDEV_SUBDEV_MC ] = nvc0_mc_oclass; <<<<< device->oclass[NVDEV_SUBDEV_BUS] = nvc0_bus_oclass; device->oclass[NVDEV_SUBDEV_TIMER ] = &nv04_timer_oclass; That's the 0xc3 case... you have a nvce card, not nvc3 -- you would need to change the NVDEV_SUBDEV_MC line to nvc0_mc_oclass for the 0xce case. The dmesg and Xorg.0.log with the problem captured across a ssh link. # ps fax|grep X 5633 pts/0S+ 0:00 \_ grep --color=auto X 5160 tty7 Ss+0:08 \_ /usr/bin/Xorg -br :0 vt7 -nolisten tcp -auth /var/lib/kdm/AuthFiles/A:0-yqspza Also # echo mmiotrace > /sys/kernel/debug/tracing/current_tracer -bash: echo: write error: Invalid argument. Take a look at https://wiki.ubuntu.com/X/MMIOTracing -ilia Of course it's a GF114. Made the change and it boots without the command line change. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Possible 3.13-rc nouveau regression with GT 560 Ti
On 01/01/14 00:55, Ilia Mirkin wrote: On Tue, Dec 31, 2013 at 7:41 PM, Sid Boyce wrote: On 31/12/13 10:36, Ilia Mirkin wrote: On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce wrote: System x86_64 with openSUSE 13.1. X.Org version: 1.14.99.905 openSUSE 12.2 kernels boot successfully into a graphical screen, login to KDE4, etc. all normal. 3.13-rc kernels boot fully with X running but no graphical screen and it freezes in VC with not all the startup messages displayed but I could ssh in from another box to check dmesg and logs. Xorg.0.log which I thought I had saved did not log an error. dmesg said "nouveau Playlist update failed". Changed the GeForce GT 560 Ti for a GeForce 8600 GT and 3.13.0-rc6 is up and running. If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log information. Having a dmesg would be nice. One thing I can think of off-hand is that 3.13-rc has MSI turned on by default. You can turn it off by adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should show the offending commit fairly quickly. -ilia Adding "nouveau.config=NvMSI=0" to the command line fixed the problem. So it looks like commit 049ffa8ab33a63b3bff672d1a0ee6a35ad253fe8 introduced it. Any chance you might mmiotrace the blob (version 325 or later) to see which registers it fiddles with? Or alternatively, if you have a NVCE card (you never did end up providing the logs which would have made that apparent), could you try replacing nvc3_mc_oclass with nvc0_mc_oclass for the 0xce case in drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without the MSI disabling.) The switch has already been made for NVC8 in 0bae1d61c75 -- perhaps there are more "odd" ones. -ilia I'll have a look tomorrow - it is a NVCE card.. With everything running at the moment # echo mmiotrace > /sys/kernel/debug/tracing/current_tracer bash: echo: write error: Invalid argument I shall build a new kernel (3.13.0-rc51) with the change case 0xce: device->cname = "GF114"; device->oclass[NVDEV_SUBDEV_VBIOS ] = &nouveau_bios_oclass; device->oclass[NVDEV_SUBDEV_GPIO ] = &nv50_gpio_oclass; device->oclass[NVDEV_SUBDEV_I2C] = &nv94_i2c_oclass; device->oclass[NVDEV_SUBDEV_CLOCK ] = &nvc0_clock_oclass; device->oclass[NVDEV_SUBDEV_THERM ] = &nva3_therm_oclass; device->oclass[NVDEV_SUBDEV_MXM] = &nv50_mxm_oclass; device->oclass[NVDEV_SUBDEV_DEVINIT] = &nvc0_devinit_oclass; device->oclass[NVDEV_SUBDEV_MC ] = nvc3_mc_oclass; Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks [97.740] This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. [97.740] X.Org X Server 1.14.99.905 (1.15.0 RC 5) Release Date: 2013-12-19 [97.740] X Protocol Version 11, Revision 0 [97.740] Build Operating System: openSUSE SUSE LINUX [97.740] Current Operating System: Linux slipstream 3.13.0-rc6-smp+ #1 SMP PREEMPT Mon Dec 30 15:47:46 GMT 2013 x86_64 [97.740] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-rc6-smp+ root=UUID=9e02a4c0-c401-4874-a706-30ec3f0a98aa nouveau.config=NvMSI=0 quiet splash [97.740] Build Date: 22 December 2013 07:18:32PM [97.740] [97.740] Current version of pixman: 0.32.4 [97.740] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [97.740] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [97.740] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 1 00:26:25 2014 [97.741] (==) Using config directory: "/etc/X11/xorg.conf.d" [97.741] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [97.741] (==) No Layout section. Using the first Screen section. [97.741] (==) No screen section available. Using defaults. [97.741] (**) |-->Screen "Default Screen Section" (0) [97.741] (**) | |-->Monitor "" [97.741] (==) No monitor specified for screen "Default Screen Section". Usi
Re: Possible 3.13-rc nouveau regression with GT 560 Ti
On 31/12/13 10:36, Ilia Mirkin wrote: On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce wrote: System x86_64 with openSUSE 13.1. X.Org version: 1.14.99.905 openSUSE 12.2 kernels boot successfully into a graphical screen, login to KDE4, etc. all normal. 3.13-rc kernels boot fully with X running but no graphical screen and it freezes in VC with not all the startup messages displayed but I could ssh in from another box to check dmesg and logs. Xorg.0.log which I thought I had saved did not log an error. dmesg said "nouveau Playlist update failed". Changed the GeForce GT 560 Ti for a GeForce 8600 GT and 3.13.0-rc6 is up and running. If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log information. Having a dmesg would be nice. One thing I can think of off-hand is that 3.13-rc has MSI turned on by default. You can turn it off by adding "nouveau.config=NvMSI=0" to your kernel cmdline. If that doesn't help, a bisect restricted to drivers/gpu/drm/nouveau should show the offending commit fairly quickly. -ilia Adding "nouveau.config=NvMSI=0" to the command line fixed the problem. So it looks like commit 049ffa8ab33a63b3bff672d1a0ee6a35ad253fe8 introduced it. Thanks Ilia, Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Possible 3.13-rc nouveau regression with GT 560 Ti
System x86_64 with openSUSE 13.1. X.Org version: 1.14.99.905 openSUSE 12.2 kernels boot successfully into a graphical screen, login to KDE4, etc. all normal. 3.13-rc kernels boot fully with X running but no graphical screen and it freezes in VC with not all the startup messages displayed but I could ssh in from another box to check dmesg and logs. Xorg.0.log which I thought I had saved did not log an error. dmesg said "nouveau Playlist update failed". Changed the GeForce GT 560 Ti for a GeForce 8600 GT and 3.13.0-rc6 is up and running. If necessary I can go back to the GT 560 Ti to gather dmesg and Xorg log information. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 3.9-rc4 Makefile EXTRAVERSION still -rc3
On 24/03/13 15:45, Geert Uytterhoeven wrote:
On Sun, Mar 24, 2013 at 4:37 PM, Sid Boyce wrote:
tindog:/usr/src/XXX/linux # git pull
Already up-to-date.
tindog:/usr/src/XXX/linux # git show v3.9-rc4
fatal: ambiguous argument 'v3.9-rc4': unknown revision or path not in the
working tree.
So you didn't have v3.9-rc4 yet. Probably the mirror was not up-to-date.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Just this minute when I tried it is now 3.9.0-rc4 but the strange thing
is that it didn't say it was changing from rc3 to rc4 on any box, it
silently changed Makefile.
remote: Counting objects: 266, done.
remote: Compressing objects: 100% (36/36), done.
remote: Total 175 (delta 142), reused 172 (delta 139)
Receiving objects: 100% (175/175), 32.92 KiB, done.
Resolving deltas: 100% (142/142), completed with 52 local objects.
From https://github.com/torvalds/linux
c8c1f16..3912a67 master -> origin/master
Updating c8c1f16..3912a67
Fast-forward
Makefile | 2 +-
arch/tile/configs/tilegx_defconfig | 1 -
arch/tile/configs/tilepro_defconfig | 1 -
arch/x86/kernel/microcode_intel_early.c | 30
+++---
arch/x86/lib/usercopy_64.c | 4 ++--
drivers/firmware/Kconfig | 18 ++
drivers/firmware/efivars.c | 150
--
drivers/gpio/gpiolib-of.c| 5 ++---
drivers/md/md.c | 6 ++
drivers/md/md.h | 4 ++--
drivers/md/raid5.c | 116
+---
drivers/md/raid5.h | 5 +
drivers/pinctrl/mvebu/pinctrl-mvebu.c| 2 +-
drivers/pinctrl/pinconf.c| 2 +-
drivers/pinctrl/pinconf.h| 2 +-
drivers/pinctrl/pinctrl-abx500.c | 2 +-
drivers/pinctrl/pinmux.c | 5 +
drivers/target/iscsi/iscsi_target_auth.c | 5 -
drivers/target/target_core_file.h| 2 +-
drivers/target/target_core_pscsi.c | 11 ---
drivers/target/target_core_sbc.c | 7 +--
drivers/target/target_core_tpg.c | 3 ++-
drivers/vhost/tcm_vhost.c| 13 +
23 files changed, 266 insertions(+), 130 deletions(-)
tindog:/usr/src/XXX/linux # o Makefile
VERSION = 3
PATCHLEVEL = 9
SUBLEVEL = 0
EXTRAVERSION = -rc4
NAME = Unicycling Gorilla
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 3.9-rc4 Makefile EXTRAVERSION still -rc3
On 24/03/13 13:49, Geert Uytterhoeven wrote:
On Sun, Mar 24, 2013 at 2:13 PM, Sid Boyce wrote:
Using git pull or git clone this field in the Makefile remains unchanged.
Not for me:
$ git show v3.9-rc4
tag v3.9-rc4
Tagger: Linus Torvalds
Date: Sat Mar 23 16:52:52 2013 -0700
Linux 3.9-rc4
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAABAgAGBQJRTkBaAAoJEHm+PkMAQRiGnK8H/iAtbU3o8th651xsVY/X1lTy
uzFmZpfjwfM+OB5n69qcZL+V9I0b54ZKOa98OAtWlMPXifTWdznDNStqvQeRmodr
Eet/W9MwgsaBDw+/vaJKuBf5ny3msayPSA1jkVAjb1VfpheH5zvLXNo1857FoSfi
cl9jrD3tIrM6EmNwR+EWANjb1xYtJfnbtnF6xHpcEG64bcidEv8ZC7V48KNL16Dt
Duy5+ZIsGoHsMj45y35KP032NtBpPvCmmXOjkO8fwwAwK+IvyivKJFfo3UlvmVdr
seHQ5RgI/g0SCupLx6N4fBUNfYi/7yNn/ZAiNO06g0ErmOSs38KlRFDg63tLZ+g=
=yJhy
-END PGP SIGNATURE-
commit 8bb9660418e05bb1845ac1a2428444d78e322cc7
Author: Linus Torvalds
Date: Sat Mar 23 16:52:44 2013 -0700
Linux 3.9-rc4
diff --git a/Makefile b/Makefile
index 22113a7..54d2b2a 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 3
PATCHLEVEL = 9
SUBLEVEL = 0
-EXTRAVERSION = -rc3
+EXTRAVERSION = -rc4
NAME = Unicycling Gorilla
# *DOCUMENTATION*
$
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
This is from a fresh clone done today at 04:38.
tindog:/usr/src/XXX/linux # git branch
* master
tindog:/usr/src/XXX/linux # git pull
Already up-to-date.
tindog:/usr/src/XXX/linux # git show v3.9-rc4
fatal: ambiguous argument 'v3.9-rc4': unknown revision or path not in
the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
tag v3.9-rc3
Tagger: Linus Torvalds
Date: Sun Mar 17 15:59:39 2013 -0700
Linux 3.9-rc3
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAABAgAGBQJRRkrbAAoJEHm+PkMAQRiGy3oH/jrbHinYs0auurANgx4TdtWT
/WNajstKBqLOJJ6cnTR7sOqwOVlptt65EbbTs+qGyZ2Z2W/Lg0BMenHvNHo4ER8C
e7UbMdBCSLKBjAMKh1XCoZscGv4Exm8WRH3Vc5yP0Hafj3EzSAVLY1dta9WKKoQi
bh7D1ErUlbU1zczA1w5YbPF0LqFKRvyZOwebMCCAKAxv5wWAxmbcPNxVR4sufkjg
k6TkQ2ysgWivZAfy3tJYOcxiEu7ahpZVEuYdlZEJQXHRQUfoNljQlOp4BqKsYUai
5A0kaf2VpKay/7pkhvTfBBcF/jFJ68pYP6gQ2ThNdr0b5kOiAfMWj030Xyngnhg=
=iO9t
-END PGP SIGNATURE-
commit a937536b868b8369b98967929045f1df54234323
Author: Linus Torvalds
Date: Sun Mar 17 15:59:32 2013 -0700
Linux 3.9-rc3
diff --git a/Makefile b/Makefile
index a05ea42..22113a7 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 3
PATCHLEVEL = 9
SUBLEVEL = 0
-EXTRAVERSION = -rc2
+EXTRAVERSION = -rc3
NAME = Unicycling Gorilla
# *DOCUMENTATION*
The previous tree which I used to build the running 3.9.0-rc3, when
upgraded stays at 3.9.0-rc3.
This from box number 4 with a git pull. Exactly the same on 5 boxes, 2
with Kubuntu 12.10 and 3 with openSUSE 13.1 Milestone 0, all running
3.9.0-rc3.
root@sdrbox:/usr/src/XXX/linux# uname -r
3.9.0-rc3+
root@sdrbox:/usr/src/XXX/linux# git pull
remote: Counting objects: 3135, done.
remote: Compressing objects: 100% (476/476), done.
remote: Total 2111 (delta 1732), reused 2003 (delta 1631)
Receiving objects: 100% (2111/2111), 365.49 KiB | 235 KiB/s, done.
Resolving deltas: 100% (1732/1732), completed with 534 local objects.
From https://github.com/torvalds/linux
a937536..c8c1f16 master -> origin/master
Updating a937536..c8c1f16
Fast-forward
CREDITS |8
Documentation/hwmon/lm75|2 +-
Documentation/i2c/busses/i2c-diolan-u2c |2 +-
Documentation/sound/alsa/ALSA-Configuration.txt |2 +-
Documentation/sound/alsa/seq_oss.html |2 +-
MAINTAINERS | 33
+
arch/arm/Kconfig| 11 ---
arch/arm/boot/dts/at91sam9x5.dtsi | 28
++--
arch/arm/boot/dts/exynos4.dtsi |9 +
arch/arm/boot/dts/exynos5440.dtsi |6 ++
arch/arm/kernel/smp.c |2 +-
arch/arm/lib/memset.S | 33
+
arch/arm/mach-at91/include/mach/gpio.h |8
arch/arm/mach-at91/irq.c| 20
arch/arm/mach-at91/pm.c | 10 --
arch/arm/mach-davinci/dma.c |3 +++
arch/arm/mach-footbridge/Kconfig|1 +
arch/arm/mach-imx/clk-imx35.c |1 +
arch/arm/mach-imx/imx25-dt.c
3.9-rc4 Makefile EXTRAVERSION still -rc3
Using git pull or git clone this field in the Makefile remains unchanged. patch-3.9-rc4.xz has the change. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: AMD Bulldozer FX-8150 Powers off during kernel build
# uname -r 3.6.0-rc5-u1-smp+ I built a new 3.6-rc5 kernel (3.6.0-rc5-u2) using 3.6.0-rc5-u1 with 8 cores and power off didn't ocur. slipstream:/usr/src/linux-3.6.0-rc5-u1 # grep POWER .config # CONFIG_ACPI_PROCFS_POWER is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_X86_POWERNOW_K8=m # CONFIG_PCIEASPM_POWERSAVE is not set CONFIG_INPUT_POWERMATE=m CONFIG_IPMI_POWEROFF=m CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set CONFIG_PDA_POWER=m CONFIG_TEST_POWER=m CONFIG_POWER_AVS=y CONFIG_SENSORS_FAM15H_POWER=m CONFIG_SENSORS_ACPI_POWER=m CONFIG_SND_AC97_POWER_SAVE=y CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0 # CONFIG_SND_HDA_POWER_SAVE is not set # CONFIG_HID_LCPOWER is not set CONFIG_DEVFREQ_GOV_POWERSAVE=y CONFIG_EVENT_POWER_TRACING_DEPRECATED=y # CONFIG_XZ_DEC_POWERPC is not set When it was powering off "CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y" was set. slipstream:/usr/src/linux-3.6.0-rc5-u1 # grep PERFORMANCE .config # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_PCIEASPM_PERFORMANCE=y CONFIG_DEVFREQ_GOV_PERFORMANCE=y slipstream:/usr/src/linux-3.6.0-rc5-u1 # grep MCE .config CONFIG_X86_MCE=y # CONFIG_X86_MCE_INTEL is not set CONFIG_X86_MCE_AMD=y CONFIG_X86_MCE_THRESHOLD=y # CONFIG_X86_MCE_INJECT is not set CONFIG_EDAC_DECODE_MCE=y # CONFIG_EDAC_MCE_INJ is not set During the build temperature and power was around these values - fam15h_power-pci-00c4 Adapter: PCI adapter power1: 133.30 W (crit = 124.77 W) k10temp-pci-00c3 Adapter: PCI adapter temp1:+61.9°C (high = +70.0°C) (crit = +90.0°C, hyst = +87.0°C) Immediately after the build the values are much lower than what it was with the kernel and config that caused the power off. fam15h_power-pci-00c4 Adapter: PCI adapter power1: 31.10 W (crit = 124.77 W) k10temp-pci-00c3 Adapter: PCI adapter temp1:+33.2°C (high = +70.0°C) (crit = +90.0°C, hyst = +87.0°C) -- If needed I can go back to the earlier 3.6.0-rc5 kernel and config to recreate the power off situation. With the kernel that powered off, MCE was not set and CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y For the 3.6.0-rc5-u1 kernel only those 2 were changed. Regards Sid. On 13/09/12 10:44, Borislav Petkov wrote: On Thu, Sep 13, 2012 at 02:30:27AM +0100, Sid Boyce wrote: I have a huge heatsink and large CPU fan plus lots of cooling fans in the case and nothing gets hot. If I build e.g 3.6-rc5 with 8 or 6 cores, part way through it suddenly powers off. Ok, can you catch the whole dmesg when you boot the machine _after_ the sudden poweroff? You can send it to me and Andreas (on CC) privately if you prefer. Important: make sure the kernel has CONFIG_X86_MCE and CONFIG_EDAC_DECODE_MCE built-in. Please make sure to use a recent kernel, i.e. 3.4, 3.5 is fine. Thanks. (Leaving in the rest for reference) I have checked hwmon/k10temp.c to see if I could see where these values were defined. k10temp.h is 0 bytes. -rw-r--r-- 1 root root 0 Sep 9 01:59 /usr/src/linux-3.6.0-rc5/include/config/sensors/k10temp.h Currently I build with "make -j 1" and temperature and power values are around those below. # sensors k10temp-pci-00c3 Adapter: PCI adapter temp1:+60.4°C (high = +70.0°C) (crit = +90.0°C, hyst = +87.0°C) fam15h_power-pci-00c4 Adapter: PCI adapter power1: 127.49 W (crit = 124.77 W) # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 1 model name : AMD FX(tm)-8150 Eight-Core Processor stepping: 2 microcode : 0x6000626 cpu MHz : 3600.000 cache size : 2048 KB from .config:- # grep HWMON .config CONFIG_IXGBE_HWMON=y CONFIG_HWMON=y CONFIG_HWMON_VID=m # CONFIG_HWMON_DEBUG_CHIP is not set CONFIG_THERMAL_HWMON=y # grep POWERSAVE .config # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set CONFIG_CPU_FREQ_GOV_POWERSAVE=m # CONFIG_PCIEASPM_POWERSAVE is not set CONFIG_DEVFREQ_GOV_POWERSAVE=y On another 6-core box I can build kernels with "make -j 6" without problems. # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 1 model name : AMD FX(tm)-6100 Six-Core Processor stepping: 2 microcode : 0x6000623 cpu MHz : 3300.000 cache size : 2048 KB With a kernel build going on six core box, temperature and power hover around the values below. sabre:~ # sensors k10temp-pci-00c3 Adapter: PCI adapter temp1:+50.2°C (high = +70.0°C) (crit = +90.0°C, hyst = +87.0°C) fam15h_power-pci-00c4 Adapter: PCI adapter power1: 94.40 W (crit = 95.01 W) 73 ... Sid. -- -- S
AMD Bulldozer FX-8150 Powers off during kernel build
I have a huge heatsink and large CPU fan plus lots of cooling fans in the case and nothing gets hot. If I build e.g 3.6-rc5 with 8 or 6 cores, part way through it suddenly powers off. I have checked hwmon/k10temp.c to see if I could see where these values were defined. k10temp.h is 0 bytes. -rw-r--r-- 1 root root 0 Sep 9 01:59 /usr/src/linux-3.6.0-rc5/include/config/sensors/k10temp.h Currently I build with "make -j 1" and temperature and power values are around those below. # sensors k10temp-pci-00c3 Adapter: PCI adapter temp1:+60.4°C (high = +70.0°C) (crit = +90.0°C, hyst = +87.0°C) fam15h_power-pci-00c4 Adapter: PCI adapter power1: 127.49 W (crit = 124.77 W) # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 1 model name : AMD FX(tm)-8150 Eight-Core Processor stepping: 2 microcode : 0x6000626 cpu MHz : 3600.000 cache size : 2048 KB from .config:- # grep HWMON .config CONFIG_IXGBE_HWMON=y CONFIG_HWMON=y CONFIG_HWMON_VID=m # CONFIG_HWMON_DEBUG_CHIP is not set CONFIG_THERMAL_HWMON=y # grep POWERSAVE .config # CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set CONFIG_CPU_FREQ_GOV_POWERSAVE=m # CONFIG_PCIEASPM_POWERSAVE is not set CONFIG_DEVFREQ_GOV_POWERSAVE=y On another 6-core box I can build kernels with "make -j 6" without problems. # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 1 model name : AMD FX(tm)-6100 Six-Core Processor stepping: 2 microcode : 0x6000623 cpu MHz : 3300.000 cache size : 2048 KB With a kernel build going on six core box, temperature and power hover around the values below. sabre:~ # sensors k10temp-pci-00c3 Adapter: PCI adapter temp1:+50.2°C (high = +70.0°C) (crit = +90.0°C, hyst = +87.0°C) fam15h_power-pci-00c4 Adapter: PCI adapter power1: 94.40 W (crit = 95.01 W) 73 ... Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.24-rc1 oops
FUJITA Tomonori wrote: Jens, I should have CC'ed to you. On Thu, 25 Oct 2007 10:22:02 +0900 FUJITA Tomonori <[EMAIL PROTECTED]> wrote: On Thu, 25 Oct 2007 01:40:00 +0100 Sid Boyce <[EMAIL PROTECTED]> wrote: x86_64 dual, gcc version 4.2.2 (SUSE Linux). [ cut here ] kernel BUG at include/linux/scatterlist.h:50! invalid opcode: [1] SMP CPU 1 Modules linked in: ub crc_itu_t hwmon cdrom soundcore v4l1_compat videobuf_core btcx_risc ff_memless floppy sg forcedeth ehci_hcd ohci_hcd sd_mod usbcore jfs edd ext3 mbcache jbd fan pata_jmicron ahci sata_nv pata_amd libata scsi_mod thermal processor Pid: 0, comm: swapper Not tainted 2.6.24-rc1-smp #1 RIP: 0010:[] [] :ub:ub_state_sense+0x9a/0x169 RSP: 0018:810100697e60 EFLAGS: 00010093 RAX: 87654321 RBX: 810105d55000 RCX: 81011f975540 RDX: RSI: RDI: 81011f975540 RBP: 810105d51000 R08: R09: 810105d55098 R10: 810001c319b8 R11: 0286 R12: 810105d55098 R13: 810105d55260 R14: 810105d55278 R15: 810105d55298 FS: 2afb8597c6f0() GS:81011800() knlGS: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: 2afb8548200f CR3: 00010615b000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process swapper (pid: 0, threadinfo 81010069, task 810100689160) Stack: 0001 810105d55000 810105d51000 810105d55260 881f4d43 810105919998 810105d553a0 810105d553af 810105d55348 0286 810105d55058 Call Trace: [] :ub:ub_scsi_action+0x1e3/0x214 [] tasklet_action+0x54/0x97 [] __do_softirq+0x65/0xce [] call_softirq+0x1c/0x28 [] do_softirq+0x2c/0x7d [] irq_exit+0x3f/0x84 [] do_IRQ+0x13e/0x15f [] default_idle+0x0/0x3d [] default_idle+0x0/0x3d [] ret_from_intr+0x0/0xa [] default_idle+0x29/0x3d [] cpu_idle+0x93/0xbb Can you try this? Thanks, diff --git a/drivers/block/ub.c b/drivers/block/ub.c index 14143f2..78f158f 100644 --- a/drivers/block/ub.c +++ b/drivers/block/ub.c @@ -1428,6 +1428,7 @@ static void ub_state_sense(struct ub_dev *sc, struct ub_scsi_cmd *cmd) scmd->state = UB_CMDST_INIT; scmd->nsg = 1; sg = &scmd->sgv[0]; + sg_init_table(sg, UB_MAX_REQ_SG); sg_set_page(sg, virt_to_page(sc->top_sense)); sg->offset = (unsigned long)sc->top_sense & (PAGE_SIZE-1); sg->length = UB_SENSE_SIZE; @@ -1864,6 +1865,7 @@ static int ub_sync_read_cap(struct ub_dev *sc, struct ub_lun *lun, cmd->state = UB_CMDST_INIT; cmd->nsg = 1; sg = &cmd->sgv[0]; + sg_init_table(sg, UB_MAX_REQ_SG); sg_set_page(sg, virt_to_page(p)); sg->offset = (unsigned long)p & (PAGE_SIZE-1); sg->length = 8; Here's a modified version for your sg branch (for sg_set_page API changes). - From: FUJITA Tomonori <[EMAIL PROTECTED]> Subject: [PATCH] ub: add sg_init_table for sense and read capacity commands Signed-off-by: FUJITA Tomonori <[EMAIL PROTECTED]> --- drivers/block/ub.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/block/ub.c b/drivers/block/ub.c index 5e740e1..08e909d 100644 --- a/drivers/block/ub.c +++ b/drivers/block/ub.c @@ -1428,6 +1428,7 @@ static void ub_state_sense(struct ub_dev *sc, struct ub_scsi_cmd *cmd) scmd->state = UB_CMDST_INIT; scmd->nsg = 1; sg = &scmd->sgv[0]; + sg_init_table(sg, UB_MAX_REQ_SG); sg_set_page(sg, virt_to_page(sc->top_sense), UB_SENSE_SIZE, (unsigned long)sc->top_sense & (PAGE_SIZE-1)); scmd->len = UB_SENSE_SIZE; @@ -1863,6 +1864,7 @@ static int ub_sync_read_cap(struct ub_dev *sc, struct ub_lun *lun, cmd->state = UB_CMDST_INIT; cmd->nsg = 1; sg = &cmd->sgv[0]; + sg_init_table(sg, UB_MAX_REQ_SG); sg_set_page(sg, virt_to_page(p), 8, (unsigned long)p & (PAGE_SIZE-1)); cmd->len = 8; cmd->lun = lun; Boots OK, but oopses with depmod on Virtualbox and other proprietary modules. I assume these modules are out of step with 2.6.24-rc1 and not a kernel problem. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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/
2.6.23-git10 make bzImage problem
When booted, it complains that kernel size is too big, but size OK for a bzImage, not for zImage as is returned by the file command, -git9 was OK, x86_64 SMP kernel on two 64x2 boxes. I shall supplymy .config if needed, but they are the same as for -git9. # l arch/x86/boot/bzImage -rw-r--r-- 1 root root 1761496 2007-10-16 22:45 arch/x86/boot/bzImage # file arch/x86_64/boot/bzImage arch/x86_64/boot/bzImage: symbolic link to `/usr/src/linux-2.6.23-git10/arch/x86/boot/bzImage' # file arch/x86/boot/bzImage arch/x86/boot/bzImage: Linux/x86 Kernel, Setup Version 0x206, zImage, RO-rootFS, root_dev 0x801, swap_dev 0x1, Prompt for Videomode Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.23-git10 make bzImage problem
Sid Boyce wrote: When booted, it complains that kernel size is too big, but size OK for a bzImage, not for zImage as is returned by the file command, -git9 was OK, x86_64 SMP kernel on two 64x2 boxes. I shall supplymy .config if needed, but they are the same as for -git9. # l arch/x86/boot/bzImage -rw-r--r-- 1 root root 1761496 2007-10-16 22:45 arch/x86/boot/bzImage # file arch/x86_64/boot/bzImage arch/x86_64/boot/bzImage: symbolic link to `/usr/src/linux-2.6.23-git10/arch/x86/boot/bzImage' # file arch/x86/boot/bzImage arch/x86/boot/bzImage: Linux/x86 Kernel, Setup Version 0x206, zImage, RO-rootFS, root_dev 0x801, swap_dev 0x1, Prompt for Videomode Regards Sid. Fixed by the following patch. = Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> --- arch/x86/boot/Makefile | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/x86/boot/Makefile b/arch/x86/boot/Makefile index d6ed8e5..0e4912f 100644 --- a/arch/x86/boot/Makefile +++ b/arch/x86/boot/Makefile @@ -64,10 +64,10 @@ KBUILD_CFLAGS := $(LINUXINCLUDE) -g -Os -D_SETUP -D__KERNEL__ \ KBUILD_AFLAGS := $(KBUILD_CFLAGS) -D__ASSEMBLY__ $(obj)/zImage: IMAGE_OFFSET := 0x1000 -$(obj)/zImage: EXTRA_AFLAGS := $(SVGA_MODE) $(RAMDISK) +$(obj)/zImage: asflags-y += $(SVGA_MODE) $(RAMDISK) $(obj)/bzImage: IMAGE_OFFSET := 0x10 -$(obj)/bzImage: EXTRA_CFLAGS := -D__BIG_KERNEL__ -$(obj)/bzImage: EXTRA_AFLAGS := $(SVGA_MODE) $(RAMDISK) -D__BIG_KERNEL__ +$(obj)/bzImage: ccflags-y += -D__BIG_KERNEL__ +$(obj)/bzImage: asflags-y += $(SVGA_MODE) $(RAMDISK) -D__BIG_KERNEL__ $(obj)/bzImage: BUILDFLAGS := -b quiet_cmd_image = BUILD $@ Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.23-rc1-git3 init failure
Michal Piotrowski wrote: Hi Sid, On 29/07/07, Sid Boyce <[EMAIL PROTECTED]> wrote: > Boot failure on x86_64 (64X2), says it can't find init, specifically > /init. 2.6.23-rc1-git1 boots and runs successfully. I haven't tried > -git2. I shall reboot on 2.6.23-rc1-git3 tomorrow and record the full > message. > Strings from vmlinux in both the above:- > > Kernel alive > /dev/console > <4>Warning: unable to open an initial console. > <4>Failed to execute %s > <4>Failed to execute %s. Attempting defaults... > /sbin/init > /etc/init > /bin/init > /bin/sh > No init found. Try passing init= option to kernel. > > Tried option "init=/sbin/init" and got the same failure. > Regards > Sid. I see the sam problem with 2.6.23-rc1-git5. Freeing unused kernel memory: 236k freed failed to execute /init kernel panic - not syncing: No init found. Try passing init= option to kernel Copying /sbin/init to / results in the same error. openSUSE 10.3Alpha6plus # rpm -qf /sbin/init sysvinit-2.86-90 Please read chapter 4.1 and 4.5 http://www.stardust.webpages.pl/files/handbook/handbook-en-0.3-rc1.pdf It should be very simple git-bisect start git-bisect bad git-bisect good 0de085bb474f64e4fdb2f1ff3268590792648c7b and so on and so forth Regards Sid. Regards, Michal I had to do a fresh install of opeSUSE 10.3 Alpha6 to replace a failing drive. After that I again built 2.6.23-rc1-git10 which boots without problems. My guess is that something on the old hard drive got mangled. The old drive was PATA, the new one SATA, also disappeared have been the problems that suddenly appeared with sata_nv slow responses and timeouts with no devices installed and which I didn't see without the sata_nv module loaded. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.23-rc1-git3 init failure
Michal Piotrowski wrote: Hi Sid, On 29/07/07, Sid Boyce <[EMAIL PROTECTED]> wrote: > Boot failure on x86_64 (64X2), says it can't find init, specifically > /init. 2.6.23-rc1-git1 boots and runs successfully. I haven't tried > -git2. I shall reboot on 2.6.23-rc1-git3 tomorrow and record the full > message. > Strings from vmlinux in both the above:- > > Kernel alive > /dev/console > <4>Warning: unable to open an initial console. > <4>Failed to execute %s > <4>Failed to execute %s. Attempting defaults... > /sbin/init > /etc/init > /bin/init > /bin/sh > No init found. Try passing init= option to kernel. > > Tried option "init=/sbin/init" and got the same failure. > Regards > Sid. I see the sam problem with 2.6.23-rc1-git5. Freeing unused kernel memory: 236k freed failed to execute /init kernel panic - not syncing: No init found. Try passing init= option to kernel Copying /sbin/init to / results in the same error. openSUSE 10.3Alpha6plus # rpm -qf /sbin/init sysvinit-2.86-90 Please read chapter 4.1 and 4.5 http://www.stardust.webpages.pl/files/handbook/handbook-en-0.3-rc1.pdf It should be very simple git-bisect start git-bisect bad git-bisect good 0de085bb474f64e4fdb2f1ff3268590792648c7b and so on and so forth Regards Sid. Regards, Michal Looks like a job for the weekend. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.23-rc1-git3 init failure
> Boot failure on x86_64 (64X2), says it can't find init, specifically > /init. 2.6.23-rc1-git1 boots and runs successfully. I haven't tried > -git2. I shall reboot on 2.6.23-rc1-git3 tomorrow and record the full > message. > Strings from vmlinux in both the above:- > > Kernel alive > /dev/console > <4>Warning: unable to open an initial console. > <4>Failed to execute %s > <4>Failed to execute %s. Attempting defaults... > /sbin/init > /etc/init > /bin/init > /bin/sh > No init found. Try passing init= option to kernel. > > Tried option "init=/sbin/init" and got the same failure. > Regards > Sid. I see the sam problem with 2.6.23-rc1-git5. Freeing unused kernel memory: 236k freed failed to execute /init kernel panic - not syncing: No init found. Try passing init= option to kernel Copying /sbin/init to / results in the same error. openSUSE 10.3Alpha6plus # rpm -qf /sbin/init sysvinit-2.86-90 Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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/
2.6.23-rc1-git3 init failure
Boot failure on x86_64 (64X2), says it can't find init, specifically /init. 2.6.23-rc1-git1 boots and runs successfully. I haven't tried -git2. I shall reboot on 2.6.23-rc1-git3 tomorrow and record the full message. Strings from vmlinux in both the above:- Kernel alive /dev/console <4>Warning: unable to open an initial console. <4>Failed to execute %s <4>Failed to execute %s. Attempting defaults... /sbin/init /etc/init /bin/init /bin/sh No init found. Try passing init= option to kernel. Tried option "init=/sbin/init" and got the same failure. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.22-git17 boot failure
Tilman Schmidt: wrote > On my test machine with a Pentium D 940 processor, Intel DQ965GF > mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails > to come up because it cannot find the disk drives. Same issue > with a clone of the 'linus' git tree. Anything known? I don't know if this is any indication. I have no SATA drives, but I noticed booting 2.6.22-git16 x86_64 I got error messages with "sata slow in responding" also "EH timeout" and my IDE drive /dev/sda1 giving ext3 errors, ending in a filesystem not clean prompt. Did fsck.ext3 using openSUSE 10.3Alpha3 DVD, that fixed a string of wrong inode errors. Booted an earlier kernel and turned off loading the sata_nv module, then 2.6.22-git16 and later 2.6.22-git17 booted without problems, so I put it down to a motherboard problem with the SATA. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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: ov511 module does not build
Adrian Bunk wrote: On Wed, Jul 04, 2007 at 12:23:57AM +0100, Sid Boyce wrote: With the same setup in .config for linux-2.6.22-rc2-git7, it builds, after that and right up to linux-2.6.22-rc7-git1 it doesn't. /usr/src/linux-2.6.22-rc2-git7/drivers/media/video/ov511.ko # CONFIG_VIDEO_V4L1 is not set That's the problem. CONFIG_VIDEO_V4L1_COMPAT=y In any of the 2.6.22-rc kernels, there is no option to select OV511. tindog:/usr/src/linux-2.6.22-rc2-git7 # grep -i ov511 .config tindog:/usr/src/linux-2.6.22-rc2-git7 # tindog:/usr/src/linux-2.6.22-rc7-git1 # diff ../linux-2.6.22-rc2-git7/drivers/media/video/Kconfig drivers/media/video/Kconfig 14c14 < if VIDEO_CAPTURE_DRIVERS --- if VIDEO_CAPTURE_DRIVERS && VIDEO_DEV 694c694 < if V4L_USB_DRIVERS --- if V4L_USB_DRIVERS && USB tindog:/usr/src/linux-2.6.22-rc7-git1 # grep V4L .config # CONFIG_VIDEO_V4L1 is not set CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_VIDEO_V4L2=y CONFIG_V4L_USB_DRIVERS=y tindog:/usr/src/linux-2.6.22-rc2-git7 # grep V4L .config # CONFIG_VIDEO_V4L1 is not set If it built with this version and this .config, something went wrong. Are you sure this is the correct .config that built the ov511 module? CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_VIDEO_V4L2=y # CONFIG_V4L_USB_DRIVERS is not set Still does not build for 2.6.22-rc7-git2 with .config set with # CONFIG_V4L_USB_DRIVERS is not set Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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/ cu Adrian Thanks, I see, I didn't select that as it said it was DEPRECATED, now I've selected OV511. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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/
ov511 module does not build
With the same setup in .config for linux-2.6.22-rc2-git7, it builds, after that and right up to linux-2.6.22-rc7-git1 it doesn't. /usr/src/linux-2.6.22-rc2-git7/drivers/media/video/ov511.ko # CONFIG_VIDEO_V4L1 is not set CONFIG_VIDEO_V4L1_COMPAT=y In any of the 2.6.22-rc kernels, there is no option to select OV511. tindog:/usr/src/linux-2.6.22-rc2-git7 # grep -i ov511 .config tindog:/usr/src/linux-2.6.22-rc2-git7 # tindog:/usr/src/linux-2.6.22-rc7-git1 # diff ../linux-2.6.22-rc2-git7/drivers/media/video/Kconfig drivers/media/video/Kconfig 14c14 < if VIDEO_CAPTURE_DRIVERS --- > if VIDEO_CAPTURE_DRIVERS && VIDEO_DEV 694c694 < if V4L_USB_DRIVERS --- > if V4L_USB_DRIVERS && USB tindog:/usr/src/linux-2.6.22-rc7-git1 # grep V4L .config # CONFIG_VIDEO_V4L1 is not set CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_VIDEO_V4L2=y CONFIG_V4L_USB_DRIVERS=y tindog:/usr/src/linux-2.6.22-rc2-git7 # grep V4L .config # CONFIG_VIDEO_V4L1 is not set CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_VIDEO_V4L2=y # CONFIG_V4L_USB_DRIVERS is not set Still does not build for 2.6.22-rc7-git2 with .config set with # CONFIG_V4L_USB_DRIVERS is not set Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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-rc5 possible regression: KDE processes die silently [fixed]
Am 03.04.2007 00:50 schrieb Adrian Bunk: >>/ We also have one bug kwin ran into that got fixed after -rc5:/ >>/ / >>/ Subject : kwin dies silently/ >>/ References : http://lkml.org/lkml/2007/2/28/112/ >>/ Submitter : Sid Boyce <[EMAIL PROTECTED]>/ >>/ Boris Mogwitz <[EMAIL PROTECTED]>/ >>/ Michael Wu <[EMAIL PROTECTED]>/ >>/ Caused-By : Eric W. Biederman <[EMAIL PROTECTED]>/ >>/ commit 0475ac0845f9295bc5f69af45f58dff2c104c8d1/ >>/ Fixed-By : Eric W. Biederman <[EMAIL PROTECTED]>/ >>/ Commit : 14e9d5730adfca26452b3a2838a80af6950556f5/ >>/ Status : fixed in -rc6/ >> > The machine has been running -rc5-git12, then -rc6 for a total > of four days now, and the problem hasn't reoccurred. Looks like > it was indeed the same bug. > > Thanks, > Tilman No further problems since the patch was applied. Currently running 2.6.21-rc6-git7. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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-rc1 and 2.6.21-rc2 kwin dies silently
Sid Boyce wrote:
Eric W. Biederman wrote:
Sid I think I have found the problem. Could you try the following
patch. I believe I accidentally switched the sense of a test
diff --git a/kernel/exit.c b/kernel/exit.c
index f132349..b55ed4c 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -790,7 +790,7 @@ static void exit_notify(struct task_struct *tsk)
pgrp = task_pgrp(tsk);
if ((task_pgrp(t) != pgrp) &&
-(task_session(t) != task_session(tsk)) &&
+(task_session(t) == task_session(tsk)) &&
will_become_orphaned_pgrp(pgrp, tsk) &&
has_stopped_jobs(pgrp)) {
__kill_pgrp_info(SIGHUP, SEND_SIG_PRIV, pgrp);
AOK I shall apply to 2.6.21-rc5-git4 and test.
Regards
Sid.
Thanks, the patch works - tested on 2.6.21-rc5-git4.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
-
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-rc1 and 2.6.21-rc2 kwin dies silently
Eric W. Biederman wrote:
Sid I think I have found the problem. Could you try the following patch.
I believe I accidentally switched the sense of a test
diff --git a/kernel/exit.c b/kernel/exit.c
index f132349..b55ed4c 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -790,7 +790,7 @@ static void exit_notify(struct task_struct *tsk)
pgrp = task_pgrp(tsk);
if ((task_pgrp(t) != pgrp) &&
- (task_session(t) != task_session(tsk)) &&
+ (task_session(t) == task_session(tsk)) &&
will_become_orphaned_pgrp(pgrp, tsk) &&
has_stopped_jobs(pgrp)) {
__kill_pgrp_info(SIGHUP, SEND_SIG_PRIV, pgrp);
AOK I shall apply to 2.6.21-rc5-git4 and test.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist,
Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
-
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-rc1 and 2.6.21-rc2 kwin dies silently
Adrian Bunk wrote: On Wed, Mar 28, 2007 at 04:26:05AM +0100, Sid Boyce wrote: Eric W. Biederman wrote: Sid Boyce <[EMAIL PROTECTED]> writes: This is what I've got so far on the first boot, I shall have to check the manpage for git-bisect again to see if there is anything else to be added, nothing enlightening seen so far - further reboots to be done. I'm a little confused at what I am seeing below. Normally what happens is that after a kernel compile and test. You call "git-bisect bad" or "git-bisect good" and then git-bisect picks the next kernel to test. Then you compile and test that one. It looks like you called git-bisect bad several times in a row without testing Eric This is the procedure I followed. <-- snip --> # install git and cogito on your computer # clone Linus' tree: cg-clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git # start bisecting: cd linux-2.6 git bisect start git bisect bad 86a71dbd3e81e8870d0f0e56b87875f57e58222b git bisect good ac98695d6c1508b724f246f38ce57fb4e3cec356 # start round cp /path/to/.config . make oldconfig make # install kernel, check whether it's good or bad, then: git bisect [bad|good] I built and installed the kernel downloaded using "cg-clone", booted it up and ran "git bisect bad". I'm also somewhat confused as the first failing kernel is 2.6.20-git11, the Makefile says the kernel got with cg-clone is actually 2.6.21-rc4 and it built as 2.6.20-g208367ee. Regards Sid. barrabas:/usr/src/GIT/linux-2.6 # git bisect bad Bisecting: 22 revisions left to test after this [3fc605a2aa38899c12180ca311f1eeb61a6d867e] knfsd: allow the server to provide a gid list when using AUTH_UNIX authentication rrabas:/usr/src/GIT/linux-2.6 # git bisect bad ... I think I got your problem: After rebooting, you do "git bisect [bad|good]" *once*. Then recompile the kernel from the current tree, reboot, and again *once* "git bisect [bad|good]". etc. cu Adrian If I boot up on 2.6.20-git10 and run "git bisect bad", "git bisect good v2.6.20-git10" or "git bisect bad v2.6.20-git11", it says it's not a git repo. I am still no clearer what's required. If I do "cg-clone" I get 2.6.21-rc5. The previous one got me 2.6.21-rc4. The manpages and the tutorials I've looked at are quite cryptic and the commands do not produce the expected results. As indicated above, I followed the instructions bullet by bullet without any clear understanding of the tools. 1) Ran the commands as above,cg-clone; git start; git bisect bad ;git bisect good I presume. 2) 2.6.20-git10 is the last good kernel. 3) 2.6.20-git11 and later are all bad. 4) I do cg-clone which gives a kernel whose Makefile is 2.6.21-rc4 (or whatever is current). 5) I get a kernel named 2.6.20-g208367e after make - rebooted and it fails the same way as 2.6.20-git11. 6) ran "git bisect bad". Looking through the directories after cg-clone barrabas:/ftp/mar07/GIT/linux-2.6 # ls .git/refs/tags/ v2.6.11 v2.6.12-rc5 v2.6.13-rc4 v2.6.14-rc2 v2.6.15-rc2 v2.6.16 v2.6.16-rc6 v2.6.17-rc5 v2.6.18-rc4 v2.6.19-rc2 v2.6.20-rc1 v2.6.20-rc7 v2.6.11-tree v2.6.12-rc6 v2.6.13-rc5 v2.6.14-rc3 v2.6.15-rc3 v2.6.16-rc1 v2.6.17 v2.6.17-rc6 v2.6.18-rc5 v2.6.19-rc3 v2.6.20-rc2 v2.6.21-rc1 v2.6.12 v2.6.13 v2.6.13-rc6 v2.6.14-rc4 v2.6.15-rc4 v2.6.16-rc2 v2.6.17-rc1 v2.6.18 v2.6.18-rc6 v2.6.19-rc4 v2.6.20-rc3 v2.6.21-rc2 v2.6.12-rc2 v2.6.13-rc1 v2.6.13-rc7 v2.6.14-rc5 v2.6.15-rc5 v2.6.16-rc3 v2.6.17-rc2 v2.6.18-rc1 v2.6.18-rc7 v2.6.19-rc5 v2.6.20-rc4 v2.6.21-rc3 v2.6.12-rc3 v2.6.13-rc2 v2.6.14 v2.6.15 v2.6.15-rc6 v2.6.16-rc4 v2.6.17-rc3 v2.6.18-rc2 v2.6.19 v2.6.19-rc6 v2.6.20-rc5 v2.6.21-rc4 v2.6.12-rc4 v2.6.13-rc3 v2.6.14-rc1 v2.6.15-rc1 v2.6.15-rc7 v2.6.16-rc5 v2.6.17-rc4 v2.6.18-rc3 v2.6.19-rc1 v2.6.20 v2.6.20-rc6 v2.6.21-rc5 barrabas:/ftp/mar07/GIT/linux-2.6 # ls .git/refs/bisect/ bad good-ac98695d6c1508b724f246f38ce57fb4e3cec356 barrabas:/ftp/mar07/GIT/linux-2.6 # ls .git/refs/heads/ bisect master origin barrabas:/ftp/mar07/GIT/linux-2.6 # less .git/refs/heads/bisect 208367eeec8d6f6fcee1a0672af2149aeee7b658 barrabas:/ftp/mar07/GIT/linux-2.6 # ls .git/branches/ barrabas:/ftp/mar07/GIT/linux-2.6 # ls arch COPYING crypto drivers .gitinclude ipc kernel .mailmap Makefile net REPORTING-BUGS security usr block CREDITS Documentation fs .gitignore init Kbuild lib MAINTAINERS mmREADME scripts sound # less BISECT_LOG git-bisect start # bad: [86a71dbd3e81e8870d0f0e56b87875f57e58222b] sysctl: hide the sysctl proc inodes from
Re: 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently
Eric W. Biederman wrote:
Sid Boyce <[EMAIL PROTECTED]> writes:
This is what I've got so far on the first boot, I shall have to check the
manpage for git-bisect again to see if there is anything else to be added,
nothing enlightening seen so far - further reboots to be done.
I'm a little confused at what I am seeing below.
Normally what happens is that after a kernel compile and test. You call
"git-bisect bad" or "git-bisect good" and then git-bisect picks the next
kernel to test. Then you compile and test that one. It looks like
you called git-bisect bad several times in a row without testing
Eric
This is the procedure I followed.
<-- snip -->
# install git and cogito on your computer
# clone Linus' tree:
cg-clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
# start bisecting:
cd linux-2.6
git bisect start
git bisect bad 86a71dbd3e81e8870d0f0e56b87875f57e58222b
git bisect good ac98695d6c1508b724f246f38ce57fb4e3cec356
# start round
cp /path/to/.config .
make oldconfig
make
# install kernel, check whether it's good or bad, then:
git bisect [bad|good]
I built and installed the kernel downloaded using "cg-clone", booted it
up and ran "git bisect bad". I'm also somewhat confused as the first
failing kernel is 2.6.20-git11, the Makefile says the kernel got with
cg-clone is actually 2.6.21-rc4 and it built as 2.6.20-g208367ee.
Regards
Sid.
barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 22 revisions left to test after this
[3fc605a2aa38899c12180ca311f1eeb61a6d867e] knfsd: allow the server to provide a
gid list when using AUTH_UNIX authentication
rrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 11 revisions left to test after this
[ed8b4d4d7a31923db32f4684535944d69eb43677] qconf: hide empty list items
barrabas:/usr/src/GIT/linux-2.6 #
rrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 6 revisions left to test after this
[66e7c7230fed159e138fc1292ee662b8bbdb74d6] qconf: relocate Search Command
barrabas:/usr/src/GIT/linux-2.6 #
barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 3 revisions left to test after this
[895a39a084e5478121a74752a291165c4502378f] Make mkcompile_h use LANG=C and
LC_ALL=C for $CC -v
barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 2 revisions left to test after this
[8c7e4498adfdb4aea5a0d056590ec18d099ba062] search a little harder for mkimage
barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 1 revisions left to test after this
[b7de8e7e3c7b79a72c20c7fd58bd65df3d146b13] ia64: fix noncoherent DMA API so
devres builds
# git bisect bad
b7de8e7e3c7b79a72c20c7fd58bd65df3d146b13 is first bad commit
commit b7de8e7e3c7b79a72c20c7fd58bd65df3d146b13
Author: Roland Dreier <[EMAIL PROTECTED]>
Date: Wed Feb 14 00:32:53 2007 -0800
[PATCH] ia64: fix noncoherent DMA API so devres builds
On ia64, drivers/base/dma-mapping.c doesn't build because it calls
dma_alloc_noncoherent() and dma_free_noncoherent(), which appear to be
terminally broken; the calls end up generating errors like
drivers/base/dma-mapping.c: In function 'dmam_noncoherent_release':
drivers/base/dma-mapping.c:32: error: 'struct ia64_machine_vector' has no
member named 'platform_dma_free_coherent'
because the multiple levels of macro expansion in and
end up turning a call to dma_free_noncoherent() into
ia64_mv.platform_dma_free_coherent (instead of the intended
ia64_mv.dma_free_coherent).
This patch fixes this by converting dma_{alloc,free}_noncoherent() into
inline functions that call the corresponding coherent functions, instead of
trying to do this with macros.
Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
Acked-by: Tony Luck <[EMAIL PROTECTED]>
Cc: Al Viro <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
:04 04 ac36019577dc1846a5655918cf9d6b2541c398cf
ba536f54303cc9495b7839763ed1121d3a22154c M include
barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
86a71dbd3e81e8870d0f0e56b87875f57e58222b
Bisecting: 44 revisions left to test after this
[208367eeec8d6f6fcee1a0672af2149aeee7b658] sysctl: cdrom: remove unnecessary
insert_at_head flag
barrabas:/usr/src/GIT/linux-2.6 # git bisect good
ac98695d6c1508b724f246f38ce57fb4e3cec356
Bisecting: 44 revisions left to test after this
[208367eeec8d6f6fcee1a0672af2149aeee7b658] sysctl: cdrom: remove unnecessary
insert_at_head flag
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist,
Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
Sid Boyce ... Hamradio License G3VB
Re: 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently
Adrian Bunk wrote:
On Wed, Mar 21, 2007 at 06:42:58PM -0700, Randy Dunlap wrote:
On Thu, 22 Mar 2007 01:32:36 + Sid Boyce wrote:
...
There's not a lot of docs out there.
The man-page: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
Linus's email doc:
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
I worked on something over last weekend, but it doesn't really add
much to the references above.
...
FWIW:
My standard instructions for users who are asked to bisect are [1]:
<-- snip -->
# install git and cogito on your computer
# clone Linus' tree:
cg-clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
# start bisecting:
cd linux-2.6
git bisect start
git bisect bad 86a71dbd3e81e8870d0f0e56b87875f57e58222b
git bisect good ac98695d6c1508b724f246f38ce57fb4e3cec356
# start round
cp /path/to/.config .
make oldconfig
make
# install kernel, check whether it's good or bad, then:
git bisect [bad|good]
# start next round
After at about 8 reboots, you'll have found the guilty commit
("... is first bad commit").
More information on git bisecting:
man git-bisect
<-- snip -->
~Randy
cu
Adrian
[1] the start and end commits and the number of reboots are variable,
but the rest of the text is generic
This is what I've got so far on the first boot, I shall have to check
the manpage for git-bisect again to see if there is anything else to be
added, nothing enlightening seen so far - further reboots to be done.
barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 22 revisions left to test after this
[3fc605a2aa38899c12180ca311f1eeb61a6d867e] knfsd: allow the server to
provide a gid list when using AUTH_UNIX authentication
rrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 11 revisions left to test after this
[ed8b4d4d7a31923db32f4684535944d69eb43677] qconf: hide empty list items
barrabas:/usr/src/GIT/linux-2.6 #
rrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 6 revisions left to test after this
[66e7c7230fed159e138fc1292ee662b8bbdb74d6] qconf: relocate Search Command
barrabas:/usr/src/GIT/linux-2.6 #
barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 3 revisions left to test after this
[895a39a084e5478121a74752a291165c4502378f] Make mkcompile_h use LANG=C
and LC_ALL=C for $CC -v
barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 2 revisions left to test after this
[8c7e4498adfdb4aea5a0d056590ec18d099ba062] search a little harder for
mkimage
barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
Bisecting: 1 revisions left to test after this
[b7de8e7e3c7b79a72c20c7fd58bd65df3d146b13] ia64: fix noncoherent DMA API
so devres builds
# git bisect bad
b7de8e7e3c7b79a72c20c7fd58bd65df3d146b13 is first bad commit
commit b7de8e7e3c7b79a72c20c7fd58bd65df3d146b13
Author: Roland Dreier <[EMAIL PROTECTED]>
Date: Wed Feb 14 00:32:53 2007 -0800
[PATCH] ia64: fix noncoherent DMA API so devres builds
On ia64, drivers/base/dma-mapping.c doesn't build because it calls
dma_alloc_noncoherent() and dma_free_noncoherent(), which appear to be
terminally broken; the calls end up generating errors like
drivers/base/dma-mapping.c: In function 'dmam_noncoherent_release':
drivers/base/dma-mapping.c:32: error: 'struct
ia64_machine_vector' has no member named 'platform_dma_free_coherent'
because the multiple levels of macro expansion in
and
end up turning a call to dma_free_noncoherent() into
ia64_mv.platform_dma_free_coherent (instead of the intended
ia64_mv.dma_free_coherent).
This patch fixes this by converting dma_{alloc,free}_noncoherent() into
inline functions that call the corresponding coherent functions,
instead of
trying to do this with macros.
Signed-off-by: Roland Dreier <[EMAIL PROTECTED]>
Acked-by: Tony Luck <[EMAIL PROTECTED]>
Cc: Al Viro <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
:04 04 ac36019577dc1846a5655918cf9d6b2541c398cf
ba536f54303cc9495b7839763ed1121d3a22154c M include
barrabas:/usr/src/GIT/linux-2.6 # git bisect bad
86a71dbd3e81e8870d0f0e56b87875f57e58222b
Bisecting: 44 revisions left to test after this
[208367eeec8d6f6fcee1a0672af2149aeee7b658] sysctl: cdrom: remove
unnecessary insert_at_head flag
barrabas:/usr/src/GIT/linux-2.6 # git bisect good
ac98695d6c1508b724f246f38ce57fb4e3cec356
Bisecting: 44 revisions left to test after this
[208367eeec8d6f6fcee1a0672af2149aeee7b658] sysctl: cdrom: remove
unnecessary insert_at_head flag
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist,
Cricket Coach
Microsoft Windows Free Zone -
Re: 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently
Adrian Bunk wrote:
On Wed, Mar 21, 2007 at 06:42:58PM -0700, Randy Dunlap wrote:
On Thu, 22 Mar 2007 01:32:36 + Sid Boyce wrote:
...
There's not a lot of docs out there.
The man-page: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
Linus's email doc:
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt
I worked on something over last weekend, but it doesn't really add
much to the references above.
...
FWIW:
My standard instructions for users who are asked to bisect are [1]:
<-- snip -->
# install git and cogito on your computer
# clone Linus' tree:
cg-clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
# start bisecting:
cd linux-2.6
git bisect start
git bisect bad 86a71dbd3e81e8870d0f0e56b87875f57e58222b
git bisect good ac98695d6c1508b724f246f38ce57fb4e3cec356
# start round
cp /path/to/.config .
make oldconfig
make
# install kernel, check whether it's good or bad, then:
git bisect [bad|good]
# start next round
After at about 8 reboots, you'll have found the guilty commit
("... is first bad commit").
More information on git bisecting:
man git-bisect
<-- snip -->
~Randy
cu
Adrian
[1] the start and end commits and the number of reboots are variable,
but the rest of the text is generic
Kernel built and installed, so I shall have something to report in the
next couple of days.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist,
Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
-
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-rc1 and 2.6.21-rc2 kwin dies silently
Eric W. Biederman wrote:
Adrian Bunk <[EMAIL PROTECTED]> writes:
On Wed, Mar 21, 2007 at 05:43:11PM +0000, Sid Boyce wrote:
Sid Boyce wrote:
Andrew Morton wrote:
(cc restored. Please always do reply-to-all)
On Wed, 28 Feb 2007 18:05:13 +0200 [EMAIL PROTECTED] wrote:
On Wednesday 28 February 2007 17:19, Sid Boyce wrote:
openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to
require a password to unlock, but it asks for password. When the screen
unlocks, kwin is gone with no errors logged in /var/log/kdm or
/var/log/messages. No problems with 2.6.20.
Same problem on openSUSE 10.2 x86_64, KDE-3.5.5 and 2.6.21-rc2.
Regards
Sid.
This is the linux kernel mailing list. Perhaps you should post your
problem to the opensuse mailing list.
2.6.20 worked.
2.6.20-rc2 did not.
Working theory: the kernel broke.
Sid, the chances that anyone can work out what caused this are pretty
low. It would be great if you could perform a git bisection search
sometime in
the next few weeks, work out which commit caused this.
Thanks.
I shall go back to 2.6.20-git3 and work forward. Up to 2.6.20-git2 was OK.
Regards
Sid.
I tracked the problem down to 2.6.20-git11. Up to 2.6.20-git10 is OK,
but from 2.6.20-git11 up to current 2.6.21-rc4-git2 all exhibit the problem.
Thanks for this search.
Looking at the changes between 2.6.20-git10 and 2.6.20-git11, the only
suspicious changes are the 60 sysctl patches by Eric.
Eric, can you look at this issue?
git bisect between git10 (ac98695d6c1508b724f246f38ce57fb4e3cec356)
and git11 (86a71dbd3e81e8870d0f0e56b87875f57e58222b) is likely the most
productive thing that can be done right now.
I can't think of anything in my sysctl patches that would kill an
application. My sysctl work is right on the border with user space
so it is a good candidate but at the same time there should have
been no user visible changes. There were a few places where
I removed sys_sysctl support (but not /proc/sys support) but I don't
think any of those were on x86, and they were is such a messed up
state I don't think anyone could have reasonably used them anyway.
So I think either we poke blindly making random guess by hand or
we let git-bisect do it.
Sid do you think you can figure out git-bisect?
git-bisect start
git-bisect bad 86a71dbd3e81e8870d0f0e56b87875f57e58222b
git-bisect good ac98695d6c1508b724f246f38ce57fb4e3cec356
It should narrow the problem down to a single commit in 6-8 tries
after which point we should have enough information to start
making intelligent guesses.
Eric
Reading the manpage doesn't help, so I shall have to delve into the
docs or futher help is needed.
:/usr/src/linux-2.6.20-git11 # git-bisect good
ac98695d6c1508b724f246f38ce57fb4e3cec356
No revs to be shown.
:/usr/src/linux-2.6.20-git11 # ls .git/refs/bisect/
bad
good-ac98695d6c1508b724f246f38ce57fb4e3cec356
:/usr/src/linux-2.6.20-git11 # less
.git/refs/bisect/good-ac98695d6c1508b724f246f38ce57fb4e3cec356
ac98695d6c1508b724f246f38ce57fb4e3cec356
:/usr/src/linux-2.6.20-git11 # less .git/refs/bisect/bad
86a71dbd3e81e8870d0f0e56b87875f57e58222b
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist,
Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
-
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-rc1 and 2.6.21-rc2 kwin dies silently
Sid Boyce wrote: Andrew Morton wrote: (cc restored. Please always do reply-to-all) On Wed, 28 Feb 2007 18:05:13 +0200 [EMAIL PROTECTED] wrote: On Wednesday 28 February 2007 17:19, Sid Boyce wrote: openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to require a password to unlock, but it asks for password. When the screen unlocks, kwin is gone with no errors logged in /var/log/kdm or /var/log/messages. No problems with 2.6.20. Same problem on openSUSE 10.2 x86_64, KDE-3.5.5 and 2.6.21-rc2. Regards Sid. This is the linux kernel mailing list. Perhaps you should post your problem to the opensuse mailing list. 2.6.20 worked. 2.6.20-rc2 did not. Working theory: the kernel broke. Sid, the chances that anyone can work out what caused this are pretty low. It would be great if you could perform a git bisection search sometime in the next few weeks, work out which commit caused this. Thanks. I shall go back to 2.6.20-git3 and work forward. Up to 2.6.20-git2 was OK. Regards Sid. I tracked the problem down to 2.6.20-git11. Up to 2.6.20-git10 is OK, but from 2.6.20-git11 up to current 2.6.21-rc4-git2 all exhibit the problem. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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-rc1 and 2.6.21-rc2 kwin dies silently
Andrew Morton wrote: (cc restored. Please always do reply-to-all) On Wed, 28 Feb 2007 18:05:13 +0200 [EMAIL PROTECTED] wrote: On Wednesday 28 February 2007 17:19, Sid Boyce wrote: openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to require a password to unlock, but it asks for password. When the screen unlocks, kwin is gone with no errors logged in /var/log/kdm or /var/log/messages. No problems with 2.6.20. Same problem on openSUSE 10.2 x86_64, KDE-3.5.5 and 2.6.21-rc2. Regards Sid. This is the linux kernel mailing list. Perhaps you should post your problem to the opensuse mailing list. 2.6.20 worked. 2.6.20-rc2 did not. Working theory: the kernel broke. Sid, the chances that anyone can work out what caused this are pretty low. It would be great if you could perform a git bisection search sometime in the next few weeks, work out which commit caused this. Thanks. I shall go back to 2.6.20-git3 and work forward. Up to 2.6.20-git2 was OK. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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-rc1 and 2.6.21-rc2 kwin dies silently
Avi Kivity wrote:
Sid Boyce wrote:
> Avi Kivity wrote:
>> Sid Boyce wrote:
>>>> > That's very much appreciated. The point is that all vanilla
>>>> kernels up
>>>> > to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and
>>>> > 2.6.20-rc2 and like other problems reported, sic framebuffer,
etc.,
>>>> > there is a distinct likelihood that it's related to those kernels
>>>> and
>>>> > worth reporting here where it will also be seen by the openSUSE
>>>> kernel
>>>> > developers.
>>>>
>>>> Try running an strace on kwin and reporting the result.
>>>>
>>>>
>>> Modified /opt/kde3/bin/startkde as below, but got no output, not
>>> even an empty file.
>>> strace -s 256 -f kwin --lock -o /home/lancelot/KWIN.out &
>>
>> Perhaps that line is never executed.
>>
>> Try running kwin from your konsole after it dies, with the strace of
>> course. Oh, and put the '-o ...' before the kwin command, not after.
>>
>>
>
> Oops!, above text should read the same as the subject line, problems
> seen on 2.6.21-rc1 and 2.6.21-rc2.
> The strace is huge 2737627 2007-03-02 03:28 KWIN.out. Further digging
> shows kwin, kicker and klauncher and perhaps other kdeinit stuff also
> die - no desktop icons after those 3 are started from the commandline.
> Moving kdesktop_lock out of /opt/kde3/bin, everything comes back after
> the video is blanked -- no password required.
> I shall run like that (2.6.21-rc2-git1 currently) and wait for
> openSUSE to upgrade to 2.6.21. I can send the straces of kicker and
> kwin on if you think it's still worth it.
Post the last few lines of the strace.
--
Do not meddle in the internals of kernels, for they are subtle and
quick to panic.
From kwin, the exit was caused by me doing CTRL-ALT-BKSPC after the
kdeinit stuff had exited.
=
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 gettimeofday({1172806052, 373523}, NULL) = 0
7670 gettimeofday({1172806052, 373583}, NULL) = 0
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 select(4, [3], [3], NULL, NULL) = 1 (out [3])
7670 writev(3, [{"[EMAIL PROTECTED]
\0\0\0\t\0\0\0C\0\0\0\1\0\0\0\1\0\0\0\244\334\4\10\364\237}\267\230\r\304\277\220\200`\267\244\334\4\10\2\0
@[EMAIL PROTECTED]
[EMAIL PROTECTED]@[EMAIL PROTECTED]
\0\0\0
[EMAIL PROTECTED]@\0\10\0\2\0\v\0\0\1\22\0\7\0009\1\0\0k\1\0\0!\0\0\0
[EMAIL PROTECTED]
[EMAIL PROTECTED]"..., 320}], 1) = 320
7670 read(3,
"[EMAIL PROTECTED]@[EMAIL PROTECTED]@\0\34
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL
PROTECTED]
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]
\27\0\0\0\326\5\27\0\3\0\34\10\0\0\0\0\250X\227"..., 4096) = 1280
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3,
"[EMAIL PROTECTED]",
4096) = 32
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
7670 read(3, 0x8056308, 4096)
2.6.21-rc1 kwin dies silently
openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to require a password to unlock, but it asks for password. When the screen unlocks, kwin is gone with no errors logged in /var/log/kdm or /var/log/messages. No problems with 2.6.20. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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-rc1 and 2.6.21-rc2 kwin dies silently
Avi Kivity wrote: Sid Boyce wrote: > That's very much appreciated. The point is that all vanilla kernels up > to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and > 2.6.20-rc2 and like other problems reported, sic framebuffer, etc., > there is a distinct likelihood that it's related to those kernels and > worth reporting here where it will also be seen by the openSUSE kernel > developers. Try running an strace on kwin and reporting the result. Modified /opt/kde3/bin/startkde as below, but got no output, not even an empty file. strace -s 256 -f kwin --lock -o /home/lancelot/KWIN.out & Perhaps that line is never executed. Try running kwin from your konsole after it dies, with the strace of course. Oh, and put the '-o ...' before the kwin command, not after. Oops!, above text should read the same as the subject line, problems seen on 2.6.21-rc1 and 2.6.21-rc2. The strace is huge 2737627 2007-03-02 03:28 KWIN.out. Further digging shows kwin, kicker and klauncher and perhaps other kdeinit stuff also die - no desktop icons after those 3 are started from the commandline. Moving kdesktop_lock out of /opt/kde3/bin, everything comes back after the video is blanked -- no password required. I shall run like that (2.6.21-rc2-git1 currently) and wait for openSUSE to upgrade to 2.6.21. I can send the straces of kicker and kwin on if you think it's still worth it. Thanks and Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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-rc1 and 2.6.21-rc2 kwin dies silently
Avi Kivity wrote: Sid Boyce wrote: > >>/ openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to/ > >>/ require a password to unlock, but it asks for password. When the > screen/ > >>/ unlocks, kwin is gone with no errors logged in /var/log/kdm or/ > >>/ /var/log/messages. No problems with 2.6.20./ > >> > >>/ Same problem on openSUSE 10.2 x86_64, KDE-3.5.5 and 2.6.21-rc2./ > >>/ Regards/ > >>/ Sid./ > > > This is the linux kernel mailing list. Perhaps you should post your > problem to > > the opensuse mailing list. > > > > Regards > That's very much appreciated. The point is that all vanilla kernels up > to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and > 2.6.20-rc2 and like other problems reported, sic framebuffer, etc., > there is a distinct likelihood that it's related to those kernels and > worth reporting here where it will also be seen by the openSUSE kernel > developers. Try running an strace on kwin and reporting the result. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. Modified /opt/kde3/bin/startkde as below, but got no output, not even an empty file. strace -s 256 -f kwin --lock -o /home/lancelot/KWIN.out & Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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-rc1 and 2.6.21-rc2 kwin dies silently
>>/ openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to/ >>/ require a password to unlock, but it asks for password. When the screen/ >>/ unlocks, kwin is gone with no errors logged in /var/log/kdm or/ >>/ /var/log/messages. No problems with 2.6.20./ >> >>/ Same problem on openSUSE 10.2 x86_64, KDE-3.5.5 and 2.6.21-rc2./ >>/ Regards/ >>/ Sid./ > This is the linux kernel mailing list. Perhaps you should post your problem to > the opensuse mailing list. > > Regards That's very much appreciated. The point is that all vanilla kernels up to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and 2.6.20-rc2 and like other problems reported, sic framebuffer, etc., there is a distinct likelihood that it's related to those kernels and worth reporting here where it will also be seen by the openSUSE kernel developers. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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/
2.6.21-rc1 and 2.6.21-rc2 kwin dies silently
openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to require a password to unlock, but it asks for password. When the screen unlocks, kwin is gone with no errors logged in /var/log/kdm or /var/log/messages. No problems with 2.6.20. Same problem on openSUSE 10.2 x86_64, KDE-3.5.5 and 2.6.21-rc2. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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: IPV6 build failure 2.6.20-git1x
Neil Brown wrote: On Wednesday February 21, [EMAIL PROTECTED] wrote: x86_64 builds without errors on openSUSE 10.2. x86 on openSUSE 10.3 Alpha1 gcc version 4.1.2 20070115 (prerelease) (SUSE Linux) CONFIG_IPV6=m CONFIG_IPV6_PRIVACY=y CONFIG_IPV6_ROUTER_PREF=y CONFIG_IPV6_ROUTE_INFO=y # CONFIG_IPV6_MIP6 is not set CONFIG_IPV6_SIT=m # CONFIG_IPV6_TUNNEL is not set CONFIG_IPV6_MULTIPLE_TABLES=y # CONFIG_IPV6_SUBTREES is not set CONFIG_IP6_NF_MATCH_IPV6HEADER=m LD arch/i386/lib/built-in.o CC arch/i386/lib/bitops.o AS arch/i386/lib/checksum.o CC arch/i386/lib/delay.o AS arch/i386/lib/getuser.o CC arch/i386/lib/memcpy.o CC arch/i386/lib/mmx.o AS arch/i386/lib/putuser.o AS arch/i386/lib/semaphore.o CC arch/i386/lib/strstr.o CC arch/i386/lib/usercopy.o AR arch/i386/lib/lib.a GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 net/built-in.o: In function `svc_udp_recvfrom': svcsock.c:(.text+0x91f9c): undefined reference to `__ipv6_addr_type' make: *** [.tmp_vmlinux1] Error 1 :/usr/src/linux-2.6.20-git15 Yes, known. I really should get onto that Currently you cannot have IPV6=m and SUNRPC=y. All other combinations should work. NeilBrown Fixed thanks, on x86 SUNRPC was =y and on x86_64 was =m. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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/
IPV6 build failure 2.6.20-git1x
x86_64 builds without errors on openSUSE 10.2. x86 on openSUSE 10.3 Alpha1 gcc version 4.1.2 20070115 (prerelease) (SUSE Linux) CONFIG_IPV6=m CONFIG_IPV6_PRIVACY=y CONFIG_IPV6_ROUTER_PREF=y CONFIG_IPV6_ROUTE_INFO=y # CONFIG_IPV6_MIP6 is not set CONFIG_IPV6_SIT=m # CONFIG_IPV6_TUNNEL is not set CONFIG_IPV6_MULTIPLE_TABLES=y # CONFIG_IPV6_SUBTREES is not set CONFIG_IP6_NF_MATCH_IPV6HEADER=m LD arch/i386/lib/built-in.o CC arch/i386/lib/bitops.o AS arch/i386/lib/checksum.o CC arch/i386/lib/delay.o AS arch/i386/lib/getuser.o CC arch/i386/lib/memcpy.o CC arch/i386/lib/mmx.o AS arch/i386/lib/putuser.o AS arch/i386/lib/semaphore.o CC arch/i386/lib/strstr.o CC arch/i386/lib/usercopy.o AR arch/i386/lib/lib.a GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 net/built-in.o: In function `svc_udp_recvfrom': svcsock.c:(.text+0x91f9c): undefined reference to `__ipv6_addr_type' make: *** [.tmp_vmlinux1] Error 1 :/usr/src/linux-2.6.20-git15 Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.19 and up to 2.6.20-rc2 Ethernet problems x86_64
Len Brown wrote: ..same problem with 2.6.20-rc3. Last worked with 2.6.19-rc6-git12, so it was 2.6.19 where it failed. Attaching both case1 normal, case2 acpi=noirq. With acpi=noirq ethernet doesn't get configured, route -n says it's an Unsupported operation, ifconfig only shows for localhost, ifconfig eth0 192.168.10.5 also complains of a config error. It seems that the "acpi=noirq" (and probably also the acpi=off) case is simply an additional broken case, not a success case to compare to. The thing we really want to compare is dmesg and /proc/interrupts from 2.6.19-rc6-git12, and the broken current release. Perhaps you can put that info in the bug report when you file it. thanks, -Len 2.6.19-rc6-git12 fails in exactly the same way, from /var/log/messages it seems 2.6.19-rc6 19/11/06 first saw the problem, details later when I boot 2.6.19-rc5. If I boot an affected kernel with the SuSEfirewall2 enabled and then stop the firewall, the problems goes away. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.19 and up to 2.6.20-rc2 Ethernet problems x86_64
Jarek Poplawski wrote: On Tue, Jan 02, 2007 at 03:32:01PM +, Sid Boyce wrote: Jarek Poplawski wrote: ... If you could send full ifconfig, route -n (or ip route if you use additional tables) and tcpdump (all packets) >from both boxes while pinging each other and a few words how it is connected (other cards, other active boxes in the network?) maybe something more could be found. ... Everything is fine with a eepro100 on the 64x2 box that gave the same problem with a nVidia Corporation MCP51 Ethernet Controller (rev a1) using the forcedeth module. On the x86_64 laptop the problem is with a Broadcom NetXtreme BCM5788 using the tg3 module. Switching back to a 2.6.18.2 kernel, there is no problem. With all configurations of cards on both, route -n is the same on all kernels and instantly reports back. With >=2.6.19 on the laptop, netstat -r takes a very long time before returning the information ~30 seconds, instantly on 2.6.18.2. This could be a problem with DNS. Could you do all tests (including pinging) with -n option? I've read your other message on netdev and see you have firewall working and addresses from various networks in logs. I think it would be much easier to exclude possible network config errors and try to isolate pinging problems by connecting (with switch or even crossed cable if possible) only 2 boxes with firewalls and other net devices disabled and try to repeat this pinging with tcpdumps. Jarek P. It seems >=2.6.19 and the SuSEfirewall are incompatible. Turning off the firewall on the laptop cured the problem using 2.6.20-rc2 and 2.6.20-rc3. I thought it was off. On the 64x2 box, the firewall is turned off, so I shall have to reconfigure the network to use the Gigabit ethernet instead of the eepro100 in case I turned it off after seeing the bug on that box, but didn't stop the firewall. There is still the problem where the ethernet doesn't get configured with acpi=off which I shall post to the acpi devel list, but this is not a showstopper for me. ifconfig eth0 192.168.10.5 returns SIOCSIFFLAGS: Function not implemented. Thanks and Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.19 and up to 2.6.20-rc2 Ethernet problems x86_64
-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=194.117.134.19 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=13907 DF PROTO=UDP SPT=1034 DPT=53 LEN=43 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=194.117.134.19 DST=192.168.10.5 LEN=138 TOS=0x00 PREC=0x00 TTL=248 ID=56 16 DF PROTO=UDP SPT=53 DPT=1036 LEN=118 SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=194.117.134.19 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=18909 DF PROTO=UDP SPT=1036 DPT=53 LEN=43 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=195.188.53.175 DST=192.168.10.5 LEN=74 TOS=0x00 PREC=0x00 TTL=247 ID=356 16 DF PROTO=UDP SPT=53 DPT=1039 LEN=54 etc.,etc. SRC=194.117.134.19 DST=192.168.10.5 LEN=119 TOS=0x00 PREC=0x00 TTL=248 ID=56 11 DF PROTO=UDP SPT=53 DPT=1028 LEN=99 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:50:22:40:0f:d2:08:00 SRC=192.168.10.1 DST=192.168.10.5 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=47746 PROTO=ICMP TYPE=0 CODE=0 ID=34575 SEQ=3 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:50:22:40:0f:d2:08:00 SRC=192.168.10.1 DST=192.168.10.5 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=47747 PROTO=ICMP TYPE=0 CODE=0 ID=34575 SEQ=4 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=62.31.176.39 DST=192.168.10.5 LEN=119 TOS=0x00 PREC=0x00 TTL=251 ID=1270 8 DF PROTO=UDP SPT=53 DPT=1029 LEN=99 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:50:22:40:0f:d2:08:00 SRC=192.168.10.1 DST=192.168.10.5 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=47748 PROTO=ICMP TYPE=0 CODE=0 ID=34575 SEQ=5 SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=195.188.53.175 LEN=58 TOS=0x00 PREC=0x00 TTL=64 ID=43443 DF PROTO=UDP SPT=1025 DPT=53 LEN=38 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=194.117.134.19 DST=192.168.10.5 LEN=119 TOS=0x00 PREC=0x00 TTL=248 ID=56 13 DF PROTO=UDP SPT=53 DPT=1028 LEN=99 SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=194.117.134.19 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=13907 DF PROTO=UDP SPT=1034 DPT=53 LEN=43 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=194.117.134.19 DST=192.168.10.5 LEN=138 TOS=0x00 PREC=0x00 TTL=248 ID=56 16 DF PROTO=UDP SPT=53 DPT=1036 LEN=118 SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=194.117.134.19 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=18909 DF PROTO=UDP SPT=1036 DPT=53 LEN=43 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=195.188.53.175 DST=192.168.10.5 LEN=74 TOS=0x00 PREC=0x00 TTL=247 ID=356 16 DF PROTO=UDP SPT=53 DPT=1039 LEN=54 etc.,etc. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.19 and up to 2.6.20-rc2 Ethernet problems x86_64
=60 TOS=0x00 PREC=0x00 TTL=64 ID=64687 DF PROTO=TCP SPT=14566 DPT=111 WINDOW=5840 RES=0x00 S YN URGP=0 OPT (020405B40402080AFFFC4A3601030302) SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=224.0.0.22 LEN=40 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF OPT (9404) PROTO=2 SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=224.0.0.251 LEN=107 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=87 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.10.5 DST=224.0.0.251 LEN=107 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=87 eth0: no IPv6 routers present SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=192.168.10.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=64689 DF PROTO=TCP SPT=14566 DPT=111 WINDOW=5840 RES=0x00 S YN URGP=0 OPT (020405B40402080AFFFC908601030302) SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=195.188.53.175 DST=192.168.10.5 LEN=119 TOS=0x00 PREC=0x00 TTL=247 ID=45 161 DF PROTO=UDP SPT=53 DPT=1025 LEN=99 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=195.188.53.175 DST=192.168.10.5 LEN=119 TOS=0x00 PREC=0x00 TTL=247 ID=45 162 DF PROTO=UDP SPT=53 DPT=1027 LEN=99 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=62.31.176.39 DST=192.168.10.5 LEN=119 TOS=0x00 PREC=0x00 TTL=251 ID=1270 7 DF PROTO=UDP SPT=53 DPT=1026 LEN=99 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:50:22:40:0f:d2:08:00 SRC=192.168.10.1 DST=192.168.10.5 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=47744 PROTO=ICMP TYPE=0 CODE=0 ID=34575 SEQ=1 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:50:22:40:0f:d2:08:00 SRC=192.168.10.1 DST=192.168.10.5 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=47745 PROTO=ICMP TYPE=0 CODE=0 ID=34575 SEQ=2 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=194.117.134.19 DST=192.168.10.5 LEN=119 TOS=0x00 PREC=0x00 TTL=248 ID=56 11 DF PROTO=UDP SPT=53 DPT=1028 LEN=99 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:50:22:40:0f:d2:08:00 SRC=192.168.10.1 DST=192.168.10.5 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=47746 PROTO=ICMP TYPE=0 CODE=0 ID=34575 SEQ=3 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:50:22:40:0f:d2:08:00 SRC=192.168.10.1 DST=192.168.10.5 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=47747 PROTO=ICMP TYPE=0 CODE=0 ID=34575 SEQ=4 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=62.31.176.39 DST=192.168.10.5 LEN=119 TOS=0x00 PREC=0x00 TTL=251 ID=1270 8 DF PROTO=UDP SPT=53 DPT=1029 LEN=99 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:50:22:40:0f:d2:08:00 SRC=192.168.10.1 DST=192.168.10.5 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=47748 PROTO=ICMP TYPE=0 CODE=0 ID=34575 SEQ=5 SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=195.188.53.175 LEN=58 TOS=0x00 PREC=0x00 TTL=64 ID=43443 DF PROTO=UDP SPT=1025 DPT=53 LEN=38 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=194.117.134.19 DST=192.168.10.5 LEN=119 TOS=0x00 PREC=0x00 TTL=248 ID=56 13 DF PROTO=UDP SPT=53 DPT=1028 LEN=99 SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=194.117.134.19 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=13907 DF PROTO=UDP SPT=1034 DPT=53 LEN=43 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=194.117.134.19 DST=192.168.10.5 LEN=138 TOS=0x00 PREC=0x00 TTL=248 ID=56 16 DF PROTO=UDP SPT=53 DPT=1036 LEN=118 SFW2-OUT-ERROR IN= OUT=eth0 SRC=192.168.10.5 DST=194.117.134.19 LEN=63 TOS=0x00 PREC=0x00 TTL=64 ID=18909 DF PROTO=UDP SPT=1036 DPT=53 LEN=43 SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:0a:e4:4e:a1:42:00:48:54:d0:22:f0:08:00 SRC=195.188.53.175 DST=192.168.10.5 LEN=74 TOS=0x00 PREC=0x00 TTL=247 ID=356 16 DF PROTO=UDP SPT=53 DPT=1039 LEN=54 etc.,etc. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.19 and up to 2.6.20-rc2 Ethernet problems x86_64
Jarek Poplawski wrote: On Sat, Dec 30, 2006 at 02:21:15AM +, Sid Boyce wrote: Jarek Poplawski wrote: On 28-12-2006 04:23, Sid Boyce wrote: I first saw the problem on the 64x2 box after upgrading to 2.6.19. The network appeared OK with ifconfig and route -n, but I had no network access. Pinging any other box, the box was responding, but no response ... barrabas:/usr/src/linux-2.6.20-rc1-git5 # ssh Boycie ifconfig Password: eth0 Link encap:Ethernet HWaddr 00:0A:E4:4E:A1:42 inet addr:192.168.10.5 Bcast:255.255.255.255 Mask:255.255.255.0 This Bcast isn't probably what you need. Regards, Jarek P. Corrected on the one box where it was not correct, problem is still there. There are many things to suspect yet: - firewall, - switch, - routing, - ifconfig, - other misonfigured box, - connecting and so on. I think you should try with some linux networking group at first and if you really think it's driver then netdev@vger.kernel.org (instead of linux-kernel@). If you could send full ifconfig, route -n (or ip route if you use additional tables) and tcpdump (all packets) from both boxes while pinging each other and a few words how it is connected (other cards, other active boxes in the network?) maybe something more could be found. Cheers, Jarek P. PS: Sorry for late responding. I have a problem with posting to linux-kernel and netdev, my mail got returned as SPAM, now it just gets dropped. postmaster says the filter is seeing a sub-string of something that is filtered. I shall try posting under another email address. Everything is fine with a eepro100 on the 64x2 box that gave the same problem with a nVidia Corporation MCP51 Ethernet Controller (rev a1) using the forcedeth module. On the x86_64 laptop the problem is with a Broadcom NetXtreme BCM5788 using the tg3 module. Switching back to a 2.6.18.2 kernel, there is no problem. With all configurations of cards on both, route -n is the same on all kernels and instantly reports back. With >=2.6.19 on the laptop, netstat -r takes a very long time before returning the information ~30 seconds, instantly on 2.6.18.2. Boycie:~ # netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.10.0* 255.255.255.0 U 0 0 0 eth0 loopback* 255.0.0.0 U 0 0 0 lo default Smoothie.site 0.0.0.0 UG0 0 0 eth0 Boycie:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.10.00.0.0.0 255.255.255.0 U 0 00 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 192.168.10.102 0.0.0.0 UG0 0 0 eth0 -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.19 and up to 2.6.20-rc2 Ethernet problems x86_64
Jarek Poplawski wrote: On Sat, Dec 30, 2006 at 02:21:15AM +, Sid Boyce wrote: Jarek Poplawski wrote: On 28-12-2006 04:23, Sid Boyce wrote: I first saw the problem on the 64x2 box after upgrading to 2.6.19. The network appeared OK with ifconfig and route -n, but I had no network access. Pinging any other box, the box was responding, but no response ... barrabas:/usr/src/linux-2.6.20-rc1-git5 # ssh Boycie ifconfig Password: eth0 Link encap:Ethernet HWaddr 00:0A:E4:4E:A1:42 inet addr:192.168.10.5 Bcast:255.255.255.255 Mask:255.255.255.0 This Bcast isn't probably what you need. Regards, Jarek P. Corrected on the one box where it was not correct, problem is still there. There are many things to suspect yet: - firewall, - switch, - routing, - ifconfig, - other misonfigured box, - connecting and so on. I think you should try with some linux networking group at first and if you really think it's driver then netdev@vger.kernel.org (instead of linux-kernel@). If you could send full ifconfig, route -n (or ip route if you use additional tables) and tcpdump (all packets) from both boxes while pinging each other and a few words how it is connected (other cards, other active boxes in the network?) maybe something more could be found. Cheers, Jarek P. PS: Sorry for late responding. I have a problem with posting to linux-kernel and netdev, my mail got returned as SPAM, now it just gets dropped. postmaster says the filter is seeing a sub-string of something that is filtered. Everything is fine with a eepro100 on the 64x2 box that gave the same problem with a nVidia Corporation MCP51 Ethernet Controller (rev a1) using the forcedeth module. On the x86_64 laptop the problem is with a Broadcom NetXtreme BCM5788 using the tg3 module. Switching back to a 2.6.18.2 kernel, there is no problem. With all configurations of cards on both, route -n is the same on all kernels and instantly reports back. With >=2.6.19 on the laptop, netstat -r takes a very long time before returning the information ~30 seconds, instantly on 2.6.18.2. Boycie:~ # netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.10.0* 255.255.255.0 U 0 0 0 eth0 loopback* 255.0.0.0 U 0 0 0 lo default Smoothie.site 0.0.0.0 UG0 0 0 eth0 Boycie:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.10.00.0.0.0 255.255.255.0 U 0 00 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 192.168.10.102 0.0.0.0 UG0 00 eth0 Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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.19 and up to 2.6.20-rc2 Ethernet problems x86_64
Jarek Poplawski wrote: On Sat, Dec 30, 2006 at 02:21:15AM +, Sid Boyce wrote: Jarek Poplawski wrote: On 28-12-2006 04:23, Sid Boyce wrote: I first saw the problem on the 64x2 box after upgrading to 2.6.19. The network appeared OK with ifconfig and route -n, but I had no network access. Pinging any other box, the box was responding, but no response ... barrabas:/usr/src/linux-2.6.20-rc1-git5 # ssh Boycie ifconfig Password: eth0 Link encap:Ethernet HWaddr 00:0A:E4:4E:A1:42 inet addr:192.168.10.5 Bcast:255.255.255.255 Mask:255.255.255.0 This Bcast isn't probably what you need. Regards, Jarek P. Corrected on the one box where it was not correct, problem is still there. There are many things to suspect yet: - firewall, - switch, - routing, - ifconfig, - other misonfigured box, - connecting and so on. I think you should try with some linux networking group at first and if you really think it's driver then netdev@vger.kernel.org (instead of linux-kernel@). If you could send full ifconfig, route -n (or ip route if you use additional tables) and tcpdump (all packets) from both boxes while pinging each other and a few words how it is connected (other cards, other active boxes in the network?) maybe something more could be found. Cheers, Jarek P. PS: Sorry for late responding. I have a problem with posting to linux-kernel and netdev, my mail got returned as SPAM, now it just gets dropped. postmaster says the filter is seeing a sub-string of something that is filtered. I shall try under my other email address. Everything is fine with a eepro100 on the 64x2 box that gave the same problem with a nVidia Corporation MCP51 Ethernet Controller (rev a1) using the forcedeth module. On the x86_64 laptop the problem is with a Broadcom NetXtreme BCM5788 using the tg3 module. Switching back to a 2.6.18.2 kernel, there is no problem. With all configurations of cards on both, route -n is the same on all kernels and instantly reports back. With >=2.6.19 on the laptop, netstat -r takes a very long time before returning the information ~30 seconds, instantly on 2.6.18.2. Boycie:~ # netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.10.0* 255.255.255.0 U 0 0 0 eth0 loopback* 255.0.0.0 U 0 0 0 lo default Smoothie.site 0.0.0.0 UG0 0 0 eth0 Boycie:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.10.00.0.0.0 255.255.255.0 U 0 00 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 192.168.10.102 0.0.0.0 UG0 0 0 eth0 -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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/
2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64
y kernel
Boycie sees just a few packets occasionally when pinged from barrabas,
but says its dropped no packets.
Also strange, I can scp a file from Boycie.
barrabas:/usr/src/linux-2.6.20-rc1-git5 # scp Boycie:/IFCONFIG /
Password:
IFCONFIG100% 907
0.9KB/s 00:00
barrabas:/usr/src/linux-2.6.20-rc1-git5 # o /IFCONFIG
eth0 Link encap:Ethernet HWaddr 00:0A:E4:4E:A1:42
inet addr:192.168.10.5 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::20a:e4ff:fe4e:a142/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:577 errors:0 dropped:0 overruns:0 frame:0
TX packets:569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:65202 (63.6 Kb) TX bytes:49404 (48.2 Kb)
Interrupt:20
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1866 (1.8 Kb) TX bytes:1866 (1.8 Kb)
barrabas:/usr/src/linux-2.6.20-rc1-git5 # ssh Boycie ifconfig
Password:
eth0 Link encap:Ethernet HWaddr 00:0A:E4:4E:A1:42
inet addr:192.168.10.5 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::20a:e4ff:fe4e:a142/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:728 errors:0 dropped:0 overruns:0 frame:0
TX packets:710 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:83960 (81.9 Kb) TX bytes:65125 (63.5 Kb)
Interrupt:20
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1866 (1.8 Kb) TX bytes:1866 (1.8 Kb)
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
-
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.13 git snapshot patches still empty
Andrew Morton wrote: Sid Boyce <[EMAIL PROTECTED]> wrote: For both -git1.gz/.bz2 and -git2.gz/.bz2. http://www.zip.com.au/~akpm/linux/patches/stuff/linus.patch.gz is updated once or twice daily. It's Linus's latest tip-of-tree. Thanks, I shall give it a whirl. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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: Touchpad errors
Lee Revell wrote: On Wed, 2005-08-03 at 00:14 +0400, Dmitrij Bogush wrote: This happens when some software check battery state or current cpu rate too often. Acer laptops are notorious for buggy SMM implementations that disable interrupts for many timer ticks. Does it work any better with HZ=100? Lee The problem, initially at least, doesn't seem as sever at HZ=100, 18 occurrences in 3 mins 30 seconds. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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: Touchpad errors
Dmitry Torokhov wrote: On 8/2/05, Sid Boyce <[EMAIL PROTECTED]> wrote: New SuSE 9.3 x86_64 install after HD crash. With 2.6.13-rc3 and up to 2.6.13-rc4-git4. I can't remember seeing these errors for quite a long time, thought they were fixed, perhaps there is a regression in recent kernels. It completely and rapidly fills up dmesg and /var/log/messages so I can't get other stuff I need to see. psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched. psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 Does it work with acpi=off? It does not boot with SuSE 9.3 default kernel, 2.6.13-rc3 or 2.6.13-rc4-git4, locks up after an initial message with a blank screen. Acer 1501LCe x86_64 laptop. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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/
Touchpad errors
New SuSE 9.3 x86_64 install after HD crash. With 2.6.13-rc3 and up to 2.6.13-rc4-git4. I can't remember seeing these errors for quite a long time, thought they were fixed, perhaps there is a regression in recent kernels. It completely and rapidly fills up dmesg and /var/log/messages so I can't get other stuff I need to see. psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched. psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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: kdb v4.4 supports OHCI keyboard in 2.6
CHK include/linux/version.h make[1]: `arch/i386/kernel/asm-offsets.s' is up to date. CHK include/linux/compile.h CHK usr/initramfs_list CC arch/i386/kernel/traps.o arch/i386/kernel/traps.c:809: error: redefinition of `do_int3' arch/i386/kernel/traps.c:709: error: `do_int3' previously defined here make[1]: *** [arch/i386/kernel/traps.o] Error 1 make: *** [arch/i386/kernel] Error 2 Both lines are the same, enabling both kprobes and kdb causes the error, so kprobes must be deselected. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks - 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 USB Keypad still not working
The latest collection of data on this problem with 2.6.13-rc2, no change
since new device installed under 2.6.12.
barrabas:/home/lancelot # cat /proc/asound/oss/sndstat
Sound Driver:3.8.1a-980706 (ALSA v1.0.9 emulation code)
Kernel: Linux barrabas 2.6.13-rc2 #1 Thu Jul 7 00:44:07 BST 2005 i686
Config options: 0
Installed drivers:
Type 10: ALSA emulation
Card config:
NVidia nForce2 with ALC650F at 0xed08, irq 201
BeyondTel USB Phone at usb-:00:02.1-2, full speed
Audio devices:
0: NVidia nForce2 (DUPLEX)
1: USB Audio (DUPLEX)
Synth devices: NOT ENABLED IN CONFIG
Midi devices: NOT ENABLED IN CONFIG
Timers:
7: system timer
Mixers:
0: Realtek ALC650F
1: USB Mixer
# aplay -l
List of PLAYBACK Hardware Devices
card 0: CH [NVidia nForce2], device 0: Intel ICH [NVidia nForce2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CH [NVidia nForce2], device 2: Intel ICH - IEC958 [NVidia
nForce2 - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Phone [USB Phone], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
# arecord -l
List of CAPTURE Hardware Devices
card 0: CH [NVidia nForce2], device 0: Intel ICH [NVidia nForce2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: CH [NVidia nForce2], device 1: Intel ICH - MIC ADC [NVidia
nForce2 - MIC ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Phone [USB Phone], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful
attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at class device '/sys/bus/usb/devices/usb3/3-2/3-2:1.3':
SUBSYSTEM="unknown"
SYSFS{bAlternateSetting}=" 0"
SYSFS{bInterfaceClass}="03"
SYSFS{bInterfaceNumber}="03"
SYSFS{bInterfaceProtocol}="00"
SYSFS{bInterfaceSubClass}="00"
SYSFS{bNumEndpoints}="02"
SYSFS{interface}="Keypad"
SYSFS{modalias}="usb:v04B4p0303d0100dc00dsc00dp00ic03isc00ip00"
# udevinfo -a -p /sys/bus/usb/devices/usb3/3-2
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful
attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at class device '/sys/bus/usb/devices/usb3/3-2':
SUBSYSTEM="unknown"
SYSFS{bConfigurationValue}="1"
SYSFS{bDeviceClass}="00"
SYSFS{bDeviceProtocol}="00"
SYSFS{bDeviceSubClass}="00"
SYSFS{bMaxPower}="100mA"
SYSFS{bNumConfigurations}="1"
SYSFS{bNumInterfaces}=" 4"
SYSFS{bcdDevice}="0100"
SYSFS{bmAttributes}="80"
SYSFS{configuration}="USB Phone"
SYSFS{devnum}="3"
SYSFS{idProduct}="0303"
SYSFS{idVendor}="04b4"
SYSFS{manufacturer}="BeyondTel"
SYSFS{maxchild}="0"
SYSFS{product}="USB Phone"
SYSFS{serial}="0004"
SYSFS{speed}="12"
SYSFS{version}=" 1.00"
barrabas:/ftp/jul05 # cat /proc/bus/input/devices
I: Bus=0003 Vendor=04b4 Product=0303 Version=0100
N: Name="BeyondTel USB Phone"
P: Phys=usb-:00:02.1-2/input3
H: Handlers=kbd event0
B: EV=13
B: KEY=e080ffdf 1cf fffe
Regards
Sid.
Sid Boyce wrote:
Andrew Morton wrote:
Sid Boyce <[EMAIL PROTECTED]> wrote:
PhoneSkype USB Phone SK-04.
It gets detected, is registered in /sys/bus/usb as a Keypad.
Everything else USB works including the phone handset. Nothing is
detected by showkey when keys are pressed.
# less /sys/bus/usb/devices/usb3/3-2/3-2:1.3/interface
Keypad
/dev/usb/hiddev? and /dev/input/keyboard say they are not valid
devices and they are the ones created by the SuSE 9.3 install, not by
udev.
From dmesg
--
usbcore: registered new driver hiddev
drivers/usb/input/hid-core.c: timeout initializing reports
=
input: USB HID v1.10 Keyboard [BeyondTel USB Phone] on
usb-:00:02.1-2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
input: USB HID v1.00 Joystick [CH PRODUCTS CH FLIGHT SIM YOKE USB ]
on usb-:00:02.1-1.1
input: USB HID v1.00 Joystick [CH PRODUCTS CH PRO PEDALS USB ] on
usb-:00:02.1-1.4
I am puzzled by the fact that the keypad is recognised, but I cannot
do anything with it.
# lsusb
Bus 003 Device 009: ID 04b8:0103 Seiko Epson Corp. Perfection 610
Bus 003 Device 008
RE: LaCie SilverScreen Runs Linux, But No Source
In their comapany blurb to investors, they also claim "in-house approach to R&D and design", "The design of most product components", including "control software". No mention is made of Linux and an equally hard rub, it's only supposed to talk to Windows and Mac. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux for all Computing Tasks - 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/
Strange italics with -ac kernels
In KDE and sometimes also seen in netscape, I get displays in italics which I don't in any non-ac kernels. All KDE menus now show up in discontinuous italics that are not really readable. I'm using XFree86-4.0.3, KDE-2.1.1 and an NVidia 32Meg TNT2 M64 card, but I've had the same with much earlier 2.4.x-ac kernels using a VOODO 3 card. Any ideas ? Regards -- Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot Linux only shop.. Tel. 44-121 422 0375 - 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: No USB under 2.4.3 and 2.4.3-ac?
I found that the SuSE 7.1 install didn't put "usbdevfs" in /etc/fstab on the Athlon, the PIII has broken USB port hardware. Regards -- Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot Linux only shop.. Tel. 44-121 422 0375 - 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/
[Fwd: No USB under 2.4.3 and 2.4.3-ac?]
-- Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot Linux only shop.. Tel. 44-121 422 0375 This happens on a PIII/GigaByte 6BXE, Athlon 900/ABit KT7 and on a friend's Cyrix M-II/333 with PC-Chips PC100 mobo and SIS chipset. The PIII is a SuSE 6.4 base +, the others are SuSE 7.1 + modutils-2.4.5 and a few other bits. During boot and "lsusb" ver 0.7 only show the on-board USB chip, it does not see the outboard Hub or devices. lsusb on the PIII will also show the on-board chip, on the other machines it returns blank. We haven't yet tried USB as modules to see if it makes a difference. # USB support # CONFIG_USB=y CONFIG_USB_DEBUG=y # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y CONFIG_USB_BANDWIDTH=y # # USB Controllers # CONFIG_USB_UHCI=y CONFIG_USB_UHCI_ALT=y on Athlon) # USB Device Class drivers CONFIG_USB_PRINTER=y # USB Imaging devices CONFIG_USB_SCANNER=m # USB Multimedia devices CONFIG_USB_OV511=m on the Athlon Regards -- Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot Linux only shop.. Tel. 44-121 422 0375
No USB under 2.4.3 and 2.4.3-ac?
This happens on a PIII/GigaByte 6BXE, Athlon 900/ABit KT7 and on a friend's Cyrix M-II/333 with PC-Chips PC100 mobo and SIS chipset. The PIII is a SuSE 6.4 base +, the others are SuSE 7.1 + modutils-2.4.5 and a few other bits. During boot and "lsusb" ver 0.7 only show the on-board USB chip, it does not see the outboard Hub or devices. lsusb on the PIII will also show the on-board chip, on the other machines it returns blank. We haven't yet tried USB as modules to see if it makes a difference. # USB support # CONFIG_USB=y CONFIG_USB_DEBUG=y # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y CONFIG_USB_BANDWIDTH=y # # USB Controllers # CONFIG_USB_UHCI=y CONFIG_USB_UHCI_ALT=y on Athlon) # USB Device Class drivers CONFIG_USB_PRINTER=y # USB Imaging devices CONFIG_USB_SCANNER=m # USB Multimedia devices CONFIG_USB_OV511=m on the Athlon Regards -- Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot Linux only shop.. Tel. 44-121 422 0375 - 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: prerelease-ac5 make dep error
It was 3.78.1, Documentation/Changes says 3.77, upgraded to 3.79.1 and it's AOK. Thanks and Regards Sid. = Keith Owens wrote: On Thu, 04 Jan 2001 10:27:59 +0000, Sid Boyce <[EMAIL PROTECTED]> wrote: > Just seen this on UP kernel build. >/usr/src/linux/Rules.make:224: *** Recursive variable `CFLAGS' >references itself (eventually). Stop. What does make --version report? -- Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot Linux only shop.. Tel. 44-121 422 0375 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
prerelease-ac5 make dep error
Just seen this on UP kernel build. /usr/src/linux/scripts/mkdep > .depend make _sfdep_acpi _sfdep_atm _sfdep_block _sfdep_cdrom _sfdep_char _sfdep_dio _sfdep_fc4 _sfdep_i2c _sfdep_ide _sfdep_ieee1394 _sfdep_input _sfdep_isdn _sfdep_macintosh _sfdep_md _sfdep_media _sfdep_message/fusion _sfdep_message/i2o _sfdep_misc _sfdep_mtd _sfdep_net _sfdep_net/hamradio _sfdep_nubus _sfdep_parport _sfdep_pci _sfdep_pcmcia _sfdep_pnp _sfdep_sbus _sfdep_scsi _sfdep_sgi _sfdep_sound _sfdep_tc _sfdep_telephony _sfdep_usb _sfdep_video _sfdep_zorro _FASTDEP_ALL_SUB_DIRS="acpi atm block cdrom char dio fc4 i2c ide ieee1394 input isdn macintosh md media message/fusion message/i2o misc mtd net net/hamradio nubus parport pci pcmcia pnp sbus scsi sgi sound tc telephony usb video zorro" make[3]: Entering directory `/usr/src/linux/drivers' make -C acpi fastdep make[4]: Entering directory `/usr/src/linux/drivers/acpi' /usr/src/linux/Rules.make:224: *** Recursive variable `CFLAGS' references itself (eventually). Stop. make[4]: Leaving directory `/usr/src/linux/drivers/acpi' make[3]: *** [_sfdep_acpi] Error 2 make[3]: Leaving directory `/usr/src/linux/drivers' make[2]: *** [fastdep] Error 2 make[2]: Leaving directory `/usr/src/linux/drivers' make[1]: *** [_sfdep_drivers] Error 2 make[1]: Leaving directory `/usr/src/linux' make: *** [dep-files] Error 2 Regards -- Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot Linux only shop.. Tel. 44-121 422 0375 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: test13-pre4-ac2/test13-pre7 ax25 undefined reference
Thanks for the prompt response. Regards Sid. Alan Cox wrote: > > > The problem showed up on the stroke of test13-pre4-ac2 and stuff from > > Alan has been merged in. I went from pre4-ac2 to pre5 (AOK) and now > > attempting pre7... > > Its definitely coming from the AX.25 related changes. Please send me your > .config and I'll go squash this one > > > drivers/net/net.o: In function `network_ldisc_init': > > drivers/net/net.o(.text.init+0x141): undefined reference to > > `mkiss_init_ctrl_dev > > ' -- Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot Linux only shop.. Tel. 44-121 422 0375 # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # 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_M686FXSR is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set CONFIG_MK7=y # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_USE_3DNOW=y CONFIG_X86_PGE=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_TOSHIBA is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID 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_SMP is not set # CONFIG_X86_UP_IOAPIC is not set # # General setup # CONFIG_NET=y # CONFIG_VISWS is not set CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y # CONFIG_EISA is not set # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # # CONFIG_PCMCIA is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PM=y CONFIG_ACPI=y CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set CONFIG_APM_DO_ENABLE=y CONFIG_APM_CPU_IDLE=y CONFIG_APM_DISPLAY_BLANK=y CONFIG_APM_RTC_IS_GMT=y CONFIG_APM_ALLOW_INTS=y # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_PC_FIFO=y # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_AMIGA is not set # CONFIG_PARPORT_MFC3 is not set # CONFIG_PARPORT_ATARI is not set # CONFIG_PARPORT_SUNBPP is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Plug and Play configuration # CONFIG_PNP=y CONFIG_ISAPNP=y # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_BLK_DEV_LOOP=m # CONFIG_BLK_DEV_NBD is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_NETLINK=y CONFIG_RTNETLINK=y # CONFIG_NETLINK_DEV is not set CONFIG_NETFILTER=y CONFIG_NETFILTER_DEBUG=y # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set # CONFIG_IP_PNP is not set CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m # CONFIG_NET_IPGRE_BROADCAST is not set CONFIG_IP_MROUTE=y # CONFIG_IP_PIMSM_V1 is not set # CONFIG_IP_PIMSM_V2 is not set # CONFIG_ARPD is not set CONFIG_INET_ECN=y CONFIG_SYN_COOKIES=y # # IP: Netfilter Configuration # CONFIG_IP_NF_CONNTRACK=y CONFIG_IP_NF_FTP=y # CONFIG_IP_NF_QUEUE is not set CONFIG_IP_NF_IPTABLES=y # CONFIG_IP_NF_MATCH_LIMIT is not set CONFIG_IP_NF_MATCH_MAC=m # CONFIG_IP_NF_MATCH_MARK is not set # CONFIG_IP_NF_MATCH_MULTIPORT is not set # CONFIG_IP_NF_MATCH_TOS is not set CONFIG_IP_NF_MATCH_STATE=m # CONFIG_IP_NF_MATCH_UNCLEAN is not set # CONFIG_IP_NF_MATCH_OWNER is not set CONFIG_IP_NF_FILTER=y CONFIG_IP_NF_TARGET_REJECT=m # CONFIG_IP_NF_TARGET_MIRROR is not set CONFIG_IP_NF_NAT=y CONFIG_IP_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=y # CONFIG_IP_NF_TARGET_REDIRECT is not set # CONFIG_IP_NF_MANGLE is not set # CONFIG_IP_NF_TARGET_LOG is not set # CONFIG_IPV6 is not set # CONFIG_KHTTPD is not set # CONFIG_ATM is not set # # # # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_DECNET is not set # CONFIG_BRIDGE is not set # CONFIG_X25 is not set #
test13-pre4-ac2/test13-pre7 ax25 undefined reference
The problem showed up on the stroke of test13-pre4-ac2 and stuff from Alan has been merged in. I went from pre4-ac2 to pre5 (AOK) and now attempting pre7... ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel /head.o arch/i386/kernel/init_task.o init/main.o init/version.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/f s.o ipc/ipc.o \ drivers/block/block.o drivers/char/char.o drivers/misc/misc.o drivers/ne t/net.o drivers/media/media.o drivers/ide/idedriver.o drivers/scsi/scsidrv.o dr ivers/cdrom/driver.o drivers/sound/sounddrivers.o drivers/pci/driver.o drivers/p np/pnp.o drivers/video/video.o drivers/net/hamradio/hamradio.o drivers/usb/usbdr v.o drivers/acpi/acpi.o \ net/network.o \ /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/lin ux/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/net/net.o: In function `network_ldisc_init': drivers/net/net.o(.text.init+0x141): undefined reference to `mkiss_init_ctrl_dev ' make: *** [vmlinux] Error 1 Regards -- Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot Linux only shop.. Tel. 44-121 422 0375 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: 2.4.0test7 panics on boot
Felix wrote: > The last non-panic message on screen is: > IPv6 v0.8 for NET4.0 > The panic reason is "attempting to kill init". > Has anyone else had this problem? > Felix Sid Boyce writes: I experienced the same problem when I compiled the kernel with IPV6 selected on one of my machines. I recompiled without IPV6 and it's AOK. I've not followed it up because I'm not using IPV6. Regards -- Sid Boyce ... hamradio G3VBV ... Cessna/Warrior Pilot Linux only shop - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
