On Monday 15 August 2005 08:22, Jesper Juhl wrote: > Can you reproduce the crash reliably? > Can you reproduce the crash with a non-tainted kernel? I've tried several times now to reproduce the oops, but there might have been another factor that led to the oops, because just booting the kernel and shutting down does not trigger it. I have tried reproducing all conditions up to the time that the oops actually occurred and think it might just be my hardware going flaky - so I have reloaded the module that taints the kernel (have done this already and having the module loaded when the powerdown started did not trigger the oops) and am seeing if using it for any period of time causes the oops to occur. If it does I will try the other driver available for the modem, although that one also contains proprietary code. The upside is that it does not make use of any functions marked as deprecated in any version of the kernel, where the official driver requires me to re-enable a deprecated function that had been made non-exported by the kernel. DRH
Attachment:
0xA6992F96300F159086FF28208F8280BB8B00C32A.asc
Description: application/pgp-keys
Attachment:
pgpXhfHi9hs7l.pgp
Description: PGP signature
- References:
- oops in 2.6.13-rc6-git5
- From: "D. ShadowWolf" <[email protected]>
- Re: oops in 2.6.13-rc6-git5
- From: Jesper Juhl <[email protected]>
- oops in 2.6.13-rc6-git5
- Prev by Date: Re: [RFC] [PATCH] cache pollution aware __copy_from_user_ll()
- Next by Date: Re: [PATCH 3/6] i386 virtualization - Make ldt a desc struct
- Previous by thread: Re: oops in 2.6.13-rc6-git5
- Next by thread: Linux 2.6.12.5
- Index(es):
