Yes, I am using 2.0.33 and I can say that my system is lightly loaded.
Since this only happens on forced check I can live with a reboot once in a
while...my previous system was win95 ;)
Thanks
> This is common with 2.0.33, is that the kernel version you are using?
> Also, just to make folks awa
I don't think it's debian specific and really a big problem...just
curious. Sometimes when booting I get this message just after the swap
partitions are initialized, so it must be when fsck is running.
The booting process goes ok to the end and the system is stable. It seems
to occur only when I h
Brandon Mitchell wrote:
>
> Kernel 2.0.30 changed the way it handles memory. It's supposed to be a
> stable kernel (by this I'm saying it's a 2.0.x and not a 2.1.x), but
> problems like this make me think it shouldn't be used in 1.3. Could you
> try downgrading to 2.0.29 and let me (or the whole
On Wed, 28 May 1997, Leslie Mikesell wrote:
> I got this recently when running in single-user mode doing mke2fs on
> a 9 gig drive, but I think my swap space wasn't activated. Has the
> install package activated swap at this point?
Yes, basically this occurs "following the prompts" when installi
29 and let me (or the whole list) know if it
> > works?
>
> This isn't the same situation, but...
>
> I've got an spare machine here, where I've been installing and
> reinstalling Debian 1.3, using the lastest available disks. Every time I
> make the fi
t; try downgrading to 2.0.29 and let me (or the whole list) know if it
> works?
This isn't the same situation, but...
I've got an spare machine here, where I've been installing and
reinstalling Debian 1.3, using the lastest available disks. Every time I
make the file system, I g
Does this by chance happen when updatedb is run from the cron script? I
had this problem a while ago ... I had to add a 32 MB temporary swap
file to solve the problem. Nowadays we run on a PPro with lots of RAM,
so I haven't seen these problems ... even the home machine has 32 MB.
Good Luck!
--
Brandon Mitchell wrote:
>
> Kernel 2.0.30 changed the way it handles memory. It's supposed to be a
> stable kernel (by this I'm saying it's a 2.0.x and not a 2.1.x), but
> problems like this make me think it shouldn't be used in 1.3. Could you
> try downgrading to 2.0.29 and let me (or the whole
ion is correct.
>
> > I installed debian on my computer last week. I left it sitting for the
> > weekend. When I returned, I found the following message updating every so
> > often on my screen: "couldn't get a free page"
If my following of one of the kernel thread
Linus Torvalds
On Tue, 27 May 1997, David Miles wrote:
> I installed debian on my computer last week. I left it sitting for the
> weekend. When I returned, I found the following message updating every so
> often on my screen: "couldn't get a free page"
>
> When I
, David Miles wrote:
> I installed debian on my computer last week. I left it sitting for the
> weekend. When I returned, I found the following message updating every so
> often on my screen: "couldn't get a free page"
>
> When I hit enter, I get the following statem
I installed debian on my computer last week. I left it sitting for the
weekend. When I returned, I found the following message updating every so
often on my screen: "couldn't get a free page"
When I hit enter, I get the following statement "Out of memory for bash" a
12 matches
Mail list logo
