In <[EMAIL PROTECTED]> Derrick J Brashear
<[EMAIL PROTECTED]> writes:
>Earlier today I swapped an Athlon (tbird) 850 and an Epox 8KTA3 in for the
>dual Celeron I had, moving all the cards into the new system. One of these
>was a Promise PDC20267 with 4 40gb disks attached. The machine would
In [EMAIL PROTECTED] Derrick J Brashear
[EMAIL PROTECTED] writes:
Earlier today I swapped an Athlon (tbird) 850 and an Epox 8KTA3 in for the
dual Celeron I had, moving all the cards into the new system. One of these
was a Promise PDC20267 with 4 40gb disks attached. The machine would not
I am struggling to get an IBM DTLA-307045 drive attached to a
promise pdc20267 controller to work in DMA mode. Right now,
whenever I enable a DMA mode, I get timeouts when accessing
the drive.
I am using an 80-pin cable, that came with the Promise controller.
Mar 16 20:57:43 ask kernel:
I am struggling to get an IBM DTLA-307045 drive attached to a
promise pdc20267 controller to work in DMA mode. Right now,
whenever I enable a DMA mode, I get timeouts when accessing
the drive.
I am using an 80-pin cable, that came with the Promise controller.
Mar 16 20:57:43 ask kernel:
In <[EMAIL PROTECTED]> Alexander Viro
<[EMAIL PROTECTED]> writes:
>On Sun, 17 Dec 2000, Jorg de Jong wrote:
>> > >On 13 Dec 2000, Henrik [ISO-8859-1] Størner wrote:
>> > >
>> > >> Just to add a "me too" on this. I didn't report when I saw it last week
>> I'd like to second that. ME TOO !
>>
In [EMAIL PROTECTED] Alexander Viro
[EMAIL PROTECTED] writes:
On Sun, 17 Dec 2000, Jorg de Jong wrote:
On 13 Dec 2000, Henrik [ISO-8859-1] Størner wrote:
Just to add a "me too" on this. I didn't report when I saw it last week
I'd like to second that. ME TOO !
Since I switched to
In <[EMAIL PROTECTED]> Anton Petrusevich
<[EMAIL PROTECTED]> writes:
>Today I saw well-known "innd bug"(truncate(tm)), and my brother said
>he had seen it with -test12-pre7. I don't know about -test12-pre3,
>neither I nor my brother hadn't noticed it since -test10. But we could
>miss it with
In [EMAIL PROTECTED] Anton Petrusevich
[EMAIL PROTECTED] writes:
Today I saw well-known "innd bug"(truncate(tm)), and my brother said
he had seen it with -test12-pre7. I don't know about -test12-pre3,
neither I nor my brother hadn't noticed it since -test10. But we could
miss it with
In <[EMAIL PROTECTED]> Henrik Størner <[EMAIL PROTECTED]> writes:
>I discovered yesterday that printing does not work in 2.4.0-test12-pre4.
OK - mea culpa. It turned out to be a configuration problem: I had
been playing with the I2C support for lm_sensors, and in my attempt to
g
I discovered yesterday that printing does not work in 2.4.0-test12-pre4.
This is a pretty stock PC system with a printer on the parallel port.
Both parport and lp is compiled into the kernel - and the parport
appears to be detected OK, but the lp driver for some reason refuses
to use it:
[snip
I discovered yesterday that printing does not work in 2.4.0-test12-pre4.
This is a pretty stock PC system with a printer on the parallel port.
Both parport and lp is compiled into the kernel - and the parport
appears to be detected OK, but the lp driver for some reason refuses
to use it:
[snip
In [EMAIL PROTECTED] Henrik Størner [EMAIL PROTECTED] writes:
I discovered yesterday that printing does not work in 2.4.0-test12-pre4.
OK - mea culpa. It turned out to be a configuration problem: I had
been playing with the I2C support for lm_sensors, and in my attempt to
get it working I had
My 2.4.0-test10-pre4 box died overnight, apparently around 4 am when the
nightly cron-jobs run. The last thing logged looks interesting:
kernel BUG at vmscan.c:102!
invalid operand:
CPU:0
EIP:0010:[try_to_swap_out+252/796]
EFLAGS: 00010286
eax: 001c ebx: 0100 ecx:
My 2.4.0-test10-pre4 box died overnight, apparently around 4 am when the
nightly cron-jobs run. The last thing logged looks interesting:
kernel BUG at vmscan.c:102!
invalid operand:
CPU:0
EIP:0010:[try_to_swap_out+252/796]
EFLAGS: 00010286
eax: 001c ebx: 0100 ecx:
In <[EMAIL PROTECTED]> "Jeff V. Merkey"
<[EMAIL PROTECTED]> writes:
>On Fri, Oct 06, 2000 at 07:55:22AM +0200, Henrik Størner wrote:
>> In <[EMAIL PROTECTED]> Christoph Lameter
><[EMAIL PROTECTED]> writes:
>>
>> >Comparing CD
In [EMAIL PROTECTED] "Jeff V. Merkey"
[EMAIL PROTECTED] writes:
On Fri, Oct 06, 2000 at 07:55:22AM +0200, Henrik Størner wrote:
In [EMAIL PROTECTED] Christoph Lameter
[EMAIL PROTECTED] writes:
Comparing CD contents with the original after burning showed mismatches 4
times in a r
In <[EMAIL PROTECTED]> Christoph Lameter
<[EMAIL PROTECTED]> writes:
>Comparing CD contents with the original after burning showed mismatches 4
>times in a row. Booted into linux 2.2.18 and everything is fine.
I had quite a few problems burning the Red Hat 7 ISO images while
running
In [EMAIL PROTECTED] Christoph Lameter
[EMAIL PROTECTED] writes:
Comparing CD contents with the original after burning showed mismatches 4
times in a row. Booted into linux 2.2.18 and everything is fine.
I had quite a few problems burning the Red Hat 7 ISO images while
running
In <[EMAIL PROTECTED]> safemode <[EMAIL PROTECTED]> writes:
[mega snip]
See http://www.unicom.com/pw/reply-to-harmful.html for all of the
good reasons why the vger lists behave just the way they should.
--
Henrik Storner | "Crackers thrive on code secrecy. Cockcroaches breed
<[EMAIL
In <[EMAIL PROTECTED]> Russell King <[EMAIL PROTECTED]>
writes:
>NAT: 3 dropping untracked packet c065d3a0 1 192.168.0.1 -> 192.168.0.9
I see loads of these, in a firewall (state matching) and SNAT setup.
When I send mail, I see them quite regularly. It is quite annoying,
since they get
In [EMAIL PROTECTED] Russell King [EMAIL PROTECTED]
writes:
NAT: 3 dropping untracked packet c065d3a0 1 192.168.0.1 - 192.168.0.9
I see loads of these, in a firewall (state matching) and SNAT setup.
When I send mail, I see them quite regularly. It is quite annoying,
since they get dumped to
On Sat, Sep 02, 2000 at 01:58:58PM -0700, Linus Torvalds wrote:
[ext2 truncate bug which caused the innd file corruption may
also affect other filesystems]
> Anyway, the way to test if you have the bug is this simple program from
> Al Viro who noticed the bug and has the fix - notice that you
On Sat, Sep 02, 2000 at 01:58:58PM -0700, Linus Torvalds wrote:
[ext2 truncate bug which caused the innd file corruption may
also affect other filesystems]
Anyway, the way to test if you have the bug is this simple program from
Al Viro who noticed the bug and has the fix - notice that you
In <[EMAIL PROTECTED]> Linus Torvalds
<[EMAIL PROTECTED]> writes:
>On Sat, 2 Sep 2000, Rik van Riel wrote:
>>
>> In fact, I plan to spend most of my time trying to track down
>> the 2 VM problems on tytso's list:
>>
>> 1) the innd data corruption bug
>This, I think, was due to a bug in ext2
In [EMAIL PROTECTED] Linus Torvalds
[EMAIL PROTECTED] writes:
On Sat, 2 Sep 2000, Rik van Riel wrote:
In fact, I plan to spend most of my time trying to track down
the 2 VM problems on tytso's list:
1) the innd data corruption bug
This, I think, was due to a bug in ext2 truncate. If so,
25 matches
Mail list logo
