* Re: Antwort: Re: Oops in Kernel 2.4.21-rc1
[not found] <OFC9BF3818.E07B98DB-ONC1256D33.004C27AB-C1256D33.004C6AE8@lidl.de>
@ 2003-05-27 14:07 ` Stephan von Krawczynski
0 siblings, 0 replies; 4+ messages in thread
From: Stephan von Krawczynski @ 2003-05-27 14:07 UTC (permalink / raw)
To: Werner.Beck; +Cc: linux-kernel
On Tue, 27 May 2003 15:54:40 +0200
Werner.Beck@Lidl.de wrote:
> unfortunately that is not possible at the moment...
>
>> Exchange the USB/ISDN part with a pci card and re-try with kernel -rc4.
>
>> Tell us if that works.
>
>> Regards,
>> Stephan
Well, what exactly do you expect to hear? There are about a million and one
possibilities about your problem. Most of them are hardware-related. Hoping
that you have already made sure that you have no defective RAM, controller,
mainboard or the like (unlikely since you mention two hosts) I would eliminate
additional risk factors like USB (always gives fun) and use the latest kernel.
Regards,
Stephan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Antwort: Re: Oops in Kernel 2.4.21-rc1
2003-05-27 13:22 Werner.Beck
@ 2003-05-27 14:01 ` Carl-Daniel Hailfinger
0 siblings, 0 replies; 4+ messages in thread
From: Carl-Daniel Hailfinger @ 2003-05-27 14:01 UTC (permalink / raw)
To: Werner.Beck; +Cc: linux-kernel
Werner.Beck@Lidl.de wrote:
> could that be the process mandb and aaa_base which where affected by the
> oops? How to disable this "feature"?
Open /etc/rc.config and try to find something like REINIT_MANDB and
DELETE_OLD_CATMAN and RUN_UPDATEDB. Set all of them to "no".
> Werner.Beck@Lidl.de wrote:
>
>>Hello,
>>I encountered a Kernel oops on two different PCs, both a configured
>>identical. The system uses an ISDN connection to an Internet ISP and then
>>establishes a VPN tunnel based on PPTP.
>>As far as I can see in /var/log/messages the problem occurred on both
>>system at the same time at 00:15, but not at the same day and not every
>>day. No special program is running at that time. Basically it is a SuSE
>>7.3 distribution, I made a Kernel upgrade.
>>Hardware is a Fujitsu Siemens N300 PC with an IDE (7200 Rpm), Intel 845GI
>>Motherboard, an ISDN PBX connected via USB to dial-up, the connection
>>wasn't established when the system oopsed.
>>Attached are some information.
Are you sure that you used the right System.map? Was this the first
Oops? Only the first Oops of a kernel is meaningful. All Oopses after
that are mostly useless for tracking down the bug.
ksymoops 2.4.2 on i686 2.4.21-rc1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.21-rc1/ (default)
-m /boot/System.map (specified)
Warning (compare_maps): ksyms_base symbol GPLONLY_ide_build_dmatable not
found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol GPLONLY_ide_destroy_dmatable
not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol GPLONLY_ide_dma_intr not found
in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol GPLONLY_ide_get_best_pio_mode
not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol
GPLONLY_ide_pci_register_driver not found in System.map. Ignoring
ksyms_base entry
Warning (compare_maps): ksyms_base symbol
GPLONLY_ide_pci_unregister_driver not found in System.map. Ignoring
ksyms_base entry
Warning (compare_maps): ksyms_base symbol GPLONLY_ide_pio_timings not
found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol GPLONLY_ide_set_xfer_rate not
found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol GPLONLY_ide_setup_dma not
found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol GPLONLY_ide_setup_pci_device
not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol GPLONLY_ide_setup_pci_devices
not found in System.map. Ignoring ksyms_base entry
Warning (compare_maps): ip_conntrack symbol
GPLONLY_ip_conntrack_expect_find_get not found in
/lib/modules/2.4.21-rc1/kernel/net/ipv4/netfilter/ip_conntrack.o.
Ignoring /lib/modules/2.4.21-rc1/ker
Warning (compare_maps): ip_conntrack symbol
GPLONLY_ip_conntrack_expect_put not found in
/lib/modules/2.4.21-rc1/kernel/net/ipv4/netfilter/ip_conntrack.o.
Ignoring /lib/modules/2.4.21-rc1/kernel/n
Warning (compare_maps): ip_conntrack symbol
GPLONLY_ip_conntrack_find_get not found in
/lib/modules/2.4.21-rc1/kernel/net/ipv4/netfilter/ip_conntrack.o.
Ignoring /lib/modules/2.4.21-rc1/kernel/net
Warning (compare_maps): ip_conntrack symbol GPLONLY_ip_conntrack_put not
found in
/lib/modules/2.4.21-rc1/kernel/net/ipv4/netfilter/ip_conntrack.o.
Ignoring /lib/modules/2.4.21-rc1/kernel/net/ipv4
May 27 00:15:10 DE-BC4212 kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
May 27 00:15:10 DE-BC4212 kernel: c012bb98
May 27 00:15:10 DE-BC4212 kernel: *pde = 00000000
May 27 00:15:10 DE-BC4212 kernel: Oops: 0000
May 27 00:15:10 DE-BC4212 kernel: CPU: 0
May 27 00:15:10 DE-BC4212 kernel: EIP: 0010:[kmem_cache_reap+212/504]
Not tainted
May 27 00:15:10 DE-BC4212 kernel: EFLAGS: 00010007
May 27 00:15:10 DE-BC4212 kernel: eax: 00000000 ebx: 00000000 ecx:
c12efea0 edx: c12efeb0
May 27 00:15:10 DE-BC4212 kernel: esi: 00000000 edi: 00000002 ebp:
00000004 esp: cf731f58
May 27 00:15:10 DE-BC4212 kernel: ds: 0018 es: 0018 ss: 0018
May 27 00:15:10 DE-BC4212 kernel: Process kswapd (pid: 5,
stackpage=cf731000)
May 27 00:15:10 DE-BC4212 kernel: Stack: 00000020 000001d0 00000020
00000006 c12efea0 c02f56ac 00000000 00000000
May 27 00:15:10 DE-BC4212 kernel: 00000000 00000000 c012c9b8
00000006 000001d0 c02b6ed4 00000000 c02b6ed4
May 27 00:15:10 DE-BC4212 kernel: c012ca52 00000020 c02b6ed4
00000001 cf730000 c012cb55 c02b6e20 00000000
May 27 00:15:10 DE-BC4212 kernel: Call Trace: [shrink_caches+28/132]
[try_to_free_pages_zone+50/80] [kswapd_balance_pgdat+69/144]
[kswapd_balance+22/44] [kswapd+163/204]
May 27 00:15:10 DE-BC4212 kernel: Code: 8b 00 47 39 d0 75 f9 89 fa 89 f1
d3 e2 85 db 74 14 8d 04 95
Using defaults from ksymoops -t elf32-i386 -a i386
Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: 8b 00 mov (%eax),%eax
Code; 00000002 Before first symbol
2: 47 inc %edi
Code; 00000002 Before first symbol
3: 39 d0 cmp %edx,%eax
Code; 00000004 Before first symbol
5: 75 f9 jne 0 <_EIP>
Code; 00000006 Before first symbol
7: 89 fa mov %edi,%edx
Code; 00000008 Before first symbol
9: 89 f1 mov %esi,%ecx
Code; 0000000a Before first symbol
b: d3 e2 shl %cl,%edx
Code; 0000000c Before first symbol
d: 85 db test %ebx,%ebx
Code; 0000000e Before first symbol
f: 74 14 je 25 <_EIP+0x25> 00000024 Before
first symbol
Code; 00000010 Before first symbol
11: 8d 04 95 00 00 00 00 lea 0x0(,%edx,4),%eax
Regards,
Carl-Daniel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Antwort: Re: Oops in Kernel 2.4.21-rc1
@ 2003-05-27 13:54 Werner.Beck
0 siblings, 0 replies; 4+ messages in thread
From: Werner.Beck @ 2003-05-27 13:54 UTC (permalink / raw)
To: skraw; +Cc: linux-kernel
unfortunately that is not possible at the moment...
|---------+---------------------------->
| | Stephan von |
| | Krawczynski |
| | <skraw@ithnet.com|
| | > |
| | |
| | 27.05.2003 15:49 |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
| |
| An: Werner.Beck@Lidl.de |
| Kopie: linux-kernel@vger.kernel.org |
| Thema: Re: Oops in Kernel 2.4.21-rc1 |
>------------------------------------------------------------------------------------------------------------------------------|
On Tue, 27 May 2003 14:01:00 +0200
Werner.Beck@Lidl.de wrote:
> Hello,
> I encountered a Kernel oops on two different PCs, both a configured
> identical. The system uses an ISDN connection to an Internet ISP and then
> establishes a VPN tunnel based on PPTP.
> As far as I can see in /var/log/messages the problem occurred on both
> system at the same time at 00:15, but not at the same day and not every
> day. No special program is running at that time. Basically it is a SuSE
7.3
> distribution, I made a Kernel upgrade.
> Hardware is a Fujitsu Siemens N300 PC with an IDE (7200 Rpm), Intel 845GI
> Motherboard, an ISDN PBX connected via USB to dial-up, the connection
> wasn't established when the system oopsed.
> Attached are some information.
> (See attached file: info.txt)(See attached file: oops.log)
Exchange the USB/ISDN part with a pci card and re-try with kernel -rc4.
Tell us if that works.
Regards,
Stephan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Antwort: Re: Oops in Kernel 2.4.21-rc1
@ 2003-05-27 13:22 Werner.Beck
2003-05-27 14:01 ` Carl-Daniel Hailfinger
0 siblings, 1 reply; 4+ messages in thread
From: Werner.Beck @ 2003-05-27 13:22 UTC (permalink / raw)
To: c-d.hailfinger.kernel.2003; +Cc: linux-kernel
could that be the process mandb and aaa_base which where affected by the
oops? How to disable this "feature"?
|---------+------------------------------------>
| | Carl-Daniel Hailfinger |
| | <c-d.hailfinger.kernel.20|
| | 03@gmx.net> |
| | |
| | 27.05.2003 14:18 |
| | |
|---------+------------------------------------>
>------------------------------------------------------------------------------------------------------------------------------|
| |
| An: Werner.Beck@Lidl.de |
| Kopie: linux-kernel@vger.kernel.org |
| Thema: Re: Oops in Kernel 2.4.21-rc1 |
>------------------------------------------------------------------------------------------------------------------------------|
Werner.Beck@Lidl.de wrote:
> Hello,
> I encountered a Kernel oops on two different PCs, both a configured
> identical. The system uses an ISDN connection to an Internet ISP and then
> establishes a VPN tunnel based on PPTP.
> As far as I can see in /var/log/messages the problem occurred on both
> system at the same time at 00:15, but not at the same day and not every
You are using SuSE 7.3, which leads me to the assumption that the
nightly cronjob at 00:15 is triggering this. One of the culprits I can
imagine is the updatedb run at that time. However, this is only
guesswork. The Oops itself does not give me any idea. Perhaps someone
else can help.
> day. No special program is running at that time. Basically it is a SuSE
7.3
> distribution, I made a Kernel upgrade.
> Hardware is a Fujitsu Siemens N300 PC with an IDE (7200 Rpm), Intel 845GI
> Motherboard, an ISDN PBX connected via USB to dial-up, the connection
> wasn't established when the system oopsed.
> Attached are some information.
> (See attached file: info.txt)(See attached file: oops.log)
HTH,
Carl-Daniel
--
http://www.hailfinger.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2003-05-27 13:54 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <OFC9BF3818.E07B98DB-ONC1256D33.004C27AB-C1256D33.004C6AE8@lidl.de>
2003-05-27 14:07 ` Antwort: Re: Oops in Kernel 2.4.21-rc1 Stephan von Krawczynski
2003-05-27 13:54 Werner.Beck
-- strict thread matches above, loose matches on Subject: below --
2003-05-27 13:22 Werner.Beck
2003-05-27 14:01 ` Carl-Daniel Hailfinger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).