linux-kernel - Re: 2.6.21-rc5 from fc7-rc2 problems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200704181711.05344.lenb@kernel.org>
Date:	Wed, 18 Apr 2007 17:11:04 -0400
From:	Len Brown <lenb@...nel.org>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Stephen.Clark@...lark.us,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...sta.de>,
	Francois Romieu <romieu@...zoreil.com>,
	Tejun Heo <htejun@...il.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: 2.6.21-rc5 from fc7-rc2 problems

On Wednesday 18 April 2007 16:23, Jeff Garzik wrote:
> Len Brown wrote:
> > < Linux version 2.6.20-1.2933.fc6
> > < (brewbuilder@...0-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@...0-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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/