Hi,
I've recently switched form 2.4.x kernel series to 2.6.x, and I've
encourted a problem with my old scanner card, lspci shows it as:
<begin lspci output>
00:0c.0 SCSI storage controller: DTC Technology Corp. Domex 536
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: I/O ports at d800 [size=32]
<end>
It worked flawlessly under 2.4 kernels, but now it hangs xsane, and logs
show this:
<begin /var/log/messages>
Apr 1 17:29:30 techno kernel: command: cdb[0]=0x0: 00 00 00 00
00 00
Apr 1 17:29:40 techno last message repeated 3 times
<end>
<begin /va/log/syslog>
Apr 1 17:29:30 techno kernel: scsi0 : aborting command
Apr 1 17:29:30 techno kernel: scsi0 : destination target 6, lun 0
Apr 1 17:29:30 techno kernel:
Apr 1 17:29:30 techno kernel: NCR5380 core release=7.
Apr 1 17:29:30 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 1 17:29:30 techno kernel: scsi0: no currently connected command
Apr 1 17:29:30 techno kernel: scsi0: issue_queue
Apr 1 17:29:30 techno kernel: scsi0 : destination target 6, lun 0
Apr 1 17:29:30 techno kernel: command = 0 (0x00)00 00 00 00 00
Apr 1 17:29:30 techno kernel: scsi0: disconnected_queue
Apr 1 17:29:30 techno kernel:
Apr 1 17:29:30 techno kernel: scsi0 : aborting command
Apr 1 17:29:30 techno kernel: scsi0 : destination target 6, lun 0
Apr 1 17:29:30 techno kernel:
Apr 1 17:29:30 techno kernel: NCR5380 core release=7.
Apr 1 17:29:30 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 1 17:29:30 techno kernel: scsi0: no currently connected command
Apr 1 17:29:30 techno kernel: scsi0: issue_queue
Apr 1 17:29:30 techno kernel: scsi0 : destination target 6, lun 0
Apr 1 17:29:30 techno kernel: command = 0 (0x00)00 00 00 00 00
Apr 1 17:29:30 techno kernel: scsi0: disconnected_queue
Apr 1 17:29:30 techno kernel:
Apr 1 17:29:40 techno kernel: scsi0 : aborting command
Apr 1 17:29:40 techno kernel: scsi0 : destination target 6, lun 0
Apr 1 17:29:40 techno kernel:
Apr 1 17:29:40 techno kernel: NCR5380 core release=7.
Apr 1 17:29:40 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 1 17:29:40 techno kernel: scsi0: no currently connected command
Apr 1 17:29:40 techno kernel: scsi0: issue_queue
Apr 1 17:29:40 techno kernel: scsi0 : destination target 6, lun 0
Apr 1 17:29:40 techno kernel: command = 0 (0x00)00 00 00 00 00
Apr 1 17:29:40 techno kernel: scsi0: disconnected_queue
Apr 1 17:29:40 techno kernel:
Apr 1 17:29:40 techno kernel: scsi0 : aborting command
Apr 1 17:29:40 techno kernel: scsi0 : destination target 6, lun 0
Apr 1 17:29:40 techno kernel:
Apr 1 17:29:40 techno kernel: NCR5380 core release=7.
Apr 1 17:29:40 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 1 17:29:40 techno kernel: scsi0: no currently connected command
Apr 1 17:29:40 techno kernel: scsi0: issue_queue
Apr 1 17:29:40 techno kernel: scsi0 : destination target 6, lun 0
Apr 1 17:29:40 techno kernel: command = 0 (0x00)00 00 00 00 00
Apr 1 17:29:40 techno kernel: scsi0: disconnected_queue
Apr 1 17:29:41 techno kernel:
Apr 1 17:29:41 techno kernel: Unable to handle kernel paging request at
virtual address 002b2c36
Apr 1 17:29:41 techno kernel: printing eip:
Apr 1 17:29:41 techno kernel: c03f1e71
Apr 1 17:29:41 techno kernel: *pde = 00000000
Apr 1 17:29:41 techno kernel: Oops: 0000 [#1]
Apr 1 17:29:41 techno kernel: PREEMPT
Apr 1 17:29:41 techno kernel: Modules linked in: nvidia
Apr 1 17:29:41 techno kernel: CPU: 0
Apr 1 17:29:41 techno kernel: EIP: 0060:[<c03f1e71>] Tainted: P
VLI
Apr 1 17:29:41 techno kernel: EFLAGS: 00010202 (2.6.11.3)
Apr 1 17:29:41 techno kernel: EIP is at sg_cmd_done+0x41/0x2f0
Apr 1 17:29:41 techno kernel: eax: 00000000 ebx: cd4ee600 ecx:
db821dec edx: db83d040
Apr 1 17:29:41 techno kernel: esi: ca037038 edi: 002b2c32 ebp:
db83d040 esp: db84deec
Apr 1 17:29:41 techno kernel: ds: 007b es: 007b ss: 0068
Apr 1 17:29:41 techno kernel: Process scsi_eh_0 (pid: 1096,
threadinfo=db84c000 task=dbcf40e0)
Apr 1 17:29:41 techno kernel: Stack: c060e3b5 db84defc c03e7c31
c060e3b5 c07bc620 db84df10 db821c00 00050000
Apr 1 17:29:41 techno kernel: 00000000 00000001 c03e97fa
db83d040 00000000 00000001 00000246 db83d040
Apr 1 17:29:41 techno kernel: db84c000 c03dacce db83d040
c03dab30 c03dab10 00000000 00000000 db84df48
Apr 1 17:29:41 techno kernel: Call Trace:
Apr 1 17:29:41 techno kernel: [<c03e7c31>] NCR5380_print_status+0x51/0x60
Apr 1 17:29:41 techno kernel: [<c03e97fa>] NCR5380_abort+0x14a/0x160
Apr 1 17:29:41 techno kernel: [<c03dacce>] scsi_send_eh_cmnd+0x13e/0x170
Apr 1 17:29:41 techno kernel: [<c03dab30>] scsi_eh_done+0x0/0x60
Apr 1 17:29:41 techno kernel: [<c03dab10>] scsi_eh_times_out+0x0/0x20
Apr 1 17:29:41 techno kernel: [<c03db045>] scsi_eh_tur+0x95/0xd0
Apr 1 17:29:41 techno kernel: [<c03db0e9>] scsi_eh_abort_cmds+0x69/0x80
Apr 1 17:29:41 techno kernel: [<c03dbd11>] scsi_unjam_host+0xa1/0xd0
Apr 1 17:29:41 techno kernel: [<c011b9c2>] complete+0x52/0x80
Apr 1 17:29:41 techno kernel: [<c03dbddf>] scsi_error_handler+0x9f/0xd0
Apr 1 17:29:41 techno kernel: [<c03dbd40>] scsi_error_handler+0x0/0xd0
Apr 1 17:29:41 techno kernel: [<c01012fd>] kernel_thread_helper+0x5/0x18
Apr 1 17:29:41 techno kernel: Code: 1c 89 7c 24 20 0f 84 b1 02 00 00 8b
5d 0c 85 db 0f 84 a6 02 00 00 8b b3 ac 00 00 00 85 f6 0f 84 98 02 00 00
8b 7e 08 85 ff 74 13 <8b> 47 04 85 c0 89 44 24 0c 74 08 0f b6 40 14 84
c0 74 2c c7 04
Apr 1 17:29:41 techno kernel: <6>note: scsi_eh_0[1096] exited with
preempt_count 1
<end>
I hope thant you can either tell me what's wrong, or anyone coudl look
at the code and fix the problem?
As an additional note I have ScanMagic 9636 S Plus Scanner with the card
thad it was sold with.
As a side not I can tell It was working with 2.4 series, but scanning
coused the mashing to either hang for a few seconds (one or twice hang
for good), while the scanning caused the machine to become jaggy, the
music played (xmms), but the graphic wasn't working well.
I'm not subscribed so please CC to me too.
--
pozdrawiam |"Help me master, I felt the burning twilight behind
[email protected]|those gates of stell..." --Perihelion, Prophecy Sequence
On Sat, 2 Apr 2005, |TEcHNO| wrote:
> Hi,
>
> I've recently switched form 2.4.x kernel series to 2.6.x, and I've encourted a
> problem with my old scanner card,
> Apr 1 17:29:41 techno kernel: Modules linked in: nvidia
^^^ Very first thing to do is try it without the nvidia module loaded and
then reproduce the problem and post the same info from your logs again.
As long as the nvidia module is loaded most people will disregard the
bugreport since the source for the module is not available so if it has
anything to do with the problem at all it is more or less un-debugable. If
the problem can be reproduced without the nvidia module loaded then the
info is more useful.
--
Jesper Juhl
Hi,
<cut, nVidia module tainting>
First of all, I don't have my X configured to work w/o that module, and
I don't think I can do it now.
Second of all, the 2.4.x kernel had this module too, and worked flawlessly.
Non the less, I'll try to do it.
--
pozdrawiam |"Help me master, I felt the burning twilight behind
[email protected]|those gates of stell..." --Perihelion, Prophecy Sequence
On Sat, 2 Apr 2005, |TEcHNO| wrote:
> Hi,
>
> <cut, nVidia module tainting>
> First of all, I don't have my X configured to work w/o that module, and I
> don't think I can do it now.
You should be able to just use the "nv" driver instead of the "nvidia"
driver - that should be the only change you need to make in xorg.conf ...
> Second of all, the 2.4.x kernel had this module too, and worked flawlessly.
>
It's probably unrelated to the problem, but being able to reproduce it
without that module will make more people take the bugreport seriously and
it will also eliminate the nvidia module as a potential cause...
--
Jesper Juhl
Hi,
As told, I tested it w/o nvidia module loaded, here's what I found:
1. It now doesn't hang on scanning for devices.
2. It now hangs on acquiring preview, logs will follow.
2a.Not it hanged on scanning for devices again, don't know why.
3. It's true for both module loaded and w/o it.
4. xsane badly reports my scanner as Plustek 12000 or such.
5. Turning on "partial updates"(or such) in view->updates, coused whole
machine to hang up, hard reset was needed. W/o this, only xsane hanged.
Shoudln't kernel protect form that somehow?
6. Anytime xsane fails/hangs, it hangs the scanner, making it blink it's
lamp all the time, and it needt to be dissconnected form electricity to
work.
7. As a side question: any way to "reload" the whole SCSI subsystem, so
I don't hjave to reboot if I connect something new?
<begin /var/log/syslog>
Apr 3 15:36:38 techno kernel: scsi0 : aborting command
Apr 3 15:36:38 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:36:38 techno kernel:
Apr 3 15:36:38 techno kernel: NCR5380 core release=7.
Apr 3 15:36:38 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 3 15:36:38 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:36:38 techno kernel: command = 42 (0x2a)00 03 00 00 00
01 10 00 00
Apr 3 15:36:38 techno kernel: scsi0: issue_queue
Apr 3 15:36:38 techno kernel: scsi0: disconnected_queue
Apr 3 15:36:38 techno kernel:
Apr 3 15:36:38 techno kernel: scsi0 : aborting command
Apr 3 15:36:38 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:36:38 techno kernel:
Apr 3 15:36:38 techno kernel: NCR5380 core release=7.
Apr 3 15:36:38 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 3 15:36:38 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:36:38 techno kernel: command = 42 (0x2a)00 03 00 00 00
01 10 00 00
Apr 3 15:36:38 techno kernel: scsi0: issue_queue
Apr 3 15:36:38 techno kernel: scsi0: disconnected_queue
Apr 3 15:36:38 techno kernel:
Apr 3 15:36:38 techno kernel:
Apr 3 15:36:38 techno kernel: NCR5380 core release=7.
Apr 3 15:36:38 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 3 15:36:38 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:36:38 techno kernel: command = 42 (0x2a)00 03 00 00 00
01 10 00 00
Apr 3 15:36:39 techno kernel: scsi0: issue_queue
Apr 3 15:36:39 techno kernel: scsi0: disconnected_queue
Apr 3 15:36:39 techno kernel:
Apr 3 15:40:26 techno kernel: Linux version 2.6.11.3 (root@techno) (gcc
version 3.3.5) #1 Tue Mar 15 14:23:17 CET 2005
<cut>
Apr 3 15:54:07 techno kernel: scsi0 : aborting command
Apr 3 15:54:07 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:54:07 techno kernel:
Apr 3 15:54:07 techno kernel: NCR5380 core release=7.
Apr 3 15:54:07 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 3 15:54:07 techno kernel: scsi0: no currently connected command
Apr 3 15:54:07 techno kernel: scsi0: issue_queue
Apr 3 15:54:07 techno kernel: scsi0: disconnected_queue
Apr 3 15:54:07 techno kernel:
Apr 3 15:54:07 techno kernel: scsi0 : aborting command
Apr 3 15:54:07 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:54:07 techno kernel:
Apr 3 15:54:07 techno kernel: NCR5380 core release=7.
Apr 3 15:54:07 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 3 15:54:07 techno kernel: scsi0: no currently connected command
Apr 3 15:54:07 techno kernel: scsi0: issue_queue
Apr 3 15:54:07 techno kernel: scsi0: disconnected_queue
Apr 3 15:54:07 techno kernel:
Apr 3 15:54:07 techno kernel: scsi0 : warning : SCSI command probably
completed successfully
Apr 3 15:54:07 techno kernel: before abortion
Apr 3 15:54:07 techno kernel:
Apr 3 15:54:07 techno kernel: NCR5380 core release=7.
Apr 3 15:54:07 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 3 15:54:07 techno kernel: scsi0: no currently connected command
Apr 3 15:54:07 techno kernel: scsi0: issue_queue
Apr 3 15:54:07 techno kernel: scsi0: disconnected_queue
Apr 3 15:54:07 techno kernel:
Apr 3 15:54:27 techno kernel: scsi0 : aborting command
Apr 3 15:54:27 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:54:27 techno kernel:
Apr 3 15:54:27 techno kernel: NCR5380 core release=7.
Apr 3 15:54:27 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 3 15:54:27 techno kernel: scsi0: no currently connected command
Apr 3 15:54:27 techno kernel: scsi0: issue_queue
Apr 3 15:54:27 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:54:27 techno kernel: command = 0 (0x00)00 00 00 00 00
Apr 3 15:54:27 techno kernel: scsi0: disconnected_queue
Apr 3 15:54:27 techno kernel:
Apr 3 15:54:27 techno kernel: scsi0 : aborting command
Apr 3 15:54:27 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:54:27 techno kernel:
Apr 3 15:54:27 techno kernel: NCR5380 core release=7.
Apr 3 15:54:27 techno kernel: Base Addr: 0x00000 io_port: d800
IRQ: 11.
Apr 3 15:54:27 techno kernel: scsi0: no currently connected command
Apr 3 15:54:27 techno kernel: scsi0: issue_queue
Apr 3 15:54:27 techno kernel: scsi0 : destination target 6, lun 0
Apr 3 15:54:27 techno kernel: command = 0 (0x00)00 00 00 00 00
Apr 3 15:54:27 techno kernel: scsi0: disconnected_queue
Apr 3 15:54:27 techno kernel:
Apr 3 15:54:27 techno kernel: Unable to handle kernel NULL pointer
dereference at virtual address 0000014c
Apr 3 15:54:27 techno kernel: printing eip:
Apr 3 15:54:27 techno kernel: c03d8143
Apr 3 15:54:27 techno kernel: *pde = 00000000
Apr 3 15:54:27 techno kernel: Oops: 0000 [#1]
Apr 3 15:54:27 techno kernel: PREEMPT
Apr 3 15:54:27 techno kernel: Modules linked in: nvidia
Apr 3 15:54:27 techno kernel: CPU: 0
Apr 3 15:54:27 techno kernel: EIP: 0060:[<c03d8143>] Tainted: P
VLI
Apr 3 15:54:27 techno kernel: EFLAGS: 00010286 (2.6.11.3)
Apr 3 15:54:27 techno kernel: EIP is at scsi_finish_command+0x63/0xc0
Apr 3 15:54:27 techno kernel: eax: 00000000 ebx: db821800 ecx:
00000000 edx: c3a6dc00
Apr 3 15:54:27 techno kernel: esi: 00000000 edi: db83d040 ebp:
db84dfb4 esp: db84df6c
Apr 3 15:54:27 techno kernel: ds: 007b es: 007b ss: 0068
Apr 3 15:54:27 techno kernel: Process scsi_eh_0 (pid: 1096,
threadinfo=db84c000 task=dbcf50e0)
Apr 3 15:54:27 techno kernel: Stack: db821800 db84dfb4 c03db86a
db84dfac db84dfac db84dfac c03dbc3d db83d040
Apr 3 15:54:27 techno kernel: db821c30 db821c30 00000286
db84dfac c03dbcfd db84dfac db84dfac db84dfac
Apr 3 15:54:27 techno kernel: db84dfac db84dfac db84dfb4
db84dfb4 db84dfd8 db821c00 00000000 00000000
Apr 3 15:54:27 techno kernel: Call Trace:
Apr 3 15:54:27 techno kernel: [<c03db86a>] scsi_eh_offline_sdevs+0x7a/0x90
Apr 3 15:54:27 techno kernel: [<c03dbc3d>] scsi_eh_flush_done_q+0x7d/0xb0
Apr 3 15:54:27 techno kernel: [<c03dbcfd>] scsi_unjam_host+0x8d/0xd0
Apr 3 15:54:27 techno kernel: [<c03dbddf>] scsi_error_handler+0x9f/0xd0
Apr 3 15:54:27 techno kernel: [<c03dbd40>] scsi_error_handler+0x0/0xd0
Apr 3 15:54:27 techno kernel: [<c01012fd>] kernel_thread_helper+0x5/0x18
Apr 3 15:54:27 techno kernel: Code: e0 70 83 f8 70 74 67 0f b7 87 98 00
00 00 66 c7 47 0a 00 01 8b 57 0c 66 c7 47 08 01 10 85 d2 66 89 87 9a 00
00 00 74 10 8b 4a 70 <8b> 81 4c 01 00 00 85 c0 89 42 04 75 16 89 3c 24
ff 57 28 8b 5c
Apr 3 15:54:27 techno kernel: <3>scsi0 (6:0): rejecting I/O to offline
device
<end>
<begin /var/log/messages>
Apr 3 15:13:20 techno kernel: scsi0 : Domex DMX3191D
Apr 3 15:13:20 techno kernel: Vendor: SCANNER Model:
Rev: V100
Apr 3 15:13:20 techno kernel: Type: Scanner
ANSI SCSI revision: 01 CCS
Apr 3 15:13:20 techno kernel: Attached scsi generic sg0 at scsi0,
channel 0, id 6, lun 0, type 6
<cut>
Apr 3 15:21:31 techno kernel: command: cdb[0]=0x12: 12 00 00 00
60 00
Apr 3 15:21:31 techno kernel: command: cdb[0]=0x12: 12 00 00 00
60 00
Apr 3 15:21:51 techno kernel: command: cdb[0]=0x0: 00 00 00 00
00 00
Apr 3 15:21:52 techno kernel: command: cdb[0]=0x0: 00 00 00 00
00 00
Apr 3 15:21:52 techno kernel: scsi: Device offlined - not ready after
error recovery: host 0 channel 0 id 6 lun 0
<cut>
Apr 3 15:36:38 techno kernel: command: cdb[0]=0x2a: 2a 00 03 00
00 00 01 10 00 00
<cut>
Apr 3 15:54:07 techno kernel: command: cdb[0]=0x12: 12 00 00 00
60 00
Apr 3 15:54:07 techno kernel: command: cdb[0]=0x12: 12 00 00 00
60 00
Apr 3 15:54:27 techno kernel: command: cdb[0]=0x0: 00 00 00 00
00 00
Apr 3 15:54:27 techno kernel: command: cdb[0]=0x0: 00 00 00 00
00 00
Apr 3 15:54:27 techno kernel: scsi: Device offlined - not ready after
error recovery: host 0 channel 0 id 6 lun 0
<end>
As previously, please CC any replies ect. to me, I'm willing to help as
much as I can.
--
pozdrawiam |"Who says the Anti-Christ has to be a man?!"
[email protected]|Art Bell - Radio Talk Show Host
On Sun, Apr 03, 2005 at 07:58:10PM +0200, |TEcHNO| wrote:
> Hi,
>
> As told, I tested it w/o nvidia module loaded, here's what I found:
> 1. It now doesn't hang on scanning for devices.
> 2. It now hangs on acquiring preview, logs will follow.
>...
> Apr 3 15:54:27 techno kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 0000014c
> Apr 3 15:54:27 techno kernel: printing eip:
> Apr 3 15:54:27 techno kernel: c03d8143
> Apr 3 15:54:27 techno kernel: *pde = 00000000
> Apr 3 15:54:27 techno kernel: Oops: 0000 [#1]
> Apr 3 15:54:27 techno kernel: PREEMPT
> Apr 3 15:54:27 techno kernel: Modules linked in: nvidia
>...
Still with nvidia.
An Oops with the nvidia module loaded since the last boot is simply not
debuggable for anyone except nvidia.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
>>As told, I tested it w/o nvidia module loaded, here's what I found:
>>1. It now doesn't hang on scanning for devices.
>>2. It now hangs on acquiring preview, logs will follow.
>>...
>>Apr 3 15:54:27 techno kernel: Unable to handle kernel NULL pointer
>>dereference at virtual address 0000014c
>>Apr 3 15:54:27 techno kernel: printing eip:
>>Apr 3 15:54:27 techno kernel: c03d8143
>>Apr 3 15:54:27 techno kernel: *pde = 00000000
>>Apr 3 15:54:27 techno kernel: Oops: 0000 [#1]
>>Apr 3 15:54:27 techno kernel: PREEMPT
>>Apr 3 15:54:27 techno kernel: Modules linked in: nvidia
>>...
> Still with nvidia.
>
> An Oops with the nvidia module loaded since the last boot is simply not
> debuggable for anyone except nvidia.
Em, there's also the same (w/o oops) with out that module, each of that
situations was separated by a reset. It was working well in 2.4.x so I
guess it'a a problem with the card's (00:0c.0 SCSI storage controller:
DTC Technology Corp. Domex 536) driver.
--
pozdrawiam |"Help me master, I felt the burning twilight behind
[email protected]|those gates of stell..." --Perihelion, Prophecy Sequence
Hi,
> Is this crash still repeatable in 2.6.12-rc5?
>
> If so, can you please verify that it still occurs if the nvidia driver was
> never loaded?
No, it works now as if it was 2.4.x series.
Now it just randomly hangs the system, ie. somewhere at the end of
scanning or suchm no nothing in logs or similar. Simply hangs. My guess
is that It shoudln't, no matter what, I always thought Linux was stable
but the current problems (CDburning problems around 2.6.9, scanner/SCSI
hanging the system) seem to contradict this. That's bad.
--
pozdrawiam |"Help me master, I felt the burning twilight behind
[email protected]|those gates of stell..." --Perihelion, Prophecy Sequence