From: Stephen Clark <Stephen.Clark@seclark.us>
To: Len Brown <lenb@kernel.org>
Cc: Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>,
Francois Romieu <romieu@fr.zoreil.com>,
Tejun Heo <htejun@gmail.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.6.21-rc5 from fc7-rc2 problems
Date: Thu, 19 Apr 2007 08:07:37 -0400 [thread overview]
Message-ID: <46275B89.5010604@seclark.us> (raw)
In-Reply-To: <200704181711.05344.lenb@kernel.org>
Len Brown wrote:
>On Wednesday 18 April 2007 16:23, Jeff Garzik wrote:
>
>
>>Len Brown wrote:
>>
>>
>>>< Linux version 2.6.20-1.2933.fc6
>>>< (brewbuilder@hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20070105
>>>< (Red Hat 4.1.1-51)) #1 SMP Mon Mar 19 11:38:26 EDT 2007
>>>---
>>>
>>>
>>>>Linux version 2.6.20-1.3023.fc7
>>>>(brewbuilder@ls20-bc1-13.build.redhat.com) (gcc version 4.1.2 20070317
>>>>(Red Hat 4.1.2-5)) #1 SMP Sun Mar 25 22:12:02 EDT 2007
>>>>
>>>>
>>>I agree that the fc7 version string looks strange, because
>>>there are other things in the fc7 dmesg which are clearly from 2.6.21,
>>>such as this:
>>>
>>>< ACPI: Core revision 20060707
>>>---
>>>
>>>
>>>>ACPI: Core revision 20070126
>>>>
>>>>
>>>Perhaps you can try building a kernel.org 2.6.21 kernel and running
>>>it on your FC6 install?
>>>
>>>The ALI15X3 stuff exists only in the working FC6 dmesg:
>>>
>>>< Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
>>>< ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
>>>< ALI15X3: IDE controller at PCI slot 0000:00:0f.0
>>>< ACPI: Unable to derive IRQ for device 0000:00:0f.0
>>>< ACPI: PCI Interrupt 0000:00:0f.0[A]: no GSI
>>>< ALI15X3: chipset revision 195
>>>< ALI15X3: not 100% native mode: will probe irqs later
>>>< ide0: BM-DMA at 0x1000-0x1007, BIOS settings: hda:DMA, hdb:pio
>>>< ide1: BM-DMA at 0x1008-0x100f, BIOS settings: hdc:DMA, hdd:pio
>>>< Probing IDE interface ide0...
>>>< hda: HITACHI_DK23CA-20, ATA DISK drive
>>>< ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>>>< Probing IDE interface ide1...
>>>< hdc: MATSHITADVD-ROM SR-8175, ATAPI CD/DVD-ROM drive
>>>< ide1 at 0x170-0x177,0x376 on irq 15
>>>< Probing IDE interface ide2...
>>>< Probing IDE interface ide3...
>>>< Probing IDE interface ide4...
>>>< Probing IDE interface ide5...
>>>< hda: max request size: 128KiB
>>>< hda: 39070080 sectors (20003 MB) w/2048KiB Cache, CHS=38760/16/63, UDMA(66)
>>>< hda: cache flushes not supported
>>>< hda: hda1 hda2
>>>< ide-floppy driver 0.99.newide
>>>
>>>FC7 looks like it is using libata instead:
>>>-Len
>>>
>>>
>>>
>>>>SCSI subsystem initialized
>>>>libata version 2.20 loaded.
>>>>ACPI: Unable to derive IRQ for device 0000:00:0f.0
>>>>ACPI: PCI Interrupt 0000:00:0f.0[A]: no GSI
>>>>ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x00011000
>>>>irq 14
>>>>ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x00011008
>>>>irq 15
>>>>scsi0 : pata_ali
>>>>PM: Adding info for No Bus:host0
>>>>ata1.00: ATA-5: HITACHI_DK23CA-20, 00H1A0A3, max UDMA/100 <========
>>>>drive can do 100
>>>>ata1.00: 39070080 sectors, multi 16: LBA
>>>>ata1.00: configured for UDMA/33 <=============== configured as 33
>>>>scsi1 : pata_ali
>>>>PM: Adding info for No Bus:host1
>>>>ata2.00: ATAPI, max UDMA/33 <=== cd can't be read now
>>>>ata2.00: configured for UDMA/33
>>>>PM: Adding info for No Bus:target0:0:0
>>>>scsi 0:0:0:0: Direct-Access ATA HITACHI_DK23CA-2 00H1 PQ: 0 ANSI: 5
>>>>PM: Adding info for scsi:0:0:0:0
>>>>PM: Adding info for No Bus:target1:0:0
>>>>ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>>>>ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in
>>>> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
>>>>ata2: soft resetting port
>>>>
>>>>
>>It looks like interrupts are not being delivered?
>>
>>
>
>Dunno, both 2.6.20 and 2.6.21 say they're looking on IRQ14 and IRQ15.
>ACPI isn't involved at all with those IRQs, as it couldn't find any info
>for 0000:00:0f.0[A] and thus the legacy hard-coding for IDE must rule the day.
>
>Is it possible to configure 2.6.21 with the driver that was running in 2.6.20?
>If yes, and that works, then we know we didn't somehow otherwise break interrupts.
>
>-Len
>
>
>
These results are from the livecd from FC7-rc2, Chuck Ebbert said a new
one is soon to be released.
Let's see what the results are for this upcoming release.
Thanks,
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
next prev parent reply other threads:[~2007-04-19 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 20:14 2.6.21-rc5 from fc7-rc2 problems Stephen Clark
2007-03-31 20:46 ` Andrew Morton
2007-03-31 21:02 ` Adrian Bunk
2007-04-01 0:27 ` Stephen Clark
2007-04-01 18:03 ` Stephen Clark
2007-04-18 20:12 ` Len Brown
2007-04-18 20:23 ` Jeff Garzik
2007-04-18 20:50 ` Alan Cox
2007-04-19 12:04 ` Stephen Clark
2007-04-19 12:09 ` Alan Cox
2007-04-18 21:11 ` Len Brown
2007-04-19 12:07 ` Stephen Clark [this message]
2007-04-18 20:25 ` Chuck Ebbert
2007-04-18 20:42 ` Stephen Clark
2007-04-18 20:52 ` Chuck Ebbert
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=46275B89.5010604@seclark.us \
--to=stephen.clark@seclark.us \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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