I have the same problem, only reboot solve the eth0 problem.
"3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux"
Aug 2 08:40:01 XSERVER /USR/SBIN/CRON[12935]: (munin) CMD (if [ -x
/usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
Aug 2 08:40:04 XSERVER kernel: [47011.896188] alx
Package: src:linux
Version: 3.10.3-1
Severity: normal
Dear Maintainer,
Running almost entirely jessie/testing I installed linux-image-3.10-1-amd64
from unstable. When using it and mounting my autofs mounting NFSv3 volume it
hangs for around 15 seconds then mounts. This is recorded in syslog when
Another workaround is to monitor dmesg, and if mei_me errors occur on
resume, perform another suspend/resume cycle to stop the errors. I have
not seen any panic when taking these precautions.
More upstream discussion about (now five) patches for 3.11 that together
appear to fix this problem:
Processing control commands:
> reassign -1 src:linux 3.2.46-1
Bug #718595 [x11-common] x11-common: Graphical and console display scrambled on
resume from sleep/hibernate
Bug reassigned from package 'x11-common' to 'src:linux'.
No longer marked as found in versions xorg/1:7.7+3~deb7u1.
Ignoring re
Package: src:linux
Version: 3.10.3-1
Followup-For: Bug #717383
I should mention these too:
Aug 2 17:29:21 kernel: [91731.535736] mei_me :00:16.0: unexpected reset:
dev_state = RESETTING
Aug 2 17:29:21 kernel: [91731.535762] mei_me :00:16.0: reset: wrong host
start response
seen in /v
I haven't heard anything on this issue and wanted to check in...
Processing control commands:
> reassign -1 live-boot
Bug #718518 [src:linux] base: fails to mount vfat filesystem.
Bug reassigned from package 'src:linux' to 'live-boot'.
Ignoring request to alter found versions of bug #718518 to the same values
previously set
Ignoring request to alter fixed vers
Control: reassign -1 live-boot
On Fri, 2013-08-02 at 16:50 +0200, Holger Levsen wrote:
> control: reassign -1 src:linux
>
> On Freitag, 2. August 2013, atar wrote:
> > Package: base
> > Severity: important
> >
> >
> > When using Debian on a USB stick with the kive-boot project, after
> > upgradi
Processing control commands:
> reassign -1 src:linux
Bug #718518 [base] base: fails to mount vfat filesystem.
Bug reassigned from package 'base' to 'src:linux'.
Ignoring request to alter found versions of bug #718518 to the same values
previously set
Ignoring request to alter fixed versions of bu
control: reassign -1 src:linux
On Freitag, 2. August 2013, atar wrote:
> Package: base
> Severity: important
>
>
> When using Debian on a USB stick with the kive-boot project, after
> upgrading the kernel to version number: 2.6.32-5-686, the system isn't
> able to mount a vfat filesystem anymore
Tejun Heo writes:
> Hello, Greg.
>
> I think the following commit should go into -stable but forgot to cc
> stable. It's now in Linus' tree. Can you please include it in
> -stable?
>
> Thanks!
>
> On Mon, Jul 22, 2013 at 05:13:07PM -0400, Tejun Heo wrote:
>> From bb9696192826a7d9279caf872e95b41
Hi there,
I appreciate you are doing this in your free time, but really this issue is
quite urgent to be addressed. I haven't been able to get to my Debian
Jessie for a while as I have my disks in RAID...
Thanks a lot!!
--
Marcos R Carot
I added rootdelay=5 and the host booted normally. It's just a timing issue.
It looks like 3.10 is just taking too long.
FYI this hardware is a standard PC motherboard and five ST3500630AS
SATA150 disks for the root part. I also have an older PC here with
three disks which I was able to repr
Thorsten,
I’d like the m68k people to read the whole eMail and test
https://www.freewrt.org/~tg/dp/dists/hacks/dirty/Crossbuilt/linux/
linux-image-3.10-0+m68k.1-m68k_3.10.1-1+m68k.1_m68k.deb
on all their boxen, at least Amiga/Atari/Macintosh
Not anytime soon - the boot disk on my Falcon just
Correct, this is mdraid, not dmraid. There is no dmraid on this host.
As for bug 678696, this could be a timeout issue, but I I don't know. I
will keep it in mind.
I will go play with it here for an hour and then let you know what I
think...
--
To UNSUBSCRIBE, email to debian-kernel-req
On Thu, 2013-08-01 at 16:35 -0700, Jesse Molina wrote:
> Package: initramfs-tools
> Version: 0.113
> Severity: serious
> Justification: unbootable
>
>
> I rebooted a system today on linux-image-3.10-1-amd64 and it was
> unable to boot.
>
> linux-image-3.2.0-x-amd64 works fine. A "initrd.img-3.2
Disregard my original comments regarding the dm-raid45 thing. That was
just a wrong hunch, as the same module info is in both initrd images and
so it is unlikely to be the cause.
I am less inclined to think this is a bug in mdadm, though I agree that
this will probably get re-assigned to so
Processing commands for cont...@bugs.debian.org:
> severity 718533 important
Bug #718533 [initramfs-tools] linux-image-3.10-1-amd64: RAID5 unbootable,
module not
Severity set to 'important' from 'serious'
> retitle 718533 linux-image-3.10-1-amd64 fails to boot with RAID5
Bug #718533 [initramfs-to
severity 718533 important
retitle 718533 linux-image-3.10-1-amd64 fails to boot with RAID5
thanks
* Jesse Molina [Thu Aug 01, 2013 at 04:35:23PM -0700]:
> I rebooted a system today on linux-image-3.10-1-amd64 and it was unable to
> boot.
> linux-image-3.2.0-x-amd64 works fine. A
> "initrd.img-
19 matches
Mail list logo
