I only have the 3B+ board - the issue was encountered, and is still
reproducible on that board. OS has always been Ubuntu.
I'll try to reduce the repro steps/conditions when I have time; my setup
is the v6 tunnel +v6 router + ip6tables + bridge reproduces the issue
immediately, so hopefully
@Chrostopher: if it's a driver problem, wouldn't your issue with WLAN be
distinct from mine, where I'm seeing the wired Ethernet break?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
FWIW, I tried the dwc2 overlay again with kernel 5.4.0-1021-raspi - as
before in #21 this changes nothing - network still dies during first
major (>100MB) download, while other USB ports continue working.
On the plus side, the Pi can now actually boot with an external NIC
plugged in. I'm not sure
@Matt I didn't find any special way to easily select between kernels on
raspberry - installing the linux-{headers,image}--raspi2 would
overwrite whatever was on the FAT partition, making it the kernel loaded
on next boot. To revert to previous kernel, its package would need to be
reinstalled (apt
@Kai - if I change the policy after startup (the default value is
med_power_with_dipm), I still have to issue a manual scan once (doesn't
matter if a device is attached or not), but subsequent attach/detach
changes are noticed as expected.
I found that kernel-cmdline equivalent of this setting
Indeed - as reported in that bug, eSATA hotplug does work on Ubuntu
16.04 (just tried the live image of 16.04.6, kernel 4.15.0-45-generic),
so this is actually a regression.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Possibly related bug #1879276
** Tags added: esata hotplug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890883
Title:
[ICH9M] (e)SATA hotplug doesn't work
Status in linux package
Public bug reported:
Hardware is a laptop - DELL Latitude E6400, SATA controller Intel ICH9M
with 4 ports, at least 2 of which should be hotplug-enabled - the
optical drive bay which has an push-to-eject mechanism, and a combo
eSATA+USB port on the side.
Trying various eSATA and plain SATA
Thanks. I hope the installation worked - I only have Focal now, and the
headers package in that folder was asking for a dependency from Eoan
which I don't have.
Still, I managed to boot the system, and unfortunately the behaviour is
the same.
Aug 1 12:04:56 rpi3 kernel: [ 117.985005]
@Hui, is there a guide/checklist how to test the Pi OS kernel on Ubuntu?
I trie replacing the contents of the FAT partition, and the kernel did
boot, but that's still missing the modules, possibly something else..?
--
You received this bug notification because you are a member of Kernel
** Attachment added: "kernel_5.4.0-1015.log"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5397093/+files/kernel_5.4.0-1015.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
I got myself the Ruideng TC66 USB tester and played a bit with it - it
appears that after the network dies on Raspberry, the system's stable
power consumption ends up higher than when it's functional and idling.
Some stray endless loop, perhaps?
** Attachment added: "RPi3B+ power consumption
@hui.wang - yes, I have seen this a few times in Focal since upgrading
about a month ago. I didn't look at the logs closely, but the message
that appears repeatedly after the interface fails is "eth0: kevent 0 may
have been dropped" I think, and bug #1647397 may be related/identical.
User from
Still observed with 5.3.0-1023 on eoan. Will be switching to focal,
seeing as it should now boot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1861936
Title:
Raspberry Pi 3
Minor update - tried to check what's going on with 5.4 kernel by
listening on the UART - there's no output. Setting standard priority on
the focal-proposed repo, and reinstalling the linux-raspi2 package
(along with its dependencies) from focal-proposed makes no difference.
--
You received this
For reference, recovered the installation with:
cd <1st partition, FAT>
for FILE in *.bak ;do mv -i ${FILE%%.bak} ${FILE%%.bak}.broken; mv -i ${FILE}
${FILE%%.bak}; done
So yeah, kernel 5.4.0.1004.4 is unbootable.
--
You received this bug notification because you are a member of Kernel
@juergh - I'm using origin/priority/pinning, so I installed that kernel
with
apt install linux-raspi2=5.4.0.1004.4 linux-image-raspi2=5.4.0.1004.4
linux-headers=5.4.0.1004.4 # (or something like that)
Now my RPi is stuck at the color palette screen. As there is no grub2
AFAICT, what do I need to
** Description changed:
- Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and
network load. Happened a few times (every time) when I tried to download a
gparted zip release (~350 MiB) directly to the SD card, and then finally when I
tried to scp the finished download
Well, I only managed to replicate it on Ubuntu, and it requires many conditions
to be met:
- 6in4 tunnel to HE.net
- ipv6 rules applied
- ipv6 forwarding enabled
Removing/replacing any one of these made downloading (wget -O /dev/null)
reliable for at least 3 repeats of a large (~1GB+) downloads.
Never mind the LAN7515 heatsink. The issue was avoided by some combination of
other missing configuration (I have since managed to trigger the issue):
- iptables-rules not loaded
- dnsmasq not running
Sometimes (in the full HE.net tunnel + v6 gateway configuration), the
problem is triggered by
Huh... even downloading over HE.net's tunnel doesn't kill it (within the
3 attempts I've tried) now. I have previously added a passive cooler to
the USB/NIC chip as the RPi3 was down for this test.
I'll keep the RPi3 up as a caching DNS + IPv6 gateway (ie. as before,
minus DHCPv4), point DNS
I made a pair of scripts - one sets up the tunnel, addresses on dummy
interfaces, and routing. The other one cleans up.
Testing with iperf does NOT replicate the issue, however. Maybe someone
else can find a test case that reliably triggers the bug. I have some
ideas which I'll try soon.
Sorry for the delayed response. I moved my network back to RPi1 so I can
do experiments on the affected RPi3.
I'm thinking, if this is indeed caused by the usage of a 6in4 tunnel,
and you're unable to set up one with HE.net because of
unavailability/ISP restrictions, it should be possible to set
Oh, I had the URL wrong (archive.ubuntu instead of ports...).
Installed .1019 kernel, headers, etc... issue persists with the new
kernel - dmesg attached.
** Attachment added: "dmesg-1019.txt"
re: dnsmasq - whoops, private repo. Here's another link:
https://paste.ubuntu.com/p/TCwQBkg9vS/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1861936
Title:
Raspberry Pi 3
@hui.wang: Only the RPi is acting as the IPv6 gateway for the network
(it sends router advertisements to internal LAN on br0, issued by
dnsmasq - the relevant dnsmasq config is here:
https://github.com/myxal/DigitalHome/blob/master/configurations/dnsmasq/dnsmasq.d/Echolife6.conf
The mac is
Not quite.
- for downloads, as the issue happens when using IPv6 tunnel, so I'd use wget
-6 ...
- for youtube - this is playing on another machine (Mac running Chromium
browser). I mentioned it because it's significant amount of traffic which, in
presence of IPv6 connectivity, will (mostly) go
How to set up bridge - is github gist link OK?
https://gist.github.com/myxal/6554bd370658a11621a30cd2e6e7d7a8
Testing without IPv6 tunnel - I'm not sure what you mean. If eth0 is the
WAN side, and only wlan0 is for the LAN side, then there's no bridge
needed... This would introduce another NAT
Sorry, got kinda stuck trying to test with a USB NIC:
https://askubuntu.com/q/1212529/325336
After disabling systemd-resolved (+ putting a public DNS IPv4 address in
resolv.conf), v6 download over the external USB NIC (Apple USB Ethernet,
05ac:1402) works fine. After switching the cable back to
> Looks like to setup a 6in4 tunnel, I need a static public IP first
I don't think that static IP is needed to make it work at least
temporarily, I don't have a static one either, just public. You only
need to have public IP on the device you can manage - e.g. router at
home, and make sure that
Where can I find the ~1019 kernel? The repositories are still at ~1018.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1861936
Title:
Raspberry Pi 3 network dies shortly after a
Hi. The USB ports still work fine - I use a USB keyboard to correctly
reboot the machine when it gets stuck. My most recent replication was
with ~1017 kernel, will try the newer ones.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@hui.wang Is there anything else needed from me? The issue still happens
(intermittently under my normal use as an IPv6 gateway).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
** Attachment added: "rules.v6"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326549/+files/rules.v6
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
** Attachment added: "15rpi3-HEnet-Prague.yaml"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326546/+files/15rpi3-HEnet-Prague.yaml
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in
** Attachment added: "99-ipv6-home.conf"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326537/+files/99-ipv6-home.conf
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
** Attachment added: "rules.v4"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326548/+files/rules.v4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
** Attachment added: "10rpi3-bridge-static.yaml"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326547/+files/10rpi3-bridge-static.yaml
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in
(This is still with full setup, ie, jool and iptunnel, traffic using the
tunnel): The first time I tried I also managed to download gparted
without issues, but next time the issue appeared again.
No jool and no tunnel: wget 2x 900MB (ubuntu iso), no issue. scp the
same iso from local machine to
Hmm, will look into this again. I'm using a feature-rich networking
setup (6in4 tunnel, jool NAT64, LAN + WLAN bridge, ip(6)tables), maybe
some of it is also required).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in
** Description changed:
- Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and
network load. Happened a few times when I tried to download a gparted zip
release (~350 MiB) directly to the SD card, and then finally when I tried to
scp the finished download from a desktop
Public bug reported:
Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and
network load. Happened a few times (every time) when I tried to download a
gparted zip release (~350 MiB) directly to the SD card, and then finally when I
tried to scp the finished download from a
@kleber-souza, I should get to it early next week. Which ubuntu releases
do you need? artful and xenial?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1758507
Title:
sky2 gigabit
Yes, the 200 variant also works (3 boots with 3 resumes).
The first boot produced this new warning, but subsequent were OK:
[ 64.072147] [ cut here ]
[ 64.072149] Delta way too big! 18446743987613365433 ts=18446744047041339774
write stamp = 59427974341
Thanks, that appears to have fixed the issue. The lid device non-
compliance message persists, but subsequent resumes by lid (tried 4)
don't kill the NIC anymore.
** Attachment added: "dmesg-4.15.0-14-15-khfeng.txt"
Well this is odd... I tried following the instructions on PM tracing
from https://wiki.ubuntu.com/DebuggingKernelSuspend (using systemctl
suspend instead of pm-suspend), but the system hangs on resume when
tracing is enabled - and this happens also when pm_test is set to
"devices" (doesn't happen
** Description changed:
- After resuming from sleep, OCCASIONALLY the NIC is not functional, and
- reloading the sky2 module does not work. Relevant parts from dmesg:
+ After resuming from sleep using the lid-open event, OFTEN (60%
+ replicable, usually after 2nd or later resume) the NIC is not
+
** Description changed:
- After resuming from sleep using the lid-open event, OFTEN (60%
- replicable, usually after 2nd or later resume) the NIC is not
- functional, and reloading the sky2 module does not help. Relevant parts
- from dmesg:
+ After resuming from sleep, OCCASIONALLY the NIC is not
Hi, I have not been keeping up with ubuntu - before 18.04, I've been using only
16.10 to the extent where this issue would show up, and it didn't appear in
that release (I would suspend and resume the machine at least twice a week).
I would also point out, that I've seen identical symptoms
** Summary changed:
- sky2 gigabit ethernet driver stops working after resume from sleep (88E8055)
+ sky2 gigabit ethernet driver sometimes stops working after resume from sleep
(88E8055)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
- After resuming from sleep, the NIC is not functional, and reloading the
- sky2 module does not work. Relevant parts from dmesg:
+ After resuming from sleep, OCCASIONALLY the NIC is not functional, and
+ reloading the sky2 module does not work. Relevant parts from dmesg:
Public bug reported:
After resuming from sleep, the NIC is not functional, and reloading the
sky2 module does not work. Relevant parts from dmesg:
[ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3
...
[ 827.613729] sky2 :04:00.0: ignoring stuck error report
Related: https://bugs.freedesktop.org/show_bug.cgi?id=93782
Some patches are available there.
** Bug watch added: freedesktop.org Bugzilla #93782
https://bugs.freedesktop.org/show_bug.cgi?id=93782
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "4.8.0-040800rc1-generic-dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+attachment/5086299/+files/4.8.0-040800rc1-generic-dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Attachment added: "4.6.0-040600rc1-generic-dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+attachment/5086297/+files/4.6.0-040600rc1-generic-dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Attachment added: "4.7.0-040700rc1-generic-dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+attachment/5086298/+files/4.7.0-040700rc1-generic-dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Attachment added: "4.5.0-040500rc7-generic-dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685442/+attachment/5086296/+files/4.5.0-040500rc7-generic-dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Strange observation - to save my eyes from the strain of looking at the
old laptop's screen, I hooked up a monitor over VGA - and the stalls
stopped (on both the tested 16.04 and on 18.04!! The message is still
there in dmesg, so this had the positive effect of cutting down the time
to find "first
Tested yesterday's bionic daily server build, issue is still present on
my FSC Esprimo Mobile U9200 (Intel GM965). Hopefully, I'll find time to
track down which -rc release introduced the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Well this is nice surprise - today's daily (liveCD session) detects the
card (inserted after booting with an empty slot) without issues and
without any extra kernel parameters. There seem to be no logs on card
insert/eject (only the first time, when the card's driver is loaded),
but the relevant
Verfied - no problems when booting with the card inserted, the relevant
device are correctly removed from the system.
Consider this bug fixed as of 3.12.0-7
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Tested with today's daily (kernel 3.12.0-7), no issues on 2
susped/resume cycles.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1007841
Title:
11ab:4363 sky2 driver (Marvell Ethernet
Aye, right - turns out I did:
http://marc.info/?l=linux-pmm=134229404527442w=2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1007841
Title:
11ab:4363 sky2 driver (Marvell Ethernet
Actually, that's the same link that's already posted in the summary
since a year ago.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1007841
Title:
11ab:4363 sky2 driver (Marvell
Hello Chris.
Regarding bug progress - sorry, no. I'm not that experienced with kernel code
and building modules.
With that said, I have installed Arch some 2 months ago (kernel 3.10, now it's
at 3.11), and a month ago a daily build of Kubuntu 13.10 (kernel
3.11-rc-something, now updated to
65 matches
Mail list logo
