Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 119978
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Daniel Drake <dsd@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: James Pattinson <jamesp@hisser.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 119978 depends on: Show dependency tree
Bug 119978 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-01-22 14:01 0000
This seems to be the same issue as reported to the Fedora mailing list at

http://www.redhat.com/archives/fedora-devel-list/2006-January/msg00313.html

This was fixed in 2.6.15-1.1826.2.10_FC5 but unfortunately I don't have any
details about the fix.

I'm using an Optronix Mobo with an Athlon 64 3500+ and an ATI chipset.

Problem exists with vanilla 2.6.15 and 2.6.15-gentoo-r1.

Any more info required please let me know.

------- Comment #1 From Daniel Drake 2006-01-23 09:20:51 0000 -------
Please post "emerge --info" output to every bug that you file.
Which was the last known working kernel?

Please reproduce on the latest development kernel (currently 2.6.16-rc1).

------- Comment #2 From James Pattinson 2006-01-23 10:02:15 0000 -------
Portage 2.0.54 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r2,
2.6.14-gentoo-r5 x86_64)
=================================================================
System uname: 2.6.14-gentoo-r5 x86_64 AMD Athlon(tm) 64 Processor 3500+
Gentoo Base System version 1.6.14
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[disabled]
dev-lang/python:     2.3.5, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O3 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -O3 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://calculon/gentoo-portage"
USE="amd64 X alsa apache2 audiofile avi berkdb bitmap-fonts bzip2 cdr crypt
cups eds emboss encode expat fam foomaticdb fortran gif gpm gstreamer idn imlib
ipv6 jpeg kde lcms lzw lzw-tiff mad mng mp3 mpeg mysql ncurses nls opengl pam
pcre pdflib perl png python qt quicktime readline samba sdl spell ssl tcpd tiff
truetype truetype-fonts type1-fonts udev usb userlocales xml2 xpm xv zlib
userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY

The last working kernel is the one from above, 2.6.14-gentoo-r5, but note that
on this kernel I need to boot with "disable_timer_pin_1" else my system clock
runs twice as fast as it should.

I have just tried booting 2.6.16-rc1 and it exhibits the same behaviour.

Since I get the problem with the vanilla kernel it's not a gentoo problem -
should I raise a bugzilla at kernel.org?

Cheers, James

------- Comment #3 From Daniel Drake 2006-01-25 06:18:04 0000 -------
I sent a mail to Dave J to see if he has any ideas. I'm doubtful as to whether
its the same bug though, as the user on that thread reported it worked fine for
him in vanilla 2.6.15 (i.e. his problem was introduced by fedora patches).

------- Comment #4 From James Pattinson 2006-01-25 06:53:59 0000 -------
Thanks. In the meantime is there any other steps you'd like me to perform? I'm
haven't ever needed to diagnose a kernel boot problem before.

Although the first thing I might try is to update to the latest BIOS on this
machine.

------- Comment #5 From Daniel Drake 2006-01-25 07:06:40 0000 -------
You could boot with the initcall_debug parameter and examine the output

------- Comment #6 From James Pattinson 2006-01-25 09:01:58 0000 -------
initcall_debug doesn't seem to print any additional info. Do I need to enable
support for this in the kernel or is adding to the kernel command line
sufficient?  Can post a screenshot if needed. Cheers

------- Comment #7 From Daniel Drake 2006-01-25 09:29:03 0000 -------
Not entirely sure, I haven't used it before, was just a suggestion I stole from
the thread you linked to.
You shouldn't need to build anything else in, and you should expect to see
messages like:

Calling initcall 0x1234 : some_func()

------- Comment #8 From James Pattinson 2006-01-28 08:29:49 0000 -------
Hi. Latest BIOS applied, same issue. Also I re-tried the initcall_debug but
didn't get anywhere with that. Cheers

------- Comment #9 From Daniel Drake 2006-02-11 03:15:24 0000 -------
Probably this bug: http://bugzilla.kernel.org/show_bug.cgi?id=6011

Please try this patch:
http://bugzilla.kernel.org/attachment.cgi?id=7284&action=view

------- Comment #10 From James Pattinson 2006-02-11 06:16:56 0000 -------
Confirmed, thanks - my kernel boots with 2.6.16-rc2 with the small USB patch
applied.

------- Comment #11 From Daniel Drake 2006-03-02 04:46:47 0000 -------
Thanks for reporting and testing. Fixed in genpatches-2.6.15-9
(gentoo-sources-2.6.15-r6).

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug