Yes, it is. Just had it yesterday with an updated testing.
Op zo 23 mei 2021 14:58 schreef Salvatore Bonaccorso :
> Control: tags -1 + moreinfo
>
> Hi,
>
> On Sun, Oct 14, 2018 at 11:21:32AM +0200, Laurent Bigonville wrote:
> > Source: linux
> > Version: 4.18.10-2
> > Followup-For: Bug #895378
>
Package: src:linux
Version: 4.15.11-1
Severity: normal
File: sky2
Dear Maintainer,
* What led up to the situation?
I started up my PC and didn't do anything. The system went into S3.
After I woke it up, all worked, except networking.
* What exactly did you do (or not do) that was effecti
Package: linux-2.6
Version: 3.2.15-1
Severity: normal
I have a Trust 320 Spacecam webcam here, which works fine, but only
after I replug it several times.
At boot time it fails to get initialized:
[2.068557] usbcore: registered new interface driver usbhid
[2.068558] usbhid: USB HID core
Hi,
Thanks Ben, updating to that version of the kernel package in unstable
indeed fixes the problem! :)
At least, I haven't been able to trigger it anymore, but I only tested
for a short time.
If I see it happening again, I'll report back, of course.
--
Kind regards,
Manuel
--
To UNSUB
Hi,
Some extra info: it also occurs on a single core:
$ taskset 0x1 ./a.out
r: 0, id: -6
a.out: monotonic2.c:16: main: Assertion `(current_time.tv_sec >
last_time.tv_sec) || (current_time.tv_nsec >= last_time.tv_nsec)' failed.
Aborted (core dumped)
Another thing: on my system the assert usual
Package: linux-image-2.6.32-4-amd64
Version: ACPI conflict
Severity: normal
When starting up I see this ACPI conflict being reported:
[3.958046] i801_smbus :00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ
18
[3.958050] ACPI: I/O resource :00:1f.3 [0x400-0x41f] conflicts with
AC
Hi,
OK, I got a normal boot again, by upgrading udev to 0.087-2 (from
unstable). It appears that the initramfs-tools from unstable also needs
a newer udev. This does make the ide-disk module get loaded and the
machine boots normally now. Of course I still don't know what the
"can't find init" prob
Hi again,
So, the problem I had is mostly solved, I can boot again, so there's no
huge problem anymore. The only problem is that the ide-disk module
isn't loaded automatically (anymore). This worked fine in the past, so,
something must be wrong.
Note that I installed initramfs-tools 0.55b and tha
Hi,
The remaining problem is that everytime I boot now, I get dropped into a busybox shell where I need to do a
modprobe ide-disk
exit
to continue booting.
Otherwise, it can't find /dev/hda6 (my root partition), because there
are no /dev/hd* devices yet (as the ide-disk module has not been loaded
Hi,
THanks for your input, Frans.2006/3/18, Frans Pop <[EMAIL PROTECTED]>:
> error that it can't find /dev/hda6 (and drops into BusyBox). I suppose> this is because /dev hasn't been populated yet...
/dev/hda6 contains your root filesystem, right?
Indeed.
When you are dropped into the shell:- chec
wat do I do now??
2006/3/17, Manuel Bilderbeek <[EMAIL PROTECTED]>:
> Hi,
>
> Next try: I ran grub-install from the chroot, mounting with -o dev
> made this work. I even did an update-grub and got a menu.lst. After
> setting it all up, I could indeed select the image and atte
Hi,
Next try: I ran grub-install from the chroot, mounting with -o dev
made this work. I even did an update-grub and got a menu.lst. After
setting it all up, I could indeed select the image and attempt a boot.
But I get exactly the same thing: no init found.
So, it doesn't seem to be a grub probl
Hi,
2006/3/17, maximilian attems <[EMAIL PROTECTED]>:
> [ again keep the bug report on cc,
> last reminder ]
Sorry, I got desperate and forgot all about it.
> the device command is crucial if you have no valid /boot/grub/device.map
> you need to adapt the said device to the device of your syst
Hi,
2006/3/17, maximilian attems <[EMAIL PROTECTED]>:
> the easiest thing for your is to look for your next local debian expert.
I'm afraid that's me :)
> you may have forgotten to install the grub package inside of your chroot.
You explicitly told me to run grub-install from outside the chroot
Hi,
2006/3/15, maximilian attems <[EMAIL PROTECTED]>:
> ok so that's the bug you hit, it's closed by 0.55b
> lilo doesn't grog that the initd.img changed without beeing rerun
> grub is much friendlier in those regards.
So I've read.
> yes you need
> a) proc from outside the chroot or maybe it's
Hi,
I'm getting rather desperate: would it be useful to do a
apt-get install --reinstall linux-image-2.6.15-1-k7
from the chroot?
2006/3/15, Manuel Bilderbeek <[EMAIL PROTECTED]>:
> Hi again,
>
> Some more info:
>
> 2006/3/15, maximilian attems <[EMAIL PROTECTED]
Hi again,
Some more info:
2006/3/15, maximilian attems <[EMAIL PROTECTED]>:
> if yes fetch 0.55 from incoming.debian.org or unstable.
Unstable has 0.53c and in incoming.debian.org I only see one file "REPORT".
So, I have no idea how to get it.
--
Grtjs,
Manuel
PS: http://manuel.msxnet.org/
Hi,
2006/3/15, maximilian attems <[EMAIL PROTECTED]>:
> do you use lilo?
Yes I do.
> if yes fetch 0.55 from incoming.debian.org or unstable.
But, will it be able to update my initrd.img via the chroot?
As you have read, I'm having loads of trouble with that.
> did you get dropped to a shell,
Hi
Running the latest Knoppix with a 2.6.12 kernel doesn't help. Please
let me know what I can do to get my system booting again...
Thanks in advance.
--
Grtjs,
Manuel
PS: http://manuel.msxnet.org/
Hi,
I got the same problem again, and it seems it has been caused by yet
another update of initramfs-tools, as there's a 0.53c version in my
/var/cache/apt/archives
The problem is that this time I don't have the other kernel image to
boot. So, I'm writing this from a boot from an old Knoppix cd.
Hi,
maximilian attems wrote:
Anyway, if my kernel image is going to be replaced, while it came from
the linux-image package, does this mean that this kernel package should
be rebuilt with the new initramfs or something?
i don't understand that question.
linux-image generates in postinstall th
Hi,
maximilian attems wrote:
please don't drop the bug report out of cc.
OK, the whole world gets to read stupid details on my system. :P
Does this take (temporarily) extra disk space? I only have 8MB left on
my /boot partition.
your boot partition should already contain an /boot/initd.img
Package: initramfs-tools
Version: 0.52b
Severity: important
Hello,
Yesterday my stock kernel 2.6.15-1-k7 booted fine, but today it panics
with the message that it can't mount the root fs. The 2.6.12 kernel
which I also still have installed works just fine.
It appears that yesterday, in the daily
Package: kernel-image-2.6.8-1-686
Followup-For: Bug #277083
I can confirm the problem:
Calling: /usr/lib/xcdroast/bin/xcdrwrap CDRECORD dev= "ATAPI:0,1,0" gracetime=2
fs=4096k driveropts=burnfree -v -useinfo speed=16 -dao -dummy -eject -pad -text
-audio "/tmp/track-01.wav" ...
scsidev: 'ATAPI:
24 matches
Mail list logo
