vserver patches for newer kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, It seems vserver patches (kernel-patch-vserver) and kernel image package with vserver-patched are already removed from debian sid repository. I also checked the latest linux-patch-debian-2.6.30 (2.6.30-8), which still have a small patch and `gen-patch' script. But no vserver patches. The latest version I can find is 2.6.26 for lenny. I wonder will vserver be included again in Debian? Thanks Regards - -Rex -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkq/NzEACgkQOl4Wbdx2/rkD4ACgnvyjESn4e0pc9PKCQf+/VFfb H9oAn2ogCJjfXuD6pfspb++5pykWjldW =K/WY -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545231: marked as done (linux-image-2.6.30-1-amd64: 18 minutes wait until X is ready to launch, instead of normal ~45 sec)
Your message dated Sun, 27 Sep 2009 12:07:20 +0200 with message-id 20090927100720.ga21...@galadriel.inutil.org and subject line Re: Problem resolved by BIOS update has caused the Debian Bug report #545231, regarding linux-image-2.6.30-1-amd64: 18 minutes wait until X is ready to launch, instead of normal ~45 sec 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.) -- 545231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-6 Severity: important When booting linux-image-2.6.30-1-amd64 my system takes some 18 minutes to boot through up until X is ready to launch. Normal for my system, for example on my current kernel linux-image-2.6.26-2-amd64, is some ~45 sec. I let it run through, and upon attempting to build new nvidia-drivers for the new kernel, it was evident that the system is really slow. CPU seems very cloggish. I tried following http://kernel-handbook.alioth.debian.org/ch-bugs.html , and so attempted to use /boot/config-2.6.30-1-amd64 on vanilla linux-2.6.30 from kernel.org, but the produced kernel did not work on my system: It does, panicking, not detect my root disk. Please let me know if you need any more information. HW relevant info that I can think of follows. lspci -vvv: 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 02) Subsystem: Giga-byte Technology Device 5000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information ? 00:01.0 PCI bridge: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: b000-bfff Memory behind bridge: f400-f7ff Prefetchable memory behind bridge: e000-efff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Giga-byte Technology Device 5000 Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 4159 Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 64ns, L1 1us ExtTag- RBE+ FLReset- DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Latency L0 256ns, L1 64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise- Slot # 20, PowerLimit 75.00; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus-
Bug#546809: marked as done (listing contents of remote directory does not show all content and can cause kernel panic)
Your message dated Sun, 27 Sep 2009 12:09:09 +0200 with message-id 20090927100909.ga28...@galadriel.inutil.org and subject line Re: fixed in 2.6.29 has caused the Debian Bug report #546809, regarding listing contents of remote directory does not show all content and can cause kernel panic 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.) -- 546809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: smbfs Version: 2:3.2.5-4lenny6 Severity: important *** Please type your report below this line *** After mounting a remote directory, I 'cd' to a directory contained therein and do an 'ls'. This directory contains over 200 files but I can see only 131. If I do an 'ls some_file' on a specific file that is not listed it will list it. Browsing the remote directories using Konqueror shows all files. If I do an 'ls|less' on the directory with over 131 files the kernel panics and the system either locks up or reboots. I was able to reproduce this bug on another server running etch with the same cifs share. 'grep -i smb /var/log/kern.log' shows the following: kern.log:Sep 14 09:30:12 localhost kernel: [318325.345106] CIFS VFS: RFC1001 size 35 bigger than SMB for Mid=34 kern.log:Sep 14 09:30:12 localhost kernel: [318325.345123] Bad SMB: : dump of 48 bytes of data at 0xf7e1f300 kern.log:Sep 15 08:11:03 localhost kernel: [ 3059.733806] CIFS VFS: RFC1001 size 35 bigger than SMB for Mid=69 kern.log:Sep 15 08:11:03 localhost kernel: [ 3059.733806] Bad SMB: : dump of 48 bytes of data at 0xf246ed80 kern.log:Sep 15 08:12:57 localhost kernel: [ 3208.781567] CIFS VFS: RFC1001 size 35 bigger than SMB for Mid=23 kern.log:Sep 15 08:12:57 localhost kernel: [ 3208.781599] Bad SMB: : dump of 48 bytes of data at 0xf7b96b00 -- System Information: Debian Release: 5.0.2 Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages smbfs depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libcomerr2 1.41.3-1 common error description library ii libkeyutils11.2-9Linux Key Management Utilities (li ii libkrb531.6.dfsg.4~beta1-5lenny1 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries ii libpopt01.14-4 lib for parsing cmdline parameters ii libtalloc1 1.2.0~git20080616-1 hierarchical pool based memory all ii libwbclient02:3.2.5-4lenny6 client library for interfacing wit ii netbase 4.34 Basic TCP/IP networking system ii samba-common2:3.2.5-4lenny6 Samba common files used by both th smbfs recommends no packages. Versions of packages smbfs suggests: ii smbclient2:3.2.5-4lenny6 a LanManager-like simple client fo -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.29-1 On Thu, Sep 24, 2009 at 12:29:04PM -0700, Crain, Kevin Mr CIV USA USAMC wrote: I installed linux-image-2.6.29-bpo.2-686 from backports.org and the problem seems to have been fixed. I have been able to list all remote content without any problems thus far. Thanks for the feedback, closing the bug. Cheers, Moritz ---End Message---
Bug#545232: marked as done (linux-image-2.6.30-1-amd64: 18 minutes wait until X is ready to launch, instead of normal ~45 sec)
Your message dated Sun, 27 Sep 2009 12:07:20 +0200 with message-id 20090927100720.ga21...@galadriel.inutil.org and subject line Re: Problem resolved by BIOS update has caused the Debian Bug report #545231, regarding linux-image-2.6.30-1-amd64: 18 minutes wait until X is ready to launch, instead of normal ~45 sec 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.) -- 545231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-6 Severity: important When booting linux-image-2.6.30-1-amd64 my system takes some 18 minutes to boot through up until X is ready to launch. Normal for my system, for example on my current kernel linux-image-2.6.26-2-amd64, is some ~45 sec. I let it run through, and upon attempting to build new nvidia-drivers for the new kernel, it was evident that the system is *really* slow. Something is making the system run at 5% speed, or so. I tried following http://kernel-handbook.alioth.debian.org/ch-bugs.html , and so attempted to use /boot/config-2.6.30-1-amd64 on vanilla linux-2.6.30 from kernel.org, but the produced kernel did not work on my system: It does, panicking, not detect my root disk. Please let me know if you need any more information. HW relevant info that I can think of follows. lspci -vvv: 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 02) Subsystem: Giga-byte Technology Device 5000 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information ? 00:01.0 PCI bridge: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: b000-bfff Memory behind bridge: f400-f7ff Prefetchable memory behind bridge: e000-efff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Giga-byte Technology Device 5000 Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 4159 Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 64ns, L1 1us ExtTag- RBE+ FLReset- DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Latency L0 256ns, L1 64us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surpise- Slot # 20, PowerLimit 75.00; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible-
Bug#538372: header failure including netlink.h (or uio.h)
On Fri, Sep 18, 2009 at 10:59:19PM +0200, Manuel Prinz wrote: Am Dienstag, den 01.09.2009, 18:53 +0200 schrieb Moritz Muehlenhoff: On Sat, Jul 25, 2009 at 01:55:04PM +0200, Bastian Blank wrote: Patches attached: * Fix uio.h * Remove socket.h backward compatibility code. uio.h has been marked __KERNEL__-only upstream in commit 812ed032cdc8138b7546eecc996879756b92d801. Did you submit your socket.h patch upstream? I am bitten by that bug as well. The change in uio.h did not fix it. I updated the patch for socket.h (attached) but I'm not sure if all changes are needed, though. Applying only the first hunk (#ifdef line) fixed all build issue for me. Can you please forward this upstream? I suppose net...@vger.kernel.org would be the best list to contact. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534978: clock drift in Xen domU with clocksource=xen
I think I've made some progress towards figuring out what's going on here. First I looked at the Xen mini-os kernel, which keeps time correctly. I added a few printk()s to getttimeofday() and saw that of the values in the HYPERVISOR_shared_info structure, the vcpu_info data change often (never more than a handful of seconds between version increments) while the wallclock timestamp is updated more rarely. Then I hacked together a Linux kernel module that adds support for /proc/xeninfo, exposing (if I did it right) the contents of the shared_info structure. What I'm seeing is the same occasional updating of the wallclock timestamp (the values are consistent with what I see in the mini-os domU) but the vcpu_info (for virtual CPU 0; data for the other VCPUs are all zeros throughout, as I believe is normal for a single-processor VM) remains stuck at version 2. A caveat here is that while I'm confident (based on the data; the shift value is also right, the multiplier is in the right ballpark) that I've found a shared_info structure I'm not sure I got the right one. The kernel doesn't seem to export all the symbols needed to find its HYPERVISOR_shared_info structure, and it needs to be mapped into memory in a special way; it's conceivable that I did something wrong here, even though I tried to reuse/imitate existing kernel code as much as I could. Anyway, the secular clock drift this bug is about seems consistent with a failure to receive updates to the vcpu_info data. Is the hypervisor somehow discriminating against Linux domU's by not updating the data, or does the domU kernel need to do something more in order to see the updates? The problem is also reproducible with the 2.6.30-bpo.1 kernel (source code from backports.org, recompiled locally), by the way. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535130: linux-image-2.6.30-1-686 fails with udev 146-3
Hi, I think I should confirm this bug? Today's aptitude update brought me udev 146-3. This causes linux-image-2.6.30-1-686 to boot incorrectly, with for instance these messages: sh cannot kill pid 563 no such process mknod //dev/ppp read-only file system X starts, but hangs, keyboard locks up and a hard reset is required. I can boot into 2.6.29-2-686 reverting to udev/testing allow me to boot into 2.6.30-1-686. Hope this helps? I'm studying /var/log/messages to see if I can come up with something more useful.. Regards, Gijs -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: vserver patches for newer kernel
On Sun, Sep 27, 2009 at 05:58:10PM +0800, Rex Tsai wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, It seems vserver patches (kernel-patch-vserver) and kernel image package with vserver-patched are already removed from debian sid repository. I also checked the latest linux-patch-debian-2.6.30 (2.6.30-8), which still have a small patch and `gen-patch' script. But no vserver patches. The latest version I can find is 2.6.26 for lenny. I wonder will vserver be included again in Debian? Thanks Regards - -Rex it is highly deprecated. as with any external patch you are on your own for the supported length. the debian kernel team met in portland the reslts of which set of patches will be still available for squeeze will be announced soon. kind regards maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535130: linux-image-2.6.30-1-686 fails with udev 146-3
Furthering on my previous message regarding this bug, I've compared the output of linux-image-2.6.30-1-686 with udev 141-2(now in testing) and udev 146-3 (now in unstable) in /var/log/syslog. It seems like the 146-3 is not able to load many (any?) of the modules needed on this system. There are about 36 lines of messages missing ... compare case 1 (linux-image-2.6.30-1-686 and 141-2) (snip) [ 3.209330] EXT3-fs: mounted filesystem with ordered data mode. [ 5.160210] udev: starting version 141 [ 5.572087] input: Power Button as /devices/LNXSYSTM:00/LNXP (snip) [ 5.572096] ACPI: Power Button [PWRF] and 32 more lines in [ 5.*] regarding for instance ACPI, Non-volatile memory driver v1.3, PC Speaker, cfg80211 [6.081959] nsc-ircc 00:0a: activated ... (snip) other modules get loaded, such as tifm_7xx1, intel_rng, thinkpad_acpi, yenta_cardbus, ath5k, i801_smbus, sn9c20x, usbcore and pcmcia_socket [ 9.466057] loop: module loaded [ 9.732145] thinkpad_ec: thinkpad_ec 0.40 loaded. [ 9.734276] tp_smapi 0.40 loading... case 2 (linux-image-2.6.30-1-686 and udev 146-3) [ 3.305530] EXT3-fs: recovery complete. [ 3.306058] EXT3-fs: mounted filesystem with ordered data mode. [ 6.202820] EXT3 FS on dm-0, internal journal [ 8.162890] loop: module loaded [ 8.408741] thinkpad_ec: thinkpad_ec 0.40 loaded. [ 8.410604] tp_smapi 0.40 loading... so, no lines at all concerning udev and no info regarding any of the modules mentioned above. -- How many coming men has one known! Where on earth do they all go to? -- Sir Arthur Wing Pinero -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548630: linux-image-2.6.26-2-686: Crash/Hang with heavy disk write when using SATA AHCI mode
Package: linux-image-2.6.26-2-686 Version: 2.6.26-19 Severity: important System was configured in BIOS with IDE mode set to AHCI. - ASUS p5q-vm MB, latest BIOS. - When having heavy disk writing (disk to disk, or via network rsync from machine 1 to target machine), system hangs after several GBytes have been written to disk. - Problem is reproducable. Happens all the time when I want to rsync 50GB from one PC to target. Reproduced atleast 10 times. 100% hitrate with rsync 50GB data. - Problems happens with two different brands of HD's (did not test more) - No logging information logged. Machine is dead - Configured logging to remote machine. Did not result in any usefull logging. - Pinging target not possible after hang. - Keyboard is dead after hang. - GUI hangs after system hang. Problem is resolved by setting in BIOS the IDE mode to IDE instead of AHCI. No hangs since change in BIOS configuration. -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-19) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Aug 19 06:06:52 UTC 2009 ** Command line: root=/dev/sda1 ro quiet ** Not tainted ** Kernel log: [2.765782] ata1.01: HPA detected: current 2930277168, native 18446744072344861488 [2.765789] ata1.01: ATA-7: SAMSUNG HD154UI, 1AG01118, max UDMA7 [2.765794] ata1.01: 2930277168 sectors, multi 16: LBA48 NCQ (depth 0/32) [2.773584] ata1.00: configured for UDMA/133 [2.782211] ata1.01: configured for UDMA/133 [3.257023] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [3.265250] ata2.00: HPA detected: current 2930277168, native 18446744072344861488 [3.265256] ata2.00: ATA-7: SAMSUNG HD154UI, 1AG01118, max UDMA7 [3.265260] ata2.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 0/32) [3.273220] ata2.00: configured for UDMA/133 [3.273342] scsi 0:0:0:0: Direct-Access ATA SSDSA2SH032G1GN 045C PQ: 0 ANSI: 5 [3.273535] scsi 0:0:1:0: Direct-Access ATA SAMSUNG HD154UI 1AG0 PQ: 0 ANSI: 5 [3.273629] scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD154UI 1AG0 PQ: 0 ANSI: 5 [3.273694] ACPI: PCI Interrupt :00:1f.5[B] - GSI 19 (level, low) - IRQ 19 [3.273698] ata_piix :00:1f.5: MAP [ P0 -- P1 -- ] [3.273732] PCI: Setting latency timer of device :00:1f.5 to 64 [3.274310] scsi2 : ata_piix [3.274310] scsi3 : ata_piix [3.274310] ata3: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 19 [3.274310] ata4: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 19 [3.604057] ata3: SATA link down (SStatus 0 SControl 300) [3.933491] ata4: SATA link down (SStatus 0 SControl 300) [3.948892] Driver 'sd' needs updating - please use bus_type methods [3.948893] sd 0:0:0:0: [sda] 6250 512-byte hardware sectors (32000 MB) [3.948893] sd 0:0:0:0: [sda] Write Protect is off [3.948893] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [3.948893] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.948893] sd 0:0:0:0: [sda] 6250 512-byte hardware sectors (32000 MB) [3.948893] sd 0:0:0:0: [sda] Write Protect is off [3.948893] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [3.948893] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.948893] sda: sda1 sda2 [3.950456] sd 0:0:0:0: [sda] Attached SCSI disk [3.950807] sd 0:0:1:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) [3.950807] sd 0:0:1:0: [sdb] Write Protect is off [3.950807] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00 [3.950807] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.950807] sd 0:0:1:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) [3.950807] sd 0:0:1:0: [sdb] Write Protect is off [3.950807] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00 [3.950807] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.950807] sdb: sdb1 [3.959031] sd 0:0:1:0: [sdb] Attached SCSI disk [3.959031] sd 1:0:0:0: [sdc] 2930277168 512-byte hardware sectors (1500302 MB) [3.959031] sd 1:0:0:0: [sdc] Write Protect is off [3.959031] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [3.959031] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.959031] sd 1:0:0:0: [sdc] 2930277168 512-byte hardware sectors (1500302 MB) [3.959031] sd 1:0:0:0: [sdc] Write Protect is off [3.959031] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [3.959031] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.959031] sdc: sdc1 [3.975103] sd 1:0:0:0: [sdc] Attached SCSI disk [4.165903] kjournald starting. Commit interval 5 seconds [4.165903] EXT3-fs: mounted filesystem with ordered data mode. [4.428209] udevd version 125 started [4.707991]
DKMS in squeeze
Dear DKMS maintainers, The Debian kernel team held a series of face-to-face meetings in Portland this week http://wiki.debian.org/DebianKernel/Meetings. One of the issues we discussed was auto-building out-of-tree modules. Currently we have the conglomeration source packages (linux-modules-extra-2.6, linux-modules-nonfree-2.6, and formerly linux-modules-contrib-2.6) which build binaries from a number of packaged module sources. Among other problems, this does not create a relationship between the real source and binary packages that can be used by the archive software (dak) to keep them together, which raises the risk of Debian being unable to comply with GPL conditions. So we cannot continue to build these. The official minutes will be sent out later, but the key decisions we resolved for this item were: - the conglomeration packages will be removed - a few important out-of-tree modules will be included in the linux-2.6 source package - we will encourage maintainers of other out-of-tree module packages to support DKMS The result is that DKMS may become more widely used in Debian in the near future. Please be prepared for this! Ben. -- Ben Hutchings Any sufficiently advanced bug is indistinguishable from a feature. signature.asc Description: This is a digitally signed message part
Bug#548466: real kernel is undependable
On Sat, 2009-09-26 at 16:06 +0200, Harald Dunkel wrote: Package: linux-latest-2.6 Version: 2.6.30+20 Severity: wishlist linux-image-amd64 and linux-image-2.6-amd64 seem to be pretty fragile. Every other day their dependency to the real kernel package is broken, because the kernel has been updated and linux-latest-2.6 is not in sync. Do you think it would be possible to increase the stability of these packages wrt. the dependencies? I would like to have a reliable way to install a kernel without knowing the version information. AFAICS there are several options: - merge the source packages for linux-latest-26 and linux-2.6, making sure the packages are in sync - make linux-image-amd64 a virtual package provided by the real kernel, or create a new virtual package for this purpose The separation between linux-2.6 and linux-latest-2.6 allows for a later kernel version to be added to a suite without replacing the previous one, as with 2.6.24 added in etch-and-1/2. Neither of these options can achieve that. - don't put too much version information into the name of the real kernel package, and use the debian version number instead No, the binary package names must change for every ABI change, just as for shared libraries. Surely there are other options that I do not see. It would be very nice if this problem could be resolved. Ben. -- Ben Hutchings Any sufficiently advanced bug is indistinguishable from a feature. signature.asc Description: This is a digitally signed message part
DANO MORAL PRATICADO PELO EMPREGADO - Ultimas Vagas
== TREINAMENTO DANO MORAL PRATICADO PELO EMPREGADO - 2ªedição Como Prevenir, Identificar e o que Fazer Quando o Dano Moral é Praticado pelo Empregado ao Empregador? 6 de outubro de 2009 - São Paulo == OVERVIEW Embora o empregador seja alvo de freqüentes Reclamações Trabalhistas para indenizar empregado por dano moral, muitas são as circunstâncias em que o próprio empregado prejudica o empregador, causando-lhe evidente Dano Moral. Um dos objetivos específicos deste treinamento é identificar as possibilidades de danos morais ocasionados por empregados ou pelo próprio empregador, que é de extrema importância para o universo empresarial, para prevenir passivos e ainda será apresentado um projeto especial de comunicação interna, em caráter preventivo, para eliminar qualquer possibilidade que configure o dano moral advindo de empregado ou empregador. ___ PROGRAMAÇÃO Dano Moral Configuração de Dano Moral Dano Moral Ocasionado pelo Empregador Dano Moral Ocasionado pelo Empregado Motivos freqüentes de Reclamação Trabalhista - empregado ___ PALESTRANTE Cintia Yazigi Profissional com 20 anos de experiência na área trabalhista empresarial. Inscrita na OAB desde 1991 é Graduada pela Universidade Presbiteriana Mackenzie e Pós Graduada em Direito Empresarial pela mesma Universidade. Em 1995, desenvolveu um Projeto de Prevenção de Reclamação Trabalhista que proporcionou Prêmio de reconhecimento concedido pelo Jornal S.A. O Estado de S. Paulo, onde atuou como Advogada Trabalhista Sênior por 6 anos. Durante 12 anos, na condição de advogada patronal, defendeu dezenas de empresas multinacionais e nacionais de grande porte, através de escritórios altamente conceituados no mercado (Drausio Rangel Associados, Bueno Magano Advocacia e Araújo e Policastro Advogados). Atualmente é Coordenadora da equipe trabalhista do Tess Advogados. ___ Solicite o Programa Completo pela Central de Atendimento - Condições especiais para grupo. Inscrições e Informações: (11) 3513-9600 ___ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
