From: Nick Levinson <nick_levinson@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: a kernel failure message
Date: Sat, 15 Aug 2009 09:29:51 -0700 (PDT) [thread overview]
Message-ID: <10435.90035.qm@web33501.mail.mud.yahoo.com> (raw)
The following appeared earlier today, after logging into a nonroot account (the only login today) and opening the Firefox 3.0.4 browser; kernel failures were reported on several recent days but I did not report them to you, not knowing the email address at the time (I prefer email over machine-to-machine contact); they did not occur after the clean install of Fedora 10 Linux until recently; and I have not changed the hardware or installed new software in recent days:
* * * * *
Kernel failure message 1:
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xda/0x12d()
NETDEV WATCHDOG: eth1 (orinoco_cs): transmit timed out
Modules linked in: vfat fat usb_storage fuse ipt_MASQUERADE iptable_nat nf_nat sco bridge stp bnep l2cap bluetooth sunrpc ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 dm_multipath uinput orinoco_cs orinoco hermes ppdev dcdbas snd_intel8x0 snd_intel8x0m snd_ac97_codec snd_seq_dummy ac97_bus snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm irda snd_timer crc_ccitt floppy snd soundcore pcspkr joydev snd_page_alloc iTCO_wdt firewire_ohci iTCO_vendor_support firewire_core 3c59x crc_itu_t yenta_socket intel_rng rsrc_nonstatic mii video output parport_pc parport ata_generic pata_acpi sha256_generic cbc aes_i586 aes_generic dm_crypt crypto_blkcipher [last unloaded: microcode]
Pid: 3048, comm: gnome-screensav Not tainted 2.6.27.5-117.fc10.i686 #1
[<c042bb3a>] warn_slowpath+0x4b/0x6c
[<c043a716>] ? __queue_work+0x26/0x2b
[<c043a784>] ? queue_work_on+0x3b/0x46
[<c048a971>] ? virt_to_head_page+0x22/0x2e
[<c050c0d4>] ? queue_flag_clear+0x18/0x54
[<c050c17b>] ? __freed_request+0x6b/0x72
[<c0420940>] ? __enqueue_entity+0xe3/0xeb
[<c06a77cc>] ? _spin_lock_irqsave+0x29/0x30
[<c051bf6e>] ? strlcpy+0x17/0x49
[<c063e554>] dev_watchdog+0xda/0x12d
[<c043495a>] ? mod_timer+0x30/0x34
[<c0635d02>] ? neigh_periodic_timer+0x13f/0x151
[<c04341f5>] run_timer_softirq+0x14b/0x1bb
[<c063e47a>] ? dev_watchdog+0x0/0x12d
[<c063e47a>] ? dev_watchdog+0x0/0x12d
[<c043076f>] __do_softirq+0x84/0x109
[<c04306eb>] ? __do_softirq+0x0/0x109
[<c0405eec>] do_softirq+0x77/0xdb
[<c046417b>] ? handle_level_irq+0x0/0xbe
[<c04303d6>] irq_exit+0x44/0x83
[<c0405e5e>] do_IRQ+0xe7/0xfe
[<c0404654>] common_interrupt+0x28/0x30
=======================
---[ end trace eaf12f13083bf783 ]---
* * * * *
I probably won't report future ones to you unless something indicates a difference or a long pause intervenes.
Thank you.
--
Nick
reply other threads:[~2009-08-15 16:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10435.90035.qm@web33501.mail.mud.yahoo.com \
--to=nick_levinson@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®