(solved)error in 3.5.3-1 kernel
Posted: Sep 1, 12, 11:46 dark-D
 Status: Contributor
Joined: 27 May 2010
Posts: 68
Location: shadows
Reply Quote
hello, after running the new kernel for a awhile, the system gives an error and switches from gui to a tty like in a kernel panic. if i use ctrl+alt+f7 i can get back to the gui. here is the latest incarnation of the error from /var/log/syslog, i got it 3 times so far, just letting you know.

:: Code ::
Sep  1 20:52:53 hell kernel: ------------[ cut here ]------------
Sep  1 20:52:53 hell kernel: kernel BUG at /home/damentz/src/zen/future/linux-liquorix/debian/build/source_i386_none/mm/uksm.c:4227!
Sep  1 20:52:53 hell kernel: invalid opcode: 0000 [#1] PREEMPT SMP
Sep  1 20:52:53 hell kernel: Modules linked in: xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ip_tables x_tables pppoe pppox cpufreq_stats af_packet ppp_generic slhc arc4 iwl3945 iwlegacy mac80211 cfg80211 r592 memstick r852 sm_common nand nand_ecc nand_bch bch nand_ids mtd snd_hda_codec_conexant i2c_i801 coretemp snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss i915 drm_kms_helper drm i2c_algo_bit snd_pcm snd_page_alloc thinkpad_acpi nvram snd_seq_dummy snd_seq_oss snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd rfkill i2c_core soundcore pcmcia psmouse hid_generic evdev intel_agp microcode yenta_socket pcmcia_rsrc pcmcia_core pcspkr intel_gtt agpgart lpc_ich serio_raw battery video ac button tpm_tis tpm tpm_bios rtc_cmos ext4 crc16 jbd2 mbcache usbhid hid sg sr_mod sd_mod cdrom ata_generic pata_acpi ahci libahci ata_piix libata sdhci_pci sdhci mmc_core firewire_ohci firewire_core crc_itu_t scsi_mod tg3 uhci_hcd ehci_hcd thermal [last unloaded: scsi_wait_scan]
Sep  1 20:52:53 hell kernel:
Sep  1 20:52:53 hell kernel: Pid: 565, comm: uksmd Not tainted 3.5.0-3.dmz.1-liquorix-686 #1 LENOVO 89329WU/89329WU
Sep  1 20:52:53 hell kernel: EIP: 0060:[<c10fe6dd>] EFLAGS: 00010206 CPU: 0
Sep  1 20:52:53 hell kernel: EIP is at uksm_do_scan+0x29fd/0x2d80
Sep  1 20:52:53 hell kernel: EAX: fffffffc EBX: 00000014 ECX: 00000001 EDX: 003fffff
Sep  1 20:52:53 hell kernel: ESI: 00000000 EDI: 00000000 EBP: 00000000 ESP: f2973ed0
Sep  1 20:52:53 hell kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Sep  1 20:52:53 hell kernel: CR0: 8005003b CR2: b9449128 CR3: 0161b000 CR4: 00000790
Sep  1 20:52:53 hell kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
Sep  1 20:52:53 hell kernel: DR6: ffff0ff0 DR7: 00000400
Sep  1 20:52:53 hell kernel: Process uksmd (pid: 565, ti=f2972000 task=f28dfbc0 task.ti=f2972000)
Sep  1 20:52:53 hell kernel: Stack:
Sep  1 20:52:53 hell kernel: c1613180 c160efcc f286ad60 f28dfd80 0103ba03 c10202e8 f28dfbc0 00000004
Sep  1 20:52:53 hell kernel: c1638280 194753d7 00000002 00000036 f28a0000 f28a0000 00000014 f28dfbc0
Sep  1 20:52:53 hell kernel: f2973f4c c10fea60 00000286 f28dfbc0 00000286 1947608b 00000002 c10fea60
Sep  1 20:52:53 hell kernel: Call Trace:
Sep  1 20:52:53 hell kernel: [<c10202e8>] ? smp_apic_timer_interrupt+0x58/0x90
Sep  1 20:52:53 hell kernel: [<c10fea60>] ? uksm_do_scan+0x2d80/0x2d80
Sep  1 20:52:53 hell kernel: [<c10fea60>] ? uksm_do_scan+0x2d80/0x2d80
Sep  1 20:52:53 hell kernel: [<c1042351>] ? del_timer_sync+0x21/0x40
Sep  1 20:52:53 hell kernel: [<c139ba82>] ? schedule_timeout+0x132/0x300
Sep  1 20:52:53 hell kernel: [<c1041100>] ? usleep_range+0x40/0x40
Sep  1 20:52:53 hell kernel: [<c10fea60>] ? uksm_do_scan+0x2d80/0x2d80
Sep  1 20:52:53 hell kernel: [<c10febe5>] ? uksm_scan_thread+0x185/0x200
Sep  1 20:52:53 hell kernel: [<c105ce10>] ? complete+0x40/0x60
Sep  1 20:52:53 hell kernel: [<c10fea60>] ? uksm_do_scan+0x2d80/0x2d80
Sep  1 20:52:53 hell kernel: [<c10520bf>] ? kthread+0x6f/0x80
Sep  1 20:52:53 hell kernel: [<c1052050>] ? kthread_worker_fn+0x160/0x160
Sep  1 20:52:53 hell kernel: [<c139fcbe>] ? kernel_thread_helper+0x6/0xd
Sep  1 20:52:53 hell kernel: Code: 0e 56 c1 e9 c4 e7 ff ff 89 d8 e8 3f d9 f6 ff 84 c0 0f 85 d0 e7 ff ff e9 c2 d6 ff ff c7 05 b4 e9 67 c1 01 00 00 00 e9 83 ea ff ff <0f> 0b 0f 0b 0f 0b e8 1e 9c 29 00 c7 05 b0 f0 67 c1 00 00 00 00
Sep  1 20:52:53 hell kernel: EIP: [<c10fe6dd>] uksm_do_scan+0x29fd/0x2d80 SS:ESP 0068:f2973ed0
Sep  1 20:52:53 hell kernel: ---[ end trace 7a91bb9e4e5f40a1 ]---
Sep  1 20:52:56 hell acpid: client 2611[0:0] has disconnected
Sep  1 20:53:10 hell acpid: client connected from 2611[0:0]
Sep  1 20:53:10 hell acpid: 1 client rule loaded
Sep  1 20:53:12 hell acpid: client 2611[0:0] has disconnected
Sep  1 20:53:13 hell acpid: client connected from 2611[0:0]
Sep  1 20:53:13 hell acpid: 1 client rule loaded


also here is my inxi -b, debian sid btw

:: Code ::
System:    Host: hell Kernel: 3.5.0-3.dmz.1-liquorix-686 i686 (32 bit) Desktop: Fluxbox 1.3.2 Distro: antiX
Machine:   System: LENOVO (portable) product: 89329WU version: ThinkPad R61/R61i
           Mobo: LENOVO model: 89329WU Bios: LENOVO version: 7OETC3WW (2.23 ) date: 05/12/2009
CPU:       Dual core Intel Core2 Duo CPU T5250 (-MCP-) clocked at 1000.00 MHz
Graphics:  Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary)
           X.Org: 1.12.3.902 drivers: intel (unloaded: fbdev,vesa) Resolution: 1280x800@60.0hz
           GLX Renderer: Mesa DRI Intel 965GM x86/MMX/SSE2 GLX Version: 2.1 Mesa 8.0.4
Network:   Card-1: Broadcom NetLink BCM5787M Gigabit Ethernet PCI Express driver: tg3
           Card-2: Intel PRO/Wireless 3945ABG [Golan] Network Connection driver: iwl3945
Drives:    HDD Total Size: 120.0GB (35.4% used)
Info:      Processes: 95 Uptime: 2:41 Memory: 400.8/999.2MB Client: Shell inxi: 1.8.14


< Edited by dark-D :: Sep 17, 12, 11:10 >
Back to top
Posted: Sep 1, 12, 18:20 damentz
 Status: Assistant
Joined: 09 Sep 2008
Posts: 1143
Reply Quote
Thanks for reporting, I'll see if I can get the UKSM authors to look at this trace. In the meantime, I'll push an update with UKSM enabled so no one else runs into this.

This is the "future" branch, so I'm in no particular hurry to update it. You may want to track "main" if you need your system to be reliable until then.
Back to top
Posted: Sep 1, 12, 22:00 dark-D
 Status: Contributor
Joined: 27 May 2010
Posts: 68
Location: shadows
Reply Quote
there is no problem for me. i just wanted to help you if possible. i assume the "risks" when i run the unstable and future repos. and this is my main rig, i don't need reliability on it. that sounded very hilarious, but you get the point. thanks.

edit: using 3.5.3-3 from day of release to current date, no more error. thanks.
Back to top
Display posts from previous:   

All times are GMT - 8 Hours
Contact Us
Hosting: Pair Networks: 0.034
Forum Style © techpatterns.com
info

tech forums