>> >I have some TRL-DLS here (P-III). They have dual AIC onboard which
are
>> not
>> >recognised under 2.4.24 but work flawlessly with ACPI in 2.4.23.
>>
>> Are you sure? You seems to want to say this is a regression.
>
>Yes. That is exactly what happened.
>
>2.4.23 works flawlessly
>2.4.24 does not recognise both onboard aic
Since you are so sure, could you file a tracker on bugzilla, and post
info
to demonstrate that fact. It's really interesting.
On Monday 12 Jan 2004 5:14 am, Yu, Luming wrote:
> >> >I have some TRL-DLS here (P-III). They have dual AIC onboard which
>
> are
>
> >> not
> >>
> >> >recognised under 2.4.24 but work flawlessly with ACPI in 2.4.23.
> >>
> >> Are you sure? You seems to want to say this is a regression.
> >
> >Yes. That is exactly what happened.
> >
> >2.4.23 works flawlessly
> >2.4.24 does not recognise both onboard aic
>
> Since you are so sure, could you file a tracker on bugzilla, and post
> info
> to demonstrate that fact. It's really interesting.
> -
I don't know if Stephan filed the report as you requested, but I have tried to
independantly confirm this regression on a TR-DLSR server I have here, but
unfortunately neither 2.4.23 or 2.4.24 will boot from the Mylex 170 Raid card
(DAC960) with ACPI enabled, so I never get to lspci :(
I could perhaps capture the boot messages over serial port, if that would be
helpful?
Andrew Walrond
On Thu, 15 Jan 2004, Andrew Walrond wrote:
> On Monday 12 Jan 2004 5:14 am, Yu, Luming wrote:
> > >> >I have some TRL-DLS here (P-III). They have dual AIC onboard which
> >
> > are
> >
> > >> not
> > >>
> > >> >recognised under 2.4.24 but work flawlessly with ACPI in 2.4.23.
> > >>
> > >> Are you sure? You seems to want to say this is a regression.
> > >
> > >Yes. That is exactly what happened.
> > >
> > >2.4.23 works flawlessly
> > >2.4.24 does not recognise both onboard aic
> >
> > Since you are so sure, could you file a tracker on bugzilla, and post
> > info
> > to demonstrate that fact. It's really interesting.
> > -
>
> I don't know if Stephan filed the report as you requested, but I have tried to
> independantly confirm this regression on a TR-DLSR server I have here, but
> unfortunately neither 2.4.23 or 2.4.24 will boot from the Mylex 170 Raid card
> (DAC960) with ACPI enabled, so I never get to lspci :(
>
> I could perhaps capture the boot messages over serial port, if that would be
> helpful?
Yes, please, with and without ACPI. (I suppose disabling ACPI fixes the
problem?)
Stephan: There is nothing from 2.4.23 to .24 which could cause such
breakage. It probably didnt work with 2.4.23 also?
On Fri, 16 Jan 2004 08:30:13 -0200 (BRST)
Marcelo Tosatti <[email protected]> wrote:
> > I don't know if Stephan filed the report as you requested, but I have tried
> > to independantly confirm this regression on a TR-DLSR server I have here,
> > but unfortunately neither 2.4.23 or 2.4.24 will boot from the Mylex 170
> > Raid card(DAC960) with ACPI enabled, so I never get to lspci :(
> >
> > I could perhaps capture the boot messages over serial port, if that would
> > be helpful?
>
> Yes, please, with and without ACPI. (I suppose disabling ACPI fixes the
> problem?)
>
> Stephan: There is nothing from 2.4.23 to .24 which could cause such
> breakage. It probably didnt work with 2.4.23 also?
Hello,
I am sorry for the long delay, I ran completely out of time unfortunately.
In short:
You are right, there is no regression between .23 and .24, shoot me.
Anyway I know there was a former kernel that worked with ACPI on this board.
I wanted to return the info which one though, but don't have it yet.
Anyway as soon as I find some spare time I will go hunting...
Regards,
Stephan
On Friday 16 Jan 2004 10:30 am, Marcelo Tosatti wrote:
> Yes, please, with and without ACPI. (I suppose disabling ACPI fixes the
> problem?)
Yes, it does.
Since Stephan has retracted the report, I'll combine this tests into the
general ACPI report I mention in another thread
Andrew Walrond
> For the system I noticed the ACPI problems (Asus PR-DLS533),
> the regression occured after 2.4.21
>
> With pristine 2.4.21 the system could boot with ACPI enabled,
> but with the new ACPI patches introduced with the 2.4.21-ac
> series (and integrated in the 2.4.x series later on) it did not.
>
> Does your board have several PCI busses (lspci -v) ?
You asked ;-)
The last two entries are the controllers in question.
00:00.0 Host bridge: ServerWorks CNB20HE Host Bridge (rev 23)
Flags: fast devsel
00:00.1 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
Flags: bus master, medium devsel, latency 32
00:00.2 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
Flags: medium devsel
00:00.3 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
Flags: medium devsel
00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0d)
Subsystem: Intel Corp. EtherExpress PRO/100 S Server Adapter
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at ef000000 (32-bit, non-prefetchable) [size=4K]
I/O ports at d800 [size=64]
Memory at ee800000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at febf0000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
00:03.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0d)
Subsystem: Intel Corp. EtherExpress PRO/100 S Server Adapter
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at ee000000 (32-bit, non-prefetchable) [size=4K]
I/O ports at d400 [size=64]
Memory at ed800000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at febe0000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
00:04.0 VGA compatible controller: ATI Technologies Inc Radeon RV200 QW [Radeon 7500] (prog-if 00 [VGA])
Subsystem: C.P. Technology Co. Ltd RV200 QW [Radeon 7500 PCI Dual Display]
Flags: bus master, stepping, medium devsel, latency 32, IRQ 25
Memory at f0000000 (32-bit, prefetchable) [size=128M]
I/O ports at d000 [size=256]
Memory at ed000000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at effe0000 [disabled] [size=128K]
Capabilities: [50] Power Management version 2
00:05.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
Subsystem: Creative Labs SBLive! Player 5.1
Flags: bus master, medium devsel, latency 32, IRQ 26
I/O ports at b800 [size=32]
Capabilities: [dc] Power Management version 1
00:05.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07)
Subsystem: Creative Labs Gameport Joystick
Flags: bus master, medium devsel, latency 32
I/O ports at b400 [size=8]
Capabilities: [dc] Power Management version 1
00:07.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA])
Subsystem: Asustek Computer, Inc.: Unknown device 1234
Flags: bus master, stepping, medium devsel, latency 32, IRQ 19
Memory at ec000000 (32-bit, non-prefetchable) [disabled] [size=16M]
I/O ports at b000 [disabled] [size=256]
Memory at eb800000 (32-bit, non-prefetchable) [disabled] [size=4K]
Expansion ROM at effc0000 [disabled] [size=128K]
Capabilities: [5c] Power Management version 2
00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93)
Subsystem: ServerWorks CSB5 South Bridge
Flags: bus master, medium devsel, latency 32
00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93) (prog-if 8a [Master SecP PriP])
Subsystem: ServerWorks CSB5 IDE Controller
Flags: bus master, medium devsel, latency 64
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at <ignored>
I/O ports at 9400 [size=16]
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 05) (prog-if 10 [OHCI])
Subsystem: ServerWorks OSB4/CSB5 OHCI USB Controller
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at eb000000 (32-bit, non-prefetchable) [size=4K]
00:0f.3 Host bridge: ServerWorks GCLE Host Bridge
Subsystem: ServerWorks: Unknown device 0230
Flags: bus master, medium devsel, latency 0
01:02.0 RAID bus controller: 3ware Inc 3ware 7000-series ATA-RAID (rev 01)
Subsystem: 3ware Inc 3ware 7000-series ATA-RAID
Flags: bus master, medium devsel, latency 32, IRQ 17
I/O ports at 9000 [size=16]
Memory at ea800000 (32-bit, non-prefetchable) [size=16]
Memory at ea000000 (32-bit, non-prefetchable) [size=8M]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [40] Power Management version 1
01:03.0 Network controller: AVM Audiovisuelles MKTG & Computer System GmbH Fritz!PCI v2.0 ISDN (rev 01)
Subsystem: AVM Audiovisuelles MKTG & Computer System GmbH Fritz!PCI v2.0 ISDN
Flags: medium devsel, IRQ 20
Memory at e9800000 (32-bit, non-prefetchable) [size=32]
I/O ports at 8800 [size=32]
Capabilities: [40] Power Management version 2
01:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet (rev 15)
Subsystem: 3Com Corporation 3C996B-T 1000Base-T
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 21
Memory at e9000000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] PCI-X non-bridge device.
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
02:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet (rev 15)
Subsystem: 3Com Corporation 3C996B-T 1000Base-T
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 24
Memory at e8800000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] PCI-X non-bridge device.
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
02:03.0 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)
Subsystem: Adaptec AIC-7899P U160/m
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 22
BIST result: 00
I/O ports at 7800 [disabled] [size=256]
Memory at e8000000 (64-bit, non-prefetchable) [size=4K]
Expansion ROM at efde0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
02:03.1 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01)
Subsystem: Adaptec AIC-7899P U160/m
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 23
BIST result: 00
I/O ports at 7400 [disabled] [size=256]
Memory at e7800000 (64-bit, non-prefetchable) [size=4K]
Expansion ROM at efdc0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Stephan von Krawczynski wrote:
> On Fri, 16 Jan 2004 08:30:13 -0200 (BRST)
> Marcelo Tosatti <[email protected]> wrote:
>
>
>>>I don't know if Stephan filed the report as you requested, but I have tried
>>>to independantly confirm this regression on a TR-DLSR server I have here,
>>>but unfortunately neither 2.4.23 or 2.4.24 will boot from the Mylex 170
>>>Raid card(DAC960) with ACPI enabled, so I never get to lspci :(
>>>
>>>I could perhaps capture the boot messages over serial port, if that would
>>>be helpful?
>>
>>Yes, please, with and without ACPI. (I suppose disabling ACPI fixes the
>>problem?)
>>
>>Stephan: There is nothing from 2.4.23 to .24 which could cause such
>>breakage. It probably didnt work with 2.4.23 also?
>
>
> Hello,
>
> I am sorry for the long delay, I ran completely out of time unfortunately.
> In short:
> You are right, there is no regression between .23 and .24, shoot me.
> Anyway I know there was a former kernel that worked with ACPI on this board.
> I wanted to return the info which one though, but don't have it yet.
> Anyway as soon as I find some spare time I will go hunting...
>
For the system I noticed the ACPI problems (Asus PR-DLS533),
the regression occured after 2.4.21
With pristine 2.4.21 the system could boot with ACPI enabled,
but with the new ACPI patches introduced with the 2.4.21-ac
series (and integrated in the 2.4.x series later on) it did not.
Does your board have several PCI busses (lspci -v) ?
It seems the problem is with the BIOS not correctly initializing
and/or reporting some ACPI data structures, so the Linux ACPI code
does not find (and therefore initialize) some devices on higher PCI
bus numbers.
It looks like it's Asus who should fix their BIOS.
Does anyone know how the other OS(tm) does handle
ACPI PCI bus initialisation on these boards? Do
they have some workaround for such broken BIOS?
(I have never tried the other OS(tm) on this board)
- - andreas
- --
Andreas Haumer | mailto:[email protected]
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAB+O/xJmyeGcXPhERArLfAKCgPxnCWEA2gSC4O0k9plGhNp231gCgpz1m
TVH4WHTDK2u+4HVFZA3x0m4=
=NyKq
-----END PGP SIGNATURE-----