Ismail Dönmez wrote:
> On Thursday 15 March 2007 02:08:43 Stefan Richter wrote:
> [...]
>> Ismail, if you have the opportunity, the next thing you could test would
>> be to unload eth1394 explicitly before ohci1394 on 2.6.21-rc3. This
>> would _not_ oops according to my observation.
>
> On a clean
On Thursday 15 March 2007 02:08:43 Stefan Richter wrote:
[...]
>
> Ismail, if you have the opportunity, the next thing you could test would
> be to unload eth1394 explicitly before ohci1394 on 2.6.21-rc3. This
> would _not_ oops according to my observation.
On a clean reboot it works as expected ;
On Thursday 15 March 2007 02:08:43 Stefan Richter wrote:
[...]
> Ismail, if you have the opportunity, the next thing you could test would
> be to unload eth1394 explicitly before ohci1394 on 2.6.21-rc3. This
> would _not_ oops according to my observation.
rmmod eth1394 and modprobe -r eth1394 both
I wrote:
> according to a quick test I made right now it is a regression post 2.6.20.
> # modprobe ohci1394 # wait a bit, eth1394 is auto-loaded
> # modprobe -r eth1394
> # modprobe -r ohci1394
> works.
> # modprobe ohci1394 # wait a bit, eth1394 is auto-loaded
> # modprobe -r ohci1394
> oopses
Ismail Dönmez wrote:
> On Wednesday 14 March 2007 20:25:24 Stefan Richter wrote:
>> Ismail Dönmez wrote:
>> > Are you able to rmmod it?
>>
>> Yes, but on 2.6.20 and earlier kernels, most of the time with
>> development versions of the 1394 drivers. I still haven't tried
>> 2.6.21-rc, will hopefully
On Wednesday 14 March 2007 20:25:24 Stefan Richter wrote:
> Ismail Dönmez wrote:
> > On Wednesday 14 March 2007 13:14:42 Stefan Richter wrote:
> >> Do you have a script or config which marks the
> >> ohci1394 module to be unloaded before suspend?
> >
> > I used kpowersave to suspend, I failed to fi
Ismail Dönmez wrote:
> On Wednesday 14 March 2007 13:14:42 Stefan Richter wrote:
>> Do you have a script or config which marks the
>> ohci1394 module to be unloaded before suspend?
>
> I used kpowersave to suspend, I failed to find anything related to ohci1394
> in
> its config but rmmod ohci1
On Wednesday 14 March 2007 13:14:42 Stefan Richter wrote:
> (Cc'ing Greg KH and linux1394-devel)
>
> Ismail Dönmez wrote at lkml:
> > With latest GIT tree I am getting the following oops when I try to
> > suspend to RAM:
> >
> > BUG: unable to handle kernel NULL pointer dereference at virtual addre
On Wednesday 14 March 2007 13:50:47 Adrian Bunk wrote:
> On Wed, Mar 14, 2007 at 06:42:28AM +0200, Ismail Dönmez wrote:
> > Hi all,
> >
> > With latest GIT tree I am getting the following oops when I try to
> > suspend to RAM:
> >...
>
> Is this an old problem, or what was the last kernel that work
On Wed, Mar 14, 2007 at 06:42:28AM +0200, Ismail Dönmez wrote:
> Hi all,
>
> With latest GIT tree I am getting the following oops when I try to suspend to
> RAM:
>...
Is this an old problem, or what was the last kernel that worked for you?
cu
Adrian
--
"Is there not promise of rain?"
(Cc'ing Greg KH and linux1394-devel)
Ismail Dönmez wrote at lkml:
> With latest GIT tree I am getting the following oops when I try to suspend to
> RAM:
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address
> 0094
> printing eip:
> c0222af4
> *pde =
> Oops:
Hi all,
With latest GIT tree I am getting the following oops when I try to suspend to
RAM:
BUG: unable to handle kernel NULL pointer dereference at virtual address
0094
printing eip:
c0222af4
*pde =
Oops: [#1]
PREEMPT
Modules linked in: i915 drm snd_pcm_oss snd_mixer_oss snd_
12 matches
Mail list logo
