Re: Branches post-wheezy
Your decision. However, as backports is now the same dak instance as the main archive, -master should be able to find a way to make this without the overhead. You mean, simply copying the testing packages into backports if their dependencies are met within stable+backports? That would be nice. Would you like to work on dak for a while? Thats not a problem of dak. Well, dependency checks would need some code, but moving from one to the other is what we do daily for testing. This would just be another suite to move from and to. The more interesting parts to tackle are - the policy of backports suites doesn't allow this. - Backports having a certain version number schema does help a lot for users to see which they have installed with a simple dpkg -l. Those are things you want to discuss with the backports team, probably using their mailinglist. When thats done and they want it, we are at debian-dak@ldo to discuss how to best do it technically. :) -- bye, Joerg 2.5 million B.C.: OOG the Open Source Caveman develops the axe and releases it under the GPL. The axe quickly gains popularity as a means of crushing moderators heads. -- 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/87bo8v6nat@gkar.ganneff.de
Bug#706476: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2))
On Wed, May 1, 2013 at 3:33 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: This is an automatic notification regarding your Bug report which was filed against the linux-image-3.2.0-4-486 package: #706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2) It has been closed by Ben Hutchings b...@decadent.org.uk. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Ben Hutchings b...@decadent.org.uk by replying to this email. -- 706476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Forwarded message -- From: Ben Hutchings b...@decadent.org.uk To: 706476-d...@bugs.debian.org Cc: Date: Wed, 01 May 2013 03:31:35 +0100 Subject: Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2) On Tue, 2013-04-30 at 18:39 +0100, Ben Hutchings wrote: On Tue, Apr 30, 2013 at 05:22:56PM +0100, lkcl wrote: Package: linux-image-3.2.0-4-486 Severity: important discovered from another debian bugreport that pc-engines systems can be upgraded to more recent firmware and work with linux-image-3.2.0-4-486 (which is great!) and also discovered that the geodewdt kernel module has been compiled, which is also great (as it's missing from the 2.6.32 debian kernel builds) however what's not so great is that the GPIO 5535 kernel driver has been left out, and it is a requirement for the project. as native builds on 500mhz AMD Geodes take absolutely forever it would be nice if this could be corrected. kernel option is GPIO_CS5535 [...] That's odd, this was enabled in 3.1.0~rc4-1~experimental.1: * [i386] Enable GPIO_CS5535, MFD_CS5535, CS5535_MFGPT, CS5535_CLOCK_EVENT_SRC, GPIO_VX855, MFD_VX855 as modules; [i386/486] Enable OLPC_XO1_PM, OLPC_XO1_RTC, OLPC_XO1_SCI, OLPC_XO15_SCI (Closes: #639113) and is still enabled in the config files in the source package. There must be some new dependency that has forced it off again. I'll look at this later. It *is* still enabled, but it's built-in on the 486 flavour because OLPC_XO1_SCI selects it. thanks ben... investigating further: # PCI GPIO expanders: # CONFIG_GPIO_CS5535=y # CONFIG_GPIO_LANGWELL is not set CONFIG_GPIO_PCH=m CONFIG_GPIO_ML_IOH=m # CONFIG_GPIO_RDC321X is not set bizarre. so why the heck is i think it's changed quite a lot from 2.6.32, no major-minor numbers any more, to a generic GPIO interface which i've not yet understood/tracked down. so yes, more work to do but at least a route to investigate. thanks ben. l. -- 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/CAPweEDxgqV-7N2z+Bv74Q3hOj33F=iyn+v-n9f3znyworoq...@mail.gmail.com
Bug#706476: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2))
On Wed, May 1, 2013 at 10:56 AM, Luke Kenneth Casson Leighton l...@lkcl.net wrote: It *is* still enabled, but it's built-in on the 486 flavour because OLPC_XO1_SCI selects it. thanks ben... investigating further: # PCI GPIO expanders: # CONFIG_GPIO_CS5535=y # CONFIG_GPIO_LANGWELL is not set CONFIG_GPIO_PCH=m CONFIG_GPIO_ML_IOH=m # CONFIG_GPIO_RDC321X is not set bizarre. so why the heck is i think it's changed quite a lot from 2.6.32, no major-minor numbers any more, to a generic GPIO interface which i've not yet understood/tracked down. so yes, more work to do but at least a route to investigate. thanks ben. right. the issue is this: CONFIG_GPIO_CS5535 appears to hook into the standard linux kernel gpio subsystem (gpiolib), which is *not* exposed to userspace unless you set CONFIG_EXPERIMENTAL, CONFIG_SYSFS and CONFIG_SYSFS_GPIO. contrast this with 2.6.32 where CONFIG_CS5535_GPIO exposed GPIO directly into userspace as a major/minor device and you see what the issue is. # # Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks. # CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y CONFIG_GPIOLIB=y # CONFIG_DEBUG_GPIO is not set # CONFIG_GPIO_SYSFS is not set right. that's the problem - CONFIG_GPIO_SYSFS isn't set. as this alix6f2 board is being used for pulling relays on powered equipment which is mission-critical, using the LEDs for status information, resetting the internal MiniPCIe modem if it goes belly-up and so on, this is a major functional step backwards, and we may have to return to the 2.6.32 kernel with *no* watchdog support. also of note is that i had to put this into modprobe.d for 2.6.32: cs5535_gpio options cs5535_gpio mask=0x this allows us to use GPIOs which were allocated to LEDs, buzzer and so on on *this* device, whereas other devices may use those GPIOs for functions that may not be appropriate for general use. in resolving this it would be appreciated to bear in mind that we *need* that mask value. also, if the GPIO_CS5535 module is built-in and GPIO_SYSFS is enabled as well, then there's the possibility that people will randomly poke around ... but only the once :) if these are done as modules then even if GPIO_SYSFS is built-in and populates /sys/class/gpio it will at least be empty until modprobe gpio_cs5535 is called (and in our case with the mask parameter), and that will only really be done by people who know what they're doing. now to work out how to re-open this bug :) l. -- 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/capweedxrusqpfyfiq33um9cv4frcxuywxjnaqxr6a28tuee...@mail.gmail.com
Processed: Re: Bug#706476 closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2))
Processing commands for cont...@bugs.debian.org:
reopen 706476
Bug #706476 {Done: Ben Hutchings b...@decadent.org.uk}
[linux-image-3.2.0-4-486] linux-image-3.2.0-4-486: amd geode gpio-cs5535 module
not being compiled (needed for alix6f2)
Bug reopened
Ignoring request to alter fixed versions of bug #706476 to the same values
previously set
End of message, stopping processing here.
Please contact me if you need assistance.
--
706476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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/handler.s.c.13674044247901.transcr...@bugs.debian.org
Bug#706476: Info received (Bug#706476 closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2)))
i've added these at the end of debian/config/i386/none/config.i486 and then checked debian/build/build_i386_none_486/.config but CONFIG_GPIO_CS5535 had been modified to y, ah well. fakeroot make -f debian/rules.gen -j16 binary-arch_i386_none_486 still running... # # GPIOLIB and SYSFS # CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y CONFIG_GPIOLIB=y # CONFIG_DEBUG_GPIO is not set CONFIG_GPIO_SYSFS=y # # PCI GPIO expanders: # CONFIG_GPIO_CS5535=m -- 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/CAPweEDxVV6Fbe3S6rDPyEtjgo80_ShiO=iz6anqhcxa20yf...@mail.gmail.com
Processed (with 5 errors): Re: Bug#706499 closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#706499: Ethernet with Realtek R8169 only working with IPV6)
Processing commands for cont...@bugs.debian.org:
reopen 706499
Bug #706499 {Done: Ben Hutchings b...@decadent.org.uk} [firmware-realtek]
Ethernet with Realtek R8169 only working with IPV6
Bug reopened
Ignoring request to alter fixed versions of bug #706499 to the same values
previously set
|reassign| 706499 linux-image-3.2.0-4-486
Unknown command or malformed arguments to command.
Closing a bug will not fix it. ;-)
Unknown command or malformed arguments to command.
This is normally the strategy solving problems at ubuntu.
Unknown command or malformed arguments to command.
Regards
Unknown command or malformed arguments to command.
Karsten
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.
Please contact me if you need assistance.
--
706499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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/handler.s.c.136741785013470.transcr...@bugs.debian.org
Processed (with 4 errors): Re: Bug#706499 closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#706499: Ethernet with Realtek R8169 only working with IPV6)
Processing commands for cont...@bugs.debian.org: reassign 706499 linux-image-3.2.0-4-486 Bug #706499 [firmware-realtek] Ethernet with Realtek R8169 only working with IPV6 Bug reassigned from package 'firmware-realtek' to 'linux-image-3.2.0-4-486'. No longer marked as found in versions firmware-nonfree/0.36+wheezy.1. Ignoring request to alter fixed versions of bug #706499 to the same values previously set Closing a bug will not fix it. ;-) Unknown command or malformed arguments to command. This is normally the strategy solving problems at ubuntu. Unknown command or malformed arguments to command. Regards Unknown command or malformed arguments to command. Karsten Unknown command or malformed arguments to command. End of message, stopping processing here. Please contact me if you need assistance. -- 706499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.136741788914191.transcr...@bugs.debian.org
Processed: retitle 706476 to [x86] GPIOs not exposed to userland, severity of 706476 is wishlist
Processing commands for cont...@bugs.debian.org: retitle 706476 [x86] GPIOs not exposed to userland Bug #706476 [linux-image-3.2.0-4-486] linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2) Changed Bug title to '[x86] GPIOs not exposed to userland' from 'linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2)' severity 706476 wishlist Bug #706476 [linux-image-3.2.0-4-486] [x86] GPIOs not exposed to userland Severity set to 'wishlist' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 706476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13674219559505.transcr...@bugs.debian.org
Bug#648754: suspend is flakey, shutdown -h now does not power off
# approximating found 648754 linux/3.8.5-1~experimental.1 quit On Mon, Apr 29, 2013 at 02:52:19PM +0100, Ben Hutchings wrote: On Mon, Apr 29, 2013 at 07:21:11AM +, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: reassign 648754 src:linux linux-2.6/3.1.0-1~experimental.1 Please don't reassign issues to src:linux unless they've been reproduced in a kernel version that was actually built from that source package. Matthieu also experienced the bug with 3.8.10 from upstream, I'm afraid. See https://bugzilla.kernel.org/show_bug.cgi?id=57231 Thanks, Jonathan -- 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/20130501190348.go24...@google.com
Processed: Re: suspend is flakey, shutdown -h now does not power off
Processing commands for cont...@bugs.debian.org: # approximating found 648754 linux/3.8.5-1~experimental.1 Bug #648754 [src:linux] [regression] suspend is flakey, shutdown -h now does not power off Bug #648522 [src:linux] [regression] suspend is flakey, shutdown -h now does not power off Marked as found in versions linux/3.8.5-1~experimental.1. Marked as found in versions linux/3.8.5-1~experimental.1. quit Stopping processing here. Please contact me if you need assistance. -- 648522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648522 648754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13674350387530.transcr...@bugs.debian.org
Bug#706355: Fwd: Re: Bug#706355: linux-image-3.2.0-4-amd64: Kernel Panic with the new kernel during booting
Hi, OK, so this is a very simple case and it's very surprising that it fails. If you reboot back to the old kernel version, does that still work? Can you capture the kernel log from a failed boot? If you add 'break=bottom' to the kernel command line, you should get to a shell in the initramfs. You can then mount a USB flash drive or similar, and copy the boot messages to it, e.g.: (initramfs) ls -l /dev/sda2 # did the SATA drive appear This case could have a hardware (harddisk problem ?) component. I have noticed Grub to issue error messages before loading the boot option screen in some of the trial boots. The message was: Grub: error: hd0 out of disk. In one case, it even entered rescue mode. In other cases, boot screen appeared. In ~2/4 cases no problem happened despite the warning by Grub. In other 2 cases kernel reported at the start of boot: loading initramfs. No such file or directory. Then it starts loading kernel. In the next screen it panics as reported before. I did try your trick 'break=bottom' in kernel boot option line. However, this works when kernel has mostly booted, and it gives me a busybox shell. However, when kernel panic happened it happened much earlier, and no commands would work (including ALT-Sysrq-B to reboot). I could cause the old kernel to also panic in one such occasion. Hope these give some clues. Regards, Subhashis On Wed, May 1, 2013, at 10:47 PM, Subhashis Roy wrote: - Original message - From: Ben Hutchings b...@decadent.org.uk To: Subhashis Roy subhash...@fastmail.fm Cc: 706...@bugs.debian.org Subject: Re: Bug#706355: linux-image-3.2.0-4-amd64: Kernel Panic with the new kernel during booting Date: Tue, 30 Apr 2013 14:35:25 +0100 On Mon, 2013-04-29 at 13:57 +0500, Subhashis Roy wrote: Hi, This panic is expected if the root filesystem could not be mounted. So the question is, why did that fail? Is the root device a simple partition or logical volume? Is the physical device attached by SATA, USB, or other means? The root device is a simple partition '/dev/sda2' (the details of it was already part of the mail as captured by 'reportbug' when it booted from the kernel on which I flled the bug report). The physical volume is attached by SATA. OK, so this is a very simple case and it's very surprising that it fails. If you reboot back to the old kernel version, does that still work? Can you capture the kernel log from a failed boot? If you add 'break=bottom' to the kernel command line, you should get to a shell in the initramfs. You can then mount a USB flash drive or similar, and copy the boot messages to it, e.g.: (initramfs) ls -l /dev/sda2 # did the SATA drive appear? ls: /dev/sda2: No such file or directory (initramfs) mkdir /mnt (initramfs) mount /dev/sda1 /mnt # removable drive should be sda (initramfs) dmesg /mnt/dmesg (initramfs) umount /mnt (initramfs) reboot -f Ben. -- Ben Hutchings Knowledge is power. France is bacon. -- -- -- http://www.fastmail.fm - Send your email first class Email had 1 attachment: + signature.asc 1k (application/pgp-signature) -- -- -- http://www.fastmail.fm - Faster than the air-speed velocity of an unladen european swallow -- 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/1367439760.9667.140661225339837.29aed...@webmail.messagingengine.com
Bug#706355: marked as done (linux-image-3.2.0-4-amd64: Kernel Panic with the new kernel during booting)
Your message dated Thu, 02 May 2013 00:28:48 +0100 with message-id 1367450928.5106.115.ca...@deadeye.wl.decadent.org.uk and subject line Re: Fwd: Re: Bug#706355: linux-image-3.2.0-4-amd64: Kernel Panic with the new kernel during booting has caused the Debian Bug report #706355, regarding linux-image-3.2.0-4-amd64: Kernel Panic with the new kernel during booting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 706355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.2.41-2 Severity: grave Justification: renders package unusable -- I have upgraded today from Squeeze to Debian-7.0. However, while booting in the last 3 occasions, the machine hanged twice with kernel Panic. In both the occasions, the kernel waited unusually long to load the initrd, and then complained about it and then asked to touch any key to continue. Once I touched something, it panicked. What surprises me is that if it is a initrd problem, why did it boot in 2 other occasions ? Moreover, I have been using 'vmlinuz-3.2.0-0.bpo.2-amd64' taken from backport while using Squeeze, and the machine never hanged in the last 6 months. The messages were captured with a camera and I am writing down most of it as was visible in the last screen. --- No filesystem could mount root. tried: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0) Pid: 1, comm: swapper/0 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.41-2 Call Trace: ... ? panic+0x95/0x1a2 ... ... ... ? gs_change+0x13/0x13 -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=56da2c0c-5a03-4b11-b6f3-6e15ebcb7782 ro verbose resume=/dev/sda4 ** Not tainted ** Kernel log: [1.885842] usb 2-1.5: Manufacturer: Logitech [2.200896] ata5: SATA link down (SStatus 0 SControl 300) [2.520295] ata6: SATA link down (SStatus 0 SControl 300) [2.523950] sd 0:0:0:0: [sda] 78242976 512-byte logical blocks: (40.0 GB/37.3 GiB) [2.524064] sd 0:0:0:0: [sda] Write Protect is off [2.524128] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [2.524146] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [2.524629] input: Logitech USB Optical Mouse as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input1 [2.524836] generic-usb 0003:046D:C06A.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-:00:1d.0-1.5/input0 [2.524936] usbcore: registered new interface driver usbhid [2.525001] usbhid: USB HID core driver [2.530135] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [2.530227] cdrom: Uniform CD-ROM driver Revision: 3.20 [2.530429] sr 1:0:0:0: Attached scsi CD-ROM sr0 [2.564825] sda: sda1 sda2 sda3 sda4 [2.565453] sd 0:0:0:0: [sda] Attached SCSI disk [2.567646] sd 0:0:0:0: Attached scsi generic sg0 type 0 [2.567772] sr 1:0:0:0: Attached scsi generic sg1 type 5 [3.364096] Btrfs loaded [3.488917] PM: Starting manual resume from disk [3.488982] PM: Hibernation image partition 8:4 present [3.488984] PM: Looking for hibernation image. [3.504857] PM: Image not found (code -22) [3.504859] PM: Hibernation image not present or could not be loaded. [3.544870] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [5.666963] udevd[358]: starting version 175 [6.078839] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 [6.078927] ACPI: Power Button [PWRB] [6.079040] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [6.079119] ACPI: Power Button [PWRF] [6.266960] ACPI: Requesting acpi_cpufreq [6.376480] input: PC Speaker as /devices/platform/pcspkr/input/input4 [6.535696] parport_pc 00:08: reported by Plug and Play ACPI [6.535812] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [6.699277] iTCO_vendor_support: vendor-support=0 [6.719670] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [6.719797] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS [6.873779] [drm] Initialized drm 1.1.0 20060810 [6.960195] i915 :00:02.0: setting latency timer to 64 [6.979763] mtrr: type mismatch for
Processed: Re: Bug#706499: Ethernet with Realtek R8169 only working with IPV6
Processing control commands: tag -1 moreinfo Bug #706499 [linux-image-3.2.0-4-486] Ethernet with Realtek R8169 only working with IPV6 Added tag(s) moreinfo. -- 706499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b706499.136745167132008.transcr...@bugs.debian.org
Bug#706499: Ethernet with Realtek R8169 only working with IPV6
Control: tag -1 moreinfo Please provide: - Kernel boot log (/var/log/dmesg) - Network configuration files (/etc/network/interfaces and any others) - If you are using DHCP, the DHCP daemon log messages (grep dhclient /var/log/daemon.log) Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Bug#595502: [ia64] pata_cmd64x crashes at boot
On Mon, 2013-04-29 at 17:13 +0100, Steve McIntyre wrote: On Mon, Apr 29, 2013 at 03:29:17PM +0100, Steve McIntyre wrote: At Ben's suggestion, I've tried adding kernel command line options to the normal squeeze kernel (linux-image-2.6.32-5-mckinley 2.6.32-46). swiotlb=force makes no noticeable difference, but libata.dma=0 does allow the system to function normally (with the obvious proviso that without DMA disk access is *very* slow). I'm going to see if they help with the Wheezy kernel at all... No, not at all. It still fails to boot, triggering a system alarm beep sequence some time after the initramfs is loaded (with no output on serial). I've just decoded the flashing LED codes using the doc at [1]. I've got the System LED flashing red, and Diagnostic LED #3 solid red. That indicates System Board, which is a bit non-specific. Especially considering the system boots fine now using older kernels. [1] http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/lpv00324/lpv00324.pdf As discussed earlier: this failure mode seems to be an entirely different bug, as you should see some log messages before any modules are loaded. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
