From: Grissiom <chaos.proton@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel warning from latest 2.6.28-gitX
Date: Sun, 4 Jan 2009 08:55:47 +0800 [thread overview]
Message-ID: <a0adeea50901031655x3323e1fex302d0671cfa82967@mail.gmail.com> (raw)
Yes, maybe I have the same problem, here is a snippet of dmesg:
[ 0.728735] Probing IDE interface ide0...
[ 1.430414] hda: HL-DT-ST DVD+/-RW GSA-T11N, ATAPI CD/DVD-ROM drive
[ 1.760120] hda: host max PIO4 wanted PIO255(auto-tune) selected
PIO4
[ 1.760946] hda: UDMA/33 mode selected
[ 1.773525] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[ 1.789149] ide-cd driver 5.00
[ 1.802700] ide-cd: hda: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive,
2048kB Cache
[ 1.814860] Uniform CD-ROM driver Revision: 3.20
[ 1.828677] ------------[ cut here ]------------
[ 1.831992] WARNING: at kernel/lockdep.c:2197
trace_hardirqs_on_caller+0x134/0x1a0()
[ 1.831992] Hardware name: Inspiron 1501
[ 1.831992] Modules linked in:
[ 1.831992] Pid: 0, comm: swapper Not tainted
2.6.28-g14-rfkill-nophy-ledon-05692-g7d3b56b #57
[ 1.831992] Call Trace:
[ 1.831992] [<c012a049>] warn_slowpath+0x99/0xc0
[ 1.831992] [<c0140030>] posix_cpu_timer_set+0x3e0/0x410
[ 1.831992] [<c0104f5a>] dump_trace+0x6a/0xb0
[ 1.831992] [<c014e83a>] validate_chain+0x41a/0x11a0
[ 1.831992] [<c014f853>] __lock_acquire+0x293/0xa20
[ 1.831992] [<c014f853>] __lock_acquire+0x293/0xa20
[ 1.831992] [<c014e83a>] validate_chain+0x41a/0x11a0
[ 1.831992] [<c014e83a>] validate_chain+0x41a/0x11a0
[ 1.831992] [<c04d7de0>] _spin_unlock_irq+0x20/0x40
[ 1.831992] [<c014dc84>] trace_hardirqs_on_caller+0x134/0x1a0
[ 1.831992] [<c04d7de0>] _spin_unlock_irq+0x20/0x40
[ 1.831992] [<c0322280>] do_ide_request+0x40/0x570
[ 1.831992] [<c014f853>] __lock_acquire+0x293/0xa20
[ 1.831992] [<c04d7a4b>] _spin_lock_irqsave+0x4b/0x60
[ 1.831992] [<c0254435>] blk_start_queueing+0x15/0x30
[ 1.831992] [<c03219ea>] ide_do_drive_cmd+0x4a/0x70
[ 1.831992] [<c032d4c6>] cdrom_decode_status+0x116/0x380
[ 1.831992] [<c032dd40>] cdrom_newpc_intr+0x0/0x680
[ 1.831992] [<c032dd83>] cdrom_newpc_intr+0x43/0x680
[ 1.831992] [<c032dd40>] cdrom_newpc_intr+0x0/0x680
[ 1.831992] [<c0321b94>] ide_intr+0x134/0x1b0
[ 1.831992] [<c01696b0>] handle_IRQ_event+0x20/0x50
[ 1.831992] [<c016b365>] handle_edge_irq+0xb5/0x120
[ 1.831992] [<c0104dc8>] do_IRQ+0x48/0x90
[ 1.831992] [<c02688a4>] trace_hardirqs_off_thunk+0xc/0x18
[ 1.831992] [<c01039ac>] common_interrupt+0x2c/0x34
[ 1.831992] [<c01091ed>] default_idle+0x3d/0x60
[ 1.831992] [<c01093f3>] c1e_idle+0x93/0x110
[ 1.831992] [<c0101c8b>] cpu_idle+0x6b/0xd0
[ 1.831992] ---[ end trace 5a56406b278561cb ]---
[ 2.204724] Driver 'sd' needs updating - please use bus_type methods
--
Cheers,
Grissiom
next reply other threads:[~2009-01-04 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 0:55 Grissiom [this message]
2009-01-04 15:14 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2009-01-05 16:51 Larry Finger
2009-01-03 3:24 Larry Finger
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=a0adeea50901031655x3323e1fex302d0671cfa82967@mail.gmail.com \
--to=chaos.proton@gmail.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®