Bug#632734: Strange
--- On Mon, 7/25/11, Frank McCormick <fmccormick@videotron.ca> wrote:
> From: Frank McCormick <fmccormick@videotron.ca>
> Subject: Bug#632734: Strange
> To: "Ben Hutchings" <ben@decadent.org.uk>
> Cc: 632734@bugs.debian.org
> Date: Monday, July 25, 2011, 1:09 PM
> On 22/07/11 02:04 PM, Frank McCormick
> wrote:
> > On 21/07/11 08:10 PM, Ben Hutchings wrote:
> > > Please always cc the bug address when
> replying to bug-related mails.
> > >
> > > On Sat, 2011-07-16 at 09:54 -0400, Frank
> McCormick wrote:
> > >> On 11/07/11 12:12 AM, Ben Hutchings
> wrote:
> > >>> On Tue, 2011-07-05 at 17:29 -0400,
> Frank wrote:
> > >>>> On 05/07/11 04:23 PM, Ben
> Hutchings wrote:
> > >>>>> On Tue, Jul 05, 2011 at
> 02:48:26PM -0400, Frank M wrote:
> > >>>>>> I find it strange that
> the PAE kernel is the ONLY one which
> > gives me
> > >>>>>> any trouble.
> > >>>>>> I guess it could be
> hardware related, but 2.6.38-1 and 2.6.38-2
> > have both been
> > >>>>>> booting fine for
> months.
> > >>>>>> Is there something
> about the PAE series that would uncover
> > hardware faults which
> > >>>>>> may have existed for a
> long time ?
> > >>>>>
> > >>>>> Have you tried booting
> those earlier versions recently?
> > >>
> > >>>>
> > >>>> Yes I've been booting them
> everyday for the past month or so - the
> > >>>> PAE series is the first time in
> years, literally, that I have had
> > >>>> problems like this.
> > >>>
Frank, I reported very similar findings also.
I also have been keeping track of 5 or 6 other bug reports that look similar, with a Pentium 4 3GHz 800 MHz bus / 512kb of L2 cache
see my bug report at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627019
My Pentium D 3GHz 800 MHz bus / 1mb of L2 cache ( next generation) is not showing any of these issues ( yet).
> > >
> > > This sounds like there is some sort of
> hardware fault, but I can't see
> > > why it would only occur when using PAE. It
> is just possible that the
> > > circuitry for PAE is faulty, but I think
> that is only a very small part
> > > of the chip.
> > >
> > > Please do consider the suggestions in<http://www.bitwizard.nl/sig11/>.
> >
> > Will do.
> >
> >
>
> Well I have solved this problem..but I'm not
> sure I like the solution. I installed the "new" 3.0.0 kernel
> this morning and started trying changing things in the BIOS
> setup. Nothing worked to allow me to boot UNTIL I turned off
> what Intel calls "hyper-threading". Now the kernel boots
> fine, but according to lshw-gtk, the system sees only one
> CPU. This is a dual-core system which was always seen by
> Linux as a dual core with in effect two CPU's.
> What's the connection between hyper-threading , and PAE
> which is apparently the only change in the new kernels ??
>
Again, very similarly, I have been able to boot successfully using the 486
flavor kernel ( but also not gettting SMP support for hyper threading.
I have had some success boot the 686-pae flavor by adding
debug=3 or debug=4 to the linux commandline in grub-pc
I also have compiled a vanilla (upstreams default config) linux-image-3.0-rc7
and it worked well for several days ( but still showing minor glitches at boot time)
But, after the udev upgrade to 172-1
the upstream kernel started showing the same seg faults and other stuff the debian 686-pae flavor kernels since 2.6.39-rc3-686-pae (iirc) have been showing.
I just upgraded to 3.0.0-1-686-pae and it took three reboots to get to a login screen.
The hang point on the second boot attempt was
waiting for dev to be fully populated ( which froze there, but I only waited a minute or two before I shut down than rebooted.
Than the third time I still got a udevd seg fault, but it was not fatal this time and I'm able to login.
I didn't upgrade the grub packages yet, holding for next time.
>
>
> -- Cheers
> Frank
Reply to: