Hello,
On Thu, 03 Oct 2002 10:26:44 +0400
"Vasil Petrov" <[EMAIL PROTECTED]> wrote:
> Shte im pisha. No smqtam, che prosto neshto se e skapalo. Trudno e da
> razbera kakvo i saotvetno da podam malko poveche info po vaprosa.
Veroiatnosta da ima bug v bash e pochti nula v sluchaia, grymva i exitva.
Problema e tova dolu.
> Sistemata si raboteshe dosta vreme bez nikakvi problemi i izvednuj se
> skapa, kakto i s drugite mashini. Sluchava mi se _samo_ sas Slackware
> 8.0, nai lesnoto e da si install Slack 8.1.1, no mi i interesno na
Moje li da kajesh tochna versia na kernel i config? Ne vsichki pomniat kakvo
tochno ima v slackware 8.0?
/usr/src/linux/REPORTING-BUGS pishe slednoto:
[1.] One line summary of the problem: - Kratko opisanie na problema
[2.] Full description of the problem/report: - Pulno opisanie na problema
[3.] Keywords (i.e., modules, networking, kernel): - Za kakvo se otnasia
[4.] Kernel version (from /proc/version): - VERSIA - cat /proc/version
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt) - Po dolu za oops (obiknovenno te
+ chast ot tezi 8 sa dostatychni v zavisimost kude e problema)
[6.] A small shell script or example program which triggers the
problem (if possible) - Example script / comandi - neshto koeto kato se napravi i
se poluchava oops.
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here) - izhoda na ver_linux
Example:
. /usr/src/linux/scripts/ver_linux
Linux alex 2.4.19 #3 Thu Jun 6 14:19:04 EEST 2002 i686 unknown
Gnu C egcs-2.91.66
[cut]
Sh-utils 2.0
Modules Loaded esssolo1 8139too
[7.2.] Processor information (from /proc/cpuinfo): cat /proc/cpuinfo
[7.3.] Module information (from /proc/modules): cat /proc/modules
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem) - cat
/proc/....
[7.5.] PCI information ('lspci -vvv' as root) - Tova dava informacia za kakvi devices
ima na PCI i tehnite parametri
[7.6.] SCSI information (from /proc/scsi/scsi) - cat /proc/....
[7.7.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant): - Neshto drugo koeto e svyrzano s oops ?
[X.] Other notes, patches, fixes, workarounds:
T.e. za da razberesh tova koeto ti e interesno triabva da se napravi tova tova
i tova, vsichko si go pishe :)
Ne vsichko e neobhodimo, ako se otsee samo vajnoto info e po dobre no za pulnota.
> kakvo se duljat tiq zabivki. Spored oops-tracing.txt tova e problem v
> nqkoi driver. Dori i sega kato pisha maila i cheta oops-tacin.txt
Spored oops-tracing.txt nikude ne se spomenava za problem v neshto konkretno
driver/etc.
pishe kak ot oops moje da se izvadi poleznata informacia ot oops:
Install ksymoops from
ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops
Read the ksymoops man page.
ksymoops < the_oops.txt
Instaliraite si ksymoops ot ... Prochetete man page sled tova pusnete oops-texta.txt
prez ksymoops.
Problema e slednia za da se razbere neshto ot oops-a triabvat:
Call trace s imena na funkcii, tezi addresi koito ima dolu se smeniat pri vsiaka
kompilacia i ne pomagat.
Primer za neshto koeto vyrshi rabota:
Call Trace:
[<c013232f>]__kmem_cache_alloc+0xaf/0xc0
[<c01318cd>]kmem_cache_alloc+0xd/0x20
[<c01f7a70>]blk_init_free_list+0x70/0xe0
[<c010ac82>]setup_irq+0xa2/0xe0
[<c01f7aed>]blk_init_queue+0xd/0x100
[<c020c688>]ide_init_queue+0x28/0x80
[<c0213680>]do_ide_request+0x0/0x20
[<c020c890>]init_irq+0x1b0/0x360
[<c020ccc6>]hwif_init+0xc6/0x280
[<c020cfa7>]ideprobe_init+0xe7/0x100
[<c0105075>]init+0x35/0x160
[<c0105040>]init+0x0/0x160
[<c0107081>]kernel_thread_helper+0x5/0x24
Addressite i imenata gi ima i v edin file koito se kazva System.map i sedi
obiknovenno v /boot i se poluchava v
/usr/src/linux/System.map sled compilacia na kernel, ako niama mnogo murzel i ksymoops
moje i ot tam da se izvadiat.
(ksymoops iska pravilen System.map za da izvadi veren output). Osven ksymoops syshto
i klogd pravi tova i otiva v syslog-a,
no za da stane triabva da ima veren System.map v /boot.
> izbozq :> Unable to handle kernel paging request at virtual address
> f1487474*pde = 00000000
> Oops: 0002
> CPU: 0
> EIP: 0010:[<c01231b4>] Not tainted
^^^^^^^^^^^^^^
Tova e sledvashtoto vajno neshto:
gdb /usr/src/linux/vmlinux
gdb> disassemble 0xc01231b4
<output koito pokazva kude tochno e grymnalo vyv funkciata i tuk veche pomagat
registrite po dolu>
> EFLAGS: 00010002
> eax: 00000000 ebx: 0c10e8e7 ecx: c104d0c0 edx: 00000001
> esi: c107f580 edi: 00000282 ebp: 000000dc esp: c0299e4c
> ds: 0018 es: 0018 ss: 0018
> Process kjournald (pid: 21, stackpage=c0299000)
^^^^^^^^^ tova ako ne se luja e ext3 - polzva li se?
Dolu gore e tova, ostanaloto sa predpolojenia.
Userspace programite (bash,pam, etc) kakvoto i da praviat ne triabva da oopsva
kernel-a.
Praviloto e che kernel-a ne viarva na tova koeto idva ot userspace, t.e. ako mu se
podavat
kofti danni triabva da vryshta greshka, a ne da gyrmi.
--
have fun,
alex
============================================================================
A mail-list of Linux Users Group - Bulgaria (bulgarian linuxers).
http://www.linux-bulgaria.org - Hosted by Internet Group Ltd. - Stara Zagora
To unsubscribe: http://www.linux-bulgaria.org/public/mail_list.html
============================================================================
