Bug#895378: sky2: sky2: did not recover correctly after waking up from S3
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
> >
> > Hi,
> >
> > I can confirm this (and it's quite annoying).
> >
> > It worked fine in 4.14 and it's broken since 4.15.
> >
> > I'm trying to bissect the kernel but it is not even booting ("32-bits
> > relocation outside of the kernel) and I'm not too sure how to fix that.
>
> Is this still an issue with a recent kernel?
>
> Regards,
> Salvatore
>
Bug#895378: sky2: sky2: did not recover correctly after waking up from S3
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 effective (or ineffective)? The system told me that the cable was unplugged, but it wasn't. After I remember the system woke up from S3, I removed the sky2 module and modprobed it again. After that, networking started to work again immediately. * What was the outcome of this action? * What outcome did you expect instead? I expected that networking would just work after waking up from S3. Here's the sky2 story: Boot: [0.961316] sky2: driver version 1.30 [0.961442] sky2 :02:00.0: Yukon-2 EC Ultra chip revision 3 [0.966930] sky2 :02:00.0 eth0: addr 00:22:15:0f:99:ab [7.370976] sky2 :02:00.0 eth0: enabling interface [9.036080] sky2 :02:00.0 eth0: Link is up at 100 Mbps, full duplex, flow control both Auto-suspend to S3 due to inactivity: [ 1214.668015] sky2 :02:00.0 eth0: disabling interface Waking up: [ 1219.713183] sky2 :02:00.0 eth0: enabling interface That's all. No message that the link is up. In fact: [ 1219.716325] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Me, trying to recover by rmmod and modprobing: [ 6711.523687] sky2 :02:00.0 eth0: disabling interface [ 6714.918429] sky2: driver version 1.30 [ 6714.918573] sky2 :02:00.0: Yukon-2 EC Ultra chip revision 3 [ 6714.919025] sky2 :02:00.0 eth0: addr 00:22:15:0f:99:ab [ 6714.939691] sky2 :02:00.0 eth0: enabling interface [ 6716.623117] sky2 :02:00.0 eth0: Link is up at 100 Mbps, full duplex, flow control both -- Package-specific info: ** Version: Linux version 4.15.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-12)) #1 SMP Debian 4.15.11-1 (2018-03-20) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-2-amd64 root=UUID=8efc387d-cdc0-496d-8f3c-03cc7f4ac8a5 ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 1216.216183] smpboot: Booting Node 0 Processor 1 APIC 0x1 [ 1216.223242] cache: parent cpu1 should not be sleeping [ 1216.223320] microcode: sig=0x10677, pf=0x10, revision=0x703 [ 1216.227607] microcode: updated to revision 0x70a, date = 2010-09-29 [ 1216.227817] CPU1 is up [ 1216.227846] smpboot: Booting Node 0 Processor 2 APIC 0x2 [ 1216.230620] cache: parent cpu2 should not be sleeping [ 1216.235237] CPU2 is up [ 1216.235255] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 1216.238015] cache: parent cpu3 should not be sleeping [ 1216.242645] CPU3 is up [ 1216.247339] ACPI: Waking up from system sleep state S3 [ 1216.405572] usb usb3: root hub lost power or was reset [ 1216.405591] usb usb4: root hub lost power or was reset [ 1216.405627] usb usb5: root hub lost power or was reset [ 1216.405688] usb usb6: root hub lost power or was reset [ 1216.405734] usb usb7: root hub lost power or was reset [ 1216.405760] usb usb8: root hub lost power or was reset [ 1216.405818] rtc_cmos 00:01: Alarms can be up to one month in the future [ 1216.406434] serial 00:06: activated [ 1216.417931] sd 2:0:0:0: [sda] Starting disk [ 1216.424886] sd 5:0:0:0: [sdf] Starting disk [ 1216.760886] usb 3-1: reset full-speed USB device number 2 using uhci_hcd [ 1216.787119] ata5: SATA link down (SStatus 0 SControl 300) [ 1216.787136] ata2: SATA link down (SStatus 0 SControl 300) [ 1216.908871] usb 8-2: reset low-speed USB device number 3 using uhci_hcd [ 1216.948872] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1216.948885] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 1216.949120] ata6.00: supports DRM functions and may not be fully accessible [ 1216.953581] ata6.00: supports DRM functions and may not be fully accessible [ 1216.958405] ata6.00: configured for UDMA/133 [ 1216.958457] ata6.00: Enabling discard_zeroes_data [ 1217.001936] ata4.00: configured for UDMA/100 [ 1217.172872] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 1217.175606] ata1.00: configured for UDMA/66 [ 1217.476878] usb 8-1: reset low-speed USB device number 2 using uhci_hcd [ 1219.548864] floppy driver state [ 1219.548864] --- [ 1219.548871] now=4295197184 last interrupt=4294892540 diff=304644 last called handler=reset_interrupt [floppy] [ 1219.548872] timeout_message=lock fdc [ 1219.548872] last output bytes: [ 1219.548873] 8 80 4294892535 [ 1219.548874] 8 80 4294892535 [ 1219.548875] 8 90 4294892535 [ 1219.548875] 8 80 4294892539 [ 1219.548876] 8 90 4294892539 [ 1219.548877] 8 80 4294892539 [ 1219.548877] 8 90 4294892539 [ 1219.548878] e 80 4294892539 [ 1219.548879] 13 90 4294892539 [ 1219.548879] 0 90 4294892539 [ 1219.548880] 1a 90 4294892539 [ 1219.548881] 0 90 4294892539 [ 1219.548881] 12 90 4294892539 [ 1219.548882] 0 90 4294892539 [ 1219.548883] 14 90
Bug#669894: linux-image-3.2.0-2-amd64: Webcam (ov519) only works after replugging it several times
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 driver [2.152152] usb 1-2.2: new full-speed USB device number 5 using ehci_hcd [2.240152] usb 1-2.2: device descriptor read/64, error 8 [2.432150] usb 1-2.2: device descriptor read/64, error 8 [2.624153] usb 1-2.2: new full-speed USB device number 6 using ehci_hcd [2.712149] usb 1-2.2: device descriptor read/64, error 8 other stuff [2.904149] usb 1-2.2: device descriptor read/64, error 8 [3.096152] usb 1-2.2: new full-speed USB device number 7 using ehci_hcd [3.116523] usb 1-2.2: device descriptor read/8, error -61 [3.236522] usb 1-2.2: device descriptor read/8, error -61 [3.428150] usb 1-2.2: new full-speed USB device number 8 using ehci_hcd [3.448523] usb 1-2.2: device descriptor read/8, error -61 [3.568523] usb 1-2.2: device descriptor read/8, error -61 [3.672157] hub 1-2:1.0: unable to enumerate USB device on port 2 when I replug it, it still fails: [20206.700129] usb 1-2.2: new full-speed USB device number 9 using ehci_hcd [20206.788133] usb 1-2.2: device descriptor read/64, error 8 [20206.980147] usb 1-2.2: device descriptor read/64, error 8 [20207.172135] usb 1-2.2: new full-speed USB device number 10 using ehci_hcd [20207.260131] usb 1-2.2: device descriptor read/64, error 8 [20207.452145] usb 1-2.2: device descriptor read/64, error 8 [20207.644143] usb 1-2.2: new full-speed USB device number 11 using ehci_hcd [20207.664510] usb 1-2.2: device descriptor read/8, error -61 [20207.784395] usb 1-2.2: device descriptor read/8, error -61 [20207.976145] usb 1-2.2: new full-speed USB device number 12 using ehci_hcd [20207.996513] usb 1-2.2: device descriptor read/8, error -61 [20208.116515] usb 1-2.2: device descriptor read/8, error -61 [20208.220157] hub 1-2:1.0: unable to enumerate USB device on port 2 then I replug it again and it works 100% fine: [20279.404085] usb 1-2.2: new full-speed USB device number 13 using ehci_hcd [20279.513459] usb 1-2.2: New USB device found, idVendor=05a9, idProduct=8519 [20279.513462] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [20279.513465] usb 1-2.2: Product: USB Camera [20279.513466] usb 1-2.2: Manufacturer: OmniVision Technologies, Inc. [20279.714000] Linux media interface: v0.10 [20279.727781] Linux video capture interface: v2.00 [20279.730517] gspca_main: v2.14.0 registered [20279.733294] gspca_main: ov519-2.14.0 probing 05a9:8519 [20279.916286] input: ov519 as /devices/pci:00/:00:1a.7/usb1/1-2/1-2.2/input/input8 [20279.916482] usbcore: registered new interface driver ov519 [20279.917794] usbcore: registered new interface driver snd-usb-audio As it works fine after replugging (twice), I guess it's not a problem with the hardware... -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.15-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Sun Apr 15 16:47:38 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 root=UUID=12635a70-3def-4b39-bc78-1ee0ad29a2d2 ro quiet ** Tainted: PWO (4609) * Proprietary module has been loaded. * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [19194.144009] eth1: no IPv6 routers present [19242.064006] eth1: no IPv6 routers present [19524.928020] usb 1-5: reset high-speed USB device number 3 using ehci_hcd [19586.21] usb 1-5: reset high-speed USB device number 3 using ehci_hcd [19587.840008] eth1: no IPv6 routers present [19635.536011] eth1: no IPv6 routers present [19683.856011] eth1: no IPv6 routers present [19731.584009] eth1: no IPv6 routers present [20076.080007] eth1: no IPv6 routers present [20124.624007] eth1: no IPv6 routers present [20172.256007] eth1: no IPv6 routers present [20206.700129] usb 1-2.2: new full-speed USB device number 9 using ehci_hcd [20206.788133] usb 1-2.2: device descriptor read/64, error 8 [20206.980147] usb 1-2.2: device descriptor read/64, error 8 [20207.172135] usb 1-2.2: new full-speed USB device number 10 using ehci_hcd [20207.260131] usb 1-2.2: device descriptor read/64, error 8 [20207.452145] usb 1-2.2: device descriptor read/64, error 8 [20207.644143] usb 1-2.2: new full-speed USB device number 11 using ehci_hcd [20207.664510] usb 1-2.2: device descriptor read/8, error -61 [20207.784395] usb 1-2.2: device descriptor read/8, error -61 [20207.976145] usb 1-2.2: new full-speed USB device number 12 using ehci_hcd [20207.996513] usb 1-2.2: device descriptor read/8, error -61 [20208.116515] usb 1-2.2: device descriptor read/8, error -61 [20208.220157] hub 1-2:1.0: unable to enumerate USB device on port 2 [20220.552011] eth1: no IPv6 routers present [20279.404085] usb 1-2.2: new full-speed USB device number 13 using
Bug#594742: Fixed!
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 UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c7e9aa7.5080...@msxnet.org
Bug#594742: Also on single CPU
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 usually gets hit in less than a second. HTH... Also, I heard from another user who also could reproduce it, so it's not specific to my hardware. I'll ask him to submit details. -- Kind regards, Manuel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c7d6a1c.40...@msxnet.org
Bug#576408: linux-image-2.6.32-4-amd64: ACPI conflict
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 ACPI region SMRG [0x400-0x40f] [3.958122] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver /proc/ioports reveals: 0400-041f : :00:1f.3 04d0-04d1 : pnp 00:08 This is on an Asus P5Q-E mobo. As I didn't tweak anything, I thought I'd better report it. If I can provide any more information, please let me know. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100404101349.11166.4383.report...@sonata
Bug#354458: Kernel panic after upgrading initramfs-tools
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 problem was, but upgrading udev and initramfs-tools (both!) to the ones currently in unstable certainly solved that. (Case closed, for now!) -- Grtjs,ManuelPS: http://manuel.msxnet.org/
Bug#354458: Kernel panic after upgrading initramfs-tools
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:- check if /dev/hda6 really is not there: 'ls /dev/hda*' /dev/hpts is what came closest... It wasn't there indeed. - check if the modules you need for your disk are loaded:'cat /proc/modules' (check for ide-disks too!) - if any modules are missing, use modprobe to load the manually I modprobed ide-core and ide-disk. This gave me the /dev/hda devices! - check if /dev/hda6 now appears- after it does, type exit to continue the boot YAY! It boots again! :D One thing: how do I get it to boot normally? I now did a dpkg-reconfigure linux-image-2.6.15-1-k7. I hope this is enough next time I boot (I'll report back if it isn't, and if you already konw it isn't, please let me know!) -- Grtjs,ManuelPS: http://manuel.msxnet.org/
Bug#354458: Kernel panic after upgrading initramfs-tools
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 yet). What do I do about this?-- Grtjs,ManuelPS: http://manuel.msxnet.org/
Bug#354458: Kernel panic after upgrading initramfs-tools
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 that I have a VIA 82C chipset. If this is a bug in initramfs-tools, please send me an updated package (which you actually also offered a few mails back), so I can test if it solves this problem. Thanks!-- Grtjs,ManuelPS: http://manuel.msxnet.org/
Bug#354458: Kernel panic after upgrading initramfs-tools
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 (so, the Knoppix one), so I didn't do anything else. you'll get an chroot from an recent debian etch beta 2 installer, which you can boot with rescue and there is an reinstall grub in the rescue operation menu (which will rerun the grub-install you already tried) but not install grub itself that you need to do from the chroot Well, you should have told me then :) I'll try to install grub from the chroot. How can I prevent it in the future? always keep 2 linux-images to boot into it, initramfs-tools only updates your newest one. Yeah, but unfortunately, due to my small root partition, I had to remove the older kernel. I tried to reinstall it, but 2.6.12 had been removed from etch. About your next mail: that device command simply isn't available in the grub commandline that I get. It doesn't exist. Maybe it's too old? I think it's grub 0.95. According to Knoppix it's 0.95+cvs20040624-17. -- Grtjs, Manuel PS: http://manuel.msxnet.org/
Bug#354458: Kernel panic after upgrading initramfs-tools
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 problem. Maybe the initramfs update screwed something up? I'm very close to buying a new harddisk and doing a fresh install, but I would really appreciate it if you can help me still. -- Grtjs, Manuel PS: http://manuel.msxnet.org/
Bug#354458: Kernel panic after upgrading initramfs-tools
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... My system has become unbootable! The error is (including typos): RAMDISK: couldn't find a valid RAM disk image starting at 0 VFS: Cannot open root device 306 or unknown-block at (3,6) PLease append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,6) I tried to chroot to the disk, but running update-initramfs -t -u -k 2.6.15-1-k7 updates the initrd.img, but doesn't fix the problem. Also dpkg-reconfigure linux-image-* doesn't help, I get this error: # dpkg-reconfigure linux-image-2.6.15-1-k7 sh: /dev/null: Permission denied sh: /dev/null: Permission denied Running depmod. Finding valid ramdisk creators. sh: /dev/null: Permission denied sh: /dev/null: Permission denied Failed to find suitable ramdisk generation tool for kernel version 2.6.15-1-k7 on running kernel 2.4.20-xfs in mkinitramfs-kpkg mkinitrd.yaird Both initramfs-tools and yaird are installed of course. I will now try to burn a Knoppix cd with a 2.6 kernel, to see if that improves things. Can you please do something about this problem (which causes the kernel panics)? It's quite annoying! Thanks! PLease e-mail me to this address if you have any other advice. -- Grtjs, Manuel PS: http://manuel.msxnet.org/
Bug#354458: Kernel panic after upgrading initramfs-tools
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/
Bug#354458: Kernel panic after upgrading initramfs-tools
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, No, I got a system freeze. i would need the last 2 lines above RAMDISK, what's there? I can check again, but AFAIK it is something about ACPI or so. I can check again, but rebooting takes a lot of time. which busybox are your running? dpkg -l busybox I only did this via the chroot from the Knoppix cd. But I have 1.01-4 if you want to know. good luck! I have no idea how to get my system running again... :((( -- Grtjs, Manuel PS: http://manuel.msxnet.org/
Bug#354458: Kernel panic after upgrading initramfs-tools
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/
Bug#354458: Kernel panic after upgrading initramfs-tools
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]: 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/ -- Grtjs, Manuel PS: http://manuel.msxnet.org/
Bug#354458: Kernel panic after upgrading initramfs-tools
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 enough from inside mount /proc /chroot/proc -t proc I mounted it from the inside, which seems to work. b) the devices from inside the chroot /etc/init.d/udev start This doesn't work: # /etc/init.d/udev start /lib/lsb/init-functions: line 130: /dev/null: Permission denied udev requires a mounted sysfs, not started. /lib/lsb/init-functions: line 130: /dev/null: Permission denied failed! so I did: # mount /sys -t sysfs AFter that, I get: # /etc/init.d/udev start It has been detected that the command /etc/init.d/udev has been run from an interactive shell. It will probably not do what you expect, so this script will wait 60 seconds before continuing. Press ^C to stop it. RUNNING THIS COMMAND IS HIGHLY DISCOURAGED! So, to be sure I'm asking: are you REALLY sure?? now run lilo I tried running lilo without the udev stuff, but that clearly didn't work:: # lilo /proc/misc: No entry for device-mapper found Is device-mapper driver missing from kernel? /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. /proc/misc: No entry for device-mapper found Is device-mapper driver missing from kernel? /dev/mapper/control: open failed: Permission denied Failure to communicate with kernel device-mapper driver. Incompatible libdevmapper 1.01.04 (2005-08-02)(compat) and kernel driver Fatal: open /dev/hda: Permission denied if lilo doesn't work out for you use from knoppix (adapt to your device) grub-install --root-directory=/mnt/hda1 /dev/hda I'll first try with lilo if you can confirm that I should indeed run udev as you said, ignoring the very strong warning. -- Grtjs, Manuel PS: http://manuel.msxnet.org/
Bug#354458: Kernel panic after upgrading initramfs-tools/klibc-utils/libklibc
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 the initrd.img with a preconfigured set of initramfs generators for 2.6 that's initramfs-tools and yaird. with initramfs-tools you just need to copy your boot to your new partition tell your boot loader to make it bootable and it should work. Ah, I thought the initrd image also came from the linux-image package. hmm exact error messages always help. so please retest or i can't do much about that report. Well, before I tested I did another dist-upgrade (just got back from holidays), and this installed both a new kernel and a new initramfs-tools, and now I can just boot the kernel nicely. So, as far as I'm concerned the bug can be closed. I think regenerating the initrd. img would have worked, though, but I can't check that now. -- Grtjs, Manuel PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ ) PPS: Visit my homepage at http://manuel.msxnet.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354458: Kernel panic after upgrading initramfs-tools/klibc-utils/libklibc
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 dist-upgrade (on testing), I got these packages: -rw-r--r-- 1 root root 37520 2006-02-20 14:47 initramfs-tools_0.52b_all.deb -rw-r--r-- 1 root root 117448 2006-02-18 18:47 klibc-utils_1.2.2-3_i386.deb -rw-r--r-- 1 root root 18582 2006-02-18 18:47 libklibc_1.2.2-3_i386.deb As I haven't touched the LILO or kernel setup in anyway, I strongly suspect that one of these broke my kernel boot. Any ideas for workarounds are welcome! -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages initramfs-tools depends on: ii busybox 1:1.01-4 Tiny utilities for small and embed ii cpio 2.6-10 GNU cpio -- a program to manage ar ii klibc-utils 1.2.2-3small statically-linked utilities ii udev 0.084-5/dev/ and hotplug management daemo initramfs-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354458: Kernel panic after upgrading initramfs-tools/klibc-utils/libklibc
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-2.6.15-1-k7 so that will only replace it. 8 mb should be fine, consider enlarging your partition. Of course, but it's a long story. I'll promise to buy a new disk soon and move all files to it, OK? :P 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? try aboves if it doesn't work please send the output from the busybox shell of cat /proc/cmdline, cat /proc/modules and ls /dev/sda* or ls /dev/hda* I didn't get a busybox shell... It just halted. what are the last erorr messages? As it's not recorded anywhere and I didnt' write it down, it's hard to say exactly. But the last few lines were all about that it coudln't mount the root fs and that I should pass a proper root= parameter to the kernel. -- Grtjs, Manuel PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ ) PPS: Visit my homepage at http://manuel.msxnet.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#277083: kernel-image-2.6.8-1-686: Confirmed, also with -k7 version
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:0,1,0' devname: 'ATAPI' scsibus: 0 target: 1 lun: 0 Warning: Using ATA Packet interface. Warning: The related Linux kernel interface code seems to be unmaintained
