I recieved this oops after rearranging my SMP system to include a large
(>100GB) raid5 array and copying approximately 15GB to it. The array
was still synchronizing at the time.
Motherboard is MSI 694D. RAID array in question is attached to the
Promise 20265 chipset. No drives were attached to
Hardware is a Intel 440LX, with IDE disks, 96meg of memory, voodoo 2
graphics etc. Nothing remarkable.
For about 3 days now, it has been oopsing at least once a day. Each time
the machine eventually locks up in X. The kernel is a standard 2.2.18
linus kernel with Alsa drivers (version 0.5.10)
On Fri, Dec 01, 2000 at 12:46:18PM +, Alan Cox wrote:
> > I was able to reproduce this oops with a somewhat more reliable ksymoops (I was
>ready for this nasty bug this time). Looks like the problem is in the sockets
> > code.
>
> The traces so far all match one description , this one inclu
> I was able to reproduce this oops with a somewhat more reliable ksymoops (I was
>ready for this nasty bug this time). Looks like the problem is in the sockets
> code.
The traces so far all match one description , this one included. Its the
'something scribbled a while ago and I just walked th
Alan,
I was able to reproduce this oops with a somewhat more reliable ksymoops (I was ready
for this nasty bug this time). Looks like the problem is in the sockets
code.
See attached.
Jeff
ksymoops 0.7c on i686 2.2.18pre21. Options used
EIP: 0010: []
Using defaults from ksymoops -t elf32
Alan,
I have an Oops with 2.2.18-22 that only shows up on a Linux server
that's configured as a pppd dial in server with dynamic address
assignment (no DHCP). Host IP addresses are configured in an
options.ttyS0(192.168.0.1) and options.ttyS1(192.168.0.2) files in
/etc/ppp.
We caused the Oop
6 matches
Mail list logo
