[2.2.13pre12] hard freez

Peter Hanecak (hanecak@megaloman.com)
Tue, 28 Sep 1999 13:29:10 +0200 (CEST)


while i think it is related (because hang occured while making same
operation as earlier, but in another phase), i'm replying to my previous
report about "null pointer exception in do_IRQ".

> bug-report in "/usr/src/linux/REPORTING-BUGS" format
>
> [1.]
>
> i got an kernel oops in do_IRQ

this time there was no message in /var/log/messages. just machine went
frozen.

> [2.]
>
> after copying kernel source tree from one directory (/usr/src/linux-2.2.12)
> to another (/usr/src/linux-2.2.13pre12) while preparing before applying AC
> patch my mechine hard froze twice. firtst time i found OOPs entries in
> /var/log/messages. second time it was without any log entry. freeze occured
> in the process of copying (first time) and shortly after copying process
> finished (second time).
>
> i was working on local ext2 filesystem.

while now i'm running 2.2.13pre12 and i just downloaded 2.2.13pre14 i
performed following as root in Eterm under Xwindows:

$ cd /usr/src
$ ls
linux linux-2.2.12 linux-2.2.13p12 linux.13p12 megaloman redhat
[^ link to linux-2.2.13p12; ^ link to linux-2.2.13p12]
$ mv linux-2.2.13p12 linux-2.2.13p14
$ rm linux; ln -s linux-2.2.13p14 linux
$ rm linux.13p12; ln -s linux-2.2.13p14 linux.13p14
$ cd linux
$ rm -rf *

after that machine hard freezed.

when using 2.2.13pre11 machine freezed when perforing copy operation
(cp -r /usr/src/linux-2.2.12/* /usr/src/linux-2.2.13pre12 - but not using
'cp' but using midnight commander) - that was during upgrade from
2.2.13pre11 to 2.2.13pre12.

> [4.]
>
> Linux version 2.2.13pre12 (root@m1.megaloman.sk) (gcc version egcs-2.91.66 \
> 19990314/Linux (egcs-1.1.2 release)) #2 Sun Sep 26 16:00:31 EDT 1999

now i have to make correction: previously it was 2.2.13pre11

this time i have:

Linux version 2.2.13pre12 (root@m1.megaloman.sk) (gcc version egcs-2.91.66 \
19990314/Linux (egcs-1.1.2 release)) #2 Sun Sep 26 16:00:31 EDT 1999

> [6.]

see section [2.]

> [7.]

not changed since previous report

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/