00:00.0 Host bridge: Acer Laboratories Inc. [ALi] M1531 [Aladdin IV] (rev b3)
Subsystem: Acer Laboratories Inc. [ALi] M1531 [Aladdin IV]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 32
00:02.0 ISA bridge: Acer Laboratories Inc. [ALi] M1533 PCI to ISA Bridge [Aladdin IV] (rev b4)
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: 0
00:03.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2064W [Millennium] (rev 01) (prog-if 00 [VGA])
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-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at ffafc000 (32-bit, non-prefetchable) [size=16K]
Region 1: Memory at ef800000 (32-bit, prefetchable) [size=8M]
Expansion ROM at ffae0000 [disabled] [size=64K]
00:04.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev 02) (prog-if 85)
Subsystem: Promise Technology, Inc. Ultra100TX2
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (1000ns min, 4500ns max), cache line size 08
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at eff0 [size=8]
Region 1: I/O ports at efe4 [size=4]
Region 2: I/O ports at efa8 [size=8]
Region 3: I/O ports at efe0 [size=4]
Region 4: I/O ports at ef90 [size=16]
Region 5: Memory at ffaf8000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at ffaf4000 [disabled] [size=16K]
Capabilities: [60] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
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 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at ec00 [size=256]
Region 1: Memory at ffaf3f00 (32-bit, non-prefetchable) [size=256]
00:0b.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev 20) (prog-if fa)
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 (500ns min, 1000ns max)
Interrupt: pin A routed to IRQ 0
Region 4: I/O ports at ffa0 [size=16]
Hi Fabio.
> this happend creating a new a lv with the command lvcreate -L512M
> -ntest system It did 3 times in a row then it worked again. What was
> strange is that I was in one dir and unfortunalty I don't remember
> which and it was crashing. I changed dir and then it was working. In
> the first instance I didn't thought about taking notes but atleast I
> have a full trace (the machine didn't hang or reboot... it is still
> alive 100%).
This may be completely off-track but I've seen it cause wierd problems
in the past, so worth checking - was the directory you were in when the
machine crashed one that still existed as far as the file system was
concerned?
To test this, try the following...
# cd /tmp
# mkdir X
# cd X
# mv ../X ../Y
# cd `pwd`
bash: /tmp/X: No such file or directory
#
...and then perform the test. As far as the test is concerned, the
current directory is /tmp/X but, as shown above, the file system reports
that the said directory doesn't exist, and it's not hard to work out
that you're actually in /tmp/Y instead.
Best wishes from Riley.
Riley Williams wrote:
>Hi Fabio.
>
>
>
>>this happend creating a new a lv with the command lvcreate -L512M
>>-ntest system It did 3 times in a row then it worked again. What was
>>strange is that I was in one dir and unfortunalty I don't remember
>>which and it was crashing. I changed dir and then it was working. In
>>the first instance I didn't thought about taking notes but atleast I
>>have a full trace (the machine didn't hang or reboot... it is still
>>alive 100%).
>>
>>
>
>This may be completely off-track but I've seen it cause wierd problems
>in the past, so worth checking - was the directory you were in when the
>machine crashed one that still existed as far as the file system was
>concerned?
>
Im fairly sure it is still there because I didn't made any
change in the filesystem (in terms of mv rm etc.) but
I will give it a try later since Im not close to the box
right now and a possible crash from remote is not really
a good idea ;)
Fabio
Hi Riley,
here are the results:
trider-g7:/tmp# mkdir X
trider-g7:/tmp# cd X
trider-g7:/tmp/X# mv ../X ../Y
trider-g7:/tmp/X# cd `pwd`
bash: cd: /tmp/X: No such file or directory
trider-g7:/tmp/X# lvcreate -L10M -ntest system
lvcreate -- rounding size up to physical extent boundary
lvcreate -- doing automatic backup of "system"
lvcreate -- logical volume "/dev/system/test" successfully created
trider-g7:/tmp/X#
as you can see there was no problem at all "unfortunatly".
Regards
Fabio
Riley Williams wrote:
>Hi Fabio.
>
>
>
>>this happend creating a new a lv with the command lvcreate -L512M
>>-ntest system It did 3 times in a row then it worked again. What was
>>strange is that I was in one dir and unfortunalty I don't remember
>>which and it was crashing. I changed dir and then it was working. In
>>the first instance I didn't thought about taking notes but atleast I
>>have a full trace (the machine didn't hang or reboot... it is still
>>alive 100%).
>>
>>
>
>This may be completely off-track but I've seen it cause wierd problems
>in the past, so worth checking - was the directory you were in when the
>machine crashed one that still existed as far as the file system was
>concerned?
>
>
>