Hi,
Got this booting 34-mm2. Think the are problems with the ide updates...
UP no preempth. Everything look ok up to the int loop.
Ed Tomlinson
Video mode to be used for restore is f00
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 131056
DMA zone: 4096 pages
Normal zone: 126960 pages
HighMem zone: 0 pages
Building zonelist for node : 0
Kernel command line: auto BOOT_IMAGE=Linux ro root=2103 console=tty0 console=ttyS0,38400 video=matrox:mem:32 idebus=33 profile=1
ide_setup: idebus=33
Initializing CPU#0
Detected 401.003 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 790.52 BogoMIPS
Memory: 514708k/524224k available (1053k kernel code, 9132k reserved, 517k data, 76k init, 0k highmem)
Security Scaffold v1.0.0 initialized
Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Enabling new style K6 write allocation for 511 Mb
CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line)
CPU: L2 Cache: 256K (32 bytes/line)
CPU: AMD-K6(tm) 3D+ Processor stepping 01
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
mtrr: v2.0 (20020519)
PCI: PCI BIOS revision 2.10 entry at 0xfb520, last bus=1
PCI: Using configuration type 1
usb.c: registered new driver usbfs
usb.c: registered new driver hub
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router VIA [1106/0586] at 00:07.0
Starting kswapd
BIO: pool of 256 setup, 14Kb (56 bytes/bio)
biovec: init pool 0, 1 entries, 12 bytes
biovec: init pool 1, 4 entries, 48 bytes
biovec: init pool 2, 16 entries, 192 bytes
biovec: init pool 3, 64 entries, 768 bytes
biovec: init pool 4, 128 entries, 1536 bytes
biovec: init pool 5, 256 entries, 3072 bytes
aio_setup: sizeof(struct page) = 40
Capability LSM initialized
Activating ISA DMA hang workarounds.
Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
pty: 256 Unix98 ptys configured
block request queues:
128 requests per read queue
128 requests per write queue
8 requests per batch
enter congestion at 31
exit congestion at 33
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes
VP_IDE: IDE controller at PCI slot 00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c586b (rev 47) IDE UDMA33 controller on pci00:07.1
ide0: BM-DMA at 0xa000-0xa007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xa008-0xa00f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALLP KA13.6, ATA DISK drive
hda: DMA disabled
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: CD-ROM 50X, ATAPI CD/DVD-ROM drive
hdd: HP COLORADO 20GB, ATAPI TAPE drive
hdc: DMA disabled
hdd: DMA disabled
ide1 at 0x170-0x177,0x376 on irq 15
PDC20267: IDE controller at PCI slot 00:09.0
PCI: Found IRQ 12 for device 00:09.0
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: ROM enabled at 0xeb000000
PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0xbc00-0xbc07, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xbc08-0xbc0f, BIOS settings: hdg:DMA, hdh:pio
hde: QUANTUM FIREBALLP AS40.0, ATA DISK drive
ide2 at 0xac00-0xac07,0xb002 on irq 12
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
On Thu, Sep 12 2002, Ed Tomlinson wrote:
> Hi,
>
> Got this booting 34-mm2. Think the are problems with the ide updates...
> UP no preempth. Everything look ok up to the int loop.
just delete the printk from ide.c:ide_intr(), it's not useful on adapters
with shared interrupts. patch has already been sent to Linus.
feedback on success/problems with 34-mm2 (it seems to include bk patches
up until now?) ide would also be appreciated.
Jens
On September 12, 2002 08:42 am, Jens Axboe wrote:
> On Thu, Sep 12 2002, Ed Tomlinson wrote:
> > Hi,
> >
> > Got this booting 34-mm2. Think the are problems with the ide updates...
> > UP no preempth. Everything look ok up to the int loop.
>
> just delete the printk from ide.c:ide_intr(), it's not useful on adapters
> with shared interrupts. patch has already been sent to Linus.
>
> feedback on success/problems with 34-mm2 (it seems to include bk patches
> up until now?) ide would also be appreciated.
No luck. Without the printk it just sits there. When the printk is enabled there are
hundreds (maybe thousands) of messages.
I also noticed that DMA was disabled on hda. This drive works at UDMA2 without
any problems. The drives on promise controller should be able use support UDMA4
but timeout within 24hours when using it. Degrading to UDMA2 lets me go weeks
with problems (up to 2.4.19-ac2).
Ed Tomlinson
On Thu, Sep 12 2002, Ed Tomlinson wrote:
> On September 12, 2002 08:42 am, Jens Axboe wrote:
> > On Thu, Sep 12 2002, Ed Tomlinson wrote:
> > > Hi,
> > >
> > > Got this booting 34-mm2. Think the are problems with the ide updates...
> > > UP no preempth. Everything look ok up to the int loop.
> >
> > just delete the printk from ide.c:ide_intr(), it's not useful on adapters
> > with shared interrupts. patch has already been sent to Linus.
> >
> > feedback on success/problems with 34-mm2 (it seems to include bk patches
> > up until now?) ide would also be appreciated.
>
> No luck. Without the printk it just sits there. When the printk is
> enabled there are hundreds (maybe thousands) of messages.
"just sits there" how? It stalls a boot? And where? Does
2.4.20-pre5-ac4 work for you?
> I also noticed that DMA was disabled on hda. This drive works at
> UDMA2 without any problems. The drives on promise controller should
> be able use support UDMA4 but timeout within 24hours when using it.
> Degrading to UDMA2 lets me go weeks with problems (up to 2.4.19-ac2).
So I'm thinking that you did get it to boot.
Ed, I'm sorry but your report is woefully inadequate to diagnose
anything :-)
--
Jens Axboe
On September 13, 2002 02:06 am, Jens Axboe wrote:
> On Thu, Sep 12 2002, Ed Tomlinson wrote:
> > On September 12, 2002 08:42 am, Jens Axboe wrote:
> > > On Thu, Sep 12 2002, Ed Tomlinson wrote:
> > > > Hi,
> > > >
> > > > Got this booting 34-mm2. Think the are problems with the ide
> > > > updates... UP no preempth. Everything look ok up to the int loop.
> > >
> > > just delete the printk from ide.c:ide_intr(), it's not useful on
> > > adapters with shared interrupts. patch has already been sent to Linus.
> > >
> > > feedback on success/problems with 34-mm2 (it seems to include bk
> > > patches up until now?) ide would also be appreciated.
> >
> > No luck. Without the printk it just sits there. When the printk is
> > enabled there are hundreds (maybe thousands) of messages.
>
> "just sits there" how? It stalls a boot? And where? Does
It sits at the same point I started getting the unexpected interrupt message.
I waited over five minutes to see if the boot would resume.
> 2.4.20-pre5-ac4 work for you?
I have not built any of the recient ac series - been waiting for a reiserfs patch.
Will try 2.4.20-pre5-ac4 and pre6-acx tonight.
> > I also noticed that DMA was disabled on hda. This drive works at
> > UDMA2 without any problems. The drives on promise controller should
> > be able use support UDMA4 but timeout within 24hours when using it.
> > Degrading to UDMA2 lets me go weeks with problems (up to 2.4.19-ac2).
>
> So I'm thinking that you did get it to boot.
No. The boot stalled. The hda stuff is from the dmseg log on a serial
console. The other comments on general info on long standing promise
issues (hopfully fixed in ac).
> Ed, I'm sorry but your report is woefully inadequate to diagnose
> anything :-)
Realize how anemic this report is. I am willing to get more info on
this - just am not sure what you need or how to get the info. IDE and
the boot sequence is not an area of the kernel I know much about.
Please let me know what would give you the best clues.
Meanwhile I wil try the recient ac(s).
Ed
Hi,
To check if the problem I am seeing is with the port to 2.5 I tried
2.4.20-pre5-ac4 and 2.4.20-pre5-ac6. Both booted correctly.
Now to try 2.5.34+bk without Andrew's mm patch. If that fails what
debugging info would help solve the unexpected interrupt problem?
TIA,
Ed Tomlinson
On September 13, 2002 09:42 pm, Ed Tomlinson wrote:
> Hi,
>
> To check if the problem I am seeing is with the port to 2.5 I tried
> 2.4.20-pre5-ac4 and 2.4.20-pre5-ac6. Both booted correctly.
>
> Now to try 2.5.34+bk without Andrew's mm patch. If that fails what
> debugging info would help solve the unexpected interrupt problem?
to summerize
2.4.20-pre5-ac4 works
2.4.20-pre5-ac5 works
2.5.34-mm1 works (without Jens ide port of pre5-ac4)
2.5.34-mm2 fails with unexpected interrupt loop
2.5.34-bk current fails with unexpected interrupt loop
Removing the printk from ide.c does _not_ cure the problem. The ide
setting between 2.4 and 2.5 were as identical as I can make them.
A failing 2.5 boot gives:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes
VP_IDE: IDE controller at PCI slot 00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c586b (rev 47) IDE UDMA33 controller on pci00:07.1
ide0: BM-DMA at 0xa000-0xa007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xa008-0xa00f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALLP KA13.6, ATA DISK drive
hda: DMA disabled
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: CD-ROM 50X, ATAPI CD/DVD-ROM drive
hdd: HP COLORADO 20GB, ATAPI TAPE drive
hdc: DMA disabled
hdd: DMA disabled
ide1 at 0x170-0x177,0x376 on irq 15
PDC20267: IDE controller at PCI slot 00:09.0
PCI: Found IRQ 12 for device 00:09.0
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: ROM enabled at 0xeb000000
PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0xbc00-0xbc07, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xbc08-0xbc0f, BIOS settings: hdg:DMA, hdh:pio
hde: QUANTUM FIREBALLP AS40.0, ATA DISK drive
ide2 at 0xac00-0xac07,0xb002 on irq 12
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
ide_intr: unexpected interrupt!
....
A working 2.4-pre5-ac4 boot gives:
Sep 13 21:17:50 oscar kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Sep 13 21:17:50 oscar kernel: ide: Assuming 33MHz system bus speed for PIO modes
Sep 13 21:17:50 oscar kernel: VP_IDE: IDE controller at PCI slot 00:07.1
Sep 13 21:17:50 oscar kernel: VP_IDE: chipset revision 6
Sep 13 21:17:50 oscar kernel: VP_IDE: not 100%% native mode: will probe irqs later
Sep 13 21:17:50 oscar kernel: VP_IDE: VIA vt82c586b (rev 47) IDE UDMA33 controller on pci00:07.1
Sep 13 21:17:50 oscar kernel: ide0: BM-DMA at 0xa000-0xa007, BIOS settings: hda:DMA, hdb:DMA
Sep 13 21:17:50 oscar kernel: ide1: BM-DMA at 0xa008-0xa00f, BIOS settings: hdc:DMA, hdd:DMA
Sep 13 21:17:50 oscar kernel: PDC20267: IDE controller at PCI slot 00:09.0
Sep 13 21:17:50 oscar kernel: PCI: Found IRQ 12 for device 00:09.0
Sep 13 21:17:50 oscar kernel: PDC20267: chipset revision 2
Sep 13 21:17:50 oscar kernel: PDC20267: not 100%% native mode: will probe irqs later
Sep 13 21:17:50 oscar kernel: PDC20267: ROM enabled at 0xeb000000
Sep 13 21:17:50 oscar kernel: PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
Sep 13 21:17:50 oscar kernel: ide2: BM-DMA at 0xbc00-0xbc07, BIOS settings: hde:DMA, hdf:pio
Sep 13 21:17:50 oscar kernel: ide3: BM-DMA at 0xbc08-0xbc0f, BIOS settings: hdg:DMA, hdh:pio
Sep 13 21:17:50 oscar kernel: hda: QUANTUM FIREBALLP KA13.6, ATA DISK drive
Sep 13 21:17:50 oscar kernel: hda: DMA disabled
Sep 13 21:17:50 oscar kernel: blk: queue c02a83c0, I/O limit 4095Mb (mask 0xffffffff)
Sep 13 21:17:50 oscar kernel: hdc: CD-ROM 50X, ATAPI CD/DVD-ROM drive
Sep 13 21:17:50 oscar kernel: hdd: HP COLORADO 20GB, ATAPI TAPE drive
Sep 13 21:17:50 oscar kernel: hdc: DMA disabled
Sep 13 21:17:50 oscar kernel: hdd: DMA disabled
Sep 13 21:17:50 oscar kernel: hde: QUANTUM FIREBALLP AS40.0, ATA DISK drive
Sep 13 21:17:50 oscar kernel: blk: queue c02a8ca8, I/O limit 4095Mb (mask 0xffffffff)
Sep 13 21:17:50 oscar kernel: hdg: QUANTUM FIREBALLP AS40.0, ATA DISK drive
Notice that 2.4 orders the boot differently. Wonder if this is significant?
What additional info would help?
Ed Tomlinson
On Fri, Sep 13 2002, Ed Tomlinson wrote:
> On September 13, 2002 09:42 pm, Ed Tomlinson wrote:
> > Hi,
> >
> > To check if the problem I am seeing is with the port to 2.5 I tried
> > 2.4.20-pre5-ac4 and 2.4.20-pre5-ac6. Both booted correctly.
> >
> > Now to try 2.5.34+bk without Andrew's mm patch. If that fails what
> > debugging info would help solve the unexpected interrupt problem?
>
> to summerize
>
> 2.4.20-pre5-ac4 works
> 2.4.20-pre5-ac5 works
> 2.5.34-mm1 works (without Jens ide port of pre5-ac4)
> 2.5.34-mm2 fails with unexpected interrupt loop
> 2.5.34-bk current fails with unexpected interrupt loop
Hmm, I just plopped in a 20267 here and it works perfectly:
PDC20267: IDE controller at PCI slot 00:0c.0
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0xa000-0xa007, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xa008-0xa00f, BIOS settings: hdg:pio, hdh:DMA
hde: IBM-DTLA-307030, ATA DISK drive
ide2 at 0xb400-0xb407,0xb002 on irq 16
hde: host protected area => 1
hde: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63,
UDMA(100)
hde: hde1 hde2 < hde5 >
> Removing the printk from ide.c does _not_ cure the problem. The ide
> setting between 2.4 and 2.5 were as identical as I can make them.
Can you please send me the config settings?
> Notice that 2.4 orders the boot differently. Wonder if this is significant?
That's expected.
--
Jens Axboe
On Sat, 2002-09-14 at 14:36, Jens Axboe wrote:
> > Notice that 2.4 orders the boot differently. Wonder if this is significant?
>
> That's expected.
Not by me. What ordering is changing here ?