From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 24702] New: Possible bug - crash during IDE interface probing.
Date: Sun, 12 Dec 2010 07:41:36 GMT [thread overview]
Message-ID: <bug-24702-11633@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=24702
Summary: Possible bug - crash during IDE interface probing.
Product: IO/Storage
Version: 2.5
Kernel Version: 2.6.36.2
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: IDE
AssignedTo: io_ide@kernel-bugs.osdl.org
ReportedBy: software+linux-kernel@kd6lvw.ampr.org
Regression: No
With 2.6.36.1, IDE probing worked. Kernel boots.
With 2.6.36.2, IDE probing crashed kernel.
Hardware: AMD Athlon (x86) 32-bit single-core. SiS5513 IDE interface. PC
Chips 810MLR motherboard (from 2002). GCC 4.5.1. [The machine is due for
retirement soon. Its replacement may be ordered before 2010 ends.]
When I upgraded (using the same basic configuration file) from .1 to .2, the .2
kernel repeatedly crashed at the point where it displayed on the screen "found
SiS5513 IDE interface" and listed it's PCI/IRQ/port numbers, but before it
printed any such device (hard drive, cdrom, etc.) found on the interface cable.
Interrupts appear disabled as a keyboard CTRL+ALT+DEL was non-functional, nor
was screen buffer lookback or keyboard LEDs for caps, num, or scroll lock.
Since the kernel initalization never finished, I have no logs. A review of the
changelog for .2 did not yield any change to the IDE driver, but some DMA and
IRQ stuff was changed. It's quite possible that some kernel configuration
setting combinations yield a non-working kernel. However, I saw no differences
that explain such.
Therefore, I must ask first: Is there a bug here? If so, with what?
If not, then where did my configuration go wrong? Thanks.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2010-12-12 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 7:41 bugzilla-daemon [this message]
2010-12-12 12:24 ` [Bug 24702] Possible bug - crash during IDE interface probing bugzilla-daemon
2010-12-12 21:55 ` bugzilla-daemon
2010-12-13 14:13 ` bugzilla-daemon
2010-12-17 8:47 ` bugzilla-daemon
2010-12-17 9:19 ` bugzilla-daemon
2010-12-20 21:11 ` bugzilla-daemon
2010-12-23 2:39 ` bugzilla-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=bug-24702-11633@https.bugzilla.kernel.org/ \
--to=bugzilla-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;
as well as URLs for NNTP newsgroup(s).