FS#19263 : [kernel26] 2.6.33.2-1 crash

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#19263 - [kernel26] 2.6.33.2-1 crash

Attached to Project: Arch Linux
Opened by Anonymous Submitter - Tuesday, 27 April 2010, 10:17 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 17 January 2011, 17:35 GMT

Task Type	Bug Report
Category	Upstream Bugs
Status	Closed
Assigned To	Tobias Powalowski (tpowa) Thomas Bächler (brain0)
Architecture	x86_64
Severity	High
Priority	Normal
Reported Version
Due in Version	Undecided
Due Date	Undecided
Percent Complete
Votes	4 Tomas Sironi (sironitomas) (2010-06-24) Daniel Micay (thestinger) (2010-05-14) Maxwell Draven (Ravenman) (2010-05-07) Tomas Mudrunka (harvie) (2010-05-02)
Private	No

Details

Description:

X windows froze up. Couldn't switch to a VT. Couldn't ssh in over network to shut the system down. System is up to date within 24 hours or so. Had to force power it off by holding down power button for 4 seconds. Ran a memtext86 afterwoods, just in case it was faulty RAM. It passed successfully. I've had no trouble with this system since I bought it about 18 months ago.

Additional info:

kernel26 2.6.33.2-1 (x86_64)

I'm not running any binary modules, and never do (nor have since starting to use Linux in 1992 ;-) )

From syslog:

Apr 26 18:04:15 opy kernel: ------------[ cut here ]------------
Apr 26 18:04:15 opy kernel: WARNING: at kernel/mutex.c:207 __mutex_lock_slowpath+0x334/0x370()
Apr 26 18:04:15 opy kernel: Hardware name: OptiPlex 755
Apr 26 18:04:15 opy kernel: Modules linked in: nls_cp437 vfat fat usb_storage radeon ttm drm_kms_helper drm sit tunnel4 serport hidp rfcomm sco bridge stp
llc bnep l2cap crc16 ip6t_LOG nf_conntrack_ipv6 ip6table_filter ip6table_raw ip6_tables xt_comment xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf
_conntrack iptable_filter ip_tables x_tables coretemp fuse pppoe pppox ppp_generic slhc macvlan ip6_tunnel tunnel6 tuner_simple tuner_types tuner msp3400
ipv6 bttv v4l2_common ir_common i2c_algo_bit videobuf_dma_sg videobuf_core btcx_risc tveeprom ir_core dummy snd_hda_codec_analog snd_seq_dummy tun uvcvide
o videodev v4l1_compat v4l2_compat_ioctl32 snd_seq_oss snd_seq_midi_event snd_seq kvm_intel snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_usb_
audio snd_hwdep snd_usb_lib snd_rawmidi snd_seq_device kvm snd_bt87x snd_pcm snd_timer snd soundcore snd_page_alloc btusb bluetooth ppdev rfkill lp i2c_i8
01 i2c_core powermate sr_mod cdrom natsemi parport_pc tpm_tis tpm e1000e msr tpm_bios parport cpuid evdev sg button microcode dcdbas cpufreq_stats cpufreq
_ondemand acpi_cpufreq freq_table processor edd rtc_cmos rtc_core rtc_lib ext3 jbd mbcache raid1 usbhid hid md_mod sd_mod uhci_hcd ahci libata ehci_hcd sc
si_mod usbcore
Apr 26 18:04:15 opy kernel: Pid: 16216, comm: wget Not tainted 2.6.33-ARCH #1
Apr 26 18:04:15 opy kernel: Call Trace:
Apr 26 18:04:15 opy kernel: [<ffffffff81052a08>] warn_slowpath_common+0x78/0xb0
Apr 26 18:04:15 opy kernel: [<ffffffff81052a4f>] warn_slowpath_null+0xf/0x20
Apr 26 18:04:15 opy kernel: [<ffffffff8135bb74>] __mutex_lock_slowpath+0x334/0x370
Apr 26 18:04:15 opy kernel: [<ffffffff812a12e6>] ? sock_aio_read+0x156/0x160
Apr 26 18:04:15 opy kernel: [<ffffffff8135bbc1>] mutex_lock+0x11/0x30
Apr 26 18:04:15 opy kernel: [<ffffffff810dd8c1>] generic_file_aio_write+0x51/0xd0
Apr 26 18:04:15 opy kernel: [<ffffffff81122002>] do_sync_write+0xd2/0x110
Apr 26 18:04:15 opy kernel: [<ffffffff81012399>] ? read_tsc+0x9/0x20
Apr 26 18:04:15 opy kernel: [<ffffffff8107d739>] ? ktime_get_ts+0xa9/0xe0
Apr 26 18:04:15 opy kernel: [<ffffffff8119fcb1>] ? security_file_permission+0x11/0x20
Apr 26 18:04:15 opy kernel: [<ffffffff81122b48>] vfs_write+0xb8/0x1a0
Apr 26 18:04:15 opy kernel: [<ffffffff81122d0c>] sys_write+0x4c/0x80
Apr 26 18:04:15 opy kernel: [<ffffffff81009fc2>] system_call_fastpath+0x16/0x1b
Apr 26 18:04:15 opy kernel: ---[ end trace 8fe4413e98156946 ]---
Apr 26 18:04:15 opy kernel: general protection fault: 0000 [#1] PREEMPT SMP
Apr 26 18:04:15 opy kernel: last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Apr 26 18:04:15 opy kernel: CPU 2
Apr 26 18:04:15 opy kernel: Pid: 5451, comm: xfce4-diskperf- Tainted: G W 2.6.33-ARCH #1 0GM819/OptiPlex 755
Apr 26 18:04:15 opy kernel: RIP: 0010:[<ffffffff811616c8>] [<ffffffff811616c8>] __break_lease+0x128/0x450
Apr 26 18:04:15 opy kernel: RSP: 0018:ffff88013188dcf8 EFLAGS: 00010206
Apr 26 18:04:15 opy kernel: RAX: 0000000000000000 RBX: ffff88012fe39c38 RCX: 56415741e5894855
Apr 26 18:04:15 opy kernel: RDX: ffff88001a13b5f8 RSI: 0000000000000001 RDI: ffff880131848720
Apr 26 18:04:15 opy kernel: RBP: ffff88013188dd88 R08: ffff88013784e3c0 R09: 0000000000000000
Apr 26 18:04:15 opy kernel: R10: 0000000000000000 R11: 2222222222222222 R12: ffff88001a0e94f0
Apr 26 18:04:15 opy kernel: R13: ffff88012fe39c38 R14: 0000000000008001 R15: 0000000000000000
Apr 26 18:04:15 opy kernel: FS: 00007f173cdff880(0000) GS:ffff880005280000(0000) knlGS:0000000000000000
Apr 26 18:04:15 opy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Apr 26 18:04:15 opy kernel: CR2: 00000000021d3000 CR3: 00000001316be000 CR4: 00000000000006e0
Apr 26 18:04:15 opy kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 26 18:04:15 opy kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr 26 18:04:15 opy kernel: Process xfce4-diskperf- (pid: 5451, threadinfo ffff88013188c000, task ffff880131848720)
Apr 26 18:04:15 opy kernel: Stack:
Apr 26 18:04:15 opy kernel: ffff88013188dd08 ffffffff8107b0dc ffff88013188dd38 ffffffff8112bd38
Apr 26 18:04:15 opy kernel: <0> 0000046c00000000 0000000000000024 ffff88001a0e94f0 0000000000008001
Apr 26 18:04:15 opy kernel: <0> ffff88013188dd68 ffffffff8112be4e ffff88013188de58 ffff88001a0e94f0
Apr 26 18:04:15 opy kernel: Call Trace:
Apr 26 18:04:15 opy kernel: [<ffffffff8107b0dc>] ? in_group_p+0x2c/0x30
Apr 26 18:04:15 opy kernel: [<ffffffff8112bd38>] ? acl_permission_check+0x58/0xc0
Apr 26 18:04:15 opy kernel: [<ffffffff8112be4e>] ? generic_permission+0x1e/0xc0
Apr 26 18:04:15 opy kernel: [<ffffffff8112e008>] may_open+0x118/0x150
Apr 26 18:04:15 opy kernel: [<ffffffff81130c80>] do_filp_open+0x7c0/0xd80
Apr 26 18:04:15 opy kernel: [<ffffffff81122112>] ? do_sync_read+0xd2/0x110
Apr 26 18:04:15 opy kernel: [<ffffffff81120144>] do_sys_open+0x64/0x130
Apr 26 18:04:15 opy kernel: [<ffffffff8112023b>] sys_open+0x1b/0x20
Apr 26 18:04:15 opy kernel: [<ffffffff81009fc2>] system_call_fastpath+0x16/0x1b
Apr 26 18:04:15 opy kernel: Code: 44 89 e0 5b 41 5c 41 5d 41 5e 41 5f c9 c3 0f 1f 44 00 00 48 89 d1 31 c0 be 01 00 00 00 65 48 8b 3c 25 00 cc 00 00 eb 09 0f 1f 00 <f6> 41 30 20 74 16 4c 8b 87 90 04 00 00 4c 39 41 28 48 8b 09 0f
Apr 26 18:04:15 opy kernel: RIP [<ffffffff811616c8>] __break_lease+0x128/0x450
Apr 26 18:04:15 opy kernel: RSP <ffff88013188dcf8>
Apr 26 18:04:15 opy kernel: ---[ end trace 8fe4413e98156947 ]---
Apr 26 18:04:15 opy kernel: general protection fault: 0000 [#2] PREEMPT SMP
Apr 26 18:04:15 opy kernel: last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Apr 26 18:04:15 opy kernel: CPU 0
Apr 26 18:04:15 opy kernel: Pid: 5450, comm: xfce4-diskperf- Tainted: G D W 2.6.33-ARCH #1 0GM819/OptiPlex 755
Apr 26 18:04:15 opy kernel: RIP: 0010:[<ffffffff811616c8>] [<ffffffff811616c8>] __break_lease+0x128/0x450
Apr 26 18:04:15 opy kernel: RSP: 0018:ffff880131845cf8 EFLAGS: 00010206
Apr 26 18:04:15 opy kernel: RAX: 0000000000000000 RBX: ffff88012f7eef18 RCX: 56415741e5894855
Apr 26 18:04:15 opy kernel: RDX: ffff88001a13b5f8 RSI: 0000000000000001 RDI: ffff880131848000
Apr 26 18:04:15 opy kernel: RBP: ffff880131845d88 R08: ffff88013784cb00 R09: 0000000000000000
Apr 26 18:04:15 opy kernel: R10: 0000000000000000 R11: 0000000000000246 R12: ffff88001a0e94f0
Apr 26 18:04:15 opy kernel: R13: ffff88012f7eef18 R14: 0000000000008001 R15: 0000000000000000
Apr 26 18:04:15 opy kernel: FS: 00007f960379b880(0000) GS:ffff880005200000(0000) knlGS:0000000000000000
Apr 26 18:04:15 opy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Apr 26 18:04:15 opy kernel: CR2: 00007fc4b6736a18 CR3: 000000013142f000 CR4: 00000000000006f0
Apr 26 18:04:15 opy kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 26 18:04:15 opy kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr 26 18:04:15 opy kernel: Process xfce4-diskperf- (pid: 5450, threadinfo ffff880131844000, task ffff880131848000)
Apr 26 18:04:15 opy kernel: Stack:
Apr 26 18:04:15 opy kernel: ffff880131845d08 ffffffff8107b0dc ffff880131845d38 ffffffff8112bd38
Apr 26 18:04:15 opy kernel: <0> 0000046100000000 0000000000000024 ffff88001a0e94f0 0000000000008001
Apr 26 18:04:15 opy kernel: <0> ffff880131845d68 ffffffff8112be4e ffff880131845e58 ffff88001a0e94f0
Apr 26 18:04:15 opy kernel: Call Trace:
Apr 26 18:04:15 opy kernel: [<ffffffff8107b0dc>] ? in_group_p+0x2c/0x30
Apr 26 18:04:15 opy kernel: [<ffffffff8112bd38>] ? acl_permission_check+0x58/0xc0
Apr 26 18:04:15 opy kernel: [<ffffffff8112be4e>] ? generic_permission+0x1e/0xc0
Apr 26 18:04:15 opy kernel: [<ffffffff8112e008>] may_open+0x118/0x150
Apr 26 18:04:15 opy kernel: [<ffffffff81130c80>] do_filp_open+0x7c0/0xd80
Apr 26 18:04:15 opy kernel: [<ffffffff81122112>] ? do_sync_read+0xd2/0x110
Apr 26 18:04:15 opy kernel: [<ffffffff81120144>] do_sys_open+0x64/0x130
Apr 26 18:04:15 opy kernel: [<ffffffff8112023b>] sys_open+0x1b/0x20
Apr 26 18:04:15 opy kernel: [<ffffffff81009fc2>] system_call_fastpath+0x16/0x1b
Apr 26 18:04:15 opy kernel: Code: 44 89 e0 5b 41 5c 41 5d 41 5e 41 5f c9 c3 0f 1f 44 00 00 48 89 d1 31 c0 be 01 00 00 00 65 48 8b 3c 25 00 cc 00 00 eb 09 0f 1f 00 <f6> 41 30 20 74 16 4c 8b 87 90 04 00 00 4c 39 41 28 48 8b 09 0f
Apr 26 18:04:15 opy kernel: RIP [<ffffffff811616c8>] __break_lease+0x128/0x450
Apr 26 18:04:15 opy kernel: RSP <ffff880131845cf8>
Apr 26 18:04:15 opy kernel: ---[ end trace 8fe4413e98156948 ]---
Apr 26 18:04:18 opy kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
Apr 26 18:04:18 opy kernel: IP: [<ffffffff8135b90b>] __mutex_lock_slowpath+0xcb/0x370
Apr 26 18:04:18 opy kernel: PGD 77eae067 PUD 77eaf067 PMD 0
Apr 26 18:04:18 opy kernel: Oops: 0002 [#3] PREEMPT SMP
Apr 26 18:04:18 opy kernel: last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Apr 26 18:04:18 opy kernel: CPU 3
Apr 26 18:04:18 opy kernel: Pid: 15881, comm: chromium Tainted: G D W 2.6.33-ARCH #1 0GM819/OptiPlex 755
Apr 26 18:04:18 opy kernel: RIP: 0010:[<ffffffff8135b90b>] [<ffffffff8135b90b>] __mutex_lock_slowpath+0xcb/0x370
Apr 26 18:04:18 opy kernel: RSP: 0018:ffff8800bea9ddd8 EFLAGS: 00010096
Apr 26 18:04:18 opy kernel: RAX: 0000000000000000 RBX: ffff880133a52f7c RCX: 0000000000000000
Apr 26 18:04:18 opy kernel: RDX: ffff880133a52f80 RSI: ffff8800bea9ddf8 RDI: ffff880133a52f78
Apr 26 18:04:18 opy kernel: RBP: ffff8800bea9de58 R08: 0000000000000001 R09: 0000000000000001
Apr 26 18:04:18 opy kernel: R10: 0000000000000001 R11: 0000000000000018 R12: ffff880133a52f78
Apr 26 18:04:18 opy kernel: R13: 0000000000000202 R14: ffff880131849560 R15: ffff8800bea9ddf8
Apr 26 18:04:18 opy kernel: FS: 00007fee27181710(0000) GS:ffff8800052c0000(0000) knlGS:0000000000000000
Apr 26 18:04:18 opy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Apr 26 18:04:18 opy kernel: CR2: 0000000000000000 CR3: 00000000be8fe000 CR4: 00000000000006e0
Apr 26 18:04:18 opy kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 26 18:04:18 opy kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr 26 18:04:18 opy kernel: Process chromium (pid: 15881, threadinfo ffff8800bea9c000, task ffff880131849560)
Apr 26 18:04:18 opy kernel: Stack:
Apr 26 18:04:18 opy kernel: ffff8800bea9dee8 ffff880133a52f80 ffff8800bea9de48 ffffffff81159319
Apr 26 18:04:18 opy kernel: <0> ffff880133a52f80 0000000000000000 1111111111111111 ffff8800bea9ddf8
Apr 26 18:04:18 opy kernel: <0> 0000000000000000 0000000000000000 0000000000000000 ffff880133a52f78
Apr 26 18:04:18 opy kernel: Call Trace:
Apr 26 18:04:18 opy kernel: [<ffffffff81159319>] ? ep_send_events_proc+0x69/0x110
Apr 26 18:04:18 opy kernel: [<ffffffff8135bbc1>] mutex_lock+0x11/0x30
Apr 26 18:04:18 opy kernel: [<ffffffff811579c9>] inotify_inode_queue_event+0x49/0x110
Apr 26 18:04:18 opy kernel: [<ffffffff81122e3d>] vfs_read+0xfd/0x1a0
Apr 26 18:04:18 opy kernel: [<ffffffff81122fbc>] sys_read+0x4c/0x80
Apr 26 18:04:18 opy kernel: [<ffffffff81009fc2>] system_call_fastpath+0x16/0x1b
Apr 26 18:04:18 opy kernel: Code: ff 49 8b 56 08 4c 89 fe 4c 89 e7 e8 90 82 d2 ff 49 8b 44 24 10 49 8d 54 24 08 4d 89 7c 24 10 48 89 55 88 48 89 55 a0 48 89 45 a8 <4c> 89 38 c7 45 cc ff ff ff ff 4c 89 75 b0 8b 45 cc 41 87 04 24
Apr 26 18:04:18 opy kernel: RIP [<ffffffff8135b90b>] __mutex_lock_slowpath+0xcb/0x370
Apr 26 18:04:18 opy kernel: RSP <ffff8800bea9ddd8>
Apr 26 18:04:18 opy kernel: CR2: 0000000000000000
Apr 26 18:04:18 opy kernel: ---[ end trace 8fe4413e98156949 ]---
Apr 26 18:04:18 opy kernel: note: chromium[15881] exited with preempt_count 1
Apr 26 18:04:20 opy kernel: general protection fault: 0000 [#4] PREEMPT SMP
Apr 26 18:04:20 opy kernel: last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Apr 26 18:04:20 opy kernel: CPU 1
Apr 26 18:04:20 opy kernel: Pid: 16552, comm: chromium-sandbo Tainted: G D W 2.6.33-ARCH #1 0GM819/OptiPlex 755
Apr 26 18:04:20 opy kernel: RIP: 0010:[<ffffffff811371d4>] [<ffffffff811371d4>] __d_lookup+0x94/0x180
Apr 26 18:04:20 opy kernel: RSP: 0018:ffff880129ed3cf8 EFLAGS: 00010206
Apr 26 18:04:20 opy kernel: RAX: 7f97e1ecf6c2fb35 RBX: 7f97e1ecf6c2fb35 RCX: 0000000000000013
Apr 26 18:04:20 opy kernel: RDX: ffff880129ed3fd8 RSI: ffff880129ed3dc8 RDI: ffff880133804240
Apr 26 18:04:20 opy kernel: RBP: ffff880129ed3d58 R08: 0000000000000005 R09: ffffffff8117b3d0
Apr 26 18:04:20 opy kernel: R10: 0000000000000004 R11: 2222222222222222 R12: 7f97e1ecf6c2fb1d
Apr 26 18:04:20 opy kernel: R13: ffff880133804240 R14: 0000000008604419 R15: ffff880129ed3dc8
Apr 26 18:04:20 opy kernel: FS: 00007ff685ef9700(0000) GS:ffff880005240000(0000) knlGS:0000000000000000
Apr 26 18:04:20 opy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 26 18:04:20 opy kernel: CR2: 0000000001dd9008 CR3: 0000000129f87000 CR4: 00000000000006e0
Apr 26 18:04:20 opy kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 26 18:04:20 opy kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr 26 18:04:20 opy kernel: Process chromium-sandbo (pid: 16552, threadinfo ffff880129ed2000, task ffff8801314ec020)
Apr 26 18:04:20 opy kernel: Stack:
Apr 26 18:04:20 opy kernel: ffff880129ed3db8 ffff880129ed3e65 ffff880129ed3e58 00000005811d4e60
Apr 26 18:04:20 opy kernel: <0> 0000000000000005 ffff880129ed3dc8 ffffffffffffffff 00000000000157a2
Apr 26 18:04:20 opy kernel: <0> ffff880129ed3dc8 ffff880133804240 ffff880133804240 ffff880129ed3dc8
Apr 26 18:04:20 opy kernel: Call Trace:
Apr 26 18:04:20 opy kernel: [<ffffffff811372fc>] d_lookup+0x3c/0x60
Apr 26 18:04:20 opy kernel: [<ffffffff81177877>] proc_fill_cache+0x87/0x170
Apr 26 18:04:20 opy kernel: [<ffffffff81133060>] ? filldir+0x0/0xd0
Apr 26 18:04:20 opy kernel: [<ffffffff8117b3d0>] ? proc_pid_instantiate+0x0/0xc0
Apr 26 18:04:20 opy kernel: [<ffffffff81133060>] ? filldir+0x0/0xd0
Apr 26 18:04:20 opy kernel: [<ffffffff81133060>] ? filldir+0x0/0xd0
Apr 26 18:04:20 opy kernel: [<ffffffff8117bad1>] proc_pid_readdir+0x121/0x1d0
Apr 26 18:04:20 opy kernel: [<ffffffff81133060>] ? filldir+0x0/0xd0
Apr 26 18:04:20 opy kernel: [<ffffffff811772d5>] proc_root_readdir+0x45/0x60
Apr 26 18:04:20 opy kernel: [<ffffffff81133060>] ? filldir+0x0/0xd0
Apr 26 18:04:20 opy kernel: [<ffffffff81133290>] vfs_readdir+0xb0/0xd0
Apr 26 18:04:20 opy kernel: [<ffffffff81077e09>] ? up_read+0x9/0x10
Apr 26 18:04:20 opy kernel: [<ffffffff81133410>] sys_getdents+0x80/0xe0
Apr 26 18:04:20 opy kernel: [<ffffffff8135dfa5>] ? page_fault+0x25/0x30
Apr 26 18:04:20 opy kernel: [<ffffffff81009fc2>] system_call_fastpath+0x16/0x1b
Apr 26 18:04:20 opy kernel: Code: bb 3e 00 83 82 44 e0 ff ff 01 48 8b 18 8b 45 bc 48 85 db 48 89 45 c0 75 0e eb 76 0f 1f 40 00 48 8b 1b 48 85 db 74 6a 4c 8d 63 e8 <48> 8b 03 45 39 74 24 30 0f 18 08 75 e7 4d 39 6c 24 28 75 e0 4d
Apr 26 18:04:20 opy kernel: RIP [<ffffffff811371d4>] __d_lookup+0x94/0x180
Apr 26 18:04:20 opy kernel: RSP <ffff880129ed3cf8>
Apr 26 18:04:20 opy kernel: ---[ end trace 8fe4413e9815694a ]---
Apr 26 18:04:20 opy kernel: note: chromium-sandbo[16552] exited with preempt_count 1
Apr 26 18:21:26 opy kernel: Initializing cgroup subsys cpuset
Apr 26 18:21:26 opy kernel: Initializing cgroup subsys cpu

At 18:04:20 I left it to see if it would recover, as mpd was still audibly playing music, and I fired up my laptop to attempt to ssh into it. As that didn't work, I hard powercycled it at 18:21.

Steps to reproduce:

Normal desktop use, although it acts as a mail server, and firewall i.e. it is directly attached to the Internet. I leave it on 24x7.

This task depends upon

Closed by Andrea Scarpino (BaSh)
Monday, 17 January 2011, 17:35 GMT
Reason for closing: No response
Additional comments about closing: in 5 months

Comments (20)
Related Tasks (0/0)

Comment by Mario Kozjak (archman-cro) - Tuesday, 27 April 2010, 13:39 GMT

Crashed on me today too! It happened when I was watching a clip on youtube with Firefox having 3 other tabs opened.
Same kernel: pacman -Qi kernel26 --> 2.6.33.2-1
Had to poweroff with a laptop power switch.
Using Openbox, latest Firefox.
System up to date (Austrian mirror) (max one day late sync)

Comment by Thomas Dziedzic (tomd123) - Wednesday, 28 April 2010, 14:14 GMT

I believe I was also affected by this crash. It seems to only happen whenever I play fullscreen hulu.com

Comment by Mario Kozjak (archman-cro) - Wednesday, 28 April 2010, 18:20 GMT

I have updated to 2.6.33.3-1 now, so I'll see with that one.

Comment by Jonathan Squirawski (sky) - Thursday, 29 April 2010, 10:04 GMT

I can confirmed it. Same kind of problem with XFS, I can't mount an XFS partition:

The kernel shouldn't have been compiled with gcc 4.5.

kernelbug.txt (3.7 KiB)

Comment by Anonymous Submitter - Thursday, 29 April 2010, 13:54 GMT

I'm up to 2.6.33.3-1 too, I'll also see how that goes. It's fortunate that a crash dump was captured though, as that means the kernel devs can probably track down exactly what caused it.

Comment by Thomas Bächler (brain0) - Thursday, 29 April 2010, 15:48 GMT

Jonathan, the XFS problem is entirely unrelated to this bug, and is probably not caused by gcc 4.5. Open a separate bug report and stop spamming other people's bugs with unrelated problems (I wonder why I have to tell people that all the time recently).

Comment by Jonathan Squirawski (sky) - Friday, 30 April 2010, 07:35 GMT

If you want. Though backtraces of all these kernel bugs seem really similar (related to vfs_read/vfs_write). And I really don't think that between 2.6.33.1 and 2.6.33.3 it could have so many regressions.

But maybe your right too.

Comment by Mario Kozjak (archman-cro) - Thursday, 06 May 2010, 20:22 GMT

Crashed now while I was using firefox again. 2.6.33.3-1.

Comment by Maxwell Draven (Ravenman) - Friday, 07 May 2010, 16:16 GMT

Crashed after kernel upgrade too, in one HP Pavilion ze2000 laptop.

errors.log (2.7 KiB)

everything.log (97.9 KiB)

kernel.log (72.2 KiB)

Comment by Thomas Bächler (brain0) - Friday, 07 May 2010, 16:31 GMT

Frankly, I don't know what to do with those traces. Maxwell, your kernel is tainted (May 2 15:14:38 MiPC kernel: Pid: 3435, comm: xfdesktop Tainted: P 2.6.33-ARCH #1) from the start, can you also reproduce the problem while no proprietary modules are loaded (so that there is no P flag)?

However, Mark doesn't have a tainted kernel, but his traces look slightly different. I can't make any sense of those either though nor can I reproduce any of this.

Comment by Anonymous Submitter - Saturday, 15 May 2010, 02:06 GMT

Thomas, I think it should be reported upstream then. The crashdump info should make it clear to the kernel devs if it is a kernel problem or not.

Unfortunately I've just suffered the same sort of problem again with 2.6.33.3-1.

Comment by Thomas Dziedzic (tomd123) - Sunday, 27 June 2010, 19:02 GMT

what's the status on this with 2.6.34 ?

Comment by Anonymous Submitter - Tuesday, 29 June 2010, 21:36 GMT

I don't know. Did you report it upstream? Did they come back with a diagnosis?

Comment by Thomas Dziedzic (tomd123) - Tuesday, 29 June 2010, 21:58 GMT

I didn't report it, since I'm not experiencing this.

Comment by Anonymous Submitter - Wednesday, 30 June 2010, 10:06 GMT

So you have exactly the same machine I do, and use that machine exactly the way I do, including running the exact same applications I'm running, and clicking the mouse at exactly the same time I am, and sending and receiving the exact network packets that I am?

Surely you see how ridiculous saying that because you haven't encountered it then there is no bug - which is what in effect you're saying? There's a kernel panic message. It's not a hardware fault. If you can't interpret it, then you should escalate it to the people who do - the Linux kernel devs.

I'm guessing you volunteered to maintain this package, which is admirable. However, if you can't or won't do want you've volunteered to do properly, that's worse that not volunteering at all. You've set false expectations for people who'll then rely on you, and wasted their time.

I gave up on this bug report after a week or so of seeing virtually no useful activity and ran up the AUR vanilla kernel package. Now I can report kernel bugs directly to the Linux devs and won't be told talk to your distro's kernel maintainer ... because I've already tried that and got no where.

Comment by Thomas Dziedzic (tomd123) - Wednesday, 30 June 2010, 12:51 GMT

RE: Mark Smith (markzzzsmith)
"So you have exactly the same machine I do, and use that machine exactly the way I do, including running the exact same applications I'm running, and clicking the mouse at exactly the same time I am, and sending and receiving the exact network packets that I am?"
No, what? I never claimed that...

"Surely you see how ridiculous saying that because you haven't encountered it then there is no bug - which is what in effect you're saying? There's a kernel panic message. It's not a hardware fault. If you can't interpret it, then you should escalate it to the people who do - the Linux kernel devs."
Yes, saying this is ridiculous...

"I'm guessing you volunteered to maintain this package, which is admirable. However, if you can't or won't do want you've volunteered to do properly, that's worse that not volunteering at all. You've set false expectations for people who'll then rely on you, and wasted their time."
No, I didn't volunteer to maintain this package, nor did I ever claim I would. In fact I'm talking to you out of good will.
Are you possibly confusing me with someone else?

"I gave up on this bug report after a week or so of seeing virtually no useful activity and ran up the AUR vanilla kernel package. Now I can report kernel bugs directly to the Linux devs and won't be told talk to your distro's kernel maintainer ... because I've already tried that and got no where."
You do realize that the archlinux kernel is completely vanilla right? Giving up on a bug report, especially if you're the original filer, is a good way to ensure that this doesn't get fixed.

Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 30 August 2010, 06:08 GMT

status with 2.6.35.4?

Comment by Mario Kozjak (archman-cro) - Saturday, 25 September 2010, 20:00 GMT

Arch didn't crash on me for at least two months now. Using 2.6.35.5 without ARCH patchset.

Comment by Thomas Dziedzic (tomd123) - Saturday, 25 September 2010, 20:19 GMT

I hate how many patches arch uses, sometimes I wonder why we aren't more vanilla [1]... </sarcasm>

references:
[1] http://repos.archlinux.org/wsvn/packages/kernel26/trunk/

Comment by Thomas Dziedzic (tomd123) - Tuesday, 04 January 2011, 21:41 GMT

status?

	Tasks related to this task (0)

Duplicate tasks of this task (0)

Arch Linux

Arch Linux

FS#19263 - [kernel26] 2.6.33.2-1 crash

Details

Loading...