On Sun, 2006-06-18 at 10:56 -0400, Ken Schneider wrote:

On Sat, 2006-06-17 at 14:01 -0600, Tom Patton wrote:

...

Just did the latest online kernel update, and now KDM hangs on bootup.

My second GRUB option of kernel -2.6.16.18 still launches KDM and onward without any problem. (I'm not config'd right for SuSE with this kernel, so I mainly by default use the SuSE issued kernel (2.6.11.4-21.11).)

After reading the traffic re SuSE module issues in 10.1, was wondering if this was SuSE induced or perhaps just a defective download...???

YAST reported that it installed the kernel patches OK...

Has anyone else experienced difficulty with the latest 9.3 Online Update?

Just a thought... Do you have a custom ATI or Nvidia driver? If so you will need to rebuild them first before "X" will start.

-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

Ken, you may be right, that was my fear that the new SuSE/Kernel policy broke the driver. Using SuSE-issued driver for Radeon 9200, haven't needed drivers from ATI or GATOS since the 7.x series, I think. X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: SuSE Linux [ELF] SuSE --> Current Operating System: Linux master 2.6.11.4-21.12-default #1 Wed May 10 09:38:20 UTC 2006 i686 Build Date: 27 April 2006 That one worked on all previous updates... X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: SuSE Linux [ELF] SuSE --> Current Operating System: Linux master 2.6.16.18-default #1 Wed May 24 00:11:45 MDT 2006 i686 Build Date: 27 April 2006 and is working now on the latest kernel from kernel.org (but I have other config problems with this one, not X-related).

From console logon, SAX will NOT start, either.

I haven't found any warnings yet to indicate the problem, and while it is hung, I still have ssh access into the system (but not ssh -X). Very strange... I'll keep digging...thanks for your reply! Tom -- 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 Mon, 2006-06-19 at 00:56 +0200, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Saturday 2006-06-17 at 14:01 -0600, Tom Patton wrote:

...

Just did the latest online kernel update, and now KDM hangs on bootup.

My second GRUB option of kernel -2.6.16.18 still launches KDM and onward without any problem. (I'm not config'd right for SuSE with this kernel, so I mainly by default use the SuSE issued kernel (2.6.11.4-21.11).)

After reading the traffic re SuSE module issues in 10.1, was wondering if this was SuSE induced or perhaps just a defective download...???

I'm using that same kernel and version, no issue. Certainly the problem affecting 10.1 has nothing to do with 9.3.

Start in runlevel 3, and try reconfiguring X. Make a backup of /etc/X11/xorg.conf, and run sax. If it fails, use --reinit.

Good suggestion, Carlos, but it didn't work. Sax hangs on a blank screen, after its third announcement of progress... I really don't think it is an X issue, since everything works fine with the 2.6.16.18 kernel, and was working fine in all previous YOU's for 9.3. I did find a couple of kernel oops in dmesg of the update (4-21.12), but haven't had time to track them down. Dmesg of the 2.6.16.18 kernel is clean. When you say you are "using the same kernel"...you _did_ mean you are using 2.6.11.4-21.12, correct? Tom -- 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 Mon, 2006-06-19 at 11:27 +0200, Carlos E. R. wrote:

Did you try with reinit?

yes, "sax2 --reinit"

It's working fine on my system. It would be interesting to know what those oops are saying: you can report them.

Well, Carlos, I'm rather forgetful these days, I guess. A couple weeks ago I updated three SuSE 9.3 pc's at work, and sure enough, they are now the 21.12 kernel version. So that puts to bed the LPGL paranoia that is going around...they are working fine. I'll have to start in earnest tracking this down, and will post the two "oops", now that I know this was a ligitimate failure of some sort. It's really odd, though, that YAST didn't report any problems during the update. Thanks for listening so far, Carlos! Tom -- 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 Tue, 2006-06-20 at 13:43 +0200, Carlos E. R. wrote:

The Monday 2006-06-19 at 21:52 -0600, Tom Patton wrote:

...

I'll have to start in earnest tracking this down, and will post the two "oops", now that I know this was a ligitimate failure of some sort. It's really odd, though, that YAST didn't report any problems during the update.

It must be something specific to that computer. You may try reinstalling the kernel, but knowing what those "oops" were about would give a clue, I suppose.

There was only one Oops this time in init 3... thpnalb@master:~/9x3Diag> cat Oops1.txt Oops: 0000 [#1] Modules linked in: ipt_LOG ipt_limit ipt_pkttype nvram speedstep_lib freq_table thermal processor fan button battery ac nfsd exportfs usbserial snd_pcm_oss snd_mixer_oss snd_seq_midi snd_seq_midi_event snd_seq vmvirtualnic vm_bridge vm_main hypervisor usbhid edd evdev joydev st sr_mod sg cx88_dvb cx8800 v4l1_compat v4l2_common cx8802 mt352 cx88xx i2c_algo_bit sk98lin ir_common btcx_risc tuner uhci_hcd ehci_hcd usbcore tveeprom videodev video_buf_dvb dvb_core i2c_viapro video_buf cx22702 via_agp i2c_core dvb_pll agpgart video1394 ohci1394 raw1394 ieee1394 capability parport_pc lp parport ipt_state ip6t_REJECT ipt_REJECT iptable_mangle iptable_filter ip6table_mangle ip_nat_ftp iptable_nat ip_conntrack_ftp ip_conntrack ip_tables snd_via82xx snd_ac97_codec snd_cmipci gameport snd_pcm snd_page_alloc snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd ip6table_filter ip6_tables soundcore ipv6 dm_mod raid0 reiserfs ide_cd cdrom ide_disk aic7xxx via82cxxx ide_core sata_via libata sd_mod scsi_mod CPU: 0 EIP: 0060:[<c01d2dff>] Tainted: PF U VLI EFLAGS: 00010246 (2.6.11.4-21.12-default) EIP is at strlcpy+0xf/0x50 eax: 00000000 ebx: f205deec ecx: ffffffff edx: 00000000 esi: 00000020 edi: 00000000 ebp: f205dedc esp: f205de78 ds: 007b es: 007b ss: 0068 Process hald (pid: 9407, threadinfo=f205c000 task=f691c080) Stack: 80685600 f9d2b1aa f205dee3 f205dedc f9d2976f f0c04001 f5ef8000 f7fcf5a0 f70d8b60 f9138b60 dfc6bf34 f0c04005 00000006 f205def4 dfc8ecac f205def4 f205df68 80685600 fffffff2 00000000 ec8fe420 f9c692cc f205dedc f205dedc Call Trace: [<f9d2976f>] video_do_ioctl+0x2df/0x820 [cx8800] [<f9138b60>] xattr_lookup_poison+0x0/0x90 [reiserfs] [<f9c692cc>] video_usercopy+0x6c/0x140 [videodev] [<c01508af>] dentry_open+0xcf/0x1b0 [<f9d29cb0>] video_ioctl+0x0/0x20 [cx8800] [<f9d29cbe>] video_ioctl+0xe/0x20 [cx8800] [<f9d29490>] video_do_ioctl+0x0/0x820 [cx8800] [<c01612a4>] do_ioctl+0x34/0x60 [<c0161445>] vfs_ioctl+0x55/0x1c0 [<c01615f0>] sys_ioctl+0x40/0x70 [<c0102c69>] sysenter_past_esp+0x52/0x79 Code: 31 c0 81 e2 ff 00 00 00 88 c8 5b 29 d0 5e 5f 5d c3 8d 74 26 00 8d bc 27 00 00 00 00 55 57 89 d7 56 89 ce 53 83 c9 ff 89 c3 31 c0 <f2> ae f7 d1 49 89 cd 85 f6 74 23 89 c8 39 f1 72 03 8d 46 ff 89 I'm thinking I should back up to the saved vmlinuz 21.11 and if that works, do another YOU. Thanks, Tom -- 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 Tuesday 20 June 2006 14:43, Tom Patton wrote:

Modules linked in: [...] vmvirtualnic vm_bridge vm_main hypervisor

EIP: 0060:[<c01d2dff>] Tainted: PF U VLI

You have modules which are non-GPL (P), forced to load (F) and unsupported (U). At first glance in that list, the above were the most likely suspects. They are from the parallels virtual machine, I believe. Try booting without it, and see if a) you get a system that isn't tainted, and b) if it still hangs without it -- 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 Wed, 2006-06-21 at 21:57 +0200, Anders Johansson wrote:

On Tuesday 20 June 2006 14:43, Tom Patton wrote: You have modules which are non-GPL (P), forced to load (F) and unsupported (U). At first glance in that list, the above were the most likely suspects. They are from the parallels virtual machine, I believe.

Try booting without it, and see if a) you get a system that isn't tainted, and b) if it still hangs without it

Good call, Anders, without parallels, system is not tainted, and still hangs in blank screen as X starts... X works fine in this kernel still: Linux master 2.6.16.18-default #1 Wed May 24 00:11:45 MDT 2006 i686 athlon i386 GNU/Linux The only other diff from the previous update to 21.11 to this 21.12 problem was the addition of a pcHDTV card, which sent me in the direction of getting the newer kernel from kernel.org. Note the cx8800 modules, they are for the pcHDTV card. (My best bet is probably to continue getting that configured fully for SuSE...but this problem bugs me mentally, ya know???) Here's the Oops without parallels: Oops: 0000 [#1] Modules linked in: ipt_LOG ipt_limit ipt_pkttype speedstep_lib freq_table thermal processor fan button battery ac nfsd exportfs nvram usbhid edd evdev joydev st sr_mod sg usbserial snd_pcm_oss snd_mixer_oss snd_seq_midi snd_seq_midi_event snd_seq cx88_dvb cx8800 v4l1_compat v4l2_common cx8802 mt352 cx88xx i2c_algo_bit ir_common btcx_risc tuner via_agp agpgart sk98lin ehci_hcd i2c_viapro tveeprom videodev video_buf_dvb dvb_core video_buf cx22702 i2c_core uhci_hcd usbcore dvb_pll video1394 ohci1394 raw1394 ieee1394 capability ipt_state ip6t_REJECT ipt_REJECT iptable_mangle iptable_filter parport_pc lp parport ip6table_mangle ip_nat_ftp iptable_nat ip_conntrack_ftp ip_conntrack ip_tables ip6table_filter ip6_tables ipv6 snd_via82xx snd_ac97_codec snd_cmipci gameport snd_pcm snd_page_alloc snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore dm_mod raid0 reiserfs ide_cd cdrom ide_disk aic7xxx via82cxxx ide_core sata_via libata sd_mod scsi_mod CPU: 0 EIP: 0060:[<c01d2dff>] Not tainted VLI EFLAGS: 00010246 (2.6.11.4-21.12-default) EIP is at strlcpy+0xf/0x50 eax: 00000000 ebx: f3f7beec ecx: ffffffff edx: 00000000 esi: 00000020 edi: 00000000 ebp: f3f7bedc esp: f3f7be78 ds: 007b es: 007b ss: 0068 Process hald (pid: 9278, threadinfo=f3f7a000 task=f660e540) Stack: 80685600 f9d331aa f3f7bee3 f3f7bedc f9d3176f ee7c7001 f2558400 ee63c8a0 f7e1eb60 f9138b60 dfc67054 ee7c7005 00000006 f3f7bef4 dfc8aa8c f3f7bef4 f3f7bf68 80685600 fffffff2 00000000 f7e617e0 f9c7f2cc f3f7bedc f3f7bedc Call Trace: [<f9d3176f>] video_do_ioctl+0x2df/0x820 [cx8800] [<f9138b60>] xattr_lookup_poison+0x0/0x90 [reiserfs] [<f9c7f2cc>] video_usercopy+0x6c/0x140 [videodev] [<c01508af>] dentry_open+0xcf/0x1b0 [<f9d31cb0>] video_ioctl+0x0/0x20 [cx8800] [<f9d31cbe>] video_ioctl+0xe/0x20 [cx8800] [<f9d31490>] video_do_ioctl+0x0/0x820 [cx8800] [<c01612a4>] do_ioctl+0x34/0x60 [<c0161445>] vfs_ioctl+0x55/0x1c0 [<c01615f0>] sys_ioctl+0x40/0x70 [<c0102c69>] sysenter_past_esp+0x52/0x79 Code: 31 c0 81 e2 ff 00 00 00 88 c8 5b 29 d0 5e 5f 5d c3 8d 74 26 00 8d bc 27 00 00 00 00 55 57 89 d7 56 89 ce 53 83 c9 ff 89 c3 31 c0 <f2> ae f7 d1 49 89 cd 85 f6 74 23 89 c8 39 f1 72 03 8d 46 ff 89 Thanks for your help, Tom -- 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 Thu, 2006-06-22 at 16:37 +0200, Anders Johansson wrote:

On Thu, 2006-06-22 at 08:19 -0600, Tom Patton wrote:

...

Good call, Anders, without parallels, system is not tainted, and still hangs in blank screen as X starts...

OK, since you get the oops with an untainted kernel, file a bug report for it in http://bugzilla.novell.com and include the oops message in it.

Also, when you create the bug report, run

hwinfo > hwinfo.txt

and attach it to the bug report.

Anders, howdy! I just got back to this project, and it looks as tho bugzilla is only accepting 10.x issues now. There is no class for 9.3 reports. I have the oops and hwinfo.tar.gz...and no where to send them! Suggestions?...or do I need new glasses? ;-) YOU has never failed me in all these years, so I did not create a backup of the 21.11 kernel/symmap/etc. Do you know a process to revert to the 21.11 kernel? I've never "un-patched" a patch, and haven't found any backup YOU may have made, either. Thanks again, Tom -- 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 Mon, 2006-06-26 at 00:52 +0200, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Sunday 2006-06-25 at 09:14 -0600, Tom Patton wrote:

...

Anders, howdy! I just got back to this project, and it looks as tho bugzilla is only accepting 10.x issues now. There is no class for 9.3 reports. I have the oops and hwinfo.tar.gz...and no where to send them!

Before this bugzilla thing, there was a feedback page where these thing were reported.

Bugzilla is slick, and Anders re-directed it to the proper 9.3 section for me. Don't know why, but the only options for me were the 10-series.

...

YOU has never failed me in all these years, so I did not create a backup of the 21.11 kernel/symmap/etc. Do you know a process to revert to the 21.11 kernel? I've never "un-patched" a patch, and haven't found any backup YOU may have made, either.

Unless you told YOU to delete rpms after install, you will have a copy in /var/lib/YaST2/you/mnt/i386/update/9.3/rpm/i586/kernel-default-2.6.11.4-21.11.i586.rpm

I considered doing that, but thought they were "patch" rpm's. I have them back to x21.7, actually. Looking at the size of them, perhaps you are correct, and they are complete.

Just install it manually, using rpm --oldpackage or --force perhaps. Notice that it is several files: -default, -default-nongpl, kernel-sources (or -smp or whatever).

Cool, I think I'll try that. Thanks, Carlos.

- -- Tom

-- 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