-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg KH wrote:
Now, I'm thinking it could be something like the udev hang which
disapeared with udev update to 058.
I don't know what can be happening. I think it is because of some type
of timeout.
If you think there is
On Sun, Jul 31, 2005 at 03:46:10AM -0300, Francisco Figueiredo Jr. wrote:
> Andrew Morton wrote:
> > "Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
> >
> >>-BEGIN PGP SIGNED MESSAGE-
> >>Hash: SHA1
> >>
> >>Andrew Morton wrote:
> >>
> >>>"Francisco Figueiredo Jr." <[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Morton wrote:
> "Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
>
>>-BEGIN PGP SIGNED MESSAGE-
>>Hash: SHA1
>>
>>Andrew Morton wrote:
>>
>>>"Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
>>>
>>>
udev S 0002
"Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Andrew Morton wrote:
> > "Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
> >
> >>udev S 0002 0 1312 11224 (NOTLB)
> >> c1653f4c 0082 c1653
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Morton wrote:
> "Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
>
>>udev S 0002 0 1312 11224 (NOTLB)
>> c1653f4c 0082 c1653f3c 0002 0001 0040 c1653f64 c1653f0c
>>c016611b bfec
"Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
>
> udev S 0002 0 1312 11224 (NOTLB)
> c1653f4c 0082 c1653f3c 0002 0001 0040 c1653f64 c1653f0c
> c016611b bfec96a8 c1653f0c 0040 0361 000241ed
> c13fb520
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Francisco Figueiredo Jr. wrote:
>>>
>>>
>
>
>
> Ok, nevermind. I just found that I didn't add the sysrq support when
> compiling my kernel :(
>
> I will recompile it and send you stack trace.
>
> Sorry for wasting your time, Andrew.
>
Ok, now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Morton wrote:
>>>
>>
>>
>>Hi Andrew.
>>I was not able to get anything when I press this key sequence.
>>
>>I checked my sysrq key with showkey -s as this doc
>>(http://snafu.freedom.org/linux2.2/docs/sysrq.txt) says and I could
>>confirm that al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Morton wrote:
>>Hi Andrew.
>>I was not able to get anything when I press this key sequence.
>>
>>I checked my sysrq key with showkey -s as this doc
>>(http://snafu.freedom.org/linux2.2/docs/sysrq.txt) says and I could
>>confirm that alt+sysrq is
"Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Andrew Morton wrote:
> > "Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
> >
> >>Indeed udev update solved my problem with "preparing system to use udev"
> >> hang. It now works lik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Morton wrote:
> "Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
>
>>Indeed udev update solved my problem with "preparing system to use udev"
>> hang. It now works like a charm. I had 030 version too.
>>
>> Only the "mounting filesystem" h
"Francisco Figueiredo Jr." <[EMAIL PROTECTED]> wrote:
>
> Indeed udev update solved my problem with "preparing system to use udev"
> hang. It now works like a charm. I had 030 version too.
>
> Only the "mounting filesystem" hangs persists :(
Please use ALT-SYSRQ-T to generate an all-task backtr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Haninger wrote:
> On 7/22/05, Francisco Figueiredo Jr. <[EMAIL PROTECTED]> wrote:
>
>>Hangs appears just before mounting filesystems message and before configuring
>>system to use udev.
>
> I don't know if this will help, but there were issues
On 7/22/05, Francisco Figueiredo Jr. <[EMAIL PROTECTED]> wrote:
> Hangs appears just before mounting filesystems message and before configuring
> system to use udev.
I don't know if this will help, but there were issues raised earlier
about older versions of udev causing hangs on newer kernels. Loo
14 matches
Mail list logo