Alexey Dobriyan [EMAIL PROTECTED] wrote:
> On Thu, Aug 25, 2005 at 02:48:55PM -0700, Lawrence Walton wrote:
> > I just switched out motherboards and CPUs From a Asus K8v SE Deluxe
> > to a to a Asus A8V-E Deluxe, and a 754 pin 3200+ to a 934 pin 3200+.
> > I am now havin
Alexey Dobriyan [EMAIL PROTECTED] wrote:
On Thu, Aug 25, 2005 at 02:48:55PM -0700, Lawrence Walton wrote:
I just switched out motherboards and CPUs From a Asus K8v SE Deluxe
to a to a Asus A8V-E Deluxe, and a 754 pin 3200+ to a 934 pin 3200+.
I am now having some fairly serious instability
Hi!
I just switched out motherboards and CPUs From a Asus K8v SE Deluxe
to a to a Asus A8V-E Deluxe, and a 754 pin 3200+ to a 934 pin 3200+.
I am now having some fairly serious instability issues. The system
locks up completely with no oops. After disabling CONFIGHIMEM and
Hi!
I just switched out motherboards and CPUs From a Asus K8v SE Deluxe
to a to a Asus A8V-E Deluxe, and a 754 pin 3200+ to a 934 pin 3200+.
I am now having some fairly serious instability issues. The system
locks up completely with no oops. After disabling CONFIGHIMEM and
Jeff Garzik [EMAIL PROTECTED] wrote:
> maxer wrote:
> >What is the status of sk98lin? Do we have to wait until Syskonnect gets
> >their act together
> >and write a new driver for 2.6.10?
> >
> >Their latest is Oct 2004 and not at all compatible with 2.6.10 and beyond.
>
> I've been telling
Jeff Garzik [EMAIL PROTECTED] wrote:
maxer wrote:
What is the status of sk98lin? Do we have to wait until Syskonnect gets
their act together
and write a new driver for 2.6.10?
Their latest is Oct 2004 and not at all compatible with 2.6.10 and beyond.
I've been telling SysKonnect for
Hello all
2.4.2-ac21 seems to have a couple problems. First the fs was acting very
strangely, while compiling; the compiler complained about being unable
to find files and directory's that existed. I was able to cd to those
directory's and see the files with ls, (I was recompiling ac20 at the
Hello all
2.4.2-ac21 seems to have a couple problems. First the fs was acting very
strangely, while compiling; the compiler complained about being unable
to find files and directory's that existed. I was able to cd to those
directory's and see the files with ls, (I was recompiling ac20 at the
Samba appears to be broken in 2.4.1-ac14
No odd dmesg, modules load fine just nothing is there.
Works in 2.4.1-ac7 just fine.
Versions follow
Samba version 2.0.7
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in
Samba appears to be broken in 2.4.1-ac14
No odd dmesg, modules load fine just nothing is there.
Works in 2.4.1-ac7 just fine.
Versions follow
Samba version 2.0.7
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in
I was doing nothing out of the ordinary wen my system froze.
Here is the oops
Yes that is the correct system map btw.
If anyone needs anything more please ask.
ksymoops 2.3.4 on i686 2.4.0-test13-pre3. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
I was doing nothing out of the ordinary wen my system froze.
Here is the oops
Yes that is the correct system map btw.
If anyone needs anything more please ask.
ksymoops 2.3.4 on i686 2.4.0-test13-pre3. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
Andrew Morton [[EMAIL PROTECTED]] wrote:
> Andrew Morton wrote:
> >
> > Andrew Morton wrote:
> > >
> > > I bet this'll catch it:
> > >
> > > --- include/linux/list.h.orig Fri Dec 1 08:33:36 2000
> > > +++ include/linux/list.hFri Dec 1 08:33:55 2000
> > > @@ -90,6 +90,7 @@
> > >
Andrew Morton [[EMAIL PROTECTED]] wrote:
Andrew Morton wrote:
Andrew Morton wrote:
I bet this'll catch it:
--- include/linux/list.h.orig Fri Dec 1 08:33:36 2000
+++ include/linux/list.hFri Dec 1 08:33:55 2000
@@ -90,6 +90,7 @@
static __inline__ void
my system has been acting slightly odd on all the pre 12 kernels
with the fs going read only with out any messages until now.
no opps or anything like that, but I did get this just now.
Nov 29 16:03:12 the-penguin kernel: EXT2-fs error (device sd(8,2)): ext2_readdir: bad
entry in directory
my system has been acting slightly odd on all the pre 12 kernels
with the fs going read only with out any messages until now.
no opps or anything like that, but I did get this just now.
Nov 29 16:03:12 the-penguin kernel: EXT2-fs error (device sd(8,2)): ext2_readdir: bad
entry in directory
It appears that SCSI cdroms as modules are broken in 2.4.0-test8.
It works fine 2.4.0-test7.
cat /dev/scd0
cat: /dev/scd0: No such device
Module Size Used by
isofs 20168 0 (autoclean)
sg 21712 0 (unused)
sr_mod 13224
It appears that SCSI cdroms as modules are broken in 2.4.0-test8.
It works fine 2.4.0-test7.
cat /dev/scd0
cat: /dev/scd0: No such device
Module Size Used by
isofs 20168 0 (autoclean)
sg 21712 0 (unused)
sr_mod 13224
18 matches
Mail list logo
