From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 206733] i2c i2c-3: i2c-powermac: modalias failure on /uni-n@f8000000/i2c@f8001000/cereal@1c0
Date: Mon, 17 May 2021 09:24:01 +0000 [thread overview]
Message-ID: <bug-206733-206035-F8UnXb0lXP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206733-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206733
Paul Osmialowski (newchief@king.net.pl) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |newchief@king.net.pl
--- Comment #4 from Paul Osmialowski (newchief@king.net.pl) ---
I've just updated to 5.10.27-gentoo on some old iBook G4, and of course I've
spotted this `i2c-powermac: modalias failure on
/uni-n@f8000000/i2c@f8001000/cereal@1c0` message. It is not worrying now after
I've found Ben's comment. I've also spotted one more error message (Flag
mismatch) that seems new to me, can you also make a judgement if it is also
harmless?:
[...]
[ 4.515861] hid-generic 0003:17EF:602E.0001: input,hidraw0: USB HID v1.11
Mouse [USB Optical Mouse] on usb-0001:10:1b.0-1/input0
[ 4.660923] input: PowerMac Beep as
/devices/pci0001:10/0001:10:17.0/input/input3
[ 4.665549] genirq: Flags mismatch irq 21. 00000001 (i2sbus: i2s-a (tx)) vs.
00000001 (PMac Output)
[...]
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2021-05-17 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 16:50 [Bug 206733] New: i2c i2c-3: i2c-powermac: modalias failure on /uni-n@f8000000/i2c@f8001000/cereal@1c0 bugzilla-daemon
2020-03-02 16:58 ` [Bug 206733] " bugzilla-daemon
2020-03-03 7:32 ` bugzilla-daemon
2020-03-05 3:42 ` bugzilla-daemon
2021-05-17 9:24 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-206733-206035-F8UnXb0lXP@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.