From RoadTripDK at MyRealBox.com  Mon Apr  3 15:46:26 2006
From: RoadTripDK at MyRealBox.com (Brian Durant)
Date: Mon Apr  3 15:47:02 2006
Subject: Switching my stock Apple keyboard in FC5.
Message-ID: <44317B92.5050506@MyRealBox.com>

I have purchased a stock (white) Apple USB keyboard with Danish language 
layout that I would like to replace the stock (white) Apple USB keyboard 
(US) keyboard that I m using now, to make it easier for me to access the 
extra Danish letters in FC 5.

How do I switch the layout so that I get the Danish layout correctly 
from the moment I boot in the command line, as well as in GNOME? I tried 
this  about 2 years ago with FC 3 on a PC and I could never get the 
keyboard layout correctly from the moment I booted in the command line. 
This is important if (for example) you have a problem with the GUI 
freezing and have to run FC 5 from runlevel 3 to solve the problem.

What is a stock (white) Apple USB keyboard that comes with a G5 listed 
as (dk, dk-latin1, etc.)?

Cheers,

Brian

From RoadTripDK at MyRealBox.com  Mon Apr 10 13:51:16 2006
From: RoadTripDK at MyRealBox.com (Brian Durant)
Date: Mon Apr 10 13:51:40 2006
Subject: FC5 PPC, support, bugzilla and package selection.
Message-ID: <443A9B14.5070707@MyRealBox.com>

I just wanted to say that despite there being a few outstanding issues, 
like with sound for G5 machines, I have been very impressed both with 
the support provided, the quick and friendly responses (even to more or 
less newbies like myself) for the PPC platform from the package 
maintainers through bugzilla, as well package selection for the PPC 
platform, that has made me a big fan of Fedora Core 5 and makes Fedora 
Core 5 my favorite distro, despite my having earlier only been 
interested in .deb based distros.

Kudos to the FC PPC team!

Brian

From e at arix.com  Thu Apr 20 02:21:04 2006
From: e at arix.com (Erick Calder)
Date: Thu Apr 20 02:21:43 2006
Subject: Bordeaux fails install
Message-ID: <C06C7660.15AFE%e@arix.com>

greetings everyone,

I've just downloaded a copy of Bordeaux, burnt the 5 disks and attempted to
upgrade my FC4 MacMini to it, reaching the disappointing message:

> The package gnome-mime-data-2.4.2-1.2.1.ppc.rpm cannot be opened.  This is due
> to a missing file or perhaps a corrupt package.  If you are installing from
> CD media this usually means the CD media is corrupt, or the CD drive is unable
> to read the medai.

> Press Retry to try again.

I've checked the sha1sums and did the media check before install.  I tried
the install a couple of times, getting these errors on different files e.g.
bluetooth-libs-0.7.0-2.ppc.rpm, crypt* and others.

I then tried a network install, in case the drive had problems.  I attempted
an FTP-based install but with similar results.

what could be wrong? what can I do?

1,000 TIA - e



From e at arix.com  Thu Apr 20 22:41:20 2006
From: e at arix.com (Erick Calder)
Date: Thu Apr 20 22:41:51 2006
Subject: Bordeaux fails install
In-Reply-To: <17479.11727.429557.256129@zot.electricrain.com>
Message-ID: <C06D9460.15B8D%e@arix.com>

I tried your suggestion but get:

"Unable to read package metadata.  This may be due to a missing repodata
directory.  Please ensure that your install tree has been correctly
generated.  Failure: repodata/primary.xml.gz from anaconda: [Errno: 256].
No more mirrors to try."

grr... what next?

> From: "Brian D. Carlstrom" <bdc@carlstrom.com>
> Reply-To: "Brian D. Carlstrom" <bdc@carlstrom.com>
> Date: Wed, 19 Apr 2006 23:44:31 -0700
> To: Erick Calder <e@arix.com>
> Cc: <fedora-ppc@lists.infradead.org>
> Subject: Bordeaux fails install
> 
> Erick Calder writes:
>> I then tried a network install, in case the drive had problems.  I attempted
>> an FTP-based install but with similar results.
> 
> I've done a half dozen G5 DVD installs of FC5 ppc without significant
> issues (the only real one is that yaboot doesn't work on a G5 2.0GHz we
> have.
> 
> I also have done two network installs, one a fresh install on ppc and
> the other an ugprade install on i386. For ppc try HTTP to
> mirrors.kernel.org:fedora/core/4/ppc/os/. In the network installs I just
> used the rescue CD.
> 
> -bri



From bdc at carlstrom.com  Fri Apr 21 13:51:05 2006
From: bdc at carlstrom.com (Brian D. Carlstrom)
Date: Fri Apr 21 13:51:58 2006
Subject: Bordeaux fails install
In-Reply-To: <C06D9460.15B8D%e@arix.com>
References: <17479.11727.429557.256129@zot.electricrain.com>
	<C06D9460.15B8D%e@arix.com>
Message-ID: <17481.7049.343636.929447@zot.electricrain.com>

Erick Calder writes:
 > I tried your suggestion but get:
 > 
 > "Unable to read package metadata.  This may be due to a missing repodata
 > directory.  Please ensure that your install tree has been correctly
 > generated.  Failure: repodata/primary.xml.gz from anaconda: [Errno: 256].
 > No more mirrors to try."
 > 
 > grr... what next?

Perhaps try the correct URL, which is not what I provided. oops! :)
NOTE I had a 4, not a 5, for the fedora core version. 

I just checked and this is a real file:
    http://mirrors.kernel.org/fedora/core/5/ppc/os/repodata/primary.xml.gz
so you need to enter
   mirrors.kernel.org
   /fedora/core/5/ppc/os
in the installer.

 > 
 > > From: "Brian D. Carlstrom" <bdc@carlstrom.com>
 > > Reply-To: "Brian D. Carlstrom" <bdc@carlstrom.com>
 > > Date: Wed, 19 Apr 2006 23:44:31 -0700
 > > To: Erick Calder <e@arix.com>
 > > Cc: <fedora-ppc@lists.infradead.org>
 > > Subject: Bordeaux fails install
 > > 
 > > Erick Calder writes:
 > >> I then tried a network install, in case the drive had problems.  I attempted
 > >> an FTP-based install but with similar results.
 > > 
 > > I've done a half dozen G5 DVD installs of FC5 ppc without significant
 > > issues (the only real one is that yaboot doesn't work on a G5 2.0GHz we
 > > have.
 > > 
 > > I also have done two network installs, one a fresh install on ppc and
 > > the other an ugprade install on i386. For ppc try HTTP to
 > > mirrors.kernel.org:fedora/core/4/ppc/os/. In the network installs I just
 > > used the rescue CD.
 > > 
 > > -bri
 > 
 > 

From e at arix.com  Fri Apr 21 23:01:55 2006
From: e at arix.com (Erick Calder)
Date: Fri Apr 21 23:02:32 2006
Subject: Bordeaux fails install
In-Reply-To: <17481.7049.343636.929447@zot.electricrain.com>
Message-ID: <C06EEAB3.15C0F%e@arix.com>

no, I did notice the 4/5 difference and used the correct url... I took a
look with the browser before I entered it into the install process, so I'm
at a loss here...

> From: "Brian D. Carlstrom" <bdc@carlstrom.com>
> Reply-To: "Brian D. Carlstrom" <bdc@carlstrom.com>
> Date: Fri, 21 Apr 2006 10:51:05 -0700
> To: Erick Calder <e@arix.com>
> Cc: <fedora-ppc@lists.infradead.org>
> Subject: Re: Bordeaux fails install
> 
> Erick Calder writes:
>> I tried your suggestion but get:
>> 
>> "Unable to read package metadata.  This may be due to a missing repodata
>> directory.  Please ensure that your install tree has been correctly
>> generated.  Failure: repodata/primary.xml.gz from anaconda: [Errno: 256].
>> No more mirrors to try."
>> 
>> grr... what next?
> 
> Perhaps try the correct URL, which is not what I provided. oops! :)
> NOTE I had a 4, not a 5, for the fedora core version.
> 
> I just checked and this is a real file:
>     http://mirrors.kernel.org/fedora/core/5/ppc/os/repodata/primary.xml.gz
> so you need to enter
>    mirrors.kernel.org
>    /fedora/core/5/ppc/os
> in the installer.
> 
>> 
>>> From: "Brian D. Carlstrom" <bdc@carlstrom.com>
>>> Reply-To: "Brian D. Carlstrom" <bdc@carlstrom.com>
>>> Date: Wed, 19 Apr 2006 23:44:31 -0700
>>> To: Erick Calder <e@arix.com>
>>> Cc: <fedora-ppc@lists.infradead.org>
>>> Subject: Bordeaux fails install
>>> 
>>> Erick Calder writes:
>>>> I then tried a network install, in case the drive had problems.  I
>>>> attempted
>>>> an FTP-based install but with similar results.
>>> 
>>> I've done a half dozen G5 DVD installs of FC5 ppc without significant
>>> issues (the only real one is that yaboot doesn't work on a G5 2.0GHz we
>>> have.
>>> 
>>> I also have done two network installs, one a fresh install on ppc and
>>> the other an ugprade install on i386. For ppc try HTTP to
>>> mirrors.kernel.org:fedora/core/4/ppc/os/. In the network installs I just
>>> used the rescue CD.
>>> 
>>> -bri
>> 
>> 



From e at arix.com  Fri Apr 21 23:09:53 2006
From: e at arix.com (Erick Calder)
Date: Fri Apr 21 23:10:35 2006
Subject: Bordeaux fails install
In-Reply-To: <C06EEAB3.15C0F%e@arix.com>
Message-ID: <C06EEC91.15C15%e@arix.com>

my guess was that maybe it had difficulty reaching the mirrors and gave up.
However, I did learn one useful thing, which is the correct layout for a
single-directory that contains the contents of all 5 disks.  I didn't have
it right before, so I fixed that in the laptop and attempted another install
via FTP against my laptop, sadly with similar results as before.

this is making me crazy.  If I verified the checksums of the ISOs I
downloaded, then I know the data is correct, so why does it think stuff is
missing or corrupt?

> From: Erick Calder <e@arix.com>
> Date: Fri, 21 Apr 2006 20:01:55 -0700
> To: "Brian D. Carlstrom" <bdc@carlstrom.com>
> Cc: <fedora-ppc@lists.infradead.org>
> Conversation: Bordeaux fails install
> Subject: Re: Bordeaux fails install
> 
> no, I did notice the 4/5 difference and used the correct url... I took a
> look with the browser before I entered it into the install process, so I'm
> at a loss here...



From bdc at carlstrom.com  Fri Apr 21 23:36:23 2006
From: bdc at carlstrom.com (Brian D. Carlstrom)
Date: Fri Apr 21 23:36:52 2006
Subject: Bordeaux fails install
In-Reply-To: <C06EEC91.15C15%e@arix.com>
References: <C06EEAB3.15C0F%e@arix.com>
	<C06EEC91.15C15%e@arix.com>
Message-ID: <17481.42167.647017.826166@zot.electricrain.com>

Erick Calder writes:
 > this is making me crazy.  If I verified the checksums of the ISOs I
 > downloaded, then I know the data is correct, so why does it think stuff is
 > missing or corrupt?

I recalled this thread from last month on the fedora-test-list. I just
wanted to refer you to it in case it had any helpful information.

-bri

https://www.redhat.com/archives/fedora-test-list/2006-March/msg01631.html

From e at arix.com  Sat Apr 22 03:34:17 2006
From: e at arix.com (Erick Calder)
Date: Sat Apr 22 03:34:55 2006
Subject: Bordeaux fails install
In-Reply-To: <17481.42167.647017.826166@zot.electricrain.com>
Message-ID: <C06F2A89.167E7%e@arix.com>

the article you posted led me to further experimentation and a little
discovery.  it appears that a whole bunch of filenames have gotten
truncated... e.g.

xorg-x11-drv-penmount-1.0.0.5-1
xorg-x11-drv-s3-0.3.5.5-2.ppc.r
xorg-x11-drv-s3virge-1.8.6.5-1.
xorg-x11-drv-savage-2.0.2.3-1.2
xorg-x11-drv-sis-0.8.1.3-1.2.pp
xorg-x11-drv-sisusb-0.7.1.3-1.2
xorg-x11-drv-spaceorb-1.0.0.5-1
xorg-x11-drv-summa-1.0.0.5-1.2.
xorg-x11-drv-tdfx-1.1.1.3-1.3.p
xorg-x11-drv-trident-1.0.1.2-1.
xorg-x11-drv-ur98-1.0.0.5-1.2.p
xorg-x11-drv-vesa-1.0.1.3-1.2.p
xorg-x11-drv-vga-4.0.0.5-2.ppc.
xorg-x11-drv-void-1.0.0.5-1.2.p
xorg-x11-drv-voodoo-1.0.0.5-1.2
xorg-x11-filesystem-7.0-1.noarc
xorg-x11-font-utils-1.0.1-3.ppc
xorg-x11-fonts-base-7.0-3.noarc
xorg-x11-fonts-truetype-7.0-3.n
xorg-x11-server-Xorg-1.0.1-8.pp
xorg-x11-server-utils-1.0.1-1.2
xorg-x11-utils-1.0.1-1.2.ppc.rp
xorg-x11-xauth-1.0.1-1.2.ppc.rp

now, the way I went about this is: after the Bittorrent download I was left
with 6 ISOs.  Double clicking on these (on OSX Panther) causes them to be
mounted... so i'm wondering whether the mount process is failing or if the
ISO contains bad filenames...  could anyone check that or suggest some other
way of extracting the contents of the ISO files?

thx - e

> From: "Brian D. Carlstrom" <bdc@carlstrom.com>
> Reply-To: "Brian D. Carlstrom" <bdc@carlstrom.com>
> Date: Fri, 21 Apr 2006 20:36:23 -0700
> To: Erick Calder <e@arix.com>
> Cc: <fedora-ppc@lists.infradead.org>
> Subject: Re: Bordeaux fails install
> 
> Erick Calder writes:
>> this is making me crazy.  If I verified the checksums of the ISOs I
>> downloaded, then I know the data is correct, so why does it think stuff is
>> missing or corrupt?
> 
> I recalled this thread from last month on the fedora-test-list. I just
> wanted to refer you to it in case it had any helpful information.
> 
> -bri
> 
> https://www.redhat.com/archives/fedora-test-list/2006-March/msg01631.html



From bdc at carlstrom.com  Sat Apr 22 03:48:06 2006
From: bdc at carlstrom.com (Brian D. Carlstrom)
Date: Sat Apr 22 03:48:40 2006
Subject: Bordeaux fails install
In-Reply-To: <C06F2A89.167E7%e@arix.com>
References: <17481.42167.647017.826166@zot.electricrain.com>
	<C06F2A89.167E7%e@arix.com>
Message-ID: <17481.57270.914216.344011@zot.electricrain.com>

Erick Calder writes:
 > Double clicking on these (on OSX Panther) causes them to be
 > mounted... so i'm wondering whether the mount process is failing or if the
 > ISO contains bad filenames...  could anyone check that or suggest some other
 > way of extracting the contents of the ISO files?

I've seen this behavior with ISO's mounted by Mac OS X. If I recall the
old Mac OS had something like a 32 character filename length limit,
which is close to what you are seeing. When I hit this problem in the
distance past I just used a Yellow Dog Linux box I had lying around to
work around the issue. Perhaps there is a unix tool available via fink
that would let you extra the ISO. Or perhaps you can use some options
with command line mount to get the right ISO filesystem type.

-bri


From dwmw2 at infradead.org  Sat Apr 22 08:18:07 2006
From: dwmw2 at infradead.org (David Woodhouse)
Date: Sat Apr 22 08:18:39 2006
Subject: Bordeaux fails install
In-Reply-To: <17481.57270.914216.344011@zot.electricrain.com>
References: <17481.42167.647017.826166@zot.electricrain.com>
	<C06F2A89.167E7%e@arix.com>
	<17481.57270.914216.344011@zot.electricrain.com>
Message-ID: <1145708287.11909.231.camel@pmac.infradead.org>

On Sat, 2006-04-22 at 00:48 -0700, Brian D. Carlstrom wrote:
> Erick Calder writes:
>  > Double clicking on these (on OSX Panther) causes them to be
>  > mounted... so i'm wondering whether the mount process is failing or if the
>  > ISO contains bad filenames...  could anyone check that or suggest some other
>  > way of extracting the contents of the ISO files?
> 
> I've seen this behavior with ISO's mounted by Mac OS X. If I recall the
> old Mac OS had something like a 32 character filename length limit,
> which is close to what you are seeing. 

$Reasons to _always_ just download or use the install tree directly
instead of mucking around with ISO images++;

-- 
dwmw2


From e at arix.com  Sat Apr 22 18:06:22 2006
From: e at arix.com (Erick Calder)
Date: Sat Apr 22 18:07:24 2006
Subject: Bordeaux fails install
In-Reply-To: <1145708287.11909.231.camel@pmac.infradead.org>
Message-ID: <00c201c66658$fe8fa5e0$030a010a@wga.org>

> $Reasons to _always_ just download or use the install tree directly
> instead of mucking around with ISO images++;

hmm... but if I download the install tree (presumably onto some other
machine), how do I boot the target machine to run the install programme?

-----Original Message-----
From: David Woodhouse [mailto:dwmw2@infradead.org] 
Sent: Saturday, April 22, 2006 5:18 AM
To: Brian D. Carlstrom
Cc: Erick Calder; fedora-ppc@lists.infradead.org
Subject: Re: Bordeaux fails install

On Sat, 2006-04-22 at 00:48 -0700, Brian D. Carlstrom wrote:
> Erick Calder writes:
>  > Double clicking on these (on OSX Panther) causes them to be
>  > mounted... so i'm wondering whether the mount process is failing or if
the
>  > ISO contains bad filenames...  could anyone check that or suggest some
other
>  > way of extracting the contents of the ISO files?
> 
> I've seen this behavior with ISO's mounted by Mac OS X. If I recall the
> old Mac OS had something like a 32 character filename length limit,
> which is close to what you are seeing. 

$Reasons to _always_ just download or use the install tree directly
instead of mucking around with ISO images++;

-- 
dwmw2


From bdc at carlstrom.com  Sat Apr 22 19:47:27 2006
From: bdc at carlstrom.com (Brian D. Carlstrom)
Date: Sat Apr 22 19:48:01 2006
Subject: Bordeaux fails install
In-Reply-To: <00c201c66658$fe8fa5e0$030a010a@wga.org>
References: <1145708287.11909.231.camel@pmac.infradead.org>
	<00c201c66658$fe8fa5e0$030a010a@wga.org>
Message-ID: <17482.49295.677555.96744@zot.electricrain.com>

Erick Calder writes:
 > > $Reasons to _always_ just download or use the install tree directly
 > > instead of mucking around with ISO images++;
 > 
 > hmm... but if I download the install tree (presumably onto some other
 > machine), how do I boot the target machine to run the install programme?

I thought you downloaded the ISO's and then extracted them on another
machine which was available via FTP. 

I think the other responder is suggesting you download the install tree
using something like rsync to mirrors.kernel.org/fedora/core/5/ppc/os
instead of of using ISOs as an intermediate format.

Since your only problem seems to be that the filesnames were truncated,
you could make a list of RPM's are trucnated based on the file extension
(or lack thereof) and just rename them. Mac OS X has a more reasonable
filename length limit of 255 characters, regardless of their ISO
mounting issues.

-bri


From e at arix.com  Sat Apr 22 23:36:14 2006
From: e at arix.com (Erick Calder)
Date: Sat Apr 22 23:37:13 2006
Subject: Bordeaux fails install
In-Reply-To: <17482.49295.677555.96744@zot.electricrain.com>
Message-ID: <C070443E.16B0D%e@arix.com>

> From: "Brian D. Carlstrom" <bdc@carlstrom.com>
> Erick Calder writes:
>> 
>> hmm... but if I download the install tree (presumably onto some other
>> machine), how do I boot the target machine to run the install programme?
> 
> I thought you downloaded the ISO's and then extracted them on another
> machine which was available via FTP.

I did

> I think the other responder is suggesting you download the install tree
> using something like rsync to mirrors.kernel.org/fedora/core/5/ppc/os
> instead of of using ISOs as an intermediate format.

yes, I understand that but my question concerns how to boot.  you see if I
boot from the disc I burnt from the ISO (which is screwed) then the
installer will attempt to install the files it knows to be in disc 1 from
the CD, even though I'm doing a network install - which means that even if I
have the right filenames on the ftp site, it won't read them because it
prefers to read from the CD and thus fails.



From bdc at carlstrom.com  Sat Apr 22 23:54:52 2006
From: bdc at carlstrom.com (Brian D. Carlstrom)
Date: Sat Apr 22 23:55:27 2006
Subject: Bordeaux fails install
In-Reply-To: <C070443E.16B0D%e@arix.com>
References: <17482.49295.677555.96744@zot.electricrain.com>
	<C070443E.16B0D%e@arix.com>
Message-ID: <17482.64140.324498.930645@zot.electricrain.com>

Erick Calder writes:
 > you see if I boot from the disc I burnt from the ISO (which is
 > screwed) then the installer will attempt to install the files it
 > knows to be in disc 1 from the CD, even though I'm doing a network
 > install - which means that even if I have the right filenames on the
 > ftp site, it won't read them because it prefers to read from the CD
 > and thus fails.

I believe you can use the Apple disk utility to burn an ISO (aka disk
image) without extracting it all. It should burn a bit-for-bit copy
without interpreting the contents, preserving the filenames.

In any case, you can burn a rescue CD instead of disc 1. That is what I
did for my network installs, since I wanted to download the minimum ISO
possible.

-bri

From ce at idtect.com  Mon Apr 24 08:29:21 2006
From: ce at idtect.com (Charles-Edouard Ruault)
Date: Mon Apr 24 08:31:30 2006
Subject: 2.6.16-1.2096_FC5, kernel exception when waking up
Message-ID: <444CC4A1.1030201@idtect.com>

Hi all,
i've just installed pmud on my powerbook and tried a sleep/resume.
I'm getting the following exception ( running the latest Fedora kernel 
2.6.16-1.2096_FC5 ).
Has anyone had this problem ?

eth0: suspending, WakeOnLan disabled
radeonfb (0000:00:10.0): suspending to state: 2...
radeonfb (0000:00:10.0): resuming from state: 2...
PCI: Enabling device 0000:00:10.0 (0000 -> 0003)
PM: Writing back config space on device 0001:10:12.0 at offset 1. (Was 
100000, writing 100004)
PM: Writing back config space on device 0001:10:12.0 at offset 3. (Was 
0, writing 1000)
PM: Writing back config space on device 0001:10:12.0 at offset 4. (Was 
0, writing a0006000)
PM: Writing back config space on device 0001:10:12.0 at offset f. (Was 
100, writing 134)
PM: Writing back config space on device 0001:10:13.0 at offset 1. (Was 
2100000, writing 2100007)
PM: Writing back config space on device 0001:10:13.0 at offset 3. (Was 
20000, writing 2a808)
PM: Writing back config space on device 0001:10:13.0 at offset 4. (Was 
0, writing a0004000)
PM: Writing back config space on device 0001:10:13.0 at offset 6. (Was 
0, writing b0141110)
PM: Writing back config space on device 0001:10:13.0 at offset 7. (Was 
0, writing 90000000)
PM: Writing back config space on device 0001:10:13.0 at offset 8. (Was 
0, writing 9ffff000)
PM: Writing back config space on device 0001:10:13.0 at offset 9. (Was 
0, writing f3000000)
PM: Writing back config space on device 0001:10:13.0 at offset a. (Was 
0, writing f33ff000)
PM: Writing back config space on device 0001:10:13.0 at offset b. (Was 
0, writing 1000)
PM: Writing back config space on device 0001:10:13.0 at offset c. (Was 
0, writing 11fc)
PM: Writing back config space on device 0001:10:13.0 at offset d. (Was 
0, writing 1400)
PM: Writing back config space on device 0001:10:13.0 at offset e. (Was 
0, writing 15fc)
PM: Writing back config space on device 0001:10:13.0 at offset f. (Was 
34001ff, writing 5c00135)
PCI: Enabling device 0001:10:1b.0 (0000 -> 0002)
PCI: Enabling device 0001:10:1b.1 (0000 -> 0002)
PCI: Enabling device 0001:10:1b.2 (0000 -> 0002)
PM: Writing back config space on device 0001:10:1b.2 at offset 1. (Was 
2100006, writing 2100016)
usb usb4: root hub lost power or was reset
ehci_hcd 0001:10:1b.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
eth0: resuming
PHY ID: 1410cc1, addr: 0
hda: Enabling Ultra DMA 5
Badness in wait_for_ready at drivers/ide/ide-iops.c:516
Call Trace:
[C0393C40] [C0007A50] show_stack+0x54/0x184 (unreliable)
[C0393C60] [C000E574] program_check_exception+0x19c/0x520
[C0393CB0] [C000FC34] ret_from_except_full+0x0/0x4c
--- Exception: 700 at wait_for_ready+0x94/0xec
    LR = wait_for_ready+0x3c/0xec
[C0393D70] [C005A01C] disable_irq_nosync+0x7c/0x90 (unreliable)
[C0393D90] [C01DF36C] pmac_ide_do_setfeature+0x108/0x320
[C0393DB0] [C01DF88C] pmac_ide_dma_check+0x308/0x490
[C0393DE0] [C01D36AC] ide_do_request+0x618/0x8cc
[C0393E50] [C01D3CF0] ide_intr+0x204/0x240
[C0393E80] [C0059CB8] handle_IRQ_event+0x54/0xa8
[C0393EA0] [C0059E10] __do_IRQ+0x104/0x188
[C0393EC0] [C00057E8] do_IRQ+0x4c/0x7c
[C0393EE0] [C000FC80] ret_from_except+0x0/0x14
--- Exception: 501 at default_idle+0x3c/0x44
    LR = default_idle+0x34/0x44
[C0393FA0] [C00247E0] cpu_idle+0x3c/0x5c (unreliable)
[C0393FB0] [C0003E70] rest_init+0x28/0x38
[C0393FC0] [C0394720] start_kernel+0x19c/0x1b0
[C0393FF0] [000037A0] 0x37a0
hdc: Enabling MultiWord DMA 2
hci_usb 1-1:1.0: no resume for driver hci_usb?
hci_usb 1-1:1.1: no resume for driver hci_usb?
eth0: Link is up at 100 Mbps, full-duplex.
eth0: Pause is disabled
adb: starting probe task...
adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f
ADB keyboard at 2, handler 1
ADB mouse at 3, handler set to 4 (trackpad)
adb: finished probe task...

Here's my /proc/cpuinfo

processor       : 0
cpu             : 7447/7457, altivec supported
clock           : 612.000000MHz
revision        : 0.1 (pvr 8002 0101)
bogomips        : 36.73
timebase        : 18432000
machine         : PowerBook5,2
motherboard     : PowerBook5,2 MacRISC3 Power Macintosh
detected as     : 287 (PowerBook G4 15")
pmac flags      : 0000001b
L2 cache        : 512K unified
pmac-generation : NewWorld

-- 
Charles-Edouard Ruault

+33 1 55 34 76 65
ce@idtect.com

Idtect SA
37 Bd des Capucines 
75002 Paris, France
www.idtect.com


From dwmw2 at infradead.org  Mon Apr 24 09:11:42 2006
From: dwmw2 at infradead.org (David Woodhouse)
Date: Mon Apr 24 09:11:37 2006
Subject: 2.6.16-1.2096_FC5, kernel exception when waking up
In-Reply-To: <444CC4A1.1030201@idtect.com>
References: <444CC4A1.1030201@idtect.com>
Message-ID: <1145884303.16166.316.camel@shinybook.infradead.org>

On Mon, 2006-04-24 at 14:29 +0200, Charles-Edouard Ruault wrote:
> Hi all,
> i've just installed pmud on my powerbook and tried a sleep/resume.
> I'm getting the following exception ( running the latest Fedora
> kernel 
> 2.6.16-1.2096_FC5 ).
> Has anyone had this problem ? 

What's the problem? Everything in there looks cosmetic and harmless.

-- 
dwmw2


From ce at idtect.com  Mon Apr 24 09:15:19 2006
From: ce at idtect.com (Charles-Edouard Ruault)
Date: Mon Apr 24 09:16:05 2006
Subject: 2.6.16-1.2096_FC5, kernel exception when waking up
In-Reply-To: <1145884303.16166.316.camel@shinybook.infradead.org>
References: <444CC4A1.1030201@idtect.com>
	<1145884303.16166.316.camel@shinybook.infradead.org>
Message-ID: <444CCF67.3040605@idtect.com>

David Woodhouse wrote:
> On Mon, 2006-04-24 at 14:29 +0200, Charles-Edouard Ruault wrote:
>   
>> Hi all,
>> i've just installed pmud on my powerbook and tried a sleep/resume.
>> I'm getting the following exception ( running the latest Fedora
>> kernel 
>> 2.6.16-1.2096_FC5 ).
>> Has anyone had this problem ? 
>>     
>
> What's the problem? Everything in there looks cosmetic and harmless.
>
>   
Well, so far i've not been able to find any side effect of this.
It's just that i don't think it's normal seeing things like that, as it 
certainly outlines a problem  in the  kernel .... and therefore should 
be fixed.

-- 
Charles-Edouard Ruault

+33 1 55 34 76 65
ce@idtect.com

Idtect SA
37 Bd des Capucines 
75002 Paris, France
www.idtect.com


From dwmw2 at infradead.org  Mon Apr 24 09:18:08 2006
From: dwmw2 at infradead.org (David Woodhouse)
Date: Mon Apr 24 09:17:51 2006
Subject: 2.6.16-1.2096_FC5, kernel exception when waking up
In-Reply-To: <444CCF67.3040605@idtect.com>
References: <444CC4A1.1030201@idtect.com>
	<1145884303.16166.316.camel@shinybook.infradead.org>
	<444CCF67.3040605@idtect.com>
Message-ID: <1145884689.16166.318.camel@shinybook.infradead.org>

On Mon, 2006-04-24 at 15:15 +0200, Charles-Edouard Ruault wrote:
> Well, so far i've not been able to find any side effect of this.
> It's just that i don't think it's normal seeing things like that, as
> it certainly outlines a problem  in the  kernel .... and therefore
> should be fixed. 

Which bit? The lack of suspend/resume for hci_usb? The harmless warning
about using mdelay() in IDE code somewhere? The one about the root USB
host?

-- 
dwmw2


From ce at idtect.com  Mon Apr 24 09:25:43 2006
From: ce at idtect.com (Charles-Edouard Ruault)
Date: Mon Apr 24 09:26:15 2006
Subject: 2.6.16-1.2096_FC5, kernel exception when waking up
In-Reply-To: <1145884689.16166.318.camel@shinybook.infradead.org>
References: <444CC4A1.1030201@idtect.com>	
	<1145884303.16166.316.camel@shinybook.infradead.org>	
	<444CCF67.3040605@idtect.com>
	<1145884689.16166.318.camel@shinybook.infradead.org>
Message-ID: <444CD1D7.5080900@idtect.com>

David Woodhouse wrote:
> On Mon, 2006-04-24 at 15:15 +0200, Charles-Edouard Ruault wrote:
>   
>> Well, so far i've not been able to find any side effect of this.
>> It's just that i don't think it's normal seeing things like that, as
>> it certainly outlines a problem  in the  kernel .... and therefore
>> should be fixed. 
>>     
>
> Which bit? The lack of suspend/resume for hci_usb? The harmless warning
> about using mdelay() in IDE code somewhere? The one about the root USB
> host?
>
>   
Well i was talking about this exception:
Badness in wait_for_ready at drivers/ide/ide-iops.c:516
Call Trace:
[C0393C40] [C0007A50] show_stack+0x54/0x184 (unreliable)
[C0393C60] [C000E574] program_check_exception+0x19c/0x520
[C0393CB0] [C000FC34] ret_from_except_full+0x0/0x4c
--- Exception: 700 at wait_for_ready+0x94/0xec
   LR = wait_for_ready+0x3c/0xec
[C0393D70] [C005A01C] disable_irq_nosync+0x7c/0x90 (unreliable)
[C0393D90] [C01DF36C] pmac_ide_do_setfeature+0x108/0x320
[C0393DB0] [C01DF88C] pmac_ide_dma_check+0x308/0x490
[C0393DE0] [C01D36AC] ide_do_request+0x618/0x8cc

Which, as you stated seems to be triggered by the use of mdelay(1) in 
wait_for_ready.
Since i'm not an expert, i won't comment on the fact that is is normal 
or not. I'm just worried when i see a message like 'Badness in 
wait_for_ready at drivers/ide/ide-iops.c:516' and then an exception 
trace ....

-- 
Charles-Edouard Ruault

+33 1 55 34 76 65
ce@idtect.com

Idtect SA
37 Bd des Capucines 
75002 Paris, France
www.idtect.com


From dwmw2 at infradead.org  Mon Apr 24 09:35:39 2006
From: dwmw2 at infradead.org (David Woodhouse)
Date: Mon Apr 24 09:35:22 2006
Subject: 2.6.16-1.2096_FC5, kernel exception when waking up
In-Reply-To: <444CD1D7.5080900@idtect.com>
References: <444CC4A1.1030201@idtect.com>
	<1145884303.16166.316.camel@shinybook.infradead.org>
	<444CCF67.3040605@idtect.com>
	<1145884689.16166.318.camel@shinybook.infradead.org>
	<444CD1D7.5080900@idtect.com>
Message-ID: <1145885739.16166.321.camel@shinybook.infradead.org>

On Mon, 2006-04-24 at 15:25 +0200, Charles-Edouard Ruault wrote:
> Badness in wait_for_ready at drivers/ide/ide-iops.c:516
> Call Trace: 

That's just a WARN_ON(), which isn't the same as an oops or even a
BUG(). It's a FIXME, which is relatively harmless.

-- 
dwmw2


From ce at idtect.com  Mon Apr 24 09:45:54 2006
From: ce at idtect.com (Charles-Edouard Ruault)
Date: Mon Apr 24 09:46:28 2006
Subject: 2.6.16-1.2096_FC5, kernel exception when waking up
In-Reply-To: <1145885739.16166.321.camel@shinybook.infradead.org>
References: <444CC4A1.1030201@idtect.com>	
	<1145884303.16166.316.camel@shinybook.infradead.org>	
	<444CCF67.3040605@idtect.com>	
	<1145884689.16166.318.camel@shinybook.infradead.org>	
	<444CD1D7.5080900@idtect.com>
	<1145885739.16166.321.camel@shinybook.infradead.org>
Message-ID: <444CD692.9060509@idtect.com>

David Woodhouse wrote:
> On Mon, 2006-04-24 at 15:25 +0200, Charles-Edouard Ruault wrote:
>   
>> Badness in wait_for_ready at drivers/ide/ide-iops.c:516
>> Call Trace: 
>>     
>
> That's just a WARN_ON(), which isn't the same as an oops or even a
> BUG(). It's a FIXME, which is relatively harmless.
>
>   
I understand it's harmless, but i guess that since it's reported it 
should be fixed anyway ... but as you say, low priority !


-- 
Charles-Edouard Ruault

+33 1 55 34 76 65
ce@idtect.com

Idtect SA
37 Bd des Capucines 
75002 Paris, France
www.idtect.com


