On Thursday 17 June 2004 09.53, Fred Miller wrote:

I'm going to guess that SUSE will fix it. It's a security fix, but I don't know what was "broken" in the kernel.

A bug in the way the FPU was managed let user space programs crash the system at will

-----Message d'origine----- De : Fred Miller [mailto:fmiller@lightlink.com] Envoyé : jeudi 17 juin 2004 10:24 À : suse-linux-e@suse.com Objet : Re: [SLE] New kernel - DON'T update!

On Friday June 18 2004 3:55 am, Anders Johansson wrote:

...

On Thursday 17 June 2004 09.53, Fred Miller wrote:

...

I'm going to guess that SUSE will fix it. It's a security fix, but I don't know what was "broken" in the kernel.

A bug in the way the FPU was managed let user space programs crash the system at will.

Ok.....thanks. 'Don't think I'm very worried about that.

Thanks!

Fred

I updated the kernel-sources and compiled yesterday, everything works OK even my scsi 4 old drives (at least 4 to 5 years). BUT, as with all the kotd kernels since june 7th, the nvidia module compiles but won't load due to different source and kernel versions !!! (I compiled from the sources) I suspected the new way to build version.h and revert to the old way, I didn't forget to downgrade the script "running-kernel" and the nvidia and vmware compile and load !! So something is wrong with the versionning ! After looking the new "running-kernel" script, I think that the problem could come from that it seems to be necessary to reboot (or at least to run : /etc/init.d/running-kernel start) after installing the sources. It is not written in the README. I'll have a try as soon as possible. Michel

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

* Anders Johansson (Fri, Jun 18, 2004 at 11:13:31AM +0200)

On Friday 18 June 2004 11.05, Catimimi wrote:

...

BUT, as with all the kotd kernels since june 7th, the nvidia module compiles but won't load due to different source and kernel versions !!! (I compiled from the sources)

Why? It's included precompiled in the kernel rpm

WTF ?? Since when are nvidia modules included with the kernel ?? We're talking about the binary only, closed source 3D accelerated 250000 fps in quake3 NVidia.o driver .. not the open source 2D only nv.o driver Currently listening to: FND2-06 Bruce Springsteen - Across The Border Gerhard, == The Acoustic Motorbiker == -- __O An all I can say is that my lifes is pretty plain =`\<, You don't like my point of view, you think that I'm insane (=)/(=) It's not sane, it's not sane

* Anders Johansson (Fri, Jun 18, 2004 at 11:23:47AM +0200)

On Friday 18 June 2004 11.21, Gerhard den Hollander wrote:

...

* Anders Johansson (Fri, Jun 18, 2004 at 11:13:31AM +0200)

...

On Friday 18 June 2004 11.05, Catimimi wrote:

...

BUT, as with all the kotd kernels since june 7th, the nvidia module compiles but won't load due to different source and kernel versions !!! (I compiled from the sources)

Why? It's included precompiled in the kernel rpm

WTF ?? Since when are nvidia modules included with the kernel ??

We're talking about the binary only, closed source 3D accelerated 250000 fps in quake3 NVidia.o driver .. not the open source 2D only nv.o driver

Yes, the "real" nvidia driver. It's been included in the "mantel" kernels precompiled for a very long time

OK, I didn;t know that .. doesn;t that violate the NVidia license ? Currently listening to: FND2-07 Bruce Springsteen - Growin' Up Gerhard, (faliquid@xs4all.nl) == The Acoustic Motorbiker == -- __O Alone in the clouds all blue, lying on an eiderdown. =`\<, Yippee! You can't see me, but I can you. (=)/(=) Screaming through the starlit sky, travelling by telephone. Hey ho, here we go ,ever so high.

On Friday, 18 June 2004 11:21, Gerhard den Hollander wrote:

3D accelerated 250000 fps in quake3 NVidia.o driver .. As in two hundred and fifty thousand fps? I might just buy a nVidia card next time.... :-)

-- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za

-----Message d'origine----- De : peter Nikolic [mailto:p.nikolic1@btinternet.com] Envoyé : vendredi 18 juin 2004 11:37 À : suse-linux-e@suse.com Objet : Re: [SLE] New kernel - DON'T update!

...

...

-----Message d'origine----- De : Fred Miller [mailto:fmiller@lightlink.com] Envoyé : jeudi 17 juin 2004 10:24 À : suse-linux-e@suse.com Objet : Re: [SLE] New kernel - DON'T update!

On Friday June 18 2004 3:55 am, Anders Johansson wrote:

...

On Thursday 17 June 2004 09.53, Fred Miller wrote:

...

I'm going to guess that SUSE will fix it. It's a security fix, but I don't know what was "broken" in the kernel.

A bug in the way the FPU was managed let user space

...

...

...

system at will.

Ok.....thanks. 'Don't think I'm very worried about that.

Thanks!

Fred

I updated the kernel-sources and compiled yesterday, everything works OK even my scsi 4 old drives (at least 4 to 5 years).

BUT, as with all the kotd kernels since june 7th, the nvidia module compiles but won't load due to different source and kernel versions !!! (I compiled from the sources)

I suspected the new way to build version.h and revert to the old way, I didn't forget to downgrade the script "running-kernel" and the nvidia and vmware compile and load !!

So something is wrong with the versionning ! After looking the new "running-kernel" script, I think that the problem could come from that it seems to be necessary to reboot (or at least to run : /etc/init.d/running-kernel start) after installing the

On Friday 18 Jun 2004 10:05, Catimimi wrote: programs crash the sources. It is

...

not written in the README.

I'll have a try as soon as possible.

Michel

...

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

I installed the new kernel from suse yesterday MADE shure i got the correct sources as well as modules ect rebooted to init 3 ran the Nvidia installer and no problems at all compiled the new driver without a hint of trouble ran init 5 and straight up with the Nvidia driver working niceley mind dont go near sax2 it craps over everything in sight it needs a complete re-write .

First, I don't think that the nvidia driver is in Mantel's kernel, I compile it from nvidia.. Second, you confirm what I thought, since you had to reboot the version.h file is set OK by the running-kernel script, and since you use the stock kernel, its version is OK. But if you compile your kernel without rebooting after installing the sources the version of the kernel is wrong and the nvidia compilation (made after reboot and then with the correct version) fails since the versions are not identical. I spent a lot of time to find that, I reported to Mantel who didn't tell me that reboot was necessary. So you people who want to compile your kernel, KEEP THAT IN MIND. Michel.

-- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan PGN

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

On Thursday 17 June 2004 22:44, Jason wrote:

On Friday 18 June 2004 03:01, Fred Miller wrote:

...

I've done 4 FRESH installs because the update kernel HANGS during bootup on the file log for /dev/sda1!!! No matter what file system is used, it FAILS! SUSE needs to be MUCH more carefull!

I've had problems with the new kernel shutting down -- it locks up the machine while killing processes before umounting the filesystems. :-(

I've reverted back to the previous 2.6.4-54.5 which works fine. I've also tried the Mantel kernel. Same problem. Athlon XP 2400 on a Gigabyte VIA 686 based motherboard, 1GB RAM, modern Seagate 120GB drive....

:-(

Jason

Locks up while killing WHAT proceesses? Locks up HOW? Keyboard lights flashing? There are several known acpi modules that should never be rmmod'ed and if you do rmmod them the system hangs (kernel panic, flashing lights, etc). SuSE provides for this in yast2. -- _____________________________________ John Andersen

On Thursday 17 June 2004 23:21, Jason wrote:

On Friday 18 June 2004 07:50, John Andersen wrote:

...

Locks up while killing WHAT proceesses? Locks up HOW? Keyboard lights flashing?

No flashing lights, no panic. My machine locks up solid on shutdown on "Sending all processes TERM signal...". I've looked in /var/log/messages -- no clues there just a gap in time until the next boot. Also happens when doing "init S".

...

There are several known acpi modules that should never be rmmod'ed and if you do rmmod them the system hangs (kernel panic, flashing lights, etc). SuSE provides for this in yast2.

I don't think it's ACPI. No ACPI modules are removed -- the setting POWERSAVE_ACPI_MODULES_NOT_TO_UNLOAD is the same as POWERSAVE_ACPI_MODULES -- I've not changed any settings -- just applied the update from YOU.

I also downloaded the KOTD, just in case it was a bad patch, but that exhibits the same problem. Boots up OK, and seems to run OK. But locks up on shutdown.

Revert back to 2.5.4-54.5 and everything is fine -- apart from the security bug, of course :-( but I think there's a greater risk from not umounting the filesystems when I shut the machine down at the end of the day...

Agreed, that security bug is only going to bite you if you allow untrusted users shell access on your box.

Any clues how I can diagnose this?

Jason

Well, probably not without re-installing the problem child. It sounds to me from reading this list that there will be another kernel within a month because of all the hard-disk problems upon re-boot. -- _____________________________________ John Andersen

Jason wrote:

On Friday 18 June 2004 03:01, Fred Miller wrote:

...

I've done 4 FRESH installs because the update kernel HANGS during bootup on the file log for /dev/sda1!!! No matter what file system is used, it FAILS! SUSE needs to be MUCH more carefull!

I've had problems with the new kernel shutting down -- it locks up the machine while killing processes before umounting the filesystems. :-(

Just don't get into a panic about it. ;-)

On Friday 18 June 2004 17:44, Brad Bourn wrote:

Running 9.1 pro on GigaByte MB with amd_64 3200+ serial ata drives, nForce chipset, nVidia Fx card

EVERYTHING WORKED

Unfortunetely I had no such luck. Had to go back to the original kernel as supplied on the installation DVD. The boot process halted during 'turning on DMA on /dev/hdc'. Which is a Hitachi 160 Gbyte drive on a SIL3112 Sata controller ! Hope they fix this soon :-(. Would be a good idea when Yast would make an extra entry so you can still boot into your previous 'working' kernel, after upgrading the kernel ! Eric -- Running Suse Linux 9.1 Pro

Joseph Loo wrote:

I had the same problem. It turned out for me any USB devices that were plugged in. If you have any, consider unplugging them.

On Thu, 2004-06-17 at 19:01, Fred Miller wrote:

...

I've done 4 FRESH installs because the update kernel HANGS during bootup on the file log for /dev/sda1!!! No matter what file system is used, it FAILS! SUSE needs to be MUCH more carefull!

Fred

-- Ronald Reagan 1911 - 2004 An American Patriot who hated Communism and Socialism, never brought shame upon himself, his family, his political offices or abused the trust of the American People. We love you and we wonder when another like you or Theodore Roosevelt will arise again.

Worked fine for me............no problems at all and am using a USB Logitech Trackball........ DeskNote Laptop 2.4Ghz Pentium 4 512MB RAM 40GB HD SuSE 9.1 Pro -- Brian Craft Yahoo Instant Messenger ID: bcraft67 AIM: linuxman67 Website: http://userdata.acd.net/javaman67/ Linux Counter id: 97873 Linux......the OS of Choice!

Fred Miller wrote:

On Saturday June 19 2004 7:47 am, Brian Craft wrote: [snip]

...

Worked fine for me............no problems at all and am using a USB Logitech Trackball........

It does vary - seems close to half of us have problems and half don't.

Must be a binary problem. ;-)

On Sunday 20 Jun 2004 03:27, James Knott wrote:

Fred Miller wrote:

...

On Saturday June 19 2004 7:47 am, Brian Craft wrote: [snip]

...

Worked fine for me............no problems at all and am using a USB Logitech Trackball........

It does vary - seems close to half of us have problems and half don't.

Must be a binary problem. ;-)

yea too much essence of GOAT ..:-). -- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan PGN

On Sunday 20 June 2004 10:40, Johan Sch wrote:

On Fri, 18 Jun 2004 18:54:23 -0400 Fred Miller wrote:

...

On Saturday June 19 2004 7:47 am, Brian Craft wrote:

It does vary - seems close to half of us have problems and half don't.

I am of the half it does not work..unable to to boot..it breaks while booting at different places with every reboot. Kingly some suggestions from those in the know..how to fix please. Regards

Did you already try the 'Failsafe' boot menu option? Cheers, Leen

Alle 18:36, domenica 20 giugno 2004, Johan Sch ha scritto:

Yes . I tried various options and went through the drill . reboot . no dice. That update broke my system. Going to re-install after format. Thanks for your reply Regards -- Johan Sch

Why are you reinstalling from scratch? If it is the kernel which is broken, just downgrade it to the one on the cd/dvd. Praise

Johan Sch wrote:

I still run suse 9.0 on my gateway . kernel update . no problem at all.

The same thing happened to me and others on a mandrake 10.0 update . system not useable . had to re-install.

It seems that this kernel 2.6.xxx is a nasty bugger.

Not having enough experience to fix all the hassels . just do a clean sweep.

Thanks for your reply

I've been running 2.6 kernels on SuSE 9.0 since 2.6.0-pre and I've only had one problem with 2.6.3-mm where they added a patch to enable 4KSTACKS and that with the nvidia video driver would reek havoc with HD's, caused a hard lockup and sometimes corrupted files - fixed in later kernels until NVIDIA issues the next driver. Currently running SuSE 9.1 x86 on a P-II 333 laptop and Athlon XP2800+, also x86_64 Acer laptop, all running 2.6.7-mm1. I haven't upgraded the kernel on the Mandrake 10.0 box yet, but 2.6.x has been as stable and probably more so than a few of the 2.4.2x kernels I've come across. I tend to hit kernel problems more so than most as I have always tried and used the latest kernel.org kernels even on my work laptop (backups on the ready, never needed so far). Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer ===== LINUX ONLY USED HERE =====

On Mon, 2004-06-21 at 18:54 -0400, Doug McGarrett wrote:

On Monday 21 June 2004 05:49, Praise wrote:

...

Alle 18:36, domenica 20 giugno 2004, Johan Sch ha scritto:

...

Yes . I tried various options and went through the drill . reboot . no dice. That update broke my system. Going to re-install after format. Thanks for your reply Regards -- Johan Sch

Why are you reinstalling from scratch? If it is the kernel which is broken, just downgrade it to the one on the cd/dvd.

How does one do this without reinstalling?

Boot from CD1 and go into rescue mode. Then mount your filesystems and do a chroot. (I think these days the rescue system does this automatically) Then install the standard kernel rpm from the CD manually. The Repair option might also help, but I am not sure of this. -- Andre Truter | Software Engineer | Registered Linux user #185282 ICQ #40935899 | AIM: trusoftzaf | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~