Re: Bugreport: Kernel 2.4.x crash

From: John Jasen (jjasen1@umbc.edu)
Date: Tue Apr 03 2001 - 09:26:06 EST

Next message: Pete Toscano: "Re: Stuck: What to do with solid locks?"
Previous message: Alan Cox: "Re: /proc/config idea"
In reply to: Jörn Engel: "Bugreport: Kernel 2.4.x crash"
Next in thread: Mark Hahn: "Re: Bugreport: Kernel 2.4.x crash"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 3 Apr 2001, [iso-8859-1] Jörn Engel wrote:

I don't necessarily believe its the hpt366, as you do. See below: (note:
I've also had it running on a stock 2.4.2 kernel for a while)

> 00:08.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366
> (rev 01)
> 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: 248 (2000ns min, 2000ns max), cache line size 08
> Interrupt: pin A routed to IRQ 11
> Region 0: I/O ports at 6100
> Region 1: I/O ports at 6200
> Region 4: I/O ports at 6300
>
> 00:08.1 Unknown mass storage controller: Triones Technologies, Inc. HPT366
> (rev 01)
> 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: 248 (2000ns min, 2000ns max), cache line size 08
> Interrupt: pin A routed to IRQ 11
> Region 0: I/O ports at 6400
> Region 1: I/O ports at 6500
> Region 4: I/O ports at 6600

00:13.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366
(rev
01)
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
        Latency: 8 min, 8 max, 120 set, cache line size 08
        Interrupt: pin A routed to IRQ 10
        Region 0: I/O ports at ac00 [size=8]
        Region 1: I/O ports at b000 [size=4]
        Region 4: I/O ports at b400 [size=256]
        Expansion ROM at ea000000 [disabled] [size=128K]

00:13.1 Unknown mass storage controller: Triones Technologies, Inc. HPT366
(rev
01)
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Step
ping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort
- <MAbort- >SERR- <PERR-
        Latency: 8 min, 8 max, 120 set, cache line size 08
        Interrupt: pin B routed to IRQ 10
        Region 0: I/O ports at b800 [size=8]
        Region 1: I/O ports at bc00 [size=4]
        Region 4: I/O ports at c000 [size=256]

[root@geisha /root]# uptime
10:25am up 8 days, 21:17, 9 users, load average: 0.00, 0.00, 0.00
[root@geisha /root]# uname -a
Linux geisha 2.4.2-ac20 #6 SMP Sat Mar 24 23:40:02 EST 2001 i686 unknown

-- -- John E. Jasen (jjasen1@umbc.edu) -- In theory, theory and practise are the same. In practise, they aren't.

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Pete Toscano: "Re: Stuck: What to do with solid locks?"
Previous message: Alan Cox: "Re: /proc/config idea"
In reply to: Jörn Engel: "Bugreport: Kernel 2.4.x crash"
Next in thread: Mark Hahn: "Re: Bugreport: Kernel 2.4.x crash"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Apr 07 2001 - 21:00:12 EST