mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominik Karall <dominik.karall@gmx.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc2-mm2
Date: Thu, 3 Jun 2004 17:03:34 +0200	[thread overview]
Message-ID: <200406031703.38722.dominik.karall@gmx.net> (raw)
In-Reply-To: <20040603015356.709813e9.akpm@osdl.org>

On Thursday 03 June 2004 10:53, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7-rc2/2.6
>.7-rc2-mm2/

SiS framebuffer works here. But my kernel does not boot, it stops at

Starting hotplug subsystem:
   input
   net
   pci
     sis900: already loaded
     8139too: already loaded
     ignore pci display device on 01:00.0
   usb

and right here it stops.

Normally it looks this way:

Starting hotplug subsystem:
   input
   net
   pci
     sis900: already loaded
     8139too: already loaded
     ignore pci display device on 01:00.0
   usb
done

Here is my lspci -vvv output of the USB controllers:

0000:00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 
Controller (rev 0f) (prog-if 10 [OHCI])
        Subsystem: Micro-Star International Co., Ltd.: Unknown device 7010
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (20000ns max), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at e2420000 (32-bit, non-prefetchable)

0000:00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 
Controller (rev 0f) (prog-if 10 [OHCI])
        Subsystem: Micro-Star International Co., Ltd.: Unknown device 7010
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (20000ns max), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin B routed to IRQ 21
        Region 0: Memory at e2421000 (32-bit, non-prefetchable)

0000:00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 
Controller (rev 0f) (prog-if 10 [OHCI])
        Subsystem: Micro-Star International Co., Ltd.: Unknown device 7010
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (20000ns max), Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin C routed to IRQ 22
        Region 0: Memory at e2422000 (32-bit, non-prefetchable)

0000:00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 
Controller (prog-if 20 [EHCI])
        Subsystem: Micro-Star International Co., Ltd.: Unknown device 7010
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (20000ns max)
        Interrupt: pin D routed to IRQ 23
        Region 0: Memory at e2423000 (32-bit, non-prefetchable)
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-



By the way, with 2.6.6-mm5 (the last working -mm patch on my machine), I get 
only following PHY messages:

eth0: Realtek RTL8201 PHY transceiver found at address 1.
eth0: Using transceiver found at address 1 as default
eth0: SiS 900 PCI Fast Ethernet at 0xdc00, IRQ 19, 00:10:dc:8f:a9:ac.

with the current 2.6.7-rc2-mm2 patch, I get

eth0: Unknown PHY transceiver found at address 0.
eth0: Realtek RTL8201 PHY transceiver found at address 1.
eth0: Unknown PHY transceiver found at address 2.
eth0: Unknown PHY transceiver found at address 3.
eth0: Unknown PHY transceiver found at address 4.
eth0: Unknown PHY transceiver found at address 5.
eth0: Unknown PHY transceiver found at address 6.
eth0: Unknown PHY transceiver found at address 7.
eth0: Unknown PHY transceiver found at address 8.
eth0: Unknown PHY transceiver found at address 9.
eth0: Unknown PHY transceiver found at address 10.
eth0: Unknown PHY transceiver found at address 11.
eth0: Unknown PHY transceiver found at address 12.
eth0: Unknown PHY transceiver found at address 13.
eth0: Unknown PHY transceiver found at address 14.
eth0: Unknown PHY transceiver found at address 15.
eth0: Unknown PHY transceiver found at address 16.
eth0: Unknown PHY transceiver found at address 17.
eth0: Unknown PHY transceiver found at address 18.
eth0: Unknown PHY transceiver found at address 19.
eth0: Unknown PHY transceiver found at address 20.
eth0: Unknown PHY transceiver found at address 21.
eth0: Unknown PHY transceiver found at address 22.
eth0: Unknown PHY transceiver found at address 23.
eth0: Unknown PHY transceiver found at address 24.
eth0: Unknown PHY transceiver found at address 25.
eth0: Unknown PHY transceiver found at address 26.
eth0: Unknown PHY transceiver found at address 27.
eth0: Unknown PHY transceiver found at address 28.
eth0: Unknown PHY transceiver found at address 29.
eth0: Unknown PHY transceiver found at address 30.
eth0: Unknown PHY transceiver found at address 31.
eth0: Using transceiver found at address 1 as default
eth0: SiS 900 PCI Fast Ethernet at 0xdc00, IRQ 19, 00:10:dc:8f:a9:ac.

It works ok, as the address 1 is used as default, but I just wanted to mention 
that.

greets dominik

  parent reply	other threads:[~2004-06-03 15:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03  8:53 2.6.7-rc2-mm2 Andrew Morton
2004-06-03 12:48 ` 2.6.7-rc2-mm2 - hpet-dont-use-new-major borked Paul Jackson
2004-06-03 14:21 ` 2.6.7-rc2-mm2 (compile stats) John Cherry
2004-06-03 15:03 ` 2.6.7-rc2-mm2 AKIYAMA Nobuyuki
2004-06-03 15:03 ` Dominik Karall [this message]
2004-06-03 23:18   ` 2.6.7-rc2-mm2 Andrew Morton
2004-06-03 23:53     ` 2.6.7-rc2-mm2 Alexander Nyberg
2004-06-04  8:17     ` 2.6.7-rc2-mm2 Dominik Karall
2004-06-04 10:34       ` 2.6.7-rc2-mm2 Lenar Lõhmus
2004-06-04 10:40     ` 2.6.7-rc2-mm2 Ralf Hildebrandt
2004-06-04 13:53   ` 2.6.7-rc2-mm2 Denis Vlasenko
2004-06-03 15:20 ` 2.6.7-rc2-mm2 Jens Axboe
2004-06-11  2:40   ` 2.6.7-rc2-mm2 Len Brown
2004-06-15  6:37     ` 2.6.7-rc2-mm2 Jens Axboe
2004-06-03 16:39 ` 2.6.7-rc2-mm2 Tim Schmielau
2004-06-04 15:05 ` 2.6.7-rc2-mm2: compile error with VIDEO_CX88=y and gcc 2.95 Adrian Bunk
2004-06-07 12:41 ` 2.6.7-rc2-mm2 Andrey Panin
     [not found]   ` <20040607220157.1e67ec39.akpm@osdl.org>
2004-06-08  5:18     ` 2.6.7-rc2-mm2 Andrey Panin
     [not found]       ` <20040607222513.6bebcbb6.akpm@osdl.org>
2004-06-08  6:34         ` 2.6.7-rc2-mm2 Andrey Panin
2004-06-08  6:42           ` 2.6.7-rc2-mm2 Andrew Morton
2004-06-08  7:18             ` 2.6.7-rc2-mm2 Andrey Panin
     [not found]               ` <20040608002245.04a3de55.akpm@osdl.org>
2004-06-08  8:04                 ` 2.6.7-rc2-mm2 Andrey Panin
2004-06-03 22:15 2.6.7-rc2-mm2 Mario ''Jorge'' Di Nitto
     [not found] <Pine.LNX.4.44L0.0406041047080.2279-100000@ida.rowland.org>
2004-06-04 15:46 ` 2.6.7-rc2-mm2 Dominik Karall

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=200406031703.38722.dominik.karall@gmx.net \
    --to=dominik.karall@gmx.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®