From: Marcel Hellwig
> Sent: 01 August 2018 11:36
> >> [] (udp_recvmsg+0x284/0x33c) from []
> >> (inet_recvmsg+0x38/0x4c):
> net/ipv4/udp.c:1234
> >
> > sin->sin_addr.s_addr = ip_hdr(skb)->saddr;
> >
> >Unaligned access trap (virtual address c14fe63a), so either sin or
> >ip_hdr(skb)
On Mon, Mar 05, 2007 at 01:23:24PM +0300, Mockern wrote:
> I have the Linux kernel oops problem sometime.
serial_pxa_irq() was passed a NULL dev_id parameter by the interrupt
layer. This can only happen if request_irq() was called with a NULL
dev_id parameter.
> How can I fix it?
Show me your m
Hi,
I have the Linux kernel oops problem sometime.
How can I fix it?
Thank you
-
Unable to handle kernel NULL pointer dereference at virtual address 0004
pgd = c0004000
[0004] *pgd=
Internal error: Oop
Hello,
I got an oops when inserting my compact flash card in my laptop.
The laptop is a Dell X1, using the builtin compact flash reader, which I
understand works through PCMCIA.
My kernel is stock ubuntu latest unstable: Linux version 2.6.20-8-386
([EMAIL PROTECTED]) (gcc version 4.1.2 20070129 (
Hi
I just got an oops with 2.4.3-ac7:
[1.] Kernel oops'es and KDE hangs.
[2.] While compiling gcc, suddenly KDE hangs. I was able to change to a
console to investigate the problem. It appears that the dying process
was kwin as X and other parts of KDE still is responsive. The kernel
seems to run
On Sunday, April 08, 2001 03:43:19 PM -0500 xOr <[EMAIL PROTECTED]> wrote:
> [1.] kernel oops in reiserfs under 2.4.2-ac28 and 2.4.3-ac3 when rming
> files
Ok, reiserfs must be picking the wrong member in an array of function
pointers, probably on a bad item from disk. We're testing some cod
[1.] kernel oops in reiserfs under 2.4.2-ac28 and 2.4.3-ac3 when rming files
[2.] when removing a directory on my harddrive with rm -rf, i get this oops.
it occurs every time i try, and only on this one folder (so far). its
actually in a subdirectory of the folder, im guessing at one file, but i
On Friday March 2, [EMAIL PROTECTED] wrote:
> 1. Problem description
> 2. Machine details
> a) Hardware
> b) Software
> 3. System log during the incident
>
> 1. Problem Description:
>
snip
> Mar 2 13:44:38 bertha kernel: Unable to handle kernel NULL pointer
> dereference at virtual
1. Problem description
2. Machine details
a) Hardware
b) Software
3. System log during the incident
1. Problem Description:
I have a software raid 5 with 1 spare. (9 total drives dedicated for raid)
with a seperate Boot drive for the system.
Before this new problem, I had many
1. Kernel oopses after cronjob starts
2. I recently noticed that my maschine crashes exactly on cronjob times.
It seems to me that it is mainly caused (because it happened 2 times at 4 o clock) by
the mandrake security scripts i installed (msec-0.9-14mdk) - after some network failure
(eg router
I am having problems with something that looks like a PCI IRQ routing
problem. Everything worked just fine up until test12-pre7. Test12-pre8 did
not even boot, it hung when initializing the SCSI adapter.
Everything after that (including test12) booted successfully, but crashed when
I loaded the F
Following the form:
[1.] PROBLEM: Kernel Oops 10% of diskless boots
[2.] When booting a diskless workstation (etherboot) the boot will fail
with an Oops, roughly 10% of the time. This has remained the failure
rate for quite some time. The included Oops if from 2.4.0-test12-pre4.
Similar
Hello,
I just bought Linux Mandrake 7.2. The problem described applies to (at
least) the kernel used to boot the installation.
It OCCURS just after the detection of the buses and harddisks:
hda:
hdc:
hdd:
Unable to handle kernel NULL pointer derefere
>
> >> Trace; c0194d36
>
> >Do you have any ISAPNP cards in your system?
>
> Yes, a Soundblaster AWE64 that has never given me any problems. I tried
> booting
> test10 and test1 with that card pulled, and they both still oopsed on boot.
>
>
Jeff, I recompiled test10 with all kernel ISA PN
Jeff, thank you for responding.
>Can you play the kernel shuffle, and narrow down exactly which kernel
>version breaks for you? Read, from the linux source tree,
>Documentation/BUG-HUNTING.
OK. I've compiled test1, and it also oopsed on boot. (Which is confusing,
since I know for sure I had t
Brad Corsello wrote:
>
> [1.] One line summary of the problem:
> kernel oops on boot in 2.4.0 test 10 (i386)
>
> [2.] Full description of the problem/report:
> On every boot of test 10, I get a kernel oops very early on.
> Is reproducibl
[1.] One line summary of the problem:
kernel oops on boot in 2.4.0 test 10 (i386)
[2.] Full description of the problem/report:
On every boot of test 10, I get a kernel oops very early on.
Is reproducible (happens every boot).
I've successfully booted 2.3 ke
17 matches
Mail list logo
