From: "D. Stimits" <stimits@idcomm.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unable to handle kernel NULL pointer dereference at virtual address - 2.4.5
Date: Thu, 21 Jun 2001 16:53:55 -0600 [thread overview]
Message-ID: <3B327B03.8C12741C@idcomm.com> (raw)
In-Reply-To: <3B3274F2.56FAB826@telerobotics.jpl.nasa.gov>
Chris Leger wrote:
>
> Hi,
>
> I have the same problem, only mine occurs early in the boot process
> (right after a message saying something like "trying to mount old
> root..."; or maybe s/mount/unmount)so I don't have a log. I have a
> similar system: dual PIIIs w/ Adaptec AIC-7xxx controller, an HP Kayak.
> I saw some earlier messages about AIC-7xxx problems w/ 2.4.5, so I tried
> using aic7xxx_old and also tried a patch someone mentioned. I have yet
> to be able to bring up my machine with 2.4.5 under any combination of
> aic7xxx drivers, so maybe it's not the driver after all.
>
> Any ideas? I built the kernel w/ gcc 2.91.66 (kgcc).
I have no problems running RH 7.l with the 2.4.5 ac series, provided I
have the patch to fs/block_dev.c (which apparently is in at around ac3;
also in 2.4.6-pre2 I think). When using an XFS filesystem patch, I also
have to use their "rebuild firmware" option, which I don't think is part
of ac or regular kernels. I use kgcc to compile all, and am running dual
pIII (I run without APIC because of the defective i840 chipset). All of
this is using the stock aic7xxx module or compiled in directly.
D. Stimits, stimits@idcomm.com
>
> Thanks,
>
> Chris Leger
>
> Rafael Martinez writes:
> > Hello
> >
> > I have got a error in my syslog about a Null pointer in the kernel:
> >
> > Kernel 2.4.5
> > glibc 2.2.12
> > gcc version 2.96 20000731 (Red Hat Linux 7.0)
> >
> > Modell: ISP2150
> > Motherboard: L440GX+ DP
> > CPU: 2 x Intel Pentium III (Coppermine) 850 MHz L2 cache: 256K / Bus: 100 MHz
> > RAM: 256 MB
> > SCSI controller: Adaptec AIC-7896/7 Ultra2
> >
> >Unable to handle kernel NULL pointer dereference at virtual address
> > 00000015
> > printing eip:
> > c014db72
> > *pde = 00000000
> > Oops: 0002
> > CPU: 1
> > EIP: 0010:[<c014db72>]
> > EFLAGS: 000
>
> --
> [ Chris Leger :: cleger@robotics.jpl.nasa.gov (818)393-4462 ]
>
> You can come up with a hundred reasons why a thing can't be done,
> and you have to eat them all when someone else does it.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-06-21 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 22:28 Unable to handle kernel NULL pointer dereference at virtual address - 2.4.5 Chris Leger
2001-06-21 22:53 ` D. Stimits [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-21 14:21 Rafael Martinez
2001-06-21 13:30 ` Brian Gerst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B327B03.8C12741C@idcomm.com \
--to=stimits@idcomm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox