[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel failure

Go Linux <golinux@yahoo.com> writes:

> No one?  FWIW.  Haven’t had a problem since I posted this several days ago.  Any thoughts?
> ------------------------------------------------
> On Sat, 12/13/14, golinux <golinux@riseup.net> wrote:
>  Subject: Kernel failure
>  To: "Debian User" <debian-user@lists.debian.org>
>  Date: Saturday, December 13, 2014, 1:40 AM
> On squeeze LTS.  Upgraded the kernel 2 days ago.  Everything was going
> OK.  Then out of nowhere I get a kernel failure popup after coming out
> of suspend. Everything seems to be working OK so I've just gone on about
> my business.  But don't want to get bit down the road.  What should I
> do?  This has never happened in the 10 years I've been using Linux so
> I'm a little lost.  Here's the log:
> Kernel failure message 1:
> ------------[ cut here ]------------
> /build/linux-2.6-bBJNRm/linux-2.6-2.6.32/debian/build/source_i386_none/kernel/rcutree.c:277
> rcu_exit_nohz+0x43/0x5d()
> Hardware name: P35-DS3L
> Modules linked in:
> ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19
>   xt_limit xt_tcpudp ipt_LOG
> ata_piix 0000:00:1f.5: setting latency timer to 64
>   ipt_MASQUERADE xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp
> xt_state sco bridge stp bnep rfcomm acpi_cpufreq l2cap bluetooth
> cpufreq_powersave rfkill cpufreq_conservative cpufreq_stats
> cpufreq_userspace ppdev lp binfmt_misc fuse iptable_nat nf_nat
> nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_mangle
> iptable_filter ip_tables x_tables ext4 jbd2 crc16 it87 hwmon_vid
> coretemp loop snd_hda_codec_realtek snd_hda_intel i2c_i801 nvidia(P)
> snd_hda_codec snd_hwdep parport_pc i2c_core processor snd_pcm snd_seq
> snd_timer snd_seq_device evdev parport snd soundcore snd_page_alloc
> pcspkr psmouse serio_raw ext3 jbd mbcache sg sr_mod cdrom sd_mod
> crc_t10dif ata_generic uhci_hcd r8169 mii pata_jmicron thermal ata_piix
> thermal_sys ehci_hcd libata button scsi_mod usbcore nls_base [last
> unloaded: scsi_wait_scan]
> Pid: 0, comm: swapper Tainted: P        W  2.6.32-5-686 #1
> Call Trace:
>   [<c10308fd>] ? warn_slowpath_common+0x5e/0x8a
>   [<c1030933>] ? warn_slowpath_null+0xa/0xc
>   [<c106f5b7>] ? rcu_exit_nohz+0x43/0x5d
>   [<c104f6a5>] ? tick_nohz_restart_sched_tick+0x6d/0x12d
>   [<c1002338>] ? cpu_idle+0x9b/0xa3
> ---[ end trace 150783a4a64aa323 ]---
> Please cc to the above address.

For problems with squeeze lts release, send email to the debian-lts[1]
mailing list.  Given that your system is basically functional, and also
using a proprietary kernel module, it's likely the bug will not be
considered severe enough for a fix in squeeze, but I guess it couldn't
hurt to get their opinion.

[1] https://wiki.debian.org/LTS/FAQ#Who_will_provide_updates_for_LTS.3F


Reply to: