Bug 141023 - Kernel Ooops when showing textmode console login
Summary: Kernel Ooops when showing textmode console login
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: x86-64 SuSE Linux 10.0
: P5 - None : Critical
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-25 11:52 UTC by Kurt Knopf
Modified: 2006-03-20 00:43 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
/var/log/messages showing the kernel oops (23.53 KB, text/plain)
2005-12-25 11:53 UTC, Kurt Knopf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Knopf 2005-12-25 11:52:45 UTC
Hi,

today I started my SuSE 10.0 server and it booted til the login prompt (console mode) where no keyboard input was accepted. Another machine couldn't reach the server either so I rebooted the server which started normally now and found the attached error Oops in /var/log/messages. 
The machine is a Asus PSCH-L with an Intel Pentium 4 2.80GHz and 1GB RAM.
This kernel oops never happened before and the machine usually runs 24h.
Comment 1 Kurt Knopf 2005-12-25 11:53:13 UTC
Created attachment 61763 [details]
/var/log/messages showing the kernel oops
Comment 2 Olaf Kirch 2006-01-02 09:18:56 UTC
Hm, this looks like memory corruption. Please try and run memtest on
this machine for at least 6-12 hours to make sure your RAM is okay.
Comment 3 Kurt Knopf 2006-01-04 11:46:07 UTC
I run memtest for 10hrs, 27 passes and got 0 errors.

Looks like something else might be responsible for the problem.
Comment 4 Kurt Knopf 2006-01-12 18:45:31 UTC
Today I got the same problem with the following info in /var/log/messages:

Jan 12 15:09:35 igelserver kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000004
Jan 12 15:09:35 igelserver kernel:  printing eip:
Jan 12 15:09:35 igelserver kernel: c0158c46
Jan 12 15:09:35 igelserver kernel: *pde = 00000000
Jan 12 15:09:35 igelserver kernel: Oops: 0002 [#1]
Jan 12 15:09:35 igelserver kernel: SMP
Jan 12 15:09:35 igelserver kernel: Modules linked in: ipt_MASQUERADE ipt_TCPMSS ipt_state nls_utf8 iptable_nat ip_conntrack ipta
ble_filter ip_tables hfsplus vfat fat subfs speedstep_lib freq_table pppoe pppox ppp_generic button battery af_packet ac ipv6 tu
n edd capidrv fcpci crc_ccitt isdn slhc ne2k_pci 8390 e1000 i2c_i801 ehci_hcd uhci_hcd intel_agp agpgart shpchp pci_hotplug gene
ric i8xx_tco usbcore capi capifs kernelcapi w83627hf i2c_sensor i2c_isa i2c_core parport_pc lp parport dm_mod reiserfs fan therm
al processor sata_promise libata sg 3w_xxxx ide_cd cdrom piix sd_mod scsi_mod ide_disk ide_core
Jan 12 15:09:35 igelserver kernel: CPU:    1
Jan 12 15:09:35 igelserver kernel: EIP:    0060:[<c0158c46>]    Tainted: P     U VLI
Jan 12 15:09:35 igelserver kernel: EFLAGS: 00010006   (2.6.13-15.7-smp)
Jan 12 15:09:35 igelserver kernel: EIP is at free_block+0x76/0x100
Jan 12 15:09:35 igelserver kernel: eax: 00000000   ebx: f5848000   ecx: f5848680   edx: 00000000
Jan 12 15:09:35 igelserver kernel: esi: c1b13c80   edi: 00000000   ebp: 00000005   esp: dfe57f20
Jan 12 15:09:35 igelserver kernel: ds: 007b   es: 007b   ss: 0068
Jan 12 15:09:35 igelserver kernel: Process events/1 (pid: 7, threadinfo=dfe56000 task=dfe41a60)
Jan 12 15:09:35 igelserver kernel: Stack: f7fea990 f7fea990 f7fea980 00000005 c1b13c80 c015940e 00000206 c1b13c80
Jan 12 15:09:35 igelserver kernel:        c1b13d70 00000000 c01594e1 00000003 c1b13d40 00000206 c18111a4 dfe46080
Jan 12 15:09:35 igelserver kernel:        00000000 c01374d2 00000000 00000000 2f2e760a dfe4608c dfe46094 dfe460a0
Jan 12 15:09:35 igelserver kernel: Call Trace:
Jan 12 15:09:35 igelserver kernel:  [<c015940e>] drain_array_locked+0x6e/0xc0
Jan 12 15:09:35 igelserver kernel:  [<c01594e1>] cache_reap+0x81/0x1d0
Jan 12 15:09:35 igelserver kernel:  [<c01374d2>] worker_thread+0x182/0x240
Jan 12 15:09:35 igelserver kernel:  [<c0159460>] cache_reap+0x0/0x1d0
Jan 12 15:09:35 igelserver kernel:  [<c0120cd0>] default_wake_function+0x0/0x10
Jan 12 15:09:35 igelserver kernel:  [<c0137350>] worker_thread+0x0/0x240
Jan 12 15:09:35 igelserver kernel:  [<c013bb9c>] kthread+0xac/0xb0
Jan 12 15:09:35 igelserver kernel:  [<c013baf0>] kthread+0x0/0xb0
Jan 12 15:09:35 igelserver kernel:  [<c01024c5>] kernel_thread_helper+0x5/0x10
Jan 12 15:09:35 igelserver kernel: Code: 00 47 39 fd 0f 84 7b 00 00 00 8b 04 24 8b 15 10 ba 48 c0 8b 0c b8 8d 81 00 00 00 40 c1
e8 0c c1 e0 05 8b 5c 10 1c 8b 13 8b 43 04 <89> 42 04 89 10 31 d2 8b 43 0c c7 03 00 01 10 00 c7 43 04 00 02
Comment 5 Greg Kroah-Hartman 2006-01-12 18:58:00 UTC
Can you duplicate this when you have not loaded a non-supported driver in the kernel?
Comment 6 Kurt Knopf 2006-01-12 20:08:58 UTC
I did not install any additional kernel module. Which module is not supported?

The problem appeared for the first time after the last official kernel patches available through Yast.
Comment 7 Greg Kroah-Hartman 2006-01-12 21:29:36 UTC
I do not know which one, but your kernel oops reports that there was one
loaded.  Have you loaded the nvidia or ati kernel drivers in the past and 
then unloaded them?
Comment 8 Kurt Knopf 2006-01-12 21:55:29 UTC
No. This machine runs in textmode only and I never installed any graphics card driver.
Comment 9 Lars Marowsky-Bree 2006-01-17 10:42:07 UTC
Have you tried running an update kernel yet? The most recent kernel of the day from ftp.suse.com/pub/projects/kernel/kotd/ might also help solve this problem for you.

(I'm sorry I don't have anything more concrete to recommend, because the bug seems rather sporadic... Even if memtest doesn't find anything, it still might be memory corruption because the kernel exercises different access patterns. Been there with my laptop myself.)
Comment 10 Chris L Mason 2006-03-20 00:43:16 UTC
No comments in quite a long time.  Please reopen this bug if you are still having problems.