From: bugme-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 11943] Boot fails at scsi0:MESH with hde: lost interrupt, AEC6260
Date: Sun, 9 Nov 2008 15:20:06 -0800 (PST) [thread overview]
Message-ID: <20081109232006.5E0AD108056@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-11943-11633@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=11943
------- Comment #19 from eshaffer1@mac.com 2008-11-09 15:20 -------
Unfortunately I am uncertain how to get that output from the "irqpoll" kernel.
I tried $cat /proc/interrupts and got this output (from Live CD no?) :
ubuntu@ubuntu:~$ cat /proc/interrupts
CPU0
16: 14 PMAC-PIC Edge MESH
18: 1 PMAC-PIC Edge PMac
19: 105 PMAC-PIC Edge PMac Output
20: 95 PMAC-PIC Edge PMac Input
21: 5 PMAC-PIC Level pcilynx
22: 0 PMAC-PIC Level radeon@pci:0000:00:10.0
25: 19152 PMAC-PIC Level ide2, ide3
27: 6992 PMAC-PIC Edge ADB
28: 1183341 PMAC-PIC Level ohci_hcd:usb1
29: 7866 PMAC-PIC Edge ide0
32: 71 PMAC-PIC Edge BMAC-txdma
33: 2 PMAC-PIC Edge BMAC-rxdma
42: 71 PMAC-PIC Edge BMAC-misc
BAD: 0
I also tried (beyond hope! :)) $cat /media/disk/proc/interrupts but receive an
error message of cat: /media/disk/proc/interrupts: no such file or directory.
Is it possible that since the "irqpoll" kernel has never completed booting this
file has not yet been written?
Someday I will know more than just enough to be a danger to my system...until
then, I need a little more guidance on this one please.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-11-09 23:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11943-11633@http.bugzilla.kernel.org/>
2008-11-03 12:48 ` [Bug 11943] Boot fails at scsi0:MESH with hde: lost interrupt, AEC6260 bugme-daemon
2008-11-03 12:52 ` bugme-daemon
2008-11-03 18:03 ` bugme-daemon
2008-11-03 18:16 ` bugme-daemon
2008-11-06 23:50 ` bugme-daemon
2008-11-08 3:13 ` bugme-daemon
2008-11-08 3:13 ` bugme-daemon
2008-11-09 16:07 ` bugme-daemon
2008-11-09 16:08 ` bugme-daemon
2008-11-09 16:58 ` bugme-daemon
2008-11-09 19:47 ` bugme-daemon
2008-11-09 19:59 ` bugme-daemon
2008-11-09 21:15 ` bugme-daemon
2008-11-09 21:50 ` bugme-daemon
2008-11-09 22:05 ` bugme-daemon
2008-11-09 22:26 ` bugme-daemon
2008-11-09 22:40 ` bugme-daemon
2008-11-09 23:00 ` bugme-daemon
2008-11-09 23:20 ` bugme-daemon [this message]
2008-11-09 23:45 ` bugme-daemon
2008-11-09 23:52 ` bugme-daemon
2008-11-10 0:10 ` bugme-daemon
2008-11-10 0:42 ` bugme-daemon
2008-11-13 21:17 ` bugme-daemon
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=20081109232006.5E0AD108056@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=linux-ide@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