I have 3 2gb disks in an lvm group (vg is disks)
I have an lv of 1.6gb (misc) with reiserfs mounted /lvm/misc
I cp /dev/zero /lvm/misc
If these 3 drives are on the internal qlogic isp controller, I have no
problems.
If these 3 drives are on the adaptec aha-2940UW, I get an oops (reply for
oops
This is just a sample of what I get:
es1371: sample rate converter timeout r = 0xeb970800
es1371: sample rate converter timeout r = 0x0087
es1371: sample rate converter timeout r = 0x0097
es1371: sample rate converter timeout r = 0xea80
This card is on the secondary PCI bus.
System:
This is just a sample of what I get:
es1371: sample rate converter timeout r = 0xeb970800
es1371: sample rate converter timeout r = 0x0087
es1371: sample rate converter timeout r = 0x0097
es1371: sample rate converter timeout r = 0xea80
This card is on the secondary PCI bus.
System:
I have 3 2gb disks in an lvm group (vg is disks)
I have an lv of 1.6gb (misc) with reiserfs mounted /lvm/misc
I cp /dev/zero /lvm/misc
If these 3 drives are on the internal qlogic isp controller, I have no
problems.
If these 3 drives are on the adaptec aha-2940UW, I get an oops (reply for
oops
What happens the day the machine hits 497 days uptime?
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
What happens the day the machine hits 497 days uptime?
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
In 2.4.0, the camera I have no longer works. It did in test9 I believe.
fccid is ksx-x9903
I would have mailed the author, but I couldn't remember his address.
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe
I've noticed, everytime I use a cardbus card, pcmcia-cs uses the name of the
driver instead of eth0 (or eth1).
If I need to upgrade pcmcia-cs, that's fine, but it appears to be a bug.
pcmcia-cs version: 3.1.20 (debian v2)
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
I've noticed, everytime I use a cardbus card, pcmcia-cs uses the name of the
driver instead of eth0 (or eth1).
If I need to upgrade pcmcia-cs, that's fine, but it appears to be a bug.
pcmcia-cs version: 3.1.20 (debian v2)
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
In 2.4.0, the camera I have no longer works. It did in test9 I believe.
fccid is ksx-x9903
I would have mailed the author, but I couldn't remember his address.
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe
> Not very portable at all...
>
> hpux = HP/UX 10.2
>
> hpux:~$ mkdir foo
> hpux:~$ cd foo
> hpux:~/foo$ rmdir "`pwd`"
> rmdir: /home/blc/foo: Cannot remove mountable directory
> hpux:~/foo$ rmdir .
> rmdir: cannot remove .. or .
> hpux:~/foo$ rmdir /home/blc/foo
> rmdir: /home/blc/foo: Cannot
Not very portable at all...
hpux = HP/UX 10.2
hpux:~$ mkdir foo
hpux:~$ cd foo
hpux:~/foo$ rmdir "`pwd`"
rmdir: /home/blc/foo: Cannot remove mountable directory
hpux:~/foo$ rmdir .
rmdir: cannot remove .. or .
hpux:~/foo$ rmdir /home/blc/foo
rmdir: /home/blc/foo: Cannot remove
This is 2.4.0-test12pre6. Wondering if anyone's looked into this yet. I
have the 0.9LVM patch and REISERFS patch. I have attached the decoded oops
--
Lab tests show that use of micro$oft causes cancer in lab animals
ksymoops 2.3.4 on alpha 2.4.0-test12-pre6-LVM-REISERFS. Options used
This is 2.4.0-test12pre6. Wondering if anyone's looked into this yet. I
have the 0.9LVM patch and REISERFS patch. I have attached the decoded oops
--
Lab tests show that use of micro$oft causes cancer in lab animals
ksymoops 2.3.4 on alpha 2.4.0-test12-pre6-LVM-REISERFS. Options used
I really hate to ask on the list, but if I was to buy a usb web cam, what
would be a good choice?
I would have tried linux-usb, but I didn't know where it was, sorry.
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line
I really hate to ask on the list, but if I was to buy a usb web cam, what
would be a good choice?
I would have tried linux-usb, but I didn't know where it was, sorry.
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line
> Hello,
> Just writing in to report a bug in 2.4.0-test12.
> Hardware:
> PCI-Matrox_Mill
> PCI-Adaptec 39160 / 160M scsi card
> PCI-Generic TNT-2 card
> PCI-Sound blaster -128 (es1370)
>
> CPU 21164a - Alpha
>
> Problem:
> There is a race condition in the aic7 driver that
Hello,
Just writing in to report a bug in 2.4.0-test12.
Hardware:
PCI-Matrox_Mill
PCI-Adaptec 39160 / 160M scsi card
PCI-Generic TNT-2 card
PCI-Sound blaster -128 (es1370)
CPU 21164a - Alpha
Problem:
There is a race condition in the aic7 driver that causes the
> What's the best way to capture (manually or otherwise) a rather long
> oops that scrolls off my console without having a second machine?
>
> I'm gonna try to compile in a framebuffer and use a high resolution and
> see if that'll hold it all when I get back later today.
Tried using a printer?
What's the best way to capture (manually or otherwise) a rather long
oops that scrolls off my console without having a second machine?
I'm gonna try to compile in a framebuffer and use a high resolution and
see if that'll hold it all when I get back later today.
Tried using a printer?
> Daryll> On Sat, Dec 09, 2000 at 09:34:59PM -0500, David Feuer wrote:
> >> For what it's worth, I absolutely agree with this. I have the same
> >> impression when I just see the word "dangerous".
>
> Daryll> Why not call a spade a spade and label it BROKEN. I do think
> Daryll> that's stronger
Daryll On Sat, Dec 09, 2000 at 09:34:59PM -0500, David Feuer wrote:
For what it's worth, I absolutely agree with this. I have the same
impression when I just see the word "dangerous".
Daryll Why not call a spade a spade and label it BROKEN. I do think
Daryll that's stronger than
I'm not sure if this happened w/o reiserfs compiled or not. I didn't leave
it running over night (crash happened about 07:00)
Last thing in the log before this was st being loaded (I have a backup that
starts at 06:00) I don't believe this has anything to do with the crash,
but the machine
I'm not sure if this happened w/o reiserfs compiled or not. I didn't leave
it running over night (crash happened about 07:00)
Last thing in the log before this was st being loaded (I have a backup that
starts at 06:00) I don't believe this has anything to do with the crash,
but the machine
I'm glad to say that this is the first 2.4 kernel that works on my noritake
alpha with a pci-pci bridge.
I have a small problem. If I reboot, the srm console can't boot from dka0.
Doing a: show dev
doesn't list any of the hard drives in the machine.
doing an init causes it to reset and find all
Andrew Morton wrote:
> Wakko Warner wrote:
> >
> > > - pre6:
> > > - Andrew Morton: exec_usermodehelper fixes
> >
> > pre4 oopsed all over the place on my alpha with modules and autoloading
> > turned on as soon as it mounted / and freed unused
> - pre6:
> - Andrew Morton: exec_usermodehelper fixes
pre4 oopsed all over the place on my alpha with modules and autoloading
turned on as soon as it mounted / and freed unused memory. I take it this
was seen on i386 as well?
Will try pre6.
--
Lab tests show that use of micro$oft
- pre6:
- Andrew Morton: exec_usermodehelper fixes
pre4 oopsed all over the place on my alpha with modules and autoloading
turned on as soon as it mounted / and freed unused memory. I take it this
was seen on i386 as well?
Will try pre6.
--
Lab tests show that use of micro$oft causes
I'm glad to say that this is the first 2.4 kernel that works on my noritake
alpha with a pci-pci bridge.
I have a small problem. If I reboot, the srm console can't boot from dka0.
Doing a: show dev
doesn't list any of the hard drives in the machine.
doing an init causes it to reset and find all
> Most architectures dump their code as a string of bytes and print the
> code after the registers and trace back. Alpha dumps the code before
> the trace and also decodes the instructions which really confuses
> ksymoops. Somebody changed 'Trace: ' to 'Trace:' between 2.2 and 2.4
> kernels so
PCI patches that were added between pre3 and pre4 allow me to boot the
kernel on my noritake alpha. Once it boots, however, it oops's in the
swapper. I've tried a few times in the past to use ksymoops on oops's on
the alpha arch, but it doesn't appear to work. (I'm using the ksymoops
that's
PCI patches that were added between pre3 and pre4 allow me to boot the
kernel on my noritake alpha. Once it boots, however, it oops's in the
swapper. I've tried a few times in the past to use ksymoops on oops's on
the alpha arch, but it doesn't appear to work. (I'm using the ksymoops
that's
Most architectures dump their code as a string of bytes and print the
code after the registers and trace back. Alpha dumps the code before
the trace and also decodes the instructions which really confuses
ksymoops. Somebody changed 'Trace: ' to 'Trace:' between 2.2 and 2.4
kernels so
> > It just oops continuously. It finds the scsi drives and says it's enabling
> > a few pci devices but it scrolls too fast to see what it really does
>
> If it finds scsi drives, PCI setup is probably ok. There could be
> a lot of other problems - too much changes since 2.2.
>
> Capturing
It just oops continuously. It finds the scsi drives and says it's enabling
a few pci devices but it scrolls too fast to see what it really does
If it finds scsi drives, PCI setup is probably ok. There could be
a lot of other problems - too much changes since 2.2.
Capturing kernel
> > Ok, I won't have time this morning to try it, but I'll try it when I get off
> > work
>
> Ok. If that patch won't help, here is another one - setting
> cacheline/latency also might cause a trouble.
the patch helped, but it ooped after finding the last scsi drive (the
cdrom). I'll try
Ok, I won't have time this morning to try it, but I'll try it when I get off
work
Ok. If that patch won't help, here is another one - setting
cacheline/latency also might cause a trouble.
the patch helped, but it ooped after finding the last scsi drive (the
cdrom). I'll try removing the
> - pre2:
> - Richard Henderson: PCI bridge initialization on alpha
Doesn't boot on noritake alpha.
It gets to POSIX conformance testing by UNIFIX
and hard locks. the halt switch doesn't even work.
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe
- pre2:
- Richard Henderson: PCI bridge initialization on alpha
Doesn't boot on noritake alpha.
It gets to POSIX conformance testing by UNIFIX
and hard locks. the halt switch doesn't even work.
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe
The changes between test10 and test11 broke st.o, nfs.o, runrpc.o and
lockd.o It's the same unresolved symbol every time:
# insmod st
Using /lib/modules/2.4.0-test11/kernel/drivers/scsi/st.o
/lib/modules/2.4.0-test11/kernel/drivers/scsi/st.o: unresolved symbol __up
The changes between test10 and test11 broke st.o, nfs.o, runrpc.o and
lockd.o It's the same unresolved symbol every time:
# insmod st
Using /lib/modules/2.4.0-test11/kernel/drivers/scsi/st.o
/lib/modules/2.4.0-test11/kernel/drivers/scsi/st.o: unresolved symbol __up
I noticed 2 things. One is quite annoying.
1) sunlance:
Nov 19 19:09:49 sparq kernel: eth0: Carrier Lost, trying AUI
Nov 19 19:09:52 sparq kernel: eth0: Carrier Lost, trying TPE
This has been going on for some time since it has been up. But I think
something oopsed to cause this
2) the oops.
I noticed 2 things. One is quite annoying.
1) sunlance:
Nov 19 19:09:49 sparq kernel: eth0: Carrier Lost, trying AUI
Nov 19 19:09:52 sparq kernel: eth0: Carrier Lost, trying TPE
This has been going on for some time since it has been up. But I think
something oopsed to cause this
2) the oops.
> It was posted to lkml, so no link (except if you want to dig through
> lkml mail archives).
It booted but then it oops'ed before userland I belive. I tried it this
morning and didn't have much time. It did find the scsi controller (which
is across the bridge) and the drives attached so it
> It was posted to lkml, so no link (except if you want to dig through
> lkml mail archives).
It booted but then it oops'ed before userland I belive. I tried it this
morning and didn't have much time. It did find the scsi controller (which
is across the bridge) and the drives attached so it
It was posted to lkml, so no link (except if you want to dig through
lkml mail archives).
It booted but then it oops'ed before userland I belive. I tried it this
morning and didn't have much time. It did find the scsi controller (which
is across the bridge) and the drives attached so it does
It was posted to lkml, so no link (except if you want to dig through
lkml mail archives).
It booted but then it oops'ed before userland I belive. I tried it this
morning and didn't have much time. It did find the scsi controller (which
is across the bridge) and the drives attached so it does
> > I'm seeing this as well, but only with PIII Xeon systems, not PII
> > Xeon. Every single timer interrupt on any CPU is accompanied by a NMI
> > and LOC increment on every CPU.
> >
> >CPU0 CPU1
> > 0: 146727 153389IO-APIC-edge timer
> > [...]
> > NMI:
I'm seeing this as well, but only with PIII Xeon systems, not PII
Xeon. Every single timer interrupt on any CPU is accompanied by a NMI
and LOC increment on every CPU.
CPU0 CPU1
0: 146727 153389IO-APIC-edge timer
[...]
NMI: 300035
> > [Wakko Warner]
> > > While this subject is fresh, what would be wrong with using the
> > > entire drive as opposed to creating a partition and adding the
> > > partition to the raid?
> >
> > Does it autodetect an entire drive? The autodetect log
> > I did upgrade that and it didn't help anything.
>
> Was your glibc compiled against 2.4 kernel headers?
That I do not know. it's v 2.1.99 that came with debian in the past week
or so
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list:
> > I attempted to create a 4gb sparce file with dd. It failed.
> > I created one that was 2.1gb in size which worked. Then I appeneded more
> > junk to the end of the file making it over 2.2gb.
> >
> > doing an ls -l shows:
> > ls: x: Value too large for defined data type
> >
> > NOTE: this
I attempted to create a 4gb sparce file with dd. It failed.
I created one that was 2.1gb in size which worked. Then I appeneded more
junk to the end of the file making it over 2.2gb.
doing an ls -l shows:
ls: x: Value too large for defined data type
NOTE: this worked in
I did upgrade that and it didn't help anything.
Was your glibc compiled against 2.4 kernel headers?
That I do not know. it's v 2.1.99 that came with debian in the past week
or so
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send
I attempted to create a 4gb sparce file with dd. It failed.
I created one that was 2.1gb in size which worked. Then I appeneded more
junk to the end of the file making it over 2.2gb.
doing an ls -l shows:
ls: x: Value too large for defined data type
NOTE: this worked in 2.4.0-test6 and I
> > Hi,
> > After I create a RAID setup on the drives,The
> > superblock will be generated at the end of the drives.
> > If I move these drives to other linux system, will
> > this
> > system recognise the RAID setup without reconfiguring
> > the Linux ?
>
> If the CHS / LBA settings are the
Hi,
After I create a RAID setup on the drives,The
superblock will be generated at the end of the drives.
If I move these drives to other linux system, will
this
system recognise the RAID setup without reconfiguring
the Linux ?
If the CHS / LBA settings are the same, and the
I attempted to create a 4gb sparce file with dd. It failed.
I created one that was 2.1gb in size which worked. Then I appeneded more
junk to the end of the file making it over 2.2gb.
doing an ls -l shows:
ls: x: Value too large for defined data type
NOTE: this worked in 2.4.0-test6 and I
> Trying to compile the current kernel (test10-pre4) with:
>
> > make clean
> > make -j 2 bzImages modules modules_install
>
> will try to install the modules before they are built...
> This has previously been working (at least in early testX kernels).
I've done it before when I wasn't
Trying to compile the current kernel (test10-pre4) with:
make clean
make -j 2 bzImages modules modules_install
will try to install the modules before they are built...
This has previously been working (at least in early testX kernels).
I've done it before when I wasn't thinking,
Something higher than the one for kernel 2.2.11 I found it once, but I can't
find it again. (and people.redhat.com isn't accepting http connections)
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Something higher than the one for kernel 2.2.11 I found it once, but I can't
find it again. (and people.redhat.com isn't accepting http connections)
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Has anyone tried this board with any recent 2.2 or 2.4 kernel?
It has:
Onboard Intel 82559 Ethernet controller
Onboard Adaptec AIC-7899 dual channel Ultra160 SCSI controller
ServerWorks ServerSet III HE-SL Chipset
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To
Doesn't boot on alpha systems with pci-pci bridges. I sent a report about
this a couple days ago and noone responds.
> There's a test10-2 out there.
>
> Notable change to people Cc'd on this mail: this contains the fix for the
> vmalloc() and ioremap() race condition, which deletes the
Doesn't boot on alpha systems with pci-pci bridges. I sent a report about
this a couple days ago and noone responds.
There's a test10-2 out there.
Notable change to people Cc'd on this mail: this contains the fix for the
vmalloc() and ioremap() race condition, which deletes the set_pgdir()
Booting test9 gives me:
PCI: failed to allocate resource 0 for: Q Logic ISP1020
PCI: failed to allocate resource 0 for:
PCI: failed to allocate resource 0 for: <3com card>
Then it gets to:
Net4: Unix domain sockets 1.0/SMP for Linux NET4.0.
and hard locks
this is an alphaserver 1000a
Booting test9 gives me:
PCI: failed to allocate resource 0 for: Q Logic ISP1020
PCI: failed to allocate resource 0 for: dec tulip card
PCI: failed to allocate resource 0 for: 3com card
Then it gets to:
Net4: Unix domain sockets 1.0/SMP for Linux NET4.0.
and hard locks
this is an alphaserver
Anyone tried this combination?
I had one small compile problem in the driver (which was a return code,
something about HASH, I forget now, but it's only defined for i386)
After that, mkfs and attempted to mount didn't work. the driver couldn't
find a valid fs on the drive.
I have successfully
Anyone tried this combination?
I had one small compile problem in the driver (which was a return code,
something about HASH, I forget now, but it's only defined for i386)
After that, mkfs and attempted to mount didn't work. the driver couldn't
find a valid fs on the drive.
I have successfully
I didn't try -test8 since it's LFS seems broken. But anyway, I was able to
crash a machine using ramfs when I filled it up. I got "Kernel panic:
attempted to kill init" on the console
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send
I didn't try -test8 since it's LFS seems broken. But anyway, I was able to
crash a machine using ramfs when I filled it up. I got "Kernel panic:
attempted to kill init" on the console
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send
> > PCI: Failed to allocate resource 1 for Symbios Logic Inc. (formerly
> >NCR) 53c875
> ...
> > This is a PCI layout as reported by 'lspci -tv':
> >
> > -[00]-+-0d.0-[01]--+-0a.0 Trident Microsystems 4DWave DX
> > |\-0d.0 Symbios Logic Inc. (formerly NCR) 53c875
>
PCI: Failed to allocate resource 1 for Symbios Logic Inc. (formerly
NCR) 53c875
...
This is a PCI layout as reported by 'lspci -tv':
-[00]-+-0d.0-[01]--+-0a.0 Trident Microsystems 4DWave DX
|\-0d.0 Symbios Logic Inc. (formerly NCR) 53c875
...
Any ideas
I'm compiling this kernel for a diskless machine. I have bootp configured
as the only way for the kernel to get the IP.
Here's the error:
cc -D__KERNEL__ -I/usr/src/linux/gohan/2.2.17/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -D__SMP__
-pipe
I'm compiling this kernel for a diskless machine. I have bootp configured
as the only way for the kernel to get the IP.
Here's the error:
cc -D__KERNEL__ -I/usr/src/linux/gohan/2.2.17/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -D__SMP__
-pipe
> The organization I do some work for purchased a rackmount server from
> Dell with the intent of running some webconferencing software under
> Linux. The salesman we had spoken to assured us that Linux fully
> supported the machine. Yeah... Right... :)
>
> Now it seems I'm stuck with a
The organization I do some work for purchased a rackmount server from
Dell with the intent of running some webconferencing software under
Linux. The salesman we had spoken to assured us that Linux fully
supported the machine. sarcasm Yeah... Right... /sarcasm :)
Now it seems I'm stuck
I have an alpha noritake that won't run any 2.4.0-test kernel (last 2 tried
were -test6 and 7)
7 seems to think that all pci devices are on irq 0
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
-test7 was the first one I tried that actually booted, the rest just froze.
I only tried 2 kernels. The first was compiled with
CONFIG_ALPHA_LEGACY_START_ADDRESS set to n, and the 2nd was with y.
First was -test6
when booting -test7, it can't find any IRQs for the PCI devices.
This is an
-test7 was the first one I tried that actually booted, the rest just froze.
I only tried 2 kernels. The first was compiled with
CONFIG_ALPHA_LEGACY_START_ADDRESS set to n, and the 2nd was with y.
First was -test6
when booting -test7, it can't find any IRQs for the PCI devices.
This is an
201 - 280 of 280 matches
Mail list logo
