From: Axel Uhl <axel.uhl@gmx.de>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Kernel Bug in ATA or SMART area
Date: Fri, 12 Feb 2010 09:46:03 +0100 [thread overview]
Message-ID: <4B75154B.8030507@gmx.de> (raw)
In-Reply-To: <4B7505CA.60409@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]
Hi Tejun, (Cc list restored),
I don't have a /var/log/boot.msg, only a /var/log/boot. Its contents:
(Nothing has been logged yet.)
Output of cat /proc/interrupts:
CPU0
0: 41922385 XT-PIC-XT timer
1: 10 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
3: 4 XT-PIC-XT
4: 1 XT-PIC-XT
6: 3 XT-PIC-XT floppy
7: 1 XT-PIC-XT
8: 4 XT-PIC-XT rtc
9: 0 XT-PIC-XT acpi
10: 1501691 XT-PIC-XT sata_promise, sata_via,
ehci_hcd:usb1, HDA Intel, eth6
11: 6089136 XT-PIC-XT saa7133[0], saa7133[0], eth5
12: 131 XT-PIC-XT i8042
14: 1570 XT-PIC-XT ide0
15: 1503 XT-PIC-XT ide1
NMI: 0 Non-maskable interrupts
TRM: 0 Thermal event interrupts
MCE: 0 Machine check exceptions
MCP: 559 Machine check polls
ERR: 1
Best,
-- Axel
Tejun Heo wrote:
> Hello,
>
> Can you please restore cc list when you reply?
>
> On 02/12/2010 03:17 PM, Axel Uhl wrote:
>> sorry, I'm not an expert on this, but are you saying the IRQ line is
>> *too* crowded and I'm having a hardware problem, or is this to say that
>> the kernel modules may not correctly handle the high frequency and total
>> number of IRQs from different devices? Is there anything I can do on the
>> hardware / BIOS side? Can I change the IRQ that some of those adapters
>> use somehow to work around the problem?
>
> The hardware, kernel and drivers should be able to handle it fine but
> it's just very unusual to have that many controllers sharing a single
> IRQ line. I have no idea whether it would have anything to do with
> the cause of the issue but it sure makes diagnosing the problem
> harder.
>
> Can you please post /var/log/boot.msg and the output of cat
> /proc/interrupts?
>
> Thanks.
>
--
Find Security Certificate at http://www.axel-uhl.de/cgi-bin/cacert.cgi
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2124 bytes --]
next prev parent reply other threads:[~2010-02-12 8:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 11:10 Axel Uhl
2010-02-11 20:21 ` Maciej Rutecki
2010-02-11 22:18 ` Axel Uhl
2010-02-12 2:32 ` Tejun Heo
[not found] ` <4B74F263.1060709@gmx.de>
[not found] ` <4B7505CA.60409@kernel.org>
2010-02-12 8:46 ` Axel Uhl [this message]
2010-02-17 2:29 ` Tejun Heo
2010-02-17 20:50 ` Axel Uhl
2010-02-18 10:50 ` Mikael Pettersson
2010-02-19 18:53 ` Axel Uhl
2010-02-19 21:03 ` Mikael Pettersson
2010-02-20 8:46 ` Axel Uhl
2010-02-20 12:10 ` Mikael Pettersson
2010-02-20 22:50 ` Axel Uhl
2010-02-20 3:50 ` Tejun Heo
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=4B75154B.8030507@gmx.de \
--to=axel.uhl@gmx.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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
Powered by JetHome